New SSH key

New SSH key

[Marc Glisse]

Hello,

it seems that my DSA key is so old that the documented way to update it 
(ssh sourceware.org updatekey < ...) won't work. Could you help me switch 
to this shiny new key? My login is glisse. I don't know what's the best 
way to prove that I am me and not some rando trying to usurp my account: I 
still have access to the old DSA key, I can use the gcc bugzilla account 
associated with this account, I can answer email at the email address I am 
sending this from, which is likely what I recorded for the sourceware 
account.

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM2PIro7d4s40hr9cHU1PUT+9ZXlJLNnug21ZMtAM+R+ glisse@stedding

-- 
Marc Glisse

Re: New SSH key

[Christopher Faylor]

On Sat, Jun 20, 2020 at 07:39:50PM +0200, Marc Glisse wrote:
>Hello,
>
>it seems that my DSA key is so old that the documented way to update
>it (ssh sourceware.org updatekey < ...) won't work. Could you help me
>switch to this shiny new key? My login is glisse. I don't know what's
>the best way to prove that I am me and not some rando trying to usurp
>my account: I still have access to the old DSA key, I can use the gcc
>bugzilla account associated with this account, I can answer email at
>the email address I am sending this from, which is likely what I
>recorded for the sourceware account.
>
>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM2PIro7d4s40hr9cHU1PUT+9ZXlJLNnug21ZMtAM+R+ glisse@stedding

I've added that modern key to your authorized_keys file so you should be
all set.

cgf

Re: New SSH key

[Marc Glisse]

On Sat, 20 Jun 2020, Christopher Faylor wrote:

> On Sat, Jun 20, 2020 at 07:39:50PM +0200, Marc Glisse wrote:
>> Hello,
>>
>> it seems that my DSA key is so old that the documented way to update
>> it (ssh sourceware.org updatekey < ...) won't work. Could you help me
>> switch to this shiny new key? My login is glisse. I don't know what's
>> the best way to prove that I am me and not some rando trying to usurp
>> my account: I still have access to the old DSA key, I can use the gcc
>> bugzilla account associated with this account, I can answer email at
>> the email address I am sending this from, which is likely what I
>> recorded for the sourceware account.
>>
>> ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIM2PIro7d4s40hr9cHU1PUT+9ZXlJLNnug21ZMtAM+R+ glisse@stedding
>
> I've added that modern key to your authorized_keys file so you should be
> all set.

I can confirm it is working, thanks!

-- 
Marc Glisse

Re: New ssh key

[Frank Ch. Eigler]

Hi -

>   Apologies, but I must request installation of a new ssh key for my
> account.  Please see attached.

Replaced old / installed.

- FChE

New ssh key

[Anthony Green]

[-- Attachment #1: Type: text/plain, Size: 142 bytes --]

Hello Overseers,

  Apologies, but I must request installation of a new ssh key for my
account.  Please see attached.

Thanks!

Anthony Green

[-- Attachment #2: id_rsa_sourceware.pub --]
[-- Type: application/vnd.ms-publisher, Size: 750 bytes --]

new ssh key

[Thomas Koenig]

[-- Attachment #1: Type: text/plain, Size: 105 bytes --]

Hi,

please find attached my new ssh key.  I guess it is time
for me to update this...

Regards

	Thomas

[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 741 bytes --]

Re: new ssh key

[Frank Ch. Eigler]

Hi -

> Hi, please use the new ssh key attached for access to lvm.

Installed.

- FChE

new ssh key

[David Teigland]

[-- Attachment #1: Type: text/plain, Size: 72 bytes --]

Hi, please use the new ssh key attached for access to lvm.
Thanks,
Dave

[-- Attachment #2: id_rsa_teigland_sourceware.pub --]
[-- Type: text/plain, Size: 410 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDF05tHsB4ZfzruH9vds5CHSt7dJSwnOCZSB+SW2ElIKriRy/8vI2ouMcoPSP+MP1M8tYpzPeJfoCsItDfKPu4loO2bAKopSxVhk9wC/utzk7zmingW0TRGrbmGkjT6Uev2Pp8c9rye7TGK/7Q/gvWaJEkr2GAqAes6+yXLi7IBd+gq600yUWMqSWz+BHYuZOI38ak/+qd9LllJEL/4RPZFnvi+iuNlFmrfku9x0uejG3vOlPP7bNHczi/kDOyQ6YowFgz2vsXimqMwCSyZsuU6Q8SO4NaNpvhsr4xqf0LaufMjRn0edp9L0kSDqBeYKkrI8owDox6Q1S2rjwdxpCld teigland@null.msp.redhat.com

Re: New SSH key.

[Ian Lance Taylor]

Simon Dardis <Simon.Dardis@imgtec.com> writes:

> Sorry, I should have been more specific, I've lost the passphrase for
> the old key.

OK, I updated the key.

Ian

RE: New SSH key.

[Simon Dardis]

Sorry, I should have been more specific,  I've lost the passphrase for the old key.

Thanks,
Simon

> -----Original Message-----
> From: Ian Lance Taylor [mailto:ian@airs.com]
> Sent: 04 February 2016 16:58
> To: Simon Dardis
> Cc: overseers@gcc.gnu.org
> Subject: Re: New SSH key.
> 
> Simon Dardis <Simon.Dardis@imgtec.com> writes:
> 
> > Could my current SSH key be replaced with the attached one?
> 
> You should be able to do it yourself using
>     ssh dardiss@gcc.gnu.org replacekey < NEWKEY
> 
> Let us know if that doesn't work.
> 
> Ian

Re: New SSH key.

[Ian Lance Taylor]

Simon Dardis <Simon.Dardis@imgtec.com> writes:

> Could my current SSH key be replaced with the attached one?

You should be able to do it yourself using
    ssh dardiss@gcc.gnu.org replacekey < NEWKEY

Let us know if that doesn't work.

Ian

New SSH key.

[Simon Dardis]

[-- Attachment #1: Type: text/plain, Size: 89 bytes --]

Hello,

Could my current SSH key be replaced with the attached one?

Thanks,
Simon

[-- Attachment #2: sshkeydardiss.pub --]
[-- Type: application/x-mspublisher, Size: 392 bytes --]

Re: new SSH key

[Ian Lance Taylor]

Ben Elliston <bje@air.net.au> writes:

> Can I supply an ED25519 key to replace my weak DSA key?  This message
> is signed by me.

I installed it but I don't know whether it will work.

Ian

new SSH key

[Ben Elliston]

[-- Attachment #1: Type: text/plain, Size: 198 bytes --]

Hi.

Can I supply an ED25519 key to replace my weak DSA key?  This message
is signed by me.

Thanks,
Ben

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAII6rZyDb77csy1yHT1ybrgmPJbfuKbxhewWYHHOlrCQC bje@bapbop

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

Re: new ssh key

[Ian Lance Taylor]

Richard Henderson <rth@redhat.com> writes:

> Ho hum.  Apparently I've waited too long, since I can't use
> the replacekey mechanism now that the v1 keys are off.

Added.

Ian

new ssh key

[Richard Henderson]

[-- Attachment #1: Type: text/plain, Size: 129 bytes --]

Ho hum.  Apparently I've waited too long, since I can't use
the replacekey mechanism now that the v1 keys are off.

Thanks,


r~

[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 404 bytes --]

Re: new ssh key

[Ralf Wildenhues]

* Christopher Faylor wrote on Mon, Jun 02, 2008 at 09:40:34PM CEST:
> 
> Hmm.  If you didn't know that you could interactively login that would imply
> that you probably don't need login privileges.

Yes, I haven't needed them so far.

> Maybe you slipped through the cracks when we tightened this up.

Can't help you there.

> Unless I hear otherwise from you I'll be changing your privileges to source
> control access only.  Once that happens then the "replacekey" and "appendkey"
> commands will work.

OK.  I suppose if I ever need login privileges, you will hear from me
again.

Cheers, and thanks,
Ralf

Re: new ssh key

[Christopher Faylor]

On Mon, Jun 02, 2008 at 09:19:18PM +0200, Ralf Wildenhues wrote:
>Hello Christopher,
>
>* Christopher Faylor wrote on Mon, Jun 02, 2008 at 08:17:08PM CEST:
>> On Mon, Jun 02, 2008 at 07:57:06PM +0200, Ralf Wildenhues wrote:
>> >Hello overseers,
>> >
>> >please drop my old SSH key in the digital waste bin, and install the
>> >attached one instead, for access to sources.redhat.com.
>> 
>> Can you use the 'replacekey' functionalty of your account?
>> 
>> ssh sourceware.org 'replacekey' < newkey.pub
>
>That did not work:
>$ ssh rwild@sourceware.org replacekey < id_rsa.pub
>bash: replacekey: command not found
>
>However, I did not know until now that I can just interactively log in
>to sourceware.org and replace the key in .ssh/authorized_keys myself.
>I've done that now, and things seem to work fine.

Hmm.  If you didn't know that you could interactively login that would imply
that you probably don't need login privileges.  Maybe you slipped through the
cracks when we tightened this up.

Unless I hear otherwise from you I'll be changing your privileges to source
control access only.  Once that happens then the "replacekey" and "appendkey"
commands will work.

cgf

Re: new ssh key

[Ralf Wildenhues]

Hello Christopher,

* Christopher Faylor wrote on Mon, Jun 02, 2008 at 08:17:08PM CEST:
> On Mon, Jun 02, 2008 at 07:57:06PM +0200, Ralf Wildenhues wrote:
> >Hello overseers,
> >
> >please drop my old SSH key in the digital waste bin, and install the
> >attached one instead, for access to sources.redhat.com.
> 
> Can you use the 'replacekey' functionalty of your account?
> 
> ssh sourceware.org 'replacekey' < newkey.pub

That did not work:
$ ssh rwild@sourceware.org replacekey < id_rsa.pub
bash: replacekey: command not found

However, I did not know until now that I can just interactively log in
to sourceware.org and replace the key in .ssh/authorized_keys myself.
I've done that now, and things seem to work fine.

Thanks!
Ralf

Re: new ssh key

[Christopher Faylor]

On Mon, Jun 02, 2008 at 07:57:06PM +0200, Ralf Wildenhues wrote:
>Hello overseers,
>
>please drop my old SSH key in the digital waste bin, and install the
>attached one instead, for access to sources.redhat.com.

Can you use the 'replacekey' functionalty of your account?

ssh sourceware.org 'replacekey' < newkey.pub

cgf

new ssh key

[Ralf Wildenhues]

[-- Attachment #1.1: Type: text/plain, Size: 186 bytes --]

Hello overseers,

please drop my old SSH key in the digital waste bin, and install the
attached one instead, for access to sources.redhat.com.

Thank you for your efforts.

Cheers,
Ralf

[-- Attachment #1.2: id_rsa.pub --]
[-- Type: text/plain, Size: 381 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA1kq6X3+MHCnUGvq+ZIiC9ABON7Gc3VoXdxIYR76CoNPZBz+RDtlujv+Tym60MOmjCXodtyh3mZ6iQMtHNYLTJc/8MUwae/iPN9pOLqs8Ecel0NxgT9C0AmGBP3iSuUkte+eSYEliMQ2yyxXDWVeH6oKPRpJ6SnLABgZJnGpv7qGha0DBjvlOk2QM7nmpyvfs0n6TQXYceGkImBbj4kJcnwEpWRV+pZh1iW82autWaMIUMs1lXWqkWHFExQucMMnAfktH1QClGwMqfv1g3IPhqhuGkkRvpbQKZnl+r1wMN7+fUizT+eyzNz/65nUgvajTBp/sFZDhrbDWyBmwzpyd1w==

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: new ssh key

[Jonathan Larmour]

Thiago Jung Bauermann wrote:
> Could you please change my SSH key to the one attached? My username is
> bauermann.

Done.

Jifl
-- 
------["The best things in life aren't things."]------      Opinions==mine

new ssh key

[Thiago Jung Bauermann]

[-- Attachment #1: Type: text/plain, Size: 164 bytes --]

Hi,

Could you please change my SSH key to the one attached? My username is
bauermann.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

[-- Attachment #2: id_rsa.pub --]
[-- Type: text/plain, Size: 398 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA0a3S6ZWJCtxdTzTl1d76IQQZqpSjDAH1q9Ww5ejzCFiT/WWaZxqaMxSrq4nJGC+cj+4wWtYELxFhbTo2XG4+zwBcljlJhHSiQpuLmhoRQt0/iNF5rQi9HtgwTIEEXHwwsK3NMa/4WcjxWxxQB4PxMFR+y2ZQw3WgNW+iry4yUSawfbglYDopLoxlLv8mVCReaqG9/azhK4gZyS/CXLzxXSvVuLTT+fC1w7Y6r2NSOfVzOKgTk5525qkzdrEZxR5VsHNTNEDhZ7gKdn7KV0mIkr3eRlWe5/ZzzhPEDc7qlseLih+z04Mf5BQa4S+E0SZd51EPrvdp03bgCBARjiythw== bauermann@hactar

new ssh key

[Jonathan Brassow]

I recently changed my ssh keys...  I need to get my s.r.c accounts
updated.

Am I talking to the right people?  (I am on the LVM2, cluster, and
device-mapper commit lists.)
 brassow

Old key:
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAxNPY5LFppORk1Lr3iEDpSaYSHKgr09tstPJ0XF0lSp4Fsg0KiDfSwYvMLRp4fy8Zd9XqJXCd62ebnWHVCGBnRFbBri+aSwCodo0ugOhmZKdNGRWk16jlTjHLEGZTmJ7hClnswVWzfmprZscmdw8fQhT2qqKyBIOdqo7D6qlujss= jbrassow@hydrogen
New key:
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAvbRCRLAEgWy9GEirjTALb/is6ENhpgPIHlPYT1PYpqWOCUv1KkdgacxJAfFzsGv6fAGuMRpS+ScYznHbTxmvJ9aGEHLLB88IWVyj3uJUA9dGgAqXcZLX5CXzkFk6rWdg0MvKPauahX1TYs/Uzz2XiaTVn4Scem6Nnc6Rb6VdX00bjIa99dFNJhMTFnZiryj9gpcMqvcXkTTKqZmVJ+TBC9TdGTbP+abHlLprw0Ar2/AQ53Dts9fjt/V6+CPM+2TxoQzWK4cWU6AoMXFDk927QV1lebMd7gppHWvBMP3cwSzq2jMdJI30FKsSvSC1/uRVJzVDOa2WIYGKDOCVuQYVMw== jbrassow@hydrogen.msp.redhat.com

Re: New SSH key

[Frank Ch. Eigler]

Hi -

dgilbert wrote:

> [...]  Can I have my account updated with the new key (attached) please? 

Authenticated and done.

- FChE

New SSH key

[David Gilbert]

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

Last month I was set up with an account (dgilbert@sources.redhat.com) so
that I have write access to the CVS repository for Mauve.  Today when I
tried to use it for the first time I found that I've forgotten the
passphrase for my SSH key, so I've generated a new one.  Can I have my
account updated with the new key (attached) please? 

Regards,

Dave Gilbert

[-- Attachment #2: id_rsa.pub --]
[-- Type: text/plain, Size: 226 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA0iOZRdwoTvXjQylgCmf3+/dF2PERy4zNsausZdVTB2MnV4rr8UWzI6ptAXA2VzJpD2p9GcrIkr3NfbyQlK6A49vO1ZKtzcF5AyuOz9mq1e3TOorz5jh2pEDXK+VQKmXnFY6UbO9xACcsdEZyD/R7USArGBIudsTmgweOGGCZ9w0= dgilbert@linux42

New SSH key

[Jesper Skov]

Hi

Could I ask you to install this new SSH key for me?

Thanks,
Jesper

1024 37 135115216232492796012403222218578240045656780016789775184778371998685143688696140280621179898537960065880632768220717125998517890948695942512900272203363199274364695114603540630875077253613641955149492082480857718896696589435219888878052044477894854745615925178394794564405467252773768802599293597855713781111 jskov@thinktwice.zoftcorp.dk

Re: New SSH key

[Jeffrey A Law]

  In message < 200006160942.LAA28711@thinktwice.zoftcorp.dk >you write:
  > Hi
  > 
  > Could I ask you to install this new SSH key for me?
Done.  You might want to remove the old keys from ~/.ssh/authorized_keys

jeff

Re: New SSH key

[Jeffrey A Law]

  In message < 200006160942.LAA28711@thinktwice.zoftcorp.dk >you write:
  > Hi
  > 
  > Could I ask you to install this new SSH key for me?
Done.  You might want to remove the old keys from ~/.ssh/authorized_keys

jeff

New SSH key

[Jesper Skov]

Hi

Could I ask you to install this new SSH key for me?

Thanks,
Jesper

1024 37 135115216232492796012403222218578240045656780016789775184778371998685143688696140280621179898537960065880632768220717125998517890948695942512900272203363199274364695114603540630875077253613641955149492082480857718896696589435219888878052044477894854745615925178394794564405467252773768802599293597855713781111 jskov@thinktwice.zoftcorp.dk