From: Jean-Paul C. <ex...@di...> - 2008-09-17 21:01:56
|
On Wed, 17 Sep 2008 22:51:40 +0200, Sebastian Greatful <seb...@gm...> wrote: ><snip /> >>This isn't a complete example (and the line numbers would make it annoying >>to actually run if it were ;). A complete, minimal reproduction of the >>problem would make it easier to diagnose. > >Sorry, I'm just copy pasting from vim. > >Server: http://paste.pocoo.org/show/85562/ >FileServer: http://paste.pocoo.org/show/85561/ >HttpServer: http://paste.pocoo.org/show/85563/ >Httplib: http://paste.pocoo.org/show/85564/ > > >Is that better? Just let me know how you want it. > The client code is important too (since it's the thing supplying the certificate), as are the keys and certificates (since they determine what the connection is actually verifying). The HTTP parts probably aren't important since the failure is happening at the SSL layer, so the HTTP code probably never gets involved. If you can provide a file containing a server and a file containing a client such that when run the client connects to the server and the server fails to decide that the client's certificate is valid, that'd be best (basically, make it possible for me to be really lazy, so that I am inclined to work on this instead of on real work ;). Jean-Paul |