From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/52323 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: I have to enter my passphrase twice? Date: Mon, 05 May 2003 19:22:47 +0200 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <878ytlpit9.fsf@pooh.honeypot.net> <873cjt5te4.fsf@pooh.honeypot.net> <871xzdnz1s.fsf@pooh.honeypot.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1052156035 22037 80.91.224.249 (5 May 2003 17:33:55 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 5 May 2003 17:33:55 +0000 (UTC) Cc: ding@hpc.uh.edu Original-X-From: ding-owner+M865@lists.math.uh.edu Mon May 05 19:33:52 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19CjfU-0004Ge-00 for ; Mon, 05 May 2003 19:22:24 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19Cjg5-00016W-00; Mon, 05 May 2003 12:23:01 -0500 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=root) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 19Cjfx-00016Q-00 for ding@lists.math.uh.edu; Mon, 05 May 2003 12:22:54 -0500 Original-Received: from yxa.extundo.com (178.230.13.217.in-addr.dgcsystems.net [217.13.230.178]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id MAA11115 for ; Mon, 5 May 2003 12:24:03 -0500 (CDT) Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h45HMlbT015055; Mon, 5 May 2003 19:22:47 +0200 Original-To: Kirk Strauser Mail-Copies-To: nobody X-Payment: hashcash 1.2 0:030505:kirk@strauser.com:df20b32701180d1c X-Hashcash: 0:030505:kirk@strauser.com:df20b32701180d1c X-Payment: hashcash 1.2 0:030505:ding@hpc.uh.edu:d1eef0a2a8acc26d X-Hashcash: 0:030505:ding@hpc.uh.edu:d1eef0a2a8acc26d In-Reply-To: <871xzdnz1s.fsf@pooh.honeypot.net> (Kirk Strauser's message of "Mon, 05 May 2003 11:22:39 -0500") User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/20.7 (gnu/linux) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:52323 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:52323 Kirk Strauser writes: > At 2003-05-05T15:55:29Z, Simon Josefsson writes: > >> Do you use GCC? Perhaps the message that is mailed is signed correctly, >> but the second signature (for GCC) fails, and the GCC code doesn't signal >> an error. Can you look in your GCC group? > > Yes, I use GCC. Out of curiosity, why would it sign the message twice? Because the body in GCC may be encoded differently than the body that is sent via mail. If this sounds weird, here is an elaboration: Consider if you set gnus-gcc-externalize-attachments and attach a file to your message. Then the body encoded for GCC is very different than the body encoded for mail. (Namely, the latter one includes the file, whereas the former only includes a external MIME reference.) If you posted your message to a newsgroup too (that is, both via mail and news, and GCC), you might have to sign the message three times, since Usenet have different encoding requirements than mail (e.g., iso-8859-1 may be prefered over utf-8 in one newsgroup, and the other way around in another, and any choice may be different from what is prefered for mail). In general, a given MML message encoded for mail, news or GCC do not necessarily look the same. So they need different signatures. I guess the security system could "cache" (unsigned-msg, signed-msg) tuples so the user is not queried twice if the encodings are identical. But this sounds like work, and might end up not being used in the majority of cases anyway due to subtle differences. Perhaps you object to these ideas, and want GCC to simply save a _copy_ of what was actually mailed. Currently this is not what GCC does, but if you want that behavior instead, BCC yourself and filter them into your sent-mail folder. > One lingering question, though: where did it get "kirk@strauser.com" as my > key ID? That happens to be a userid on the key I use, but I never specified > it anywhere. It was taken from the From: header.