Even with splice??? This is a weird way of MS Store of handling things I was sure that when I am using SPLICE it is expected to work. Maybe there is a way to handle these IP addresses before even peeking, which should work. I think that there is some level of a BUMP happening when it shouldn't. I will try to test it with another proxy which only looks at the SNI. Eliezer ---- Eliezer Croitoru Tech Support Mobile: +972-5-28704261 Email: ngtech1ltd@xxxxxxxxx Zoom: Coming soon -----Original Message----- From: squid-users <squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx> On Behalf Of Lorenzo Marcantonio Sent: Tuesday, January 12, 2021 10:58 AM To: squid-users@xxxxxxxxxxxxxxxxxxxxx Subject: Re: Microsoft store issues with ssl-bump On Tue, Jan 12, 2021 at 10:33:00AM +0200, Eliezer Croitoru wrote: > > Any hints might help to find and resolve this issue >From my experience MS Update and probably the store too use custom root certificates; check if that's the case. It's also possible that that connection is so hardwired that it doesn't accept a redirect. So it sees that and become suspicious (Windows Update is extremely suspicious :D) For some antivirus (avast maybe? I don't remember) the updater actually checks the server certificate fingerprint so you can't bump it and you need a special NAT rule for all the fscking IPs it uses (if you set a proxy it does a connect BY IP and not by name, and the IPs are hardcoded and not resolved by DNS). So it is possible you can't bump a store connection (remember that technically a bump is a MITM intrusion that TLS is explicitely design to detect!) -- Lorenzo Marcantonio _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
