Still pretty newbie here. I wanted to install the AES Crypt GUI. (I already have the AES Crypt in the terminal but would like the GUI too.)

So I followed the instructions (see screenshot). When I was done I did not get the GUI. Here are the results of the terminal. (at pastebin)

http://pastebin.com/B8hXv1vd

Two questions:

1) Did I do something wrong?
2) If getting the GUI isn't do-able, should I get rid of all that stuff (that the pastebin shows), and if so, how?

Thanks.

Attached Thumbnails

 

Gregg, where you write that you “did not get the GUI”, it would be interesting to know, *how* you tried to start the GUI. The information that I find indicates that the program to call is aescrypt-gui and that it must be called via the context-menu of a file manager application like Nautilus, Dolphin, Thunar and the like. The messages that you publish on pastebin do in their majority not concern AESCrypt but your desktop-environment.

Nautilus and Dolphin appear to show aescrypt-gui after its installation, for others you must configure the shortcut yourself (PCManFM, Thunar ...).

The specificities of your desktop-environment seem more important for the solution of your problem than the way, that the installation is organized. And the protocol on pastebin does not succeed in arousing my interest in KDE... rather the contrary.

1 members found this post helpful.

Thanks very much, Michael. Your reply got me thinking and then more closely checking the 'how to use' pdf from AES crypt. The GUI is just that when you right click on the file it gives you the option of opening it with AES Crypt. Well, I did that. It kind of confused me because it was asking me to open something that was not encrypted (but now I know it was just asking to open the AES crypt app.) And it also confused me because once the AES crypt was chosen and I entered a password it just gave another pop-up window asking for the password again.I figured it wasn't working. Well, a closer look at the instructions revealed that I needed to enter that password twice. When I did, it worked perfectly. And so did the de-crypting. Really appreciate your help.

Any competently coded encryption app will require entering the initial password twice. It's very common to put a typo in the first time, and if that's accepted, your password is not what you think it is. Requiring two matching entries before accepting the password makes this less likely.

1 members found this post helpful.

That makes sense. Thanks.

I use zuluCrypt which is a front-end GUI app to cryptsetup.


You can use the wizard to create an encrypted container for a hard drive, usb stick or you can create an encrypted container in a file. The file will act like an encrypted loop back device to hold your files.

My grandmother made the best apple-cake in all the world. Ever.

Could someone remove the reputation-point that I got for the odd idea to help the OP get *his* software run correctly? As.., like everybody knows, the best solution (ever) for any problem with any program under the sky is to use a different program.

1 members found this post helpful.

In another thread, someone has suggested encfs. This might be a viable solution. It's in the Debian repositories, and there are tutorials available through the magic of Google Search. I hadn't heard of it, but I'm trying it out.

Sounds cool.

Ha ha. No the reputation point stays. (I'm staying with AES crypt--your help was not in vain!)