Tatsuya Kinoshita <firstname.lastname@example.org> writes: > I think that the alpaca package isn't meaningless even if less > people use alpaca than EasyPG. Grr. It's FEWER! > > `alpaca' uses symmetric encryption with "--cipher-algo AES" for a > new *.gpg file by default, while I haven't found an easy way to > customizet EasyPG. > Anyway, the point of this post: gpg's default symmetric encryption algorithm is CAST5 . Looking through the epg code, I agree that there isn't currently a way to customise this. However, a lot of the infrastructure to make this easy is available: in epg.el line 36 there is a constant, epg-cipher-algorithm-alist. Using that as a filter, it would be quite simple to add a selection mechanism for the output type. I don't intend to do this, since I'm not sure what the appropriate semantics would be: should the user be pestered? should it be available via some prefix arg? Certainly there should be a customisation option. However, I'm sure that the epg maintainers would be interested in patches and/or further discussion about this. Maybe you should take the topic to their mailing list? Rupert  See the gpg manpage, COMMANDS section, under -c.
Description: PGP signature