Bug 28160 - python-nassl bundles openssl
Summary: python-nassl bundles openssl
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact: Sec team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-18 17:18 CET by David Walser
Modified: 2021-01-18 18:11 CET (History)
1 user (show)

See Also:
Source RPM: python-nassl-3.1.0-5.mga8.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2021-01-18 17:18:31 CET
It should build against system openssl.  Also, since it's not built on aarch64, it causes a dependency problem for python-sslyze.
Comment 1 Guillaume Rousse 2021-01-18 17:39:07 CET
Feel free to make it work against system openssl. It builds, but doesn't work correctly, either because of different build options, or because it has not been designed for dynamic linking. BTW, it actually link against two different versions of openssl.

I'll disable python-sslyze on aarch64 too.
Comment 2 David Walser 2021-01-18 17:49:30 CET
We shouldn't be importing this package now if it can't be fixed.
Comment 3 Nicolas Lécureuil 2021-01-18 17:54:52 CET
looking to https://pypi.org/project/nassl/0.13.7/ this does not seems possible.

Maybe we can a a provide to know it bundles openssl

Provides: bundle(OpenSSL-1.0.2e) or something like this

guillaume does not tell it can't be fixed :-)

CC: (none) => mageia

Comment 4 David Walser 2021-01-18 17:58:07 CET
Bundling 1.0.2 is even worse, because that branch is dead.  I really don't think we should be shipping this package.
Comment 5 Guillaume Rousse 2021-01-18 18:07:56 CET
It doesn't "bundle" anything, ie it doesn't ship anything another package could use, it just reuse statically openssl code, including old and deprecated version, in order to test for deprecated protocol versions.

And it's an ssl scanrer, not a regular client or server, we don't care about openssl vulnerabilities here. Just provide a credible exploitation scenario before asserting usual policy apply here.
Comment 6 David Walser 2021-01-18 18:11:35 CET
Fine...

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.