On Fri, Dec 15, 2023 at 06:06:26AM +, John Kehayias wrote:
> I suppose I should have been more specific than "something bad" :) I
> merely meant this wasn't an actual security issue of losing control of
> a private key, but merely moving to a new one for other reasons.
The old key "expired" la
On Thu, Dec 14, 2023 at 11:16 AM, Leo Famulari wrote:
> On Wed, Dec 13, 2023, at 22:17, John Kehayias wrote:
>> And I assume all this was just to use a new key (did I see some
>> mention of subkeys on #guix? that's what I use) and not because of
>> something bad happening to the old one right?
>
>
On Wed, Dec 13, 2023, at 22:17, John Kehayias wrote:
> And I assume all this was just to use a new key (did I see some
> mention of subkeys on #guix? that's what I use) and not because of
> something bad happening to the old one right?
I don't know if anything bad happened to the old key. That's f
On Wed, Dec 13, 2023 at 09:10 PM, Leo Famulari wrote:
> On Tue, Dec 12, 2023 at 12:02:33PM -0500, Maxim Cournoyer wrote:
>> Note that I believe you can simply update to your new key yourself.
>> You'll want to add your new key to the keyring branch, then adjust the
>> .guix-authorizations file wit
On Tue, Dec 12, 2023 at 12:02:33PM -0500, Maxim Cournoyer wrote:
> Note that I believe you can simply update to your new key yourself.
> You'll want to add your new key to the keyring branch, then adjust the
> .guix-authorizations file with its new keygrip.
Thanks, I pushed to 'keyring' as
935e3c9
Hi,
Maxim Cournoyer writes:
> Hi,
>
> Leo Famulari writes:
>
>> Hello,
>>
>> I'm changing my Guix signing key from
>> B0515948F1E7D3C1B98038A02646FA30BACA7F08 to
>> 68407224D3A64EE53EAC6AAC1963757F47FF.
>>
>> Patches to follow. Testing is appreciated!
>
> Thanks for the heads-up!
Note that
Hi,
Leo Famulari writes:
> Hello,
>
> I'm changing my Guix signing key from
> B0515948F1E7D3C1B98038A02646FA30BACA7F08 to
> 68407224D3A64EE53EAC6AAC1963757F47FF.
>
> Patches to follow. Testing is appreciated!
Thanks for the heads-up!
--
Thanks,
Maxim
Hello,
I'm changing my Guix signing key from
B0515948F1E7D3C1B98038A02646FA30BACA7F08 to
68407224D3A64EE53EAC6AAC1963757F47FF.
Patches to follow. Testing is appreciated!
Leo
signature.asc
Description: PGP signature
Hi Tobias,
On Tue, 29 Jun 2021 at 16:40, Tobias Geerinckx-Rice wrote:
> Question: I think committers should be trusted with discretion in
> how they prefer to manage their keys, but how about briefly
> documenting a suggested sane key-management strategy to new
> committers, like we already de
Hello,
Tobias Geerinckx-Rice skribis:
> Question: I think committers should be trusted with discretion in how
> they prefer to manage their keys, but how about briefly documenting a
> suggested sane key-management strategy to new committers, like we
> already describe some rando's editor set-up?
Hi Tobias,
On Tue, 2021-06-29 at 16:40 +0200, Tobias Geerinckx-Rice wrote:
> Question: I think committers should be trusted with discretion in
> how they prefer to manage their keys, but how about briefly
> documenting a suggested sane key-management strategy to new
> committers, like we alread
Question: I think committers should be trusted with discretion in
how they prefer to manage their keys, but how about briefly
documenting a suggested sane key-management strategy to new
committers, like we already describe some rando's editor set-up?
:-)
I don't think most people *insist* on
Hi,
Eric Bavier skribis:
> On Wed, 2021-06-23 at 15:48 +0200, Ludovic Courtès wrote:
[...]
>> In
>> d1d2bf3eb6ba74b058969756a97a30aec7e0c4d1 I added your new key and
>> renamed the old one, but perhaps we can just remove the old one, if the
>> old sub-key is still in the new one?
>
> I think
On Wed, 2021-06-23 at 15:48 +0200, Ludovic Courtès wrote:
> Hi,
>
> Apologies for the delay!
>
> Eric Bavier skribis:
>
> > I've updated my GPG key on Savannah with a new signing subkey and uid.
>
> Done in 3694c0d4fee0f7faf130ecd9386ea45932a19543.
Thank you Thank you!
> In
> d1d2bf3eb6ba7
Hi,
Apologies for the delay!
Eric Bavier skribis:
> I've updated my GPG key on Savannah with a new signing subkey and uid.
Done in 3694c0d4fee0f7faf130ecd9386ea45932a19543. In
d1d2bf3eb6ba74b058969756a97a30aec7e0c4d1 I added your new key and
renamed the old one, but perhaps we can just remove
On Tue, 2021-06-15 at 03:05 +, Eric Bavier wrote:
> Hello Guix,
>
> I've updated my GPG key on Savannah with a new signing subkey and uid.
> Could a maintainer do the necessary repo updates?
Ping?
>
> Thanks,
> `~Eric
signature.asc
Description: This is a digitally signed message part
Hello Guix,
I've updated my GPG key on Savannah with a new signing subkey and uid.
Could a maintainer do the necessary repo updates?
Thanks,
`~Eric
signature.asc
Description: This is a digitally signed message part
Guix,
Brett Gilio 写道：
As per my email a few days ago, I have lost control of my
signing key. I
have, as per instructions, refreshed the key on Savannah and am
signing
this email.
I've authorised Brett in commit
ba1d9680d61d3b06d9b81a81863448f494d654a7.
Kind regards,
T G-R
signature.asc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey all,
As per my email a few days ago, I have lost control of my signing key. I
have, as per instructions, refreshed the key on Savannah and am signing
this email.
I have familiarized myself with the changes to the contribution process,
and am lo
Roel,
Roel Janssen 写道：
I am trying to find the revocation key (printed) to revoke the
old key
as reassurance that I am still me, and no malice is going on.
As I
moved twice since printing and securely storing the revocation
key,
this will take some time.
Thanks for taking the time to do tha
Hello Ludo’ and Guix,
I lost the password of the old key. I updated my OpenPGP key on
Savannah to the new one (F556FD94FB8F8B8779E36832CBD0CD5138C19AFC).
I am trying to find the revocation key (printed) to revoke the old key
as reassurance that I am still me, and no malice is going on. As I
mov
Hello Roel,
You signed commit cc51c03ff867d4633505354819c6d88af88bf919 and its
parent with OpenPGP key F556FD94FB8F8B8779E36832CBD0CD5138C19AFC, which
differs from the one registered in ‘build-aux/git-authenticate.scm’
(17CB 2812 EB63 3DFF 2C7F 0452 C3EC 1DCA 8430 72E1) that you used
previously.
On Wed, Dec 05, 2018 at 03:49:42AM +0300, Oleg Pykhalov wrote:
> Hello Guix,
>
> Recently I've changed my signing subkey, here is it:
>
> 7238 7123 8EAC EB63 4548 5857 167F 8EA5 001A FA9C
Thanks for letting us know. Please remember to update the key on your
Savannah user page:
https://savannah
Hello Guix,
Recently I've changed my signing subkey, here is it:
7238 7123 8EAC EB63 4548 5857 167F 8EA5 001A FA9C
Oleg.
signature.asc
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
Just to clarify that I lost the key I've been using to sign commits the
past year and didn't have a backup:
pub rsa4096 2017-06-09 [SC]
DB34 CB51 D25C 9408 156F CDD6 A12F 8797 8D70 1B99
uid [ full ] Jan Nieuwenh
25 matches
Mail list logo
