Complete and qualify the Crypt::OpenSSL::RSA CPAN port

Aperta
#2,096 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java, perl
Ambito
backend

Direzione di ricerca

Start by reading src/main/java/org/perlonjava/runtime/perlmodule/CryptOpenSSLRSA.java, CryptOpenSSLBignum.java, src/main/perl/lib/Crypt/OpenSSL/Bignum.pm, and dev/modules/rdf_crypt.md; first pin the upstream release and run its unmodified suite on system Perl and both PerlOnJava backends. Track failures and environment exclusions, then use those results to define compatibility gaps and focused regressions. Done means the stated acceptance checks pass and the porting documentation records the release, test evidence, and unsupported surface.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Goal

Complete and document the existing PerlOnJava implementation of Crypt::OpenSSL::RSA against the current upstream distribution.

Current state

The repository already has a Bouncy Castle-backed Java provider (CryptOpenSSLRSA) and a bundled Crypt::OpenSSL::Bignum provider. RDF::Crypt work reused these providers and fixed the use_pkcs1_padding selector. The RSA API is also listed as an exit criterion for the Net::SSLeay completion plan. This issue tracks the standalone module port and its upstream compatibility qualification; it does not assume that a second crypto provider is needed.

Work

  • Pin the upstream Crypt-OpenSSL-RSA release and inspect its Perl, XS, tests, fixtures, and supported behavior.
  • Run the unmodified upstream suite on system Perl and PerlOnJava; record unavailable prerequisites or environment-specific exclusions separately.
  • Close remaining compatibility gaps in the existing Java/Perl providers, preserving upstream Perl behavior and using Bouncy Castle where needed.
  • Add project-owned regressions for externally observed gaps and validate them first with system Perl.
  • Verify bundled loading without an installed CPAN overlay and run the module tests on both JVM and interpreter backends.
  • Update bundled-module and feature-matrix documentation when acceptance is met.

Acceptance

  • The selected upstream test suite passes on both PerlOnJava backends, with any unsupported or environment-dependent cases explicitly documented and justified.
  • Focused project regressions cover each externally observed defect and pass with system Perl and both PerlOnJava backends.
  • The bundled providers load in an isolated CPAN home without relying on installed copies.
  • The porting documentation records the upstream release, test evidence, and remaining unsupported surface.

Initial evidence

The implementation lives in src/main/java/org/perlonjava/runtime/perlmodule/CryptOpenSSLRSA.java and CryptOpenSSLBignum.java; the Perl wrapper is in src/main/perl/lib/Crypt/OpenSSL/Bignum.pm. dev/modules/rdf_crypt.md records previous reuse and one compatibility fix. dev/modules/netssleay_complete.md lists Crypt::OpenSSL::RSA tests as an exit criterion for its RSA phase.

No current standalone upstream run or failing test is asserted here; refresh the evidence against the pinned release before implementation.

Lingua principale
Perl
Stelle
67
Fork
8
Merge medio
5h 12m
PR unite (30g)
131

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fglock/PerlOnJava

Tutte le issue di fglock/PerlOnJava

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.