You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Semb Wever (Jira)" <ji...@apache.org> on 2020/01/30 09:43:00 UTC
[jira] [Updated] (CASSANDRA-15534) add mick's second (RSA) gpg key
to the project's KEYS file
[ https://issues.apache.org/jira/browse/CASSANDRA-15534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-15534:
-------------------------------------------
Change Category: Quality Assurance
Complexity: Low Hanging Fruit
Component/s: Build
Status: Open (was: Triage Needed)
> add mick's second (RSA) gpg key to the project's KEYS file
> ----------------------------------------------------------
>
> Key: CASSANDRA-15534
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15534
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Michael Semb Wever
> Priority: Normal
>
> Following on from CASSANDRA-15360...
> The signing RPMs with `rpmsign` during the release process requires a RSA key. So my existing DSA key from 15360 does not work with `rpmsign`
> The patch adds my gpg public key to the project's KEYS file found at https://dist.apache.org/repos/dist/release/cassandra/KEYS
> My gpg public key here has the fingerprint
> A4C4 65FE A0C5 5256 1A39 2A61 E913 35D7 7E3E 87CB
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org