Re: Choose signing key

[Bruno Miguel <brunoalexandremiguel gmail com>]

Em 02-08-2008 17:13:26 Albrecht Dreß escreveu:
> Hi all:
> 
> Attached is a simple patch against svn rev. 7953 which lets you  
> explicitly specify a key id for an identity, instead of letting Balsa 
> 
> choose a key.  In the text entry, enter the 8-digit hex id of the key 
> 
> which shall be used.  If the entry is empty, Balsa will automagically 
> 
> choose the proper key for the identity (mail address), or display a  
> dialogue to choose one if more are available.  Any comments are of  
> course welcome!

Thanks. :) I' try to give feedback today.
 
> Am 02.08.08 16:00 schrieb(en) Bruno Miguel:
> > > be improved, though.  If you have any ideas, they would be
> welcome!
> > 
> > The ability to create signing filters, so a specific email address  
> > would be automatically signed with a specific key, also allowing 
> the
>  
> > sender to remove the signature if he wanted.
> 
> Well, I thought more about dealing with the GnuPG trust data, see  
> <http://www.dewinter.com/gnupg_howto/english/
> GPGMiniHowto-1.html#ss1.3>.
>   
> IMHO, the information you are referring to goes beyond the scope of  
> Balsa and would better be stored in an address book or a similar data 
> 
> base.  It could contain the following information for each person:
> * shall receive signed messages
>    - yes/no
>    - use key with ID xxx (optional)
> * shall receive encrypted messages
>    - yes/no
>    - use key with ID yyy (optional)
> * use protocol: RFC 2440/2633/3156
> * (maybe more could be usefu8l, like default language etc.)
> 
> However, dealing with this information is not so easy - what should  
> Balsa do if you send a message to multiple recipients with  
> contradictory statements?

Balsa as a simple address book, so that could be used, no? Or it could 
allow the creation of filters, just like the filters for emails, so 
users can specify which addresses are signed with which key.

When sending an email to multiple addresses with different keys, the 
user should be notified and prompted for an action:
 - not to sign the email;
 - sign with a key of his choice;
 - divide the sending in parts. for example, send the signed email to 
the addresses that are in one rule, then send the signed email to the 
addresses that are in other rule and then send, not signed, the 
addresses that aren't in any rule.