Recent changes to feature-requests

#10 Support for Android 5

Max Ponozka — Fri, 28 Jun 2024 14:26:35 -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.

#12 Option to keep rather than wiping original files.

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

status: open --> closed

#12 Option to keep rather than wiping original files.

Calle Oxwall — Fri, 06 Oct 2023 19:35:43 -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 my very very small scripting/coding skills. I have just written a CC_EN.CMD and a CC_DE.CMD (respetively), to do what I wish for:

The encoding script is pretty straightforward:
if "%~1" == "" ( echo use: cc_en FIL_ATT_KRYPTERA ) else ( ccrypt -e < "%~1" > "%~1.cpt" )

Whilst the decrypting part is more complicated. Assuming the encrypted file has .cpt suffix and in best of worlds I would not need to put in both "input" and "output" but only input.cpt and it would just cut the .cpt extention for output. Without having to write nestled Windows batch code I think I would need to call GAWK.EXE or some other GNU-Win32-binary to strip the .cpt etcetera etcetera. This was just too complicated so I ended up with using both "%1" and "%2" for decryption, see below.

if "%~1" == "" ( echo use: cc_de "FIL_ATT_DEKRYPTERA" "UTDATA_FIL" ) else ( ccrypt -d < "%~1" > "%~2" )

With a -keep switch built into ccrypt all this scripting would be uncalled for, and also one would not have to write equivalent script for Linux environment.

Anyways, such feature is on my personal wish list.
But hey, thanks for a really great piece of software! :)

#12 Option to keep rather than wiping original files.

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.

#12 Option to keep rather than wiping original files.

Calle Oxwall — 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! :)

Option to keep rather than wiping original files.

Calle Oxwall — Thu, 05 Oct 2023 19:02:32 -0000

Found this old thread:
https://sourceforge.net/p/ccrypt/feature-requests/8/

But even though Mr. Sellinger answered right away I can't seem to get his approach to work. For instance, I have file.txt and want to encrypt it to file.txt.cpt BUT without having file.txt removed when encryption is done. This, I have yet not found a way to do. Also, the other way around, when deencrypting file.txt.cpt I would like a way to just decrypt the file.txt but not wiping the .cpt it came out of.

Option to keep rather than wiping original files.

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

Ticket 12 has been modified: Option to keep rather than wiping original files.
Edited By: Peter Selinger (selinger)
Status updated: 'open' => 'closed'

#11 Progress display while encrupting

Peter Selinger — Wed, 09 Dec 2020 01:25:55 -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 of an extreme case.

I don't promise to implement this feature right away, but I'll keep it in mind. -- Peter

Progress display while encrupting

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

It would be very useful (when encrypting disk dumps for example) if there is a progress display with some useful information - % done, speed (mb/s), estimated time remaining (based on current speed). The progress info could be off by default and turned on using an option.
In theory I could use pv for progress, but then I'm left with unencrypted copy of the file that I need to securely erase.
It might be a little hard to decide how to make the progress when multiple files are passed - do you simply display current file progress or you only display the total progress or both. You probably wouldn't want to spend too much time on it. Maybe a total progress would be fine.
If it's too much to estimate time, speed etc. a simple progress in percent will be enough. Usually when I want to get up from the computer and get back when it's finished I can time how long takes for 1% or 10% and multiply by 100 or 10 respectively.

#10 Support for Android 5

Peter Selinger — Sat, 05 Nov 2016 04:00:42 -0000

Thanks for writing, and sorry for the delayed reply. The Android binaries on the ccrypt website are created by a third party, and he has told me that there are problems with generating the binaries for Android 5 and up. So unfortunately, there are no Android 5 binaries unless somebody figures out how to do it and sends them to me. Sorry about that! -- Peter