Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 449BE6DE0B7C for ; Mon, 7 Sep 2015 23:01:49 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.648 X-Spam-Level: X-Spam-Status: No, score=0.648 tagged_above=-999 required=5 tests=[AWL=0.715, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9iQiExda6qDH for ; Mon, 7 Sep 2015 23:01:47 -0700 (PDT) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by arlo.cworth.org (Postfix) with ESMTPS id 82FF26DE0B64 for ; Mon, 7 Sep 2015 23:01:46 -0700 (PDT) Received: by wicfx3 with SMTP id fx3so101891797wic.0 for ; Mon, 07 Sep 2015 23:01:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:in-reply-to:references:user-agent :from:date:message-id:mime-version:content-type; bh=H3CS5cNp73iI4JQ4lNPIyqlcIxFufa5XR/4PUgn8G8k=; b=GO21dRksProrM1rf/Z8F1acUrQIK9mLMarhv1zNKQylw7LUQfjyH5gbXWFpSyW28Zi AUZlM0rR2QrM2tTRmGF4b5I1llxAvxOXfFn2No8RNB882Le8a7S4pB+bWyAbv6fBxyF0 EZpoU+xL+tcq3VyRqxQA8gVcSbAAR9Z1QRd5zlWZuboZmY8WWg9jS2FjMwF5mqSpTXle 7jbJkeITXwABSmBYyE0FsSeE3+19wmkKAiaxRL66V9NFmpWfzo+pg2lOVppUUd9bpJl2 g8+aYMks7knMlFc2VZaqoBwn9IxVfhxBXD2+kKL7F7LxcE+mf4wJe3jOSPi+xoFoL7TT 1zqQ== X-Gm-Message-State: ALoCoQl/qwpw5GhMS9ONaEZX45A4FFcxWiFT865/lNHa6NSZML8soWPA0CSK15N3psy43R2L8pa7 X-Received: by 10.194.110.37 with SMTP id hx5mr43376464wjb.149.1441692104118; Mon, 07 Sep 2015 23:01:44 -0700 (PDT) Received: from disaster-area.hh.sledj.net ([2a01:348:1a2:1:ea39:35ff:fe2c:a227]) by smtp.gmail.com with ESMTPSA id cm6sm3788303wib.22.2015.09.07.23.01.43 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Sep 2015 23:01:43 -0700 (PDT) Received: from localhost (30000@localhost [local]); by localhost (OpenSMTPD) with ESMTPA id 82f827f7; Tue, 8 Sep 2015 06:01:42 +0000 (UTC) To: Daniel Kahn Gillmor , notmuch@notmuchmail.org Subject: Re: using the fringe to indicate good signatures In-Reply-To: <87d1xtn8s8.fsf@alice.fifthhorseman.net> References: <87d1xtn8s8.fsf@alice.fifthhorseman.net> User-Agent: none From: David Edmondson Date: Tue, 08 Sep 2015 07:01:42 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2015 06:01:49 -0000 On Mon, Sep 07 2015, Daniel Kahn Gillmor 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? 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)).