I found an old thread from Oct 2008, hijacked by some r*tard.
Is blocking by user-agent string: DynGate the ultima ratio?
Doesn't teamviewer simply fallback to https://?
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin
On Thu, 16 Oct 2008 09:01:48 +0530
Tharanga [EMAIL PROTECTED] wrote:
Hi folks,
...
did anyone succesfully block the team viewer access in squid acl.
I block it by its user-agent string: DynGate .
I am using squid in ubuntu 8.04 and its already blocked (by default).
I am trying to connect to my linux server from home through broadband,
but the connection is not going through.
First, it said, the screen in locked, then i got the screen unlocked,
then, it said the password was accepted by
On tor, 2008-10-16 at 09:01 +0530, Tharanga wrote:
I need to block team viewer (remote access software) on squid. I analyse the
connection establishmet . it goes through port 80 to teamviewer server ( ip
is dynamic).
Team viewer clinetport 80 -- Team viewer main server (dynamic
Hi folks,
I need to block team viewer (remote access software) on squid. I analyse the
connection establishmet . it goes through port 80 to teamviewer server ( ip
is dynamic).
Team viewer clinetport 80 -- Team viewer main server (dynamic
ip's) --- (port 80) team viewer
