Re: Encrypting outgoing message but not Gcc?

[Lloyd Zusman <ljz@asfast.com>]

[ NOTE:  this is a repost which has been slightly modified
         from the original post, in an attempt to get past
         the "partial message checksum" message I got from
         the moderator-bot. ]

Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

> [ ... ]
>
> ,----[ C-h v pgg-encrypt-for-me RET ]
> | pgg-encrypt-for-me's value is t
> | 
> | Documentation:
> | If t, encrypt all outgoing messages with user's public key.
> `----
>
> The default value has bee changed to `t' recently (2003-11-10).

I was wondering why this option didn't work for me, and I found the code
below in yesterday's CVS.  Notice that it makes my user ID known to gpg
by means of the `--remote-user' option.  However, this option is no
longer used in recent versions of gpg ... it's been replaced with
`--recipient'.

I think that we need a configuration variable that allows us to specify
one or the other of these option flags, so that the code can be made to
work with both older and newer versions of gpg.


From pgg-gpg.el ...

  (defun pgg-gpg-encrypt-region (start end recipients &optional sign)
    "Encrypt the current region between START and END.
  ;;; ... etc. ...
             (if recipients
                 (apply #'nconc
                        (mapcar (lambda (rcpt)
                                  (list "--remote-user" rcpt))
                                (append recipients
                                        (if pgg-encrypt-for-me
                                            (list pgg-gpg-user-id)))))))))
  ;;; ... etc. ...



-- 
 Lloyd Zusman
 ljz@asfast.com