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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to