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. > I agree that using --list-packets is not acceptable, since GnuPG > upstream refuses to support it as an API. Right, this is a debug interface. Bypassing software layers is one of the major causes for hard to pinpoint bugs and a major maintenance hassle. --list-packets tells something about the underlying protocol which should not be exposed by the tool implementing that protocol. Shalom-Salam, Werner -- # Please read: Daniel Ellsberg - The Doomsday Machine # Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpuThlBibTlB.pgp
Description: PGP 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
