> > > Anyway, I would really like OpenSSL to decide whether it's an SSL
> > > connection or not (it's more general, because the underlying
> > > protocol might
> > How could the OpenSSL library possibly determine whether or not a
> > connection conformed to a protocol that it had no knowledge of
On 11 Jan, Holger Reif wrote:
> With regard to HTTP/HTTPS, a look into the mod_ssl sources
> available from www.modssl.org might worth a look. There is
> this feature implemented.
I had some looks into mod_ssl when I integrated SSL in thttpd. It uses
somthing like
if ( ERR_GET_REASON( ERR
On Wed, Jan 10, 2001 at 10:55:46AM +0200, Itay Zandbank wrote:
> I was hoping I could keep ignoring this entire bio issue, because I didn't
> find it all that exciting, and because I'm not sure m2crypto (a lowlevel
> Python wrapping of the OpenSSL library) supports it.
In M2Crypto.SSL.Connectio
[EMAIL PROTECTED] writes:
> On 10 Jan, Itay Zandbank wrote:
>
> > However, Lutz's comment from before was correct. It's hard to do it for
> > EVERY protocol, since some protocols require the server to speak first. It
> > might even be impossible, because OpenSSL might actually SEND something t
On 10 Jan, Itay Zandbank wrote:
> However, Lutz's comment from before was correct. It's hard to do it for
> EVERY protocol, since some protocols require the server to speak first. It
> might even be impossible, because OpenSSL might actually SEND something to
> the client before realizing this
> > Anyway, I would really like OpenSSL to decide whether it's an SSL
> > connection or not (it's more general, because the underlying
> > protocol might
> How could the OpenSSL library possibly determine whether or not a
> connection conformed to a protocol that it had no knowledge of? This has
t
> Anyway, I would really like OpenSSL to decide whether it's an SSL
> connection or not (it's more general, because the underlying
> protocol might
> change in the future). I guess I could still use my own bio that remembers
> everything that goes through it, and when SSL_accept fails,
> access t
On Wed, Jan 10, 2001 at 10:55:46AM +0200, Itay Zandbank wrote:
> > You may need to implement this by creating your own in-memory bio so that
> > you can peek at the incoming data to determine whether it is an HTTP
> > request. Then if it's not HTTP, call SSL_accept on your bio.
>
> I was hopin
> You may need to implement this by creating your own in-memory bio so that
> you can peek at the incoming data to determine whether it is an HTTP
> request. Then if it's not HTTP, call SSL_accept on your bio.
I was hoping I could keep ignoring this entire bio issue, because I didn't
find it a
