unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: using the fringe to indicate good signatures
Date: Tue, 08 Sep 2015 02:43:49 -0400	[thread overview]
Message-ID: <87twr5jtqy.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <m2vbbl8n5l.fsf@heart-of-gold.hh.sledj.net>

On Tue 2015-09-08 02:01:42 -0400, David Edmondson wrote:
> On Mon, Sep 07 2015, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
>> On Thu 2015-08-20 09:12:26 -0400, David Edmondson wrote:
>>> After listening to bremner, dkg et al. from Heidelberg, I threw together
>>> a quick patch to see how we might indicate signature validity in the
>>> fringe. The intention is to prompt more discussion - this code is not
>>> ready to ship.
>>
>>> The patch is attached. The result looks something like:
>>>     http://dme.org/data/images/notmuch-signed-fringe.png
>>
>> I like the basic idea of this, thanks for putting it together.  It's
>> good to put security indicators in a region of the UI that the message
>> content cannot modify or spoof.
>>
>> What do we think should be done if there are multiple nested signatures?
>
> Cry?

heh :)

> More seriously, we could use the indentation space for a similar
> indicator, which would allow us some room at an appropriate depth for
> each message (but not each part (in the default configuration)).

hm, but couldn't the indentation space be spoofed by a well-crafted
message?  that is: a non-indented message will consume space up to (but
not including) the fringe.  so a well-crafted message could be made to
*look* like an indented message, including whatever is comparable to the
chrome/UI elements we would use for an actual signed message.

I think it is also acceptable to just punt at some level -- we can say
"notmuch-emacs will indicate the outermost signed message part in the
fringe; it will not indicate nested signed messages in the fringe".
this is still an improvement from the status quo.

     --dkg

  reply	other threads:[~2015-09-08  6:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 13:12 using the fringe to indicate good signatures David Edmondson
2015-09-07 22:50 ` Daniel Kahn Gillmor
2015-09-08  6:01   ` David Edmondson
2015-09-08  6:43     ` Daniel Kahn Gillmor [this message]
2015-09-08  9:53       ` David Edmondson
2015-09-08 18:00         ` Tomi Ollila

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=87twr5jtqy.fsf@alice.fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=dme@dme.org \
    --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).