Hi Jedd, Sorry for the late response.
Back to this issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288090 I've investiaged a little bit, and .dc and .nc files are not different versions, but mcrypt appends .dc to the filename and writes to this output file, if you use decryption and the filename didn't have some encryption suffix. So if you have .dc files, they should contain decrypted data already. At least this is what the code tells me. Unfortunately the manpage is quite ambiguous: When encrypting or decrypting a file, a new file is created with the extension .nc and mode 0600. Then later: mdecrypt takes a list of files on its command line and creates a new file for each file whose name ends with .nc by removing the ".nc" or by adding ".dc" to the end of the file name if .nc is not in the encrypted file’s name. Still, I think that my assumption is right. Another problem: according to archive.debian.org, the first debian version which had mcrypt in it is woody (released 19 July 2002). The first debian/changelog entry is: -- Raphael Bossek <[email protected]> Sat, 15 Apr 2000 11:38:48 +0200 And the first upstream changelog entry is: 2000-05-22 13:07 nmav At least according to the changelogs available today. Google can't find anything useful for "mcrypt potato" or "mcrypt slink". Are you absolutely sure, that you have created those .dc files with mcrypt and they are actually encrypted (probably they were produced because of some error in an old version or because of a usage error and they couldn't have been decrypted at all). If I can help in any meaningful way, I'm willing to. If you have any more data which can help or you can figure anything out, I'm willing to listen. Otherwise I would like to close this bugreport, because .dc files seems to be decrypted files and other users have never reported bugs like this. (And I assume it's quite a big and noticable bug, if your encrypted files can't be decrypted anymore after an upgrade.) Thank you for your bug report, Gergely -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
