Encryption vs. Gcc

Encryption vs. Gcc

[Ludovic Courtès]

To keep a clear-text copy of encrypted messages that I send, I tried
this, as evasively suggested by the manual:

--8<---------------cut here---------------start------------->8---
;; Keep a clear-text copy of sent messages.
(setq gnus-gcc-post-body-encode-hook
      'mml-unsecure-message)
--8<---------------cut here---------------end--------------->8---

However, that doesn’t work, apparently because when the hook is called
the buffer that is current is not the message (see ‘gnus-inews-do-gcc’.)

Anyway, a more ideal solution for Gcc: would be this: if the message is
encrypted, then keep a copy encrypted with the sender’s public key
(rather than clear-text); otherwise keep a copy as is.

Does anyone have something like this?

TIA,  :-)
Ludo’.

Re: Encryption vs. Gcc

[Philipp Haselwarter]

I added a line with

hidden-encrypt-to $MY_FINGERPRINT (* meta-variable *)

to ~/gnupg/gpg.conf and now I can read all the stuff I encrypt without
it being obvious that I'm the sender. Neat.

-- 
Philipp Haselwarter

Re: Encryption vs. Gcc

[Ludovic Courtès]

Philipp Haselwarter <philipp@haselwarter.org> skribis:

> I added a line with
>
> hidden-encrypt-to $MY_FINGERPRINT (* meta-variable *)
>
> to ~/gnupg/gpg.conf and now I can read all the stuff I encrypt without
> it being obvious that I'm the sender. Neat.

Oh nice, thanks!

Ludo’.

Re: Encryption vs. Gcc

[Adam Sjøgren]

ludo@gnu.org (Ludovic Courtès) writes:

> Anyway, a more ideal solution for Gcc: would be this: if the message is
> encrypted, then keep a copy encrypted with the sender’s public key
> (rather than clear-text); otherwise keep a copy as is.

I am using:

  hidden-encrypt-to 0xMYKYHERE!

in my ~/.gnupg/gpg.conf to achieve this.

From gpg(1):

       --hidden-encrypt-to name
              Same  as  --hidden-recipient  but this one is intended for use in the
              options file and may be used  with  your  own  user-id  as  a  hidden
              "encrypt-to-self".  These  keys  are  only  used when there are other
              recipients given either by use of --recipient or by  the  asked  user
              id.   No trust checking is performed for these user ids and even dis‐
              abled keys can be used.


  Best regards,

    Adam

-- 
 "It's not denial. I'm just very selective about the          Adam Sjøgren
  reality I accept."                                     asjo@koldfront.dk

Re: Encryption vs. Gcc

[Christopher Schmidt]

ludo@gnu.org (Ludovic Courtès) writes:
> However, that doesn’t work, apparently because when the hook is called
> the buffer that is current is not the message (see
> ‘gnus-inews-do-gcc’.)

    (ah gnus-gcc-pre-body-encode-hook
        (goto-char (message-goto-body))
        (while (re-search-forward "^<#\\(secure .*mode=\\(sign\\)?encrypt.*>\\)$"
                                  nil
                                  t)
            (replace-match "<|rms\\1")))

    (ah gnus-gcc-post-body-encode-hook
        (goto-char (message-goto-body))
        (while (re-search-forward "^<|rms\\(.*\\)$" nil t)
          (replace-match "<#\\1"))))

        Christopher