Bug #7524
closed
Squid MITM/SSL-Bump broken with Chrome due to missing SAN in generated certificates
Added by Kill Bill over 7 years ago.
Updated about 7 years ago.
Affected Architecture:
All
Patricio Stegmann wrote:
I can confirm the bug in pfSense 2.3.4 and the fix on squid issue tracker at http://bugs.squid-cache.org/show_bug.cgi?id=4711 working on >=3.5 ... Hope this gets applied to pfSense soon as it seems quite a simple fix.
Perhaps file a bug at https://bugs.freebsd.org/ instead. Apparently noone cares there so there's nothing to apply on pfSense.
- Assignee set to Renato Botelho
We should be able to pull that in unless there is something I'm not seeing. Assigning to Renato to check it over.
Jim Pingle wrote:
We should be able to pull that in unless there is something I'm not seeing. Assigning to Renato to check it over.
Thanks, would really help.
- Assignee changed from Renato Botelho to Jim Pingle
I'm getting 3.5.26 pulled into the package branches right now, should be building and up soon.
- Status changed from New to Feedback
Packages are up for 2.4 and 2.3.4, 2.3.x snapshots will be up next time a snapshot runs. Test and let us know if it is working now.
- Status changed from Feedback to Resolved
This works for me now. I can browse secure sites through squid HTTPS MITM with Chrome and there are no certificate errors. Inspecting the certificate shows it has proper SANs filled in now, too.
- Target version deleted (
2.3.4-p1)
Also available in: Atom
PDF