Re: encrypt.el and pgp argument...

[Ted Zlatanov <tzz@lifelogs.com>]

The following message is a courtesy copy of an article
that has been posted to gnus.gnus-bug as well.

On Fri, 23 Mar 2007 08:50:59 +0100 Bruno Marmol <Bruno.Marmol@inrialpes.fr> wrote: 

BM> When we use the --passphrase-fd argument, it seems that pgp needs to have the --batch
BM> argument.

BM> So encrypt-gpg-process-buffer 

BM> (defun encrypt-gpg-process-buffer (passphrase 
BM> 					cipher 
BM> 					&optional encode)
BM>   "With PASSPHRASE, use GPG to encode or decode the current buffer."
BM>   (let* ((program encrypt-gpg-path)
BM> 	 (input (buffer-substring-no-properties (point-min) (point-max)))
BM> 	 (temp-maker (if (fboundp 'make-temp-file) 
BM> 			 'make-temp-file 
BM> 		       'make-temp-name))
BM> 	 (temp-file (funcall temp-maker encrypt-temp-prefix))
BM> 	 (default-enable-multibyte-characters nil)
BM> 	 (args `("--cipher-algo" ,cipher
BM> 		 "--status-fd" "2"
BM> 		 "--logger-fd" "2"
BM>                  "--batch"                ; <<<======= Add this arg here or other method to add (for correct portability)
BM> 		 "--passphrase-fd" "0"
BM> 		 "--no-tty"))
BM> 	 exit-status exit-data)

Thank you, Bruno.  So the syntax is different in GPG and PGP.
Wouldn't it be better to have a separate encrypt-pgp-process-buffer
function?  They may be similar (and I will abstract what I can), but I
don't want to add extra parameters to the GPG function for PGP
functionality.

I only use GPG so I'm looking for opinions...

Ted