www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7039) keys-fetch.py does not handle V3 key fingerprints
Date Mon, 03 Feb 2014 15:32:11 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889556#comment-13889556

Gavin commented on INFRA-7039:

I've had a look around, there are servers that support v3 - like sks and its pool, however
the percentage of users on v3 as opposed to v4 is like 4%. How about we just dont support
v3 and ask folks to migrate to v4+ ?

> keys-fetch.py does not handle V3 key fingerprints
> -------------------------------------------------
>                 Key: INFRA-7039
>                 URL: https://issues.apache.org/jira/browse/INFRA-7039
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: LDAP
>         Environment: https://svn.apache.org/repos/asf/infrastructure/site/trunk/people/keys-fetch.py
>            Reporter: Sebb
>            Priority: Minor
> If an LDAP key entry uses V3 fingerprint, the key fetch process does not work.
> This is because the server that is used - keys.gnupg.net - does not support v3 fingerprints.
> As a temporary work-round, I have added a command-line option to load keys by id; this
means finding the id which corresponds to the v3 fingerprint.
> It is not possible to derive the id directly from a v3 fingerprint, so this requires
a manual search, followed by manually adding the id.
> It would be useful if V3 fingerprints were directly supported.
> For example, maybe there is a GPG server that supports search by V3 fingerprint?
> Alternatively, perhaps the manual search could be automated?

This message was sent by Atlassian JIRA

View raw message