On 28.05.18 18:32, Werner Koch wrote:
> On Sun, 27 May 2018 20:12, d...@fifthhorseman.net said:
> 
>>> 1. creating the Autocrypt header: the key is specified to contain
>>> exactly one UID one public/signing key and one encryption key. There is
>>> no function in GnuPG to extract this from a key. Users that have many
>>> UIDs or many subkeys keys cannot use Autocrypt with GnuPG because the
>>> header gets too long. See https://sourceforge.net/p/enigmail/bugs/731/
>>
>> ok, so this might be typically solvable if we can get GnuPG to fix:
> 
> I have not looked at these bug reports but what Enigmail needs is
> already implemented in GnuPG and actively used.  The gpg-wks-client does
> basically the same; something like
> 
>   gpg --import-options=import-export         \
>   --import-filter keep-uid=uid=THEUSERID \
>   --import  <THEKEY >STRIPPEDKEY
>   
> I am not sure whether the export-minimal option keeps only the latest
> subkeys; this would be easy to add.  It might be that is one of the bug
> reports you mentioned.  In general gpg-wks-client and gpg-wks-server are
> worth to look for code snippets utilizing advanced features.

Thanks, I'll look into gpg-wks-*. gpg --import-options=import-export
seems to at least allow a part of what is needed.


-Patrick

Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to