Activity for ccrypt

Peter Selinger posted a comment on ticket #5

Peter Selinger — Mon, 13 Apr 2026 19:23:36 -0000

Hi, thanks for this. However, that is not what the fix is. What needs to be removed is the dependency on libcrypt3 (the "unix crypt" library), not the --unixcrypt functionality. Ccrypt already emulates libcrypt3, so all that needs to be done is basically use --disable-libcrypt every time, instead of trying to use the system-wide libcrypt3. I've already fixed this upstream, but I haven't made a release yet.

Alef created ticket #5

Alef — Sun, 12 Apr 2026 17:19:51 -0000

Remove unix-crypt and crypt3 dep

Peter Selinger modified a comment on ticket #8

Peter Selinger — Sat, 02 Aug 2025 01:37:42 -0000

Thanks for reporting; this is a duplicate of https://sourceforge.net/p/ccrypt/bugs/30/.

Peter Selinger posted a comment on ticket #8

Peter Selinger — Sat, 02 Aug 2025 01:36:58 -0000

This is a duplicate of https://sourceforge.net/p/ccrypt/bugs/24/ and https://sourceforge.net/p/ccrypt/bugs/30/.

John McCue posted a comment on ticket #8

John McCue — Sat, 02 Aug 2025 01:25:25 -0000

Forgot, I know nothing about lisp, but if I find something I will add it here

John McCue created ticket #8

John McCue — Sat, 02 Aug 2025 01:06:37 -0000

ccrypt ps-ccrypt.el + Emacs 30.1

Peter Selinger posted a comment on ticket #4

Peter Selinger — Mon, 21 Apr 2025 22:36:27 -0000

Great, thanks for the clarification. According to the documentation, (make-vector 31 0) should be both backward and forward compatible. That change was already made with https://sourceforge.net/p/ccrypt/bugs/30/, though I haven't yet made a release since then.

Nil Geisweiller posted a comment on ticket #4

Nil Geisweiller — Sun, 20 Apr 2025 04:23:24 -0000

obarray-make has been introduced in Emacs 25.1.

Peter Selinger posted a comment on ticket #4

Peter Selinger — Sun, 20 Apr 2025 03:10:12 -0000

Will this break support for Emacs versions prior to 30.1?

Nil Geisweiller created ticket #4

Nil Geisweiller — Sat, 19 Apr 2025 14:34:00 -0000

Replace make-vector by obarray-make in Emacs 30.1

Max Ponozka posted a comment on ticket #10

Max Ponozka — Fri, 28 Jun 2024 14:26:36 -0000

I know this is an old topic but this hack fixes the problem: change the 17th byte of the ccrypt binary from value 02 to 03 using a hex editor.

Peter Selinger modified ticket #30

Peter Selinger — Tue, 05 Mar 2024 02:35:30 -0000

ps-crypt 1.11 breaks with development version of emacs

Peter Selinger posted a comment on ticket #30

Peter Selinger — Tue, 05 Mar 2024 02:35:11 -0000

At least (make-vector 31 0) doesn't seem to break anything for me, so I'm happy to make that change.

Dan Christensen posted a comment on ticket #30

Dan Christensen — Mon, 04 Mar 2024 21:01:49 -0000

Changing (make-vector 31 nil) to (make-vector 31 0) seems to fix it for me, but I'm not an expert and this is only very lightly tested.

Dan Christensen created ticket #30

Dan Christensen — Mon, 04 Mar 2024 20:55:10 -0000

ps-crypt 1.11 breaks with development version of emacs

Peter Selinger modified ticket #29

Peter Selinger — Thu, 29 Feb 2024 04:59:11 -0000

Spelling error in manual page

Peter Selinger posted a comment on ticket #29

Peter Selinger — Thu, 29 Feb 2024 04:58:42 -0000

Thanks. This is a duplicate of 0020-man-page-spelling-error.patch in the Debian distribution. Will be fixed in the next release.

Sven Geuer created ticket #29

Sven Geuer — Wed, 28 Feb 2024 22:00:52 -0000

Spelling error in manual page

Peter Selinger modified ticket #12

Peter Selinger — Sat, 07 Oct 2023 03:19:58 -0000

Option to keep rather than wiping original files.

Mr. Oxw@ll posted a comment on ticket #12

Mr. Oxw@ll — Fri, 06 Oct 2023 19:35:44 -0000

Thanks for quick response(s) on the matter. Yeah, I'm sometimes in Windows, sometimes in Linux. I reckon your "< > method" works in CMD.EXE environment, W10. However, I hold to the opinion that a simple switch for keeping original files would be great. That way, one who has the need for such possibility and who does not want to type the < > stuff every time won't have to write different batch scripts for different operating systems. Also, such scripts are not made with ease, well at least not with...

Peter Selinger posted a comment on ticket #12

Peter Selinger — Thu, 05 Oct 2023 23:20:05 -0000

Yes, and also, the method mentioned in my response to feature request 8 works, i.e., you can do ccrypt < infile > outfile. This of course presupposes that you are using an operating system that understands pipelines, like "<" and ">". Certainly Mac OS and Linux do; with Windows, it may depend on what kind of command line prompt you are using.

Mr. Oxw@ll posted a comment on ticket #12

Mr. Oxw@ll — Thu, 05 Oct 2023 19:10:26 -0000

Heh, if I had read the man page just a bit more I would have found the -c switch, which makes it possible to > the output wherever is to my liking. Neat. Anyways, this way I still have to type a phony filename for the output. A e.g. -k(eep) switch that simply uses the same naming uniform but keeps input (regardless of -d or -e for action) would still be highly appreciated! :)

Mr. Oxw@ll created ticket #12

Mr. Oxw@ll — Thu, 05 Oct 2023 19:02:33 -0000

Option to keep rather than wiping original files.

Marius posted a comment on ticket #28

Marius — Fri, 21 Apr 2023 08:18:37 -0000

Hi, the ccrypt package was removed from Fedora 38 as compilation fails. Could this be fixed, please?

Mattia Micomonaco posted a comment on discussion Open Discussion

Mattia Micomonaco — Thu, 02 Mar 2023 10:52:48 -0000

Hi. We are using ccrypt 1.11 in an Alpine-based Docker image. I have a question. Is glibc used in ccrypt at runtime / compile time? If so, which version? Thanks in advance. Regards, Mattia Micomonaco

papoteur posted a comment on ticket #28

papoteur — Tue, 12 Apr 2022 15:59:10 -0000

Hello Peter, With --disable-libcrypt configuration option, the test is skipped, thus this is OK. Thanks.

Peter Selinger posted a comment on ticket #28

Peter Selinger — Tue, 12 Apr 2022 12:40:40 -0000

I believe the failed test is caused by recent versions of the crypt3 library not being backward compatible. Please use the --disable-libcrypt configuration option (with ./configure). Then ccrypt will work correctly (although the crypt3 test may still fail). Also note that the crypt3 library is only used in unix-crypt mode, i.e., when ccrypt is used with the -u option. Hopefully this is extremely rarely used, as it's been about 25 years since unix crypt even existed. I'll remove this test and the...

papoteur posted a comment on ticket #28

papoteur — Tue, 12 Apr 2022 05:40:38 -0000

The end of the test: Discrepancy for salt zv, password length 4 Discrepancy for salt zv, password length 7 Discrepancy for salt zT, password length 6 Failed: 817 discrepancies. FAIL crypt3-check (exit status: 1)

papoteur created ticket #28

papoteur — Tue, 12 Apr 2022 05:39:01 -0000

Crypt3_check fails with GCC 12

Dana Booth modified a comment on discussion Open Discussion

Dana Booth — Thu, 21 Oct 2021 17:27:16 -0000

I keep ccrypt.exe and cgwin1.dll in a local bin dir within my "Users" directory in Windows, and it is in my user path. I had never used the --recursive option to encrypt whole directory structures before, but when I did try this morning, ccrypt encrypted the first four files in the target directory and stopped. Additionally, ccrypt.exe mysteriously disappeared from its own directory, and I had to re-extract a new copy from its archive. I re-created this several times using different directories and...

Dana Booth posted a comment on discussion Open Discussion

Dana Booth — Thu, 21 Oct 2021 13:22:19 -0000

I keep ccrypt.exe and ccrypt.dll in a local bin dir within my "Users" directory in Windows, and it is in my user path. I had never used the --recursive option to encrypt whole directory structures before, but when I did try this morning, ccrypt encrypted the first four files in the target directory and stopped. Additionally, ccrypt.exe mysteriously disappeared from its own directory, and I had to re-extract a new copy from its archive. I re-created this several times using different directories and...

Peter Selinger posted a comment on ticket #11

Peter Selinger — Wed, 09 Dec 2020 01:25:57 -0000

Hi NickSoft, thanks for writing. That feature request makes a lot of sense. You have probably already discovered the "-v" option, which tells you which file is currently being encrypted (but does not the progress within each file). That is useful if you are encrypting many files and you want to know how many are finished. Not so useful if you just have one gigantic file. ccrypt is so fast that I never needed a progress bar before for any kind of normal sized file. But indeed, disk dumps are a bit...

NickSoft created ticket #11

NickSoft — Tue, 08 Dec 2020 21:15:59 -0000

Progress display while encrupting

Yahe posted a comment on ticket #27

Yahe — Wed, 02 Dec 2020 12:56:57 -0000

I will end the discussion here and just proceed to advise anyone who is asking against using ccrypt.

Peter Selinger posted a comment on ticket #27

Peter Selinger — Wed, 02 Dec 2020 12:50:33 -0000

At this point you are just flaming me. Here is the definition of "Encryption" from Wikipedia. The information you seem to be misunderstanding is right there in the 4th sentence: "In cryptography, encryption is the process of encoding information. This process converts the original representation of the information, known as plaintext, into an alternative form known as ciphertext. Ideally, only authorized parties can decipher a ciphertext back to plaintext and access the original information. Encryption...

Yahe posted a comment on ticket #27

Yahe — Wed, 02 Dec 2020 07:21:18 -0000

I still think that your FAQs are misleading. The answer to the question "We are thinking of using ccrypt in our company to encrypt our data. Is ccrypt still a strong encryption that is very hard to break?" should be a "No." The response to the question "Does ccrypt implement an authenticated encryption scheme to protect the integrity of the encrypted data? " implies that not providing integrity protection is not a big deal and your suggestion to add an outdated SHA-1 hash at the beginning of the...

Yahe posted a comment on ticket #27

Yahe — Wed, 02 Dec 2020 07:14:55 -0000

Perhaps people expect the author of an encryption tool to provide a proper solution. I was personally asked by a colleague if it is okay to use your application and I had to advise against it. You expect end users to know their way around cryptography which is a false assumption.

Peter Selinger posted a comment on ticket #27

Peter Selinger — Wed, 02 Dec 2020 00:57:44 -0000

I have added this question to the FAQ. The reason it was not there is that nobody has asked this question before. Perhaps not everybody skips the documentation.

Yahe posted a comment on ticket #27

Yahe — Tue, 01 Dec 2020 19:28:13 -0000

This must be some kind of joke. This problem should be mentioned directly on the website and in the security section of the FAQs. Instead you hide this crucial information in the manpages in a section that starts with the false claim that "ccrypt is believed to provide very strong cryptographic security". Actually, I dispute this claim as providing integrity guarantees is part of providing very strong cryptographic security. As I see it right now, ccrypt is outdated cryptographic software that hides...

Peter Selinger modified ticket #27

Peter Selinger — Tue, 01 Dec 2020 17:36:15 -0000

Missing integrity protection

Peter Selinger posted a comment on ticket #27

Peter Selinger — Tue, 01 Dec 2020 17:36:15 -0000

As this is not a bug report, I am closing it.

Peter Selinger posted a comment on ticket #27

Peter Selinger — Tue, 01 Dec 2020 17:35:48 -0000

Yes, that is correct. The documentation also says this. From the man page: "On the other hand, ccrypt does not attempt to provide data integrity, i.e., it will not attempt to detect whether the ciphertext was modified after encryption. In particular, encrypted data can be truncated, leaving the corresponding decrypted data also truncated, but otherwise consistent. If one needs to ensure data integrity as well as secrecy, this can be achieved by other methods. The recommended method is to prepend...

Yahe created ticket #27

Yahe — Tue, 01 Dec 2020 10:21:55 -0000

Missing integrity protection

spaceman modified a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:52:02 -0000

Allow me to suggest to be your WindowsXP test guy, should you decide to continue with the compiler that you used upto 1.10 :)

spaceman posted a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:51:43 -0000

I am willing to be your WindowsXP test guy, should you decide to continue with the compiler that you used upto 1.10 :)

Peter Selinger posted a comment on ticket #26

Peter Selinger — Thu, 25 Apr 2019 20:39:46 -0000

In that case it means that I myself could not have performed Solution #2 either? (Compiling myself) I don't know. You have one decisive advantage, which is that you actually own a copy of Windows XP. I imagine that whatever compiler comes with XP would probably work. I haven't had a computer running XP in many years, so it is hard for me to test.

spaceman modified a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:36:55 -0000

Hi Peter >the problem is that likely I will not have access to an older compiler. In that case it means that I myself could not have performed Solution #2 either? (Compiling myself) >1.7. Is this the latest version that runs on XP? That's actually a terrific idea. I downloaded now 1.8 till 1.11 (wanted to try 1.11 again). The results are: 1.8: Working :) 1.9: Working :) 1.10: Working :) 1.11: Not Working :)) So it seems the problem only starts from 1.11.. All version upto it work great. I tried both...

spaceman modified a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:36:30 -0000

spaceman modified a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:35:50 -0000

spaceman modified a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:34:20 -0000

spaceman posted a comment on ticket #26

spaceman — Thu, 25 Apr 2019 20:33:52 -0000

Hi Peter >the problem is that likely I will not have access to an older compiler. In that case it means that I myself could not have performe Solution #2? (Compiling myself) >1.7. Is this the latest version that runs on XP? That's actually a terrific idea. I downloaded now 1.8 till 1.11 (wanted to try 1.11 again). The results are: 1.8: Working :) 1.9: Working :) 1.10: Working :) 1.11: Not Working :)) So it seems the problem only starts from 1.11.. All version upto it work great. I tried both running,...

Peter Selinger posted a comment on ticket #26

Peter Selinger — Thu, 25 Apr 2019 20:20:00 -0000

Hi Spaceman, the problem is that likely I will not have access to an older compiler. But the changes to ccrypt in the last 15 years have been mostly compatibility updates, so there is nothing wrong in principle with using ccrypt 1.7. Is this the latest version that runs on XP? -- Peter

spaceman modified a comment on ticket #26

spaceman — Thu, 25 Apr 2019 16:42:13 -0000

Hi Peter Thank you very much for the reply. I downloaded v1.7 (file: http://ccrypt.sourceforge.net/download/1.7/ccrypt-1.7.cygwin-i386.zip ) and indeed it now runs well, and I also tested it and it Encrypts and Decrypts well. Is it maybe possible in the next version to compile it to work for XP too? (assuming it does not require any change in the code, and justmeans using a different/older compiler)

spaceman posted a comment on ticket #26

spaceman — Thu, 25 Apr 2019 16:39:41 -0000

Peter Selinger modified ticket #26

Peter Selinger — Thu, 25 Apr 2019 14:58:06 -0000

ccrypt on Windows XP

Peter Selinger posted a comment on ticket #26

Peter Selinger — Thu, 25 Apr 2019 14:55:29 -0000

Thanks for reporting this. The error message likely means that the Windows XP kernel is too old to support this version of ccrypt. You have several options: (1) use an older precompiled version of ccrypt. You can find the older files here: http://ccrypt.sourceforge.net/download/ For example, release 1.7 from 2004 will most likely run on Windows XP. There have been no major bugfixes since 1.7, so this version will work just fine. (2) Compile it yourself from sources. This requires installing Cygwin...

spaceman created ticket #26

spaceman — Thu, 25 Apr 2019 13:00:35 -0000

ccrypt on Windows XP

Peter Selinger modified a comment on ticket #25

Peter Selinger — Sat, 29 Dec 2018 03:47:30 -0000

Thanks for reporting this. I will fix this bug in the next release. It may be caused by an incompatibility between the GNU getopt library and the one included in cygwin. Meanwhile, please configure with ./configure --with-included-getopt This should make the problem go away. Thanks, -- Peter

Peter Selinger posted a comment on ticket #25

Peter Selinger — Sat, 29 Dec 2018 03:47:12 -0000

Thanks for reporting this. I will fix this bug in the next release. It may be caused by an incompatibility between the GNU getopt library and the one included in cygwin. Meanwhile, please configure with configure --with-included-getopt This should make the problem go away. Thanks, -- Peter

marco atzeri created ticket #25

marco atzeri — Sun, 23 Dec 2018 13:32:30 -0000

ccrypt-check.sh wrong test

ccrypt released /1.7/README