.--.      .--.      .--.      .--.      .--.      .--.      .--.
:::::.\::::::::.\::::::::.\::::::::.\::::::::.\::::::::.\::::::::.\
'      `--'      `--'      `--'      `--'      `--'      `--'

 DATE : 2019.03.29
 TIME : 09:57
AUTHOR : [email protected]
 MOOD : ANNOYED
TITLE : THE ANNOYANCE OF TRANSPARENT PROXY

 .--.      .--.      .--.      .--.      .--.      .--.      .--.
:::::.\::::::::.\::::::::.\::::::::.\::::::::.\::::::::.\::::::::.\
'      `--'      `--'      `--'      `--'      `--'      `--'

Time for a little rant. At work they make use of bluecoat proxies
for outbound web monitoring. In most cases this is not a concern
because you never see it, it just does its think and your browser
doesn't mind because it have the bluecoat as a trusted CA.

For you conspiracy types, this is a regulated work environment,
if you are using the web for personal things, that's the users
decision. They shouldn't be using it for personal work.

Where my annoyance comes in is with python based tools I am trying
to use that make use of external connectivity. There is no easy
way to globally fix the python SSL VERIFY errors I am getting. The
various environmental settings and config settings to ssl_verify 0
are not working, and it's annoying as fuck.

So I'll continue to look. So annoying.



-Snowcrash

¯\_(ツ)_/¯

You are viewing proxied material from sdf.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.