fSekrit 1.35 shrinkwrapped!

[f0dder]

There, fSekrit 1.35 has been released!

After a relatively short beta period, this Christmas 2007 release sports the following features:

Version 1.35 - December 23, 2007 - 100kb/50.5kb

• fixed: file->export appends ".txt" instead of ".exe" if no extension given.
• fixed: file->new now clears passphrase and read-only state.
• fixed: menu items are now properly enabled/disabled depending on read-only state and whether text field is empty or not.
• added: drag&drop support: you can now drop a text file onto the fSekrit window, and fSekrit will load the dropped file.
• added: right-click popup menu with edit actions
• added: redo support
• added: unicode text support (only the note text, not filenames yet)
• added: now everything sensitive is always wiped from memory after use, as far as it's possible (with the exception of the RichEdit control).

As always, I hope there aren't any bugs I haven't caught

[mouser]

awesome 

[SKA]

Truly a generous gift for Christmas !

Grateful for your patience and perseverance to come out with a new version in record time !

Thanks indeed ,
SKA

[cemole]

I tried to export to a .txt file but the exported file still had .exe appended to it. I was able to change the extension to .txt and open the file without any problems, so I believe the problem might be how the program writes the filename when its trying to save to the specified location.

[f0dder]

I tried to export to a .txt file but the exported file still had .exe appended to it. I was able to change the extension to .txt and open the file without any problems, so I believe the problem might be how the program writes the filename when its trying to save to the specified location.

Which fSekrit version? With 1.35, the default extension for export should be .txt, I just verified with the version from http://www.donationcoder.com/Software/Other/fSekrit/ ...

[cemole]

I'm using version 1.35, however, I believe the problem might be because of files created with an earlier version. I get .exe appended to these files if I try to export them. On the other hand, files export as stated if they are also created with version 1.35.
Thank you.

[f0dder]

I'm using version 1.35, however, I believe the problem might be because of files created with an earlier version. I get .exe appended to these files if I try to export them. On the other hand, files export as stated if they are also created with version 1.35.
Thank you.

Yes, for previous versions, you get .exe appended if you do export, that's a known bug. But the only information stored when you export (or copy to clipboard) is your actual note data, so if you import (or paste) to v1.35, I can't see how that would affect 1.35 export...

Can you post a .exe here that exhibits this bug? (pick something insensitive with a silly password, of course, and please .zip the file before attaching).

[cemole]

You hit the nail on the head, I think that's where I had my problems. I had files created with an earlier version of fsekrit, however, didn't re-create them or import (not directly at least) to the latest version. I should have been more aware that each file is independent and includes a copy of the fsekrit.exe with which it's been created (an earlier version in my case). Lesson: read user instructions more carefully.

Maybe I can suggest something like importing .exe files when appropriate passphrase is entered which may make life easier when updating files from earlier versions.

[f0dder]

Maybe I can suggest something like importing .exe files when appropriate passphrase is entered which may make life easier when updating files from earlier versions.

That's a thing I have on my todo-list, I'm still pondering how to do it in a "user friendliness efficient" way

[tomos]

hi f0dder or anyone
I found a use for this - or should that be the other way round do you have any recommendations for the password?
I presume it would be the usual recommendations
have a number or two, maybe a symbol or two, and maybe a break in it

again presume you use the same password for all/any notes on the one usb stick?

[f0dder]

Just choose something that's not in a dictionary, isn't too short, and preferably has a couple of numbers in it. The only way to break fSekrit containers would be bruteforcing them... I think there was a table posted here somewhere with some rough estimates of how long it would take to bruteforce varying keyspaces. Personally I go for ~10 chars or more, depending on how secure the stuff needs to be.

Btw, ever since v1.2, saving identical data with identical passphrase does not generate the same output files (randomized IVs).

[tomos]

great, thanks f0dder

[rjbull]

do you have any recommendations for the password?

Not the answer to the question, but allied; you could use KeePass to generate passwords.  Or, look at Johannes Wallroth's Password Generator

A useful tool for creating passwords that nobody can guess. Use a mixture of upper/lowercase letters, numbers and a selection of user defined special characters. Generate up to 1000 passwords at a time and save them to a file.

[f0dder]

Trick about passphrases is that you need to be able to memorize them, though, otherwise you end up writing them down on a piece of paper or whatever

[rjbull]

Trick about passphrases is that you need to be able to memorize them, though, otherwise you end up writing them down on a piece of paper or whatever

"Try his first wife's maiden name,
Bomb it out and try again,
This is more than just a game,
It's hacking, hacking, hacking..."

[simonrl]

If I try create a new file starting from a read-only one by clicking on the "New" option, the new window has the option "make read-only" available, implying apparently that the new file about to be created is not protected, and yet I am unable to enter any text from the keyboard or import any text. Am I missing something? Thanks for a wonderful and very useful piece of software.

[f0dder]

If I try create a new file starting from a read-only one by clicking on the "New" option, the new window has the option "make read-only" available, implying apparently that the new file about to be created is not protected, and yet I am unable to enter any text from the keyboard or import any text. Am I missing something? Thanks for a wonderful and very useful piece of software.

The whole way "read-only" works is something I've been planning to redesign for a while, it is not intuitive at all! You have to start with a new note, enter your text, and only then do you enable read-only. After that, you can use "Save As" or "Exit", to get your file saved.