You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate use of M2Crypto in postgres workflow #424
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
❓ Question: Is M2Crypto still needed in the postgres extra for 0.9.0, or can a follow-up keep it only in accelerated?
Both postgres and accelerated already install cryptography==40.0.2, and Key in morango/models/fields/crypto.py selects CryptographyKey whenever cryptography imports cleanly. Meanwhile, M2Crypto versions below 0.51.0 carry CVE-2026-109087 (CVSS 7.4 in M2Crypto.SSL.Checker, which Morango does not import), and 0.46.0 through 0.51.0 cannot be pinned across all supported runtimes because their pyproject.toml[build-system] omits setuptools on Python 3.7 and 3.8.
Because [testenv:postgres] in tox.ini already lists both postgres and accelerated, removing M2Crypto from postgres in a follow-up would keep CI coverage for M2CryptoKey while sparing downstream morango[postgres] installs from SWIG source builds and scanner alerts on 0.45.1:
Activity