Community discussions

MikroTik App
 
kurifat
just joined
Topic Author
Posts: 1
Joined: Fri Jan 22, 2016 9:09 am

HTTPS traffic redirect problem

Tue Nov 14, 2017 9:13 pm

How to redirect all HTTPS traffic Webproxy? Please give me a solution.
 
Sayrax
just joined
Posts: 24
Joined: Mon Jun 26, 2017 4:44 pm
Location: Kharkiv
Contact:

Re: HTTPS traffic redirect problem

Wed Nov 15, 2017 11:00 pm

Do you use a web-proxy on mikrotik or a third-party server?
 
User avatar
normis
MikroTik Support
MikroTik Support
Posts: 26968
Joined: Fri May 28, 2004 11:04 am
Location: Riga, Latvia
Contact:

Re: HTTPS traffic redirect problem

Thu Nov 16, 2017 9:22 am

You can't transparently redirect https traffic to proxy, without the user getting certificate issues.
 
User avatar
Jotne
Forum Guru
Forum Guru
Posts: 3349
Joined: Sat Dec 24, 2016 11:17 am
Location: Magrathean

Re: HTTPS traffic redirect problem

Thu Nov 16, 2017 12:12 pm

Not 100% correctly

At our work we uses Forcepoint to block unwanted traffic.

Here how it works.
1. You need a local installed certificate from Forcepoint
2. You try to open an https site.
3. WCCP (web redirecting proxy) see that you are coming form at destination that we like to inspect, sends it to Forcepoint
4. Forcepoint strips of https certificate, looks at were you go and allow/block session. If it allows session it uses the real cert from the site you are visiting.

So at the client site you can see the look is green on the https sites, but if you look at certificate its a spesial created one, not the site cert.

This works fine in most of cases, but if you have application that read https and do not see or understand that you have a local certificate, it will not work. So Browser traffic is ok, but for application, you need exceptions.

There are other vendors that can do this like Check Point
This video explain how it works:
https://www.youtube.com/watch?v=1lJBBRsc03A
 
reinerotto
Long time Member
Long time Member
Posts: 524
Joined: Thu Dec 04, 2008 2:35 am

Re: HTTPS traffic redirect problem

Sun Nov 19, 2017 6:33 pm

Not 100% correct.
squid (open source) can do the same. So, in open Linux environments (also on openwrt/LEDE), this can be done without separate product.
 
User avatar
Cha0s
Forum Guru
Forum Guru
Posts: 1162
Joined: Tue Oct 11, 2005 4:53 pm

Re: HTTPS traffic redirect problem

Mon Nov 20, 2017 5:09 pm

Both methods require to install custom root CA cert on the clients.
There's is no way to not get browser warnings unless the client installs your certificate. Which is not a very good practice anyway both from security and management point of view.

So not viable for most out there.
Not to mention it's not very secure to mess with root CAs unless you REALLY know what you are doing, just see the stupidity by Lenovo and others a few years back. Installing a custom root CA cert it's almost like installing a backdoor.

In closed controlled environments (ie: a company with specific security policy and centralized management - like active directory) this might be a solution.
In others (ie: hotspot) it is most definitely not a solution.
 
reinerotto
Long time Member
Long time Member
Posts: 524
Joined: Thu Dec 04, 2008 2:35 am

Re: HTTPS traffic redirect problem

Mon Nov 20, 2017 7:03 pm

Both methods require to install custom root CA cert on the clients.
Again, in case you want to filter/log certain _hostnames_ (_NOT_ complete URLs) or IPs, you do _NOT_ need to install the certificate for https.
Exactly, what I did for a special router (openwrt/LEDE) for parental control. Which is an example, that https-filter/logging makes sense. And is legal.
 
User avatar
Cha0s
Forum Guru
Forum Guru
Posts: 1162
Joined: Tue Oct 11, 2005 4:53 pm

Re: HTTPS traffic redirect problem

Mon Nov 20, 2017 7:21 pm

Right... except the fact that OP asked for redirect not blocking or logging...
 
reinerotto
Long time Member
Long time Member
Posts: 524
Joined: Thu Dec 04, 2008 2:35 am

Re: HTTPS traffic redirect problem

Mon Nov 20, 2017 7:51 pm

So sorry, mixed up with this one:
>Forcepoint strips of https certificate, looks at were you go and allow/block session. If it allows session it uses the real cert from the site you are visiting.<