Re: Execute connect_ssl() twice to connect - is this right?

My server is based on the demo echod-async.py (echo.py as the client). The
demo currently fails because of bad certificates, but the basic idea looks
like it still applies.

I'm not sure what you find strange about the code, but I want to be very
specific in the context version and cipher combination that I use, so I
initialize some things that I may not have to otherwise.

In my code, if you replace <server.home.com> with localhost and setup a
client before accepting any ssl connections, it should work (in other words,
the client socket needs to be connected before even trying to accept any ssl
connections from the client). Of course, all of this is what makes me think
that I'm simply missing something.


On 2/28/07, Heikki Toivonen <[email protected]> wrote:
>
> Latitia Haskins wrote:
> > I would like to verify some behavior that I observe in my code when I
> > connect a client and server using M2Crypto. I am finding that I have to
>
> I find your code very strange, and the server code does not work for me
> at all. I would advice you to take a look at the test_ssl.py file for
> some guaranteed to work client samples. After that take a look at the
> demos for some more samples, including server samples, but keep in mind
> that the demos may no longer work.
>
> --
>   Heikki Toivonen
>
>
>
>