unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: jens.lechtenboerger@fsfe.org, 18718@debbugs.gnu.org
Subject: bug#18718: Encrypted messages expose Bcc identities
Date: Sun, 27 Dec 2015 20:20:02 +0200	[thread overview]
Message-ID: <83wprzg3e5.fsf@gnu.org> (raw)
In-Reply-To: <87vb7jepsj.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  27 Dec 2015 18:59:08 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 27 Dec 2015 18:59:08 +0100
> Cc: 18718@debbugs.gnu.org
> 
> Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
> 
> > A patch is attached.  The new function mml-secure-bcc-is-safe does
> > nothing on its own but can be added to message-send-hook or called
> > from message-send and friends.
> 
> Looks good.  Do you have Emacs copyright assignment papers on file?

He does.





  reply	other threads:[~2015-12-27 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878u4fd4zr.fsf@gnus.org>
     [not found] ` <86y4sitzcx.fsf@informationelle-selbstbestimmung-im-internet.de>
2015-12-26 21:34   ` bug#18718: Encrypted messages expose Bcc identities Lars Ingebrigtsen
2015-12-27 15:51     ` Jens Lechtenboerger
2015-12-27 17:59       ` Lars Ingebrigtsen
2015-12-27 18:20         ` Eli Zaretskii [this message]
2015-12-27 18:26       ` Lars Ingebrigtsen
2015-12-27 20:09         ` Jens Lechtenboerger
2015-12-27 20:13           ` Lars Ingebrigtsen
     [not found]   ` <handler.18718.C.145124724816035.notifdonectrl.0@debbugs.gnu.org>
2016-01-02 14:49     ` bug#18718: acknowledged by developer (control message for bug #18718) Jens Lechtenboerger
2016-01-03  9:08       ` Lars Magne Ingebrigtsen
2016-01-03 14:57         ` Jens Lechtenboerger
2016-01-04  0:57           ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wprzg3e5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18718@debbugs.gnu.org \
    --cc=jens.lechtenboerger@fsfe.org \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).