Your message dated Sat, 25 Jul 2026 16:48:45 +0000
with message-id <[email protected]>
and subject line Bug#1142014: fixed in libcrypt-openssl-rsa-perl 0.41-2
has caused the Debian Bug report #1142014,
regarding Can no longer parse RSA private keys with additional text
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1142014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142014
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libcrypt-openssl-rsa-perl
Version: 0.41-1
Severity: important
Tags: upstream
X-Debbugs-Cc: [email protected]

Greetings,

it seems Crypt::OpenSSL::RSA::new_private_key can no longer handle a
private key in the PEM format with additional text - like it used to
since possibly the last ten years.

How to repeat:

Generate an according key. Using GnuTLS that's

    certtool --generate-privkey --outfile /tmp/privkey.pem

Or, using OpenSSL and an exsting key:

    openssl rsa -text </path/to/some-private-key  >/tmp/privkey.pem

Then run

    perl parse-key /tmp/privkey.pem

where parse-key:

```
#!/usr/bin/perl

use 5.010;
use strict;
use warnings;

use Crypt::OpenSSL::RSA;
use File::Slurp;
use Test::More;

diag ("Version: $Crypt::OpenSSL::RSA::VERSION");

my $rsa = eval {
    my $content = read_file ($ARGV[0]);
    Crypt::OpenSSL::RSA->new_private_key ($content);
};

ok (defined ($rsa)) or diag ($@);

done_testing;
```

Expected (using Debian 14, "forky"):

```
# Version: 0.35
ok 1
1..1
```

Got (using Debian unstable):

```
# Version: 0.41
not ok 1
#   Failed test at parse-key line 18.
# unrecognized key format: expected PEM-encoded key (starting with 
'-----BEGIN') or DER-encoded key (binary ASN.1 data) at parse-key line 15.
1..1
# Looks like you failed 1 test of 1.
```


To be honest, I didn't spend much time in investigation. It seems the
new_private_key method exists in the newer version only - perhaps it
used to be pure XS code in the past that was more flexible in that
regard?

This however fixes the issue for me:

[ RSA.pm:61 ]
-    if ( $p_key_string =~ /^-----/ ) {
+    if ( $p_key_string =~ /^-----/m ) {

Cheers,

    Christoph

-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.94 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libcrypt-openssl-rsa-perl depends on:
ii  libc6                                       2.42-17
ii  libcrypt-openssl-bignum-perl                0.09-2+b4
ii  libcrypt-openssl-random-perl                0.17-1+b3
ii  libssl3t64                                  3.6.3-1
ii  perl                                        5.40.1-8
ii  perl-base [perlapi-5.40.1]                  5.40.1-8
ii  perl-openssl-defaults [perl-openssl-abi-3]  7+b2

libcrypt-openssl-rsa-perl recommends no packages.

libcrypt-openssl-rsa-perl suggests no packages.

-- no debconf information

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: libcrypt-openssl-rsa-perl
Source-Version: 0.41-2
Done: gregor herrmann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libcrypt-openssl-rsa-perl, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann <[email protected]> (supplier of updated 
libcrypt-openssl-rsa-perl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 25 Jul 2026 18:26:05 +0200
Source: libcrypt-openssl-rsa-perl
Architecture: source
Version: 0.41-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <[email protected]>
Changed-By: gregor herrmann <[email protected]>
Closes: 1142014
Changes:
 libcrypt-openssl-rsa-perl (0.41-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch from upstream Git to fix parsing keys with additional tests.
     Thanks to Christoph Biedl for the bug report.
     (Closes: #1142014)
Checksums-Sha1:
 e1246ded517d2fab65df8200600944fa954a2417 2655 
libcrypt-openssl-rsa-perl_0.41-2.dsc
 aebe3170e1b3a9bab12e516113a9fdcf779df6d6 5388 
libcrypt-openssl-rsa-perl_0.41-2.debian.tar.xz
Checksums-Sha256:
 a33ac647122dff0153d27d727f5fc0e727af84922f09e1724d360d56f15015b3 2655 
libcrypt-openssl-rsa-perl_0.41-2.dsc
 d98d6f772169260341488e68e5fecda346b430906efdcd92f6a01fcbca95b3f9 5388 
libcrypt-openssl-rsa-perl_0.41-2.debian.tar.xz
Files:
 e8190253f14e87b09b8c2eed4ef01925 2655 perl optional 
libcrypt-openssl-rsa-perl_0.41-2.dsc
 32762d8f69c26776ad14569679202500 5388 perl optional 
libcrypt-openssl-rsa-perl_0.41-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmpk5LxfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZmuBAAgAhdDr2GIQZXGIQtTK4qeY6bFzCc7CJ6qt+a8Wu9cTzI2LoncFfsSt/M
CdyT3DxnhTtGTiwSLXxyqJNcmyOrGEpRXdonfrIBsPiSqqZv9AV9MJK1aaT4/woj
xLua5ixPPlg6WL8k8/4Lci6A/lXb71aBQMkIWvp6CQYZ6KtorxH3u75D2XDWSY3b
I6O+ONFZX+2BSFj+++AZhzg0ZUQurdag+Qegh8mSQ/31SWWDJfot0dJC4OnyeEiU
ygRmd+7uSHRqBkqrPKXzad7YjIqv5S/mTkmgUkcie0BNePqPRtdjIfs/WCfRy0Xp
Lkph+7JLYlWpKUxuz5Q9c/+UEVcZGai+UV11M+rtZ+UzTS3rB072+OKRp0vcV3ON
81xjBTc9IKsovAGs/UtiykLIEE3liWEOW6f1Hh8Ty8qPHtdYJqgTzlfdei9GSMjD
eVdYIddGwHImHYlfoTI964nH9PLr1Rak9mtuLVYy+b6qjEXvrVOVVREUbfp1EVto
F4YAYAwjMAydEeOmPfba55+V424OLIB6dUo5BY032pDR1l5MMItYe+zgYKZwIcFx
oGceSIjhZjOM97NcrnG5HV/RXyChjk9rfspqCjeI7/T22cesPEerBgSYA76shqRf
WC9qK8vnoZqAWkVuYpBCBUTQUrHbtquBDP1L+qNKZ21rH3RORjY=
=cgkV
-----END PGP SIGNATURE-----

Attachment: pgpPqXegwtlMm.pgp
Description: PGP signature


--- End Message ---

Reply via email to