[aescrypt] Suggestions - permissions, timestamps, and source file namingfrom Sabrina

[Paul E. Jones]

Andy, (or Sabrina?)

These are all good suggestions.  When I get a moment, I'll add them to the wish list we're maintaining on the aescrypt.com site.

I'm not sure when we'll get around to implementing the suggestions.  Usually, people contribute when they need something.  For a while, it seems people have largely been happy with the way things work.  We've had to make a code change in quite some time.  I certainly don't have time right now, but if you're interested in working on the source, your contribution would be appreciated.

I should say that the thanks should go out to several people, though, some of whom are named in the source code and several who preferred to remain unnamed.  It has been a collaborative effort.  It's a simple tool, but nonetheless useful for many.

Paul

> -----Original Message-----
> From: aescrypt-bounces at lists.packetizer.com [mailto:aescrypt-
> bounces at lists.packetizer.com] On Behalf Of Sabrina Friedman
> Sent: Thursday, August 18, 2011 4:12 PM
> To: aescrypt at lists.packetizer.com
> Subject: [aescrypt] Suggestions - permissions, timestamps, and source
> file namingfrom Sabrina
> 
> Hi Paul
> 
> Just discovered aescrypt. It seems to be exactly what I am looking for -
> a file en/decrypter which is open source and works on linux, osx and
> windows. Thanks very much for creating this.
> 
> I've been adapting it to create an rpm (for redhat style linux
> distributions) and had a couple of suggestions/observations for it:
> 
> (1) File permissions
> I notice that the .aes file created by encryption under linux seems to
> take whatever umask would give it. That may be the preferred solution -
> I genuinely do not know - but I would suggest that the .aes file should
> inherit the permissions of the file it is created from. Presumably the
> same should apply on decrypting.
> 
> (2) Time stamps
> On that subject, the encrypted version of the file, could perhaps have
> the same creation/modification time as the original. It could then also
> pass that back when it is decrypted.
> 
> (3) Name and contents of the source file It might be helpful (for
> packagers etc) if the linux source file adopted a more standard naming
> convention, and also included the man page which it also put in place.
> At present the source file is: aescrypt305_source.tar.gz I would
> suggest: aescrypt-3.0.5.tar.gz which then tar unzips to aescrypt-3.0.5/
> 
> These are all very minor points for an already good and useful piece of
> software. Again - thanks for creating this.
> Andy
> 
> 
> 
> 
> 
> Sabrina Friedman
> Billige Flüge Marketing GmbH
> Emanuelstr. 3,
> 10317 Berlin
> Deutschland
> Telefon: +49 (33) 5310967
> Email: utebachmeier at gmail.com
> Site: http://flug.airego.de - Billige Flüge vergleichen