2008/10/27 Tatsuya Kinoshita <[EMAIL PROTECTED]>:
>> > To encrypt *a new file*, epa-file.el asks recipients, while
>> > alpaca.el doesn't ask recipients, because alpaca.el always use the
>> > gpg -c option. My wish is "use gpg -c for new file" option, and
>> > setting epa-file-encrypt-to to "" seems to work like so.
>>
>> OK, I'll consider a new option which would call
>> `epa-file-default-encrypt-to' for that purpose, with an appropriate
>> docstring.
>
> Thanks for the new variable.
Alternatively, the problem is fixed by defining epa-file-encrypt-to
with defcustom, which forces users to set the variable with
setq-default.
>> > BTW, alpaca.el also uses the gpg option "--cipher-algo AES" for
>> > encryption by default. If the alpaca-cipher variable is set to
>> > "AES256", "--cipher-algo AES256" is used. Meanwhile epa-file.el
>> > seems to use the gpg default ("3DES" or "CAST5"), and I haven't
>> > found an easy way to customize it...
>>
>> Is it not sufficient to set "cipher-algo AES256" in ~/.gnupg/gpg.conf?
>
> Although ~/.gnupg/gpg.conf works, I hope an Emacs Lisp variable for
> --cipher-algo will be defined. If it exists, cipher-algo can
> temporally be switched in Emacs easily. Could you please consider it?
Well, that is a design issue which I intentionally didn't make it so
flexible. I think such a low-level option better be configured in the
central point -- ~/.gnupg/gpg.conf.
Do you have any real problem with this? Otherwise, I won't change this.
Regards,
--
Daiki Ueno
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
