Packetizer Forums

Is there anyone using AES Crypt who would like to be a Linux package manager? We've had several requests for Fedora package files and Ubuntu package files. Having those available might help a lot of users who are not familiar with compiling from source.

aescrypt-305 for linux
deb, rpm and tgz

http://ge.tt/3YClvDJ?f

If works, then is OK!

As long as the project has been around, why not get it into a mainstream extra's repo or something along those lines, I think the license is correct, unless I am missing something. I would start with Fedora and Ubuntu.

As simple as the code is, I cannot imagine it being an issue, there are no dependencies, nothing. What would really be cool is a QT interface, or GTK+ or something which would work well within Xwindows. That would be sweet, Unfortunately while I use linux almost exclusively, I only program linux server side code, console only apps. A little Perl::Tk on occasion, but, wouldn't know where to begin for a GTK/QT type interface. Actually, I don't even know if QT is provided with all distributions, if it was, that would make things much much simpler IMO to create a windows like shell extension for X. I could be talking completely out of my realm here because while haven written very basic X apps, I have never written something which interfaces with the WM functions such as right clicking a file, and popping up the context menu, and making an extension to said menu. Would be nice though,

Off topic, but, does anyone know if there is a common interface among all the window managers for adding extensions to the context menu's on the desktop? I'd imagine that would be difficult, but, creating a QT popup or something for the password entry would be easy. You'd still have to talk to X even with the popup, but, I bet it would be simpler than doing the context extension.

Anyone know off hand?

It requires a person with available time and interest to do it. AES Crypt is an entirely unfunded open source project. What gets done is only what people volunteer to do.

That said, we would have the same export restrictions that OpenSSL has to deal with. I'm not sure what the OpenSSL folks did to get past U.S. export laws, for example. It's not legal to make encryption available everywhere, though the Dept of Commerce fully recognizes that encryption on the Internet cannot be controlled. That was acknowledged when I first published AES Crypt and worked to comply with their publication requirements.

The best advice is still done by hand. (cd and terminal)

1.make

2.sudo cp aescrypt aescrypt_keygen /usr/bin/

3. whereis -b aescrypt aescrypt_keygen

Why not just do "make install"? That will effectively do the same thing.

paulej wrote:Why not just do "make install"? That will effectively do the same thing.

I have something problem with "sudo make install" and "make install",
( install: stat `aescrypt_keygen' : error.)

only "make" i use now.

That's odd. The stat error suggests the aescrypt_keygen file was not built. I just did it on my Linux machine and it worked as expected. Do you have the latest source code? I don't think that part of the Makefile was broken, but I do recall screwing up something the first time. I think I forgot to include aescrypt_keygen in the Makefile when I first released it.