Re: HTTPS
Fabian Keil <[email protected]>
| Newsgroups | gmane.comp.web.privoxy.user |
|---|---|
| Message-ID | <[email protected]> |
"joe" <[email protected]> wrote: > With more and more websites going SSL, privoxy is becoming less and less > able to do its job. > > A suggested solution is for privoxy to decrypt the HTTPS incoming, > process it and then send it to the client. This may be very hard to do, > I don't know. TOR already does something like this so maybe the > software you need is in the TOR code. Tor doesn't actually do something like this. > Good luck! > > HTTP <==> privoxy <==> client > HTTPS ==> decrypt ==> privoxy ==> encrypt ==> client > HTTPS <== encrypt <== decrypt <== client This is already on the TODO list: https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob;f=TODO;h=49da6ad425cbdea95cb510fc1bca35dea3d72122;hb=HEAD#l54 Fabian _______________________________________________ Privoxy-users mailing list [email protected] https://lists.privoxy.org/mailman/listinfo/privoxy-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEETzbBfzgWkTZUoehQaRgikYuiNxwFAlwSTNsACgkQaRgikYui NxyojhAAgxCsSTyJIrnXg9sDxHS48C0gbFKVG09cfjpJlEWETJFtANT9dTty/fFE rHLU4mWFUoC21pcPgQRul3pUmUWvNZNsnaklf7pWlod4NABbNDCxcfBIlOyxJr30 HhtU7lmeZEOGVArbg9ihveziHXQfkl/Y5KLPBDdC1fmhT2ccuHgtKC3vXA/L21qE 6o8VOTp1SA+5v5Fqki6N1jrH9k240vXMltgJGLVKOIIHbc7xaJP9tMpoqkd9cz8L q6zZvk3Z7+vlXe4iId4GfAFNX2nBj+ge4dhz2aqr+W+nck5AjC+rqrdXfAui/6Zb Dj87FWCLdy8PjAfwANgpyC7/JhUUuFUf6X7JNyco9TmbZnfI9SDvO8hkoiC8efcK fN73Ci4ieS2Rm/ms7GQvFZZW3iSCwAqyTsiDII3BFw/m8nJhoMr74pfuSQJYLuLC ugB5fdAETetNUA88yy/Pp7QSHYc2dGQtdPZ8H8UxNJG6vCp6bOKsmyf9WcTTat1t 5rBwNFhG5bGFsKaSAoPGZhDTYeBzreiL0j6nfx8aRQxNE0O+VtjE6SumpFf9xFcN CzMZ5JUgTzI34i4DjM+88A+54ViarD2H0z9sD+1uguj2Yw2RNSquhiI+W927J8ZH YgztmZWdjNgykr80BFOFj3oyHNVuIcVfTyAjIL09UPeKnmwKEBI= =4jNC -----END PGP SIGNATURE-----