'from OpenSSL import crypto' gives undefined symbol: SSLv2_method #2005

Closed
opened 2013-06-16 16:51:45 +00:00 by daira · 8 comments
daira commented 2013-06-16 16:51:45 +00:00
Owner

AF saw the following problem while trying to run Tahoe-LAFS:

  • found that openssl has a different error here:
# PYTHONPATH=support/lib/python2.7/site-packages/ python -c 'from OpenSSL
import cry
pto'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File
"/root/allmydata-tahoe-1.10.0/support/lib/python2.7/site-packages/pyOpenSSL-0.12-py2.7-linux-x86_64.egg/OpenSSL/__init__.py",
line 41, in <module>
    from OpenSSL import rand, SSL
ImportError:
/root/allmydata-tahoe-1.10.0/support/lib/python2.7/site-packages/pyOpenSSL-0.12-py2.7-linux-x86_64.egg/OpenSSL/SSL.so:
undefined symbol: SSLv2_method
The latest version is 0.13. You can get it on PyPI here
http://pypi.python.org/pypi/pyOpenSSL
SSLv2 is no longer supported in OpenSSL, and version 0.13 no longer expects it.

We should update the dependency to pyOpenSSL >= 0.13. Note that I'm assuming that we no longer need to support platforms with very old versions of OpenSSL (see #1637).

AF saw the following problem while trying to run Tahoe-LAFS: - found that openssl has a different error here: ``` # PYTHONPATH=support/lib/python2.7/site-packages/ python -c 'from OpenSSL import cry pto' Traceback (most recent call last): File "<string>", line 1, in <module> File "/root/allmydata-tahoe-1.10.0/support/lib/python2.7/site-packages/pyOpenSSL-0.12-py2.7-linux-x86_64.egg/OpenSSL/__init__.py", line 41, in <module> from OpenSSL import rand, SSL ImportError: /root/allmydata-tahoe-1.10.0/support/lib/python2.7/site-packages/pyOpenSSL-0.12-py2.7-linux-x86_64.egg/OpenSSL/SSL.so: undefined symbol: SSLv2_method ``` - found a [mailing list post](http://mail.python.org/pipermail/python-list/2012-November/634478.html)> saying: ``` The latest version is 0.13. You can get it on PyPI here http://pypi.python.org/pypi/pyOpenSSL SSLv2 is no longer supported in OpenSSL, and version 0.13 no longer expects it. ``` We should update the dependency to pyOpenSSL >= 0.13. Note that I'm assuming that we no longer need to support platforms with very old versions of OpenSSL (see #1637).
tahoe-lafs added the
packaging
normal
defect
1.10.0
labels 2013-06-16 16:51:45 +00:00
tahoe-lafs added this to the soon milestone 2013-06-16 16:51:45 +00:00
Author
Owner

Also (if that isn't implied) please update the SUMO version to pyOpenSSL 0.13 also. Debian 7.1 system couldn't install from the SUMO package, until I realized that I could just install the OS pyOpenSSL which was 0.13.

Also (if that isn't implied) please update the SUMO version to pyOpenSSL 0.13 also. Debian 7.1 system couldn't install from the SUMO package, until I realized that I could just install the OS pyOpenSSL which was 0.13.
Author
Owner

To clarify comment #1: running python setup.py build on Debian 7.1 works if the python-openssl package is already installed, but if you happened to run python setup.py build before python-openssl was installed you'll need to rm -r tahoe-lafs/support/lib/python2.7/site-packages/pyOpenSSL-0.12-* to be able to use Debian's version.

To clarify [comment #1](/tahoe-lafs/trac-2024-07-25/issues/2005#issuecomment-133714): running `python setup.py build` on Debian 7.1 works if the `python-openssl` package is already installed, but if you happened to run `python setup.py build` before `python-openssl` was installed you'll need to `rm -r tahoe-lafs/support/lib/python2.7/site-packages/pyOpenSSL-0.12-*` to be able to use Debian's version.
daira commented 2013-08-08 21:20:18 +00:00
Author
Owner

Blocked on updating the pyOpenSSL eggs on tahoe-lafs.org.

Blocked on updating the pyOpenSSL eggs [on tahoe-lafs.org](https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html).
daira commented 2013-08-31 23:26:39 +00:00
Author
Owner

(https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/pyOpenSSL-0.13-py2.7-linux-x86_64.egg) was built incorrectly and also had this problem; now that is fixed (but other copies of the egg might be broken).

(https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/pyOpenSSL-0.13-py2.7-linux-x86_64.egg) was built incorrectly and also had this problem; now that is fixed (but other copies of the egg might be broken).
tahoe-lafs modified the milestone from soon to 1.11.0 2013-08-31 23:26:39 +00:00
tahoe-lafs changed title from update pyOpenSSL dependency to >= 0.13 to 'from OpenSSL import crypto' gives undefined symbol: SSLv2_method 2013-09-02 20:06:19 +00:00
warner commented 2014-09-02 17:54:28 +00:00
Author
Owner

Two requirements for this one:

  • update _auto_deps.py to pyOpenSSL >= 0.13
  • make sure we publish eggs for 0.13
Two requirements for this one: * update `_auto_deps.py` to pyOpenSSL >= 0.13 * make sure we publish eggs for 0.13
daira commented 2014-09-02 21:05:55 +00:00
Author
Owner

Actually we should publish eggs for 0.13.1, which was the last version of pyOpenSSL before the switch to using cryptography and cffi. (We should make sure they are using the latest embedded OpenSSL to avoid recent OpenSSL security bugs.)

Actually we should publish eggs for 0.13.1, which was the last version of pyOpenSSL before the switch to using `cryptography` and `cffi`. (We should make sure they are using the latest embedded OpenSSL to avoid recent OpenSSL security bugs.)
Daira Hopwood <daira@jacaranda.org> commented 2014-10-08 11:45:57 +00:00
Author
Owner

In /tahoe-lafs/trac-2024-07-25/commit/b0b76a7c5b89c3fed5a65ef6732dc45e578f12f4:

Improve comments in _auto_deps.py. refs #2249, #2028, #2193, #2005, #1258

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
In [/tahoe-lafs/trac-2024-07-25/commit/b0b76a7c5b89c3fed5a65ef6732dc45e578f12f4](/tahoe-lafs/trac-2024-07-25/commit/b0b76a7c5b89c3fed5a65ef6732dc45e578f12f4): ``` Improve comments in _auto_deps.py. refs #2249, #2028, #2193, #2005, #1258 Signed-off-by: Daira Hopwood <daira@jacaranda.org> ```
daira commented 2014-10-08 12:03:24 +00:00
Author
Owner

Fixed by [18ffc29f4949b6098b8b89e6e89c89923121cda2/trunk].

Fixed by [18ffc29f4949b6098b8b89e6e89c89923121cda2/trunk].
tahoe-lafs added the
fixed
label 2014-10-08 12:03:24 +00:00
daira closed this issue 2014-10-08 12:03:24 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2005
No description provided.