Anyone got succesful template updates from https://repo.teamsforlinux.de/rpm/teams-for-linux.repo ?
It works fine from a networked VM, but tinyproxy always gives error 403.
Anyone got succesful template updates from https://repo.teamsforlinux.de/rpm/teams-for-linux.repo ?
It works fine from a networked VM, but tinyproxy always gives error 403.
Do you have the same qube for your test qube’s net qube and updates proxy qube?
Maybe your updates proxy qube is sys-whonix and updates using Tor are blocked for https://repo.teamsforlinux.de/rpm/teams-for-linux.repo.
Yes, my updates are torified. But I CAN access this repo with tor browser!
The DDoS protection could allow the requests from browsers (javascript challenge).
If you check with curl you’ll see that your request is blocked:
[workstation user ~]% curl https://repo.teamsforlinux.de/rpm/teams-for-linux.repo
<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>
...
It’s not what you asked, but I’m curious why wouldn’t you use original MS Teams PWA, since the one you stated should be just a wrapper around PWA?
I want it separate from my browser. However, i find it incredibly stupid to have a “protection” like that. It is literally a resource which main purpose is to be accessed without human intervention.