Hello,
The "tls-unique" channel binding is necessary to implement the
SCRAM-SHA-1-PLUS authentication mechanisms (see RFC 5802, RFC 5929).
We have a pending patch for Python's ssl binding to compute that
piece of information (*), and I would like to know if there's some
example code somewhere so
> The problem is in my include statements. The output of the following
> test program is "OpenSSL version included is: 9466063" even when I
> compile with -I/usr/local/ssl/include/openssl.
What if you try -I/usr/local/ssl/include/ instead?
__
Le mercredi 21 avril 2010 à 16:06 -0700, gary clark a écrit :
> ImportError: /usr/local/lib/python2.5/site-packages/OpenSSL/crypto.so:
> undefined symbol: PyUnicodeUCS2_Decode
This is a Python problem, not an unicode one. I suggest posting on
comp.lang.python.
Basically, you should use the pyOpenS
Le vendredi 16 avril 2010 à 10:47 -0700, Jon Strait a écrit :
> Please bear with me as I am in the midst of my crash-course in Linux
> upgrade management.
>
>
> I am trying to upgrade from openssl-0.9.8 to openssl-1.0.0 on SUSe
> 10.1 32bit with HP dl380's.
Why do you? Your Linux distribution wi
Hello again,
> I have investigated this issue of -1/SSL_ERROR_SYSCALL with errno==0.
>
>
> From the SSL_get_error(3) man page:
>
> SSL_ERROR_SYSCALL
> Some I/O error occurred. The OpenSSL error queue may contain more
> information on the error. If the error queue is empty (i.e.
> ERR_
Hello,
> Would you please confirm to the list the name of the Python module, the
> download site for it and the version you are currently working with.
> This just helps up provide assistance to this same question in future.
This is with Python trunk (from SVN). The error is easily witnessed w
come any explanations and suggestions concerning this
situation. Is it an OpenSSL bug? Or does this error return correspond to
an applicative error? (in which case, which error exactly, since the
return codes don't point to anything precise)
Thank you
A
