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

Offen
#2,096 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java, perl
Bereich
backend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Perl
Sterne
67
Forks
8
Ø Merge
5 Std. 12 Min.
Gemergte PRs (30 T.)
131

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fglock/PerlOnJava

Alle Issues in fglock/PerlOnJava

Ähnliche Issues

Weitere Issues zu Perl

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.