Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] on sup
Date: Wed, 12 Sep 2007 00:04:15 +0100	[thread overview]
Message-ID: <20070911230415.GB3448@die.therning.org> (raw)
In-Reply-To: <1189548034-sup-2005@south>

On Tue, Sep 11, 2007 at 15:08:34 -0700, William Morgan wrote:
>Excerpts from Magnus Therning's message of Thu Sep 06 00:02:27 -0700 2007:
>> These are the default behaviours I'd like to see:
>> 
>>  - Don't sign, don't encrypt
>>  - Sign all out-going messages, don't encrypt
>>  - Sign all replies to signed messages, don't encrypt
>>  - Sign all replies to signed messages, encrypt replies to encrypted
>>    messages
>>  - Sign all out-going messages, encrypt all messages to recipients with
>>    a known public key
>
>I think you've convinced me to hold off any an UI changes and just have
>a set of behaviors for signing and encryption, configurable in
>config.yaml, that are sophisticated enough to minimize the need for
>per-message actions. That should be pretty easy to do.

Now I know this might not be a very user friendly idea and probably not
ideal for the long run.  It might be a good first step to simply have a
hook like this:

 crypto_hook sender, recipient, reply_to_signed?, reply_to_encrypted? ->
 dosign, doencrypt

(Apply your mad Ruby skills to make it Ruby-esque, but you get the idea.)

That'd buy you some time to come to a conclusion, while still making sup
a lot more useful for early adopters (like me :-).

/M
-- 
Magnus Therning                             (OpenPGP: 0xAB4DFBA4)
magnus?therning?org             Jabber: magnus?therning?gmail?com
http://therning.org/magnus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070912/91e2358f/attachment.bin 


  reply	other threads:[~2007-09-11 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1188557360-sup-7369@bryma>
2007-08-31 15:31 ` William Morgan
2007-08-31 17:12   ` Magnus Therning
2007-09-02 23:03     ` William Morgan
2007-09-05  7:48       ` Magnus Therning
2007-09-05 15:27         ` William Morgan
2007-09-06  7:02           ` Magnus Therning
2007-09-11 22:08             ` William Morgan
2007-09-11 23:04               ` Magnus Therning [this message]
2007-09-05 21:55         ` William Morgan
2007-09-06  6:50           ` Magnus Therning
2007-09-11 20:48             ` William Morgan
2007-09-03 12:33     ` [sup-talk] saving sent mail to places other than the default jeff covey

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=20070911230415.GB3448@die.therning.org \
    --to=magnus@therning.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox