Your message dated Wed, 12 Mar 2025 03:24:45 +0000
with message-id <[email protected]>
and subject line Bug#1099411: Removed package(s) from unstable
has caused the Debian Bug report #401649,
regarding crypt++el: cleartext data gets corrupted after unencryption
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.)
--
401649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401649
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: crypt++el
Version: 2.92-1
Severity: grave
Justification: causes non-serious data loss
I store my passwords in an encrypted file, and used crypt++el mode to
edit them so that I don't have a plaintext version of sensitive data
on disk. However, after typing in the password in Emacs, the
unencrypted data has little changes scattered throughout the file. At
first I thought I was making typos but if I fix the character, the
exact same corruption happens again.
This problem has been plaguing me for about a year on multiple boxes.
I've been regularly upgrading XEmacs and crypt++el, to no avail. This
bug is filed on the ppc platform, but I've also reproduced it on
amd64. Please let me know
Steps to reproduce:
1. Unpack http://www.menalto.com/.outgoing/debian/crypt++el-bug.zip
2. Run "crypt test < test.cry" and see what the data should look like
3. Run "xemacs test.cry" and enter "test" as the password
4. See lines 5 and 8 are mangled like this:
- low security: (no passwordB
common^Ûsecure password: a0b1c2d3
(hopefully the special character between "common" and "secure" comes across
in this bug report).
If I had to take a wild guess at this, I'd say that it's something to
do with emacs codepages. But I don't know enough to be sure and
haven't spent enough time digging. This is a particularly scary
problem though because if it makes a subtle corruption to one of my
passwords (which are already random values) then I'll have a hard time
figuring out and fixing it.
++
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages crypt++el depends on:
ii xemacs21-mule [emacsen] 21.4.19-1 highly customizable text editor --
crypt++el recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.94-3.2+rm
Dear submitter,
as the package crypt++el has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1099411
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
