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

Heikki Toivonen <[email protected]>
Newsgroups gmane.comp.python.cryptography
Message-ID <[email protected]>
Latitia Haskins wrote:
> 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.

I'll reply to that in the next message.

> In my code, if you replace <server.home.com <http://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.

Are you saying the client needs to be connected before the server can be
started? That would make no sense.

-- 
  Heikki Toivonen
signature.asc (application/pgp-signature, 254 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF50cdb8x8KoP+JuwRAtbOAKCrZR40Hr9LkRd11ifeuD9YM9UwOQCeProK
zEJFJoy4yhhxBP+Xu8qIgHo=
=Vkmy
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.