You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2015/05/10 10:16:59 UTC
[jira] [Updated] (SQOOP-2354) Please add my new key to project KEYS
file
[ https://issues.apache.org/jira/browse/SQOOP-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira updated SQOOP-2354:
--------------------------------
Description:
I lost the password for my gpg key. No security breach, but a bit embarrassing.
I generated a new key and I'll use it to sign the Maven artifacts for 1.4.6. Can you add my pubkey (attached) to KEYS so my signature be validated against the new key?
Don't remove the old one, it was used to sign Sqoop 1.4.5 release and is still secure AFAIK.
was:
I lost the password for my gpg key. No security breach, but a bit embarrassing.
I generated a new key and I'll use it to sign the Maven artifacts for 1.4.6. Can you add my pubkey (attached) to KEYS so my signature be validated against the new key?
Don't remove the old one, it was used the sign 1.4.5 release and is still secure AFAIK.
> Please add my new key to project KEYS file
> ------------------------------------------
>
> Key: SQOOP-2354
> URL: https://issues.apache.org/jira/browse/SQOOP-2354
> Project: Sqoop
> Issue Type: Task
> Reporter: Gwen Shapira
> Attachments: SQOOP-2354.patch
>
>
> I lost the password for my gpg key. No security breach, but a bit embarrassing.
> I generated a new key and I'll use it to sign the Maven artifacts for 1.4.6. Can you add my pubkey (attached) to KEYS so my signature be validated against the new key?
> Don't remove the old one, it was used to sign Sqoop 1.4.5 release and is still secure AFAIK.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)