-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 19.08.13 16:51, Max Maass wrote:
> On 08/19/2013 04:40 PM, Daniel Kahn Gillmor wrote:
>> On 08/18/2013 06:41 AM, Max Maass wrote:
>>> As I do not have enough experience with the Enigmail Source
>>> yet, I have no idea where even to begin to look for them. So I
>>> would be very grateful for an idea on what to do next. If we
>>> want to keep the ML out of this (I don't know if this is
>>> interesting or annoying for everyone else on [Enigmail]), we
>>> can take this to personal eMail as well, if you want.
> 
>> I can't speak for the rest of the mailing list, but i'm quite
>> happy to see this discussion on-list, and in the archives.  I
>> find it useful, even though i'm just lurking in this
>> conversation.
> 
>> Thanks for your work on extending enigmail to cover this use
>> case more smoothly.
> 
> Well, there wasn't much discussion off mailinglist so far, so
> Patrick may just be able to send his solution to the mailing list,
> if he finds it. I sent him a preliminary patch containing the bug
> (I'll just call it a bug for now, it might just be me being
> stupid), and he's taking a look at it.

[Please let's stick to bottom-posting]

I just come from finishing my analysis. The problem is that
otherRandomHeaders doesn't seem to work - it breaks something in the
TB function that opens the message composition window.

However, here is an alternative: instead of setting
otherRandomHeaders, you can set the field draftId. If you set it to
something starting with "enigmail:" you're certain that the mail will
be from some Enigmail functionality, as this is a special URL.

This way, you  even go a step further. Let's assume you set draftId to
this: "enigmail:send-encrypted-signed-key/0x12345678"

Then you can tell the message composition window to attach the key
0x12345678, and set the encryption flags directly during the opening
process of message composition. You don't even need to create the
attachment separately and attach it to the message before you open the
window.

You'll need to modify composeOpen() to check for
gMsgCompose.compFields.draftId and then act accordingly.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEVAwUBUhJDask25cDiHiw+AQilsgf+LHjEIeReeTg+PAOw2TRf2WXvQciwoP3d
zpFR3OJjzUEXVy4I+gnq+XwYPW6icY3ZXHiusDT2FxZmPFUDF1/Yoo0pKFfXxFpW
2U0hR3U5dKKoXh51WCvJHPaORsLqQHnHIiCPwsCMKD3bw/CCXz3tgwJF31ymUsYC
yGx4BH82UdrKdSXacurvTzlhb6v6b96lRpxqLKkSnHxYvb5Rrlt15F6TjMwkEqSX
ThlsHYECGk0dmMn5CFKGVqpQuOC6FdTjuOw7DdtSi3r2xuAnTBVuzQvly7eDXVtH
7bDsoXEScBS3/J52UHNXO1JDnyrHElx/xmPBXRFs6PuUFm+mubspcw==
=RkRr
-----END PGP SIGNATURE-----

_______________________________________________
enigmail-users mailing list
[email protected]
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to