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

Aberta
#2,096 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, perl
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Perl
Estrelas
67
Forks
8
Merge médio
5h 12min
PRs com merge (30d)
131

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de fglock/PerlOnJava

Todas as issues de fglock/PerlOnJava

Issues semelhantes

Mais issues de Perl

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.