On 10/23/21 18:56, Marcus Kool wrote:
sslbump can be used in peek+splice and peek+bump modes.
Sure.
Depending on what Squid finds in the peek (e.g. a teamviewer FQDN) Squid
can decide to splice (not interfere) the connection.
I know.
Perhaps I wasn't clear.
What I was saying is that
sslbump can be used in peek+splice and peek+bump modes.
Depending on what Squid finds in the peek (e.g. a teamviewer FQDN) Squid can
decide to splice (not interfere) the connection.
Below is an example.
Marcus
# TLS/SSL bumping definitions
acl tls_s1_connect at_step SslBump1
# define acl
On 10/22/21 17:24, Alex Rousskov wrote:
I do not know much about TeamViewer,
...
You do not need SslBump and https_port for this.
AFAIK you *cannot* use SslBump, as TeamViewer pinpoints certificates.
If someone can prove me wrong, I'd be curious to know how they manage this.
bye
av.
On 10/22/21 5:38 AM, Forum User wrote:
> I need that only (securely) authenticated instances of TeamViewer can
> pass my network.
> There're four TeamViewer Proxy settings: IP/host, port, login, password.
I do not know much about TeamViewer, but I bet that it does not support
HTTPS proxies. If I
Hello,
I've just read
https://wiki.squid-cache.org/KnowledgeBase/Pass%20Teamviewer%20via%20SSL%20Bump-aware%20Squid
and I am confused how whole configuration should look like.
I need that only (securely) authenticated instances of TeamViewer can pass
my network.
There're four TeamViewer Proxy set
