On Wed, 06 Jul 2011 15:51:32 -0400, Johannes Hofmann <Johannes.Hofmann@gmx.de> wrote:
On Sun, Jul 03, 2011 at 03:09:52PM -0400, Benjamin Johnson wrote:
You mean certificate checking, error prompting, etc.?
Yes, plus reliable SSL connections of course.
I'm not quite sure what you mean by "reliable" there -- could you explain? I should mention that the code to handle HTTP CONNECT requests for proxying SSL is a rather ugly kludge, since I wasn't sure how to correctly hook that through the CCC's. Besides that and the missing features, I can't think of any issues off the top of my head. For what it's worth, I've been using it every day for several months with no problems. I *would* like to add that my implementation is more secure than the DPI, since there's no Unix domain sockets or other interprocess communication to worry about. And since it's hooked in through the sockets code, it can reuse Dillo's existing HTTP code with all its features, making it a much more functional and elegant solution overall (aforementioned kludge excepted). ~Benjamin