Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[FEATURE] Vendor PQCP and Ed448-Goldilocks for Post-Quantum WAMP

Abierto
  • ¿Algo no está bien?
#1,847 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c, python
Área
build-system, cryptography, security

Línea de trabajo

Comienza revisando las fuentes propuestas para src/autobahn/vendor/ y los puntos de integración existentes de CFFI en el repositorio. Después, inspecciona las pipelines de cibuildwheel y la discusión vinculada wamp-proto/wamp-proto#564. Se considera terminado cuando las fuentes vendored de PQCP y libdecaf, los wrappers de CFFI y las compilaciones de wheels manylinux y musllinux solicitadas estén integrados de forma coherente con la propuesta.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement wamp XBR
Description

Following the discussion in wamp-proto/wamp-proto#564, this issue proposes the vendoring of the PQ Code Package (PQCP) and Mike Hamburg’s libdecaf (Ed448-Goldilocks) into autobahn-python.

The goal is to provide a "Defense-Grade," zero-dependency, and high-performance implementation of Post-Quantum Cryptography (PQC) and High-Strength Classical ECC for the WAMP ecosystem, specifically targeting ML-KEM (FIPS 203) and ML-DSA (FIPS 204).

Motivation

As we move toward a Quantum-Resistant WAMP (WAMP-PQC), the protocol requires hybrid cryptographic schemes that combine classical security (Ed25519/Ed448) with lattice-based security (ML-KEM/ML-DSA).

While libraries like libsodium provide excellent support for Ed25519, they lack Ed448 and NIST-finalized PQC algorithms. To maintain Autobahn's standard of "Zero-Config" installation and high portability, we must internalize these primitives.

Proposed Implementation Strategy
1. Direct Upstream Vendoring

We will vendor the following sources directly into src/autobahn/vendor/:

  • PQCP (PQ Code Package): Utilizing mlkem-native and mldsa-native. This is the Linux Foundation-backed successor to PQClean, providing C90-compliant, formally verified, and SIMD-optimized PQC.
  • libdecaf (Ed448-Goldilocks): Sourced from Mike Hamburg’s upstream (SourceForge) - using git://git.code.sf.net/p/ed448goldilocks/code - and verified against Debian's security patches. This fills the gap for 256-bit security level signatures that libsodium does not address.
2. CFFI Wrapping

Consistent with our performance goals:

  • We will wrap these C libraries using CFFI rather than CPyExt.
  • This ensures optimal performance on PyPy via JIT-inlining while remaining highly efficient on CPython.
  • It avoids the maintenance burden of the CPython C API and the performance penalties of ctypes.
3. High-Performance Multi-Arch Wheels

We will update our cibuildwheel pipelines to publish manylinux and musllinux wheels for:

  • x86-64: Leveraging AVX2 optimizations for NTT (Number Theoretic Transform).
  • ARM64 (aarch64): Leveraging Neon instructions for high-speed PQC on ARM-based servers and high-end IoT (like Cortex-A).
Proposed Security Tiers
Tier Hybrid Combination Use Case
Standard Ed25519 + ML-DSA-65 General Purpose WAMP-Cryptosign
High-Strength Ed448 + ML-DSA-87 Defense / U.S. DoD CUI / Critical Infrastructure
Key Exchange X25519 + ML-KEM-768 Encrypted Payloads / Session Keys
Benefits
  • Zero Dependencies: No requirement for users to install liboqs, openssl-dev, or cmake.
  • Defense-Grade: Aligns with NIST FIPS 203/204 and NSA CNSA 2.0 requirements.
  • Embedded-Ready: By vendoring the native C source, we pave the way for cross-compilation to restricted environments (e.g., Cortex-M33).
Reference

Checklist

  • I have searched existing issues to avoid duplicates
  • I have described the problem clearly
  • I have provided use cases
  • I have considered alternatives
  • I have assessed impact and breaking changes
Lenguaje dominante
Python
Estrellas
2.5k
Forks
767
Merge medio
12 h 40 min
PR fusionados (30 d)
20

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de crossbario/autobahn-python

Todos los issues de crossbario/autobahn-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.