On 10.07.2015 12:26, Daniel Kahn Gillmor wrote:
> On Thu 2015-07-09 18:13:26 -0400, Patrick Brunschwig wrote:
>> On 09.07.2015 06:35, daniel Azuelos wrote:
> 
>>>   Is it possible within Enigmail when including one's public key
>>> to have the usual feedback that this attachment is done?
>>> What I would like to achieve is to "see" within the attachments
>>> window my public key.
>>> Is this possible?
>>
>> It's way too complicated when it comes to saving drafts and continuing
>> to work on saved drafts, as Thunderbird does not provide enough
>> flexibility to identify attachments. I.e. it would not be possible to
>> determine if the key already attached before the draft was saved.
> 
> I agree with daniel Azuelos that using the normal attachments workflow
> will be more intuitive to users, if we can make it happen sanely.
> 
> What if clicking the button actually generated a file (in an
> engimail-specific location in the profile directory maybe?), and
> attached the file to the draft at the moment it was clicked?
> 
> Then the button wouldn't be a toggle button, but just a "take this
> action" button.  With a well-named filename, the state of the attachment
> would be the same as the state of any other attachment.

It's the same behavior as for Thunderbird's "Attach Personal Card
(vCard)" function. I really don't see why we should try to be smarter
than they are.

> I think enigmail wouldn't be responsible for it after that (e.g. if
> saving a draft with an attachment fails to save the attachment, that's a
> bug in thunderbird, not in enigmail).
> 
> weird corner cases and questions this approach raises:
> 
>  0) how to destroy the file after the message is sent?
> 
>     maybe we don't have to do that?  if my OpenPGP cert was always
>     exported to
>     
> ~/.thunderbird/abc1234a.default/enigmail/0x0EE5BE979282D80B9F7540F1CCD2ED94D21739E9.key
>     then perhaps it's not necessary to delete the file afterward?
>     Enigmail can always update the file as the certificate changes.

Thunderbird takes care of this.


>  1) what happens if the key changes while two drafts are open?
> 
>     does this matter?  if they're both pointing at the same file, then
>     they both get the most recent update.  someone who expects to send
>     one variant of the certificate to one person and another variant to
>     another while both drafts are open might be a special case we just
>     don't cater to.
> 
>  2) If someone wants to attach their key to every e-mail, that workflow
>     becomes different.
> 
>     not sure how to make that work.  any ideas?

3) What if a user has more than one keys for his various identities?
Should we then delete the attachment upon changing the identity and add
a new one with the key of the now selected identity? And how should we
behave if the message was opened from a draft when this happened etc. etc.

When I originally implemented this feature, it was implemented it to
work as you described. But given all the corner cases that came up and
were not fixable, I decided to step back a little.

-Patrick

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to