* Ansgar Burchardt <[email protected]> [111119 20:30]:
> in the uploaders file, giving a key-id "[...]+" is supposed to also
> accept .changes files signed by a subkey, however this does not seem to
> work: having
>
> allow * by key 80E976F14A508A48E9CA3FE9BC372252CA1CF964+
>
> there will not accept files signed by my singing subkey:
Until monday I miss the resources to look into this, but I guess
the keyid must be something libgpgme supports, which AFAIR means
something like it being at most the last 16 hexdigits of the fingerprint.
(or whatever gpg --with-colo --list-key reports)
Could you test if
allow * by key BC372252CA1CF964+
works correctly?
Perhaps I should look if there is a possibility to detect cases like
that and print a warning... (Though that might be hard with the level
of indirection involved here).
Bernhard R. Link
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
