From: Jan Rychter <jan@rychter.com>
Subject: Re: Signing messages
Date: Fri, 20 Jun 2003 10:14:40 -0700 [thread overview]
Message-ID: <m2d6h8acxr.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <ilubrwt507l.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 19 Jun 2003 21:36:14 +0200")
>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
Simon> Jan Rychter <jan@rychter.com> writes:
>> WIBNI if it were possible to delay the moment of signing messages?
>>
>> As it is, if I write a message marked as <\#secure method=pgpmime
>> mode=sign>, Gnus tries to sign it right after I press C-c C-c. This
>> is probably fine for most people, but some of us are paranoid and
>> keep their secret key on a USB clipdrive, which gets attached only
>> sometimes, for a short period of time.
Simon> How about C-c C-d and when you plug in your USB clipdrive, D s
Simon> the messages?
Hmm. It does work, somewhat. It's not too convenient, as I have to
remember:
a) not to send (C-c C-c) the message when it's a signed one (I could
live with that),
b) go to drafts and pick those messages that need to be signed and
sent (my drafts folder is usually a bit polluted, so I have to find
the ones that really need sending).
Simon> Or if you make sure to have the USB clipdrive inserted between
Simon> 15:00 and 15:05 every day, you could use C-c C-j and delay
Simon> sending until that time. Perhaps the delay mechanism could be
Simon> enhanced to trigger sending when the USB clipdrive is available.
The last option would obviously be the best one -- but it boils down to
the same thing: Gnus knowing what messages await signing.
--J.
prev parent reply other threads:[~2003-06-20 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-19 19:12 Jan Rychter
2003-06-19 19:36 ` Simon Josefsson
2003-06-20 17:14 ` Jan Rychter [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2d6h8acxr.fsf@tnuctip.rychter.com \
--to=jan@rychter.com \
/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.
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 NNTP newsgroup(s).