[From nobody Mon Oct 19 12:21:05 2026
Received: (at submit) by bugs.debian.org; 8 Aug 2026 18:53:36 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-10.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 NO_RELAYS,XMAILER_REPORTBUG autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 15; hammy, 91; neutral, 32; spammy, 1.
 spammytokens:0.941-+--H*r:bugs.debian.org
 hammytokens:0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc,
 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug, 0.000-+--HTo:N*Debian
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wsmAq-002kU4-19
 for submit@bugs.debian.org; Sat, 08 Aug 2026 18:53:36 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso <carnil@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libcrypt-password-perl: Upstream not maintained since 2012, has
 security issues; should not be released with forky
Message-ID: <178621521523.106649.10640994153569065945.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0+nmu1
Date: Sat, 08 Aug 2026 20:53:35 +0200
Delivered-To: submit@bugs.debian.org

Source: libcrypt-password-perl
Version: 0.28-2
Severity: serious
Justification: unfit for forky release
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>, team@security.debian.org

Hi

libcrypt-password-perl has not been update upstream since 2012, and
has open security issues (CVE-2026-16235, CVE-2026-6656).

So rather than providing libcrypt-password-perl in Debian forky (which
got freshly introduced), we might keep it out of testing (or maybe get
it removed completely)?

Gregor, what is your opinion here?

Regards,
Salvatore
]