unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [Review] Re: new "crypto" branch providing full PGP/MIME support
Date: Mon, 28 Feb 2011 15:08:39 -0500	[thread overview]
Message-ID: <4D6C00C7.9000705@fifthhorseman.net> (raw)
In-Reply-To: <874o7o6ih5.fsf@servo.finestructure.net>

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

On 02/28/2011 02:56 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 13:59:54 -0500, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>> But: what does the "signed" tag mean? i wouldn't want to necessarily
>> conflate these four ideas:
> 
> These are good points, Daniel.  However, I had actually just been
> thinking of something much simpler, along the lines of just tagging
> "signed" any message with a "multipart/signed" part, and "encrypted" any
> message with a "multipart/encrypted" part.

this is a fair answer to my questions, not an evasion -- you're
selecting level 0 in both tracks, which is not a bad thing (it's
certainly simpler to get right!)

The outstanding question in my mind is whether those tags could be
mistaken by a naïve user for meaning one of the other concepts.  Is
there a way to name the tags to minimize that kind of confusion?

	--dkg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]

  reply	other threads:[~2011-02-28 20:08 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 19:35 PGP/MIME signature verification Daniel Kahn Gillmor
2010-11-27 21:24 ` Jameson Rollins
2010-12-13 22:02 ` David Bremner
2010-12-13 22:11   ` Daniel Kahn Gillmor
2010-12-13 22:10 ` David Bremner
2010-12-13 22:14   ` Daniel Kahn Gillmor
2010-12-20 18:22 ` Jameson Rollins
2010-12-21  9:51   ` Sebastian Spaeth
2010-12-21 15:36     ` Daniel Kahn Gillmor
2010-12-22 14:38       ` Sebastian Spaeth
2010-12-22 19:11         ` Daniel Kahn Gillmor
2011-01-27  1:13   ` Jameson Rollins
2011-02-03  1:18     ` new "crypto" branch providing full PGP/MIME support Jameson Rollins
2011-02-03 16:25       ` micah anderson
2011-02-03 19:52         ` Daniel Kahn Gillmor
2011-02-03 20:34           ` Jameson Rollins
2011-02-03 21:03             ` always encrypting messages to self [was: Re: new "crypto" branch providing full PGP/MIME support] Daniel Kahn Gillmor
2011-02-04 13:04               ` Sebastian Spaeth
2011-02-04 17:30                 ` Jameson Rollins
2011-02-04 16:59           ` new "crypto" branch providing full PGP/MIME support micah anderson
2011-02-04 17:30             ` Daniel Kahn Gillmor
2011-02-03 17:48       ` Daniel Kahn Gillmor
2011-02-03 20:42       ` Darren McGuicken
2011-02-03 21:02         ` Jameson Rollins
2011-02-04 12:09           ` Darren McGuicken
2011-02-04 17:32             ` Jameson Rollins
2011-02-05 14:50               ` Darren McGuicken
2011-02-04 21:07           ` Jameson Rollins
2011-04-25 22:35             ` Jameson Graef Rollins
2011-02-04 12:24       ` David Bremner
2011-02-04 17:24         ` Jameson Rollins
2011-02-04 17:12       ` David Bremner
2011-02-04 18:10         ` Jameson Rollins
2011-02-27  0:45       ` [Review] " David Bremner
2011-02-27 10:41         ` Darren McGuicken
2011-02-28 13:24           ` Sebastian Spaeth
2011-02-28 13:52             ` Ross Glover
2011-02-28 18:25               ` Jameson Rollins
2011-02-28 18:59                 ` Daniel Kahn Gillmor
2011-02-28 19:56                   ` Jameson Rollins
2011-02-28 20:08                     ` Daniel Kahn Gillmor [this message]
2011-03-01  2:49                       ` Jameson Rollins
2011-03-01  3:16                         ` Rob Browning
2011-03-01  3:31                           ` Jameson Rollins
2011-03-05  8:26                             ` signed/encrypted tagging in crypto branch [was: Re: [Review] Re: new "crypto" branch providing full PGP/MIME support] Jameson Rollins
2011-03-06 19:15                               ` signed/encrypted tagging in crypto branch Jameson Rollins
2011-04-14  7:48                                 ` Florian Friesdorf
2011-04-16 15:27                                 ` Pieter Praet
2011-03-01 19:32             ` [Review] Re: new "crypto" branch providing full PGP/MIME support Simon Fondrie-Teitler

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=4D6C00C7.9000705@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).