SSH key

SSH key

[David Miller]

Hello, this is for account 'davem' on sourceware.org

It looks like I only had a version 1 key on there.  Could you please
add the following version 2 key?  I would have updated it myself if
the site would allow me to :-)

Thanks!

ssh-dss AAAAB3NzaC1kc3MAAAEBALZvzYe6K74C6TV56Hgd/Zm/YxE1/LV9nSEws6DI102IwNceTNqTKx3Z0NZJnv838u0VuG3mwOcp96gPojOLfCrxFdNEtaL+O0S39fPQkz16BHt0kKK+5oMroOt3eeW6i9YN+NAekVAxumRxjBNuZX4RrfLmNkpSaSKTw+SgSRq3rYPtfwRFC95n6cgwOlQE9vN1L2pjPzBa/m0vMvJHPt7DfkAGYqBMdUBhH/DSFOqUbNa9fhRSMr5E90jh6hQAU4Gt9iPQvVIT9jyBLXObLT6WwcyBcRStmSTVmmz+D2+4hLOlvfYlSTco1gR3TKWXkc/Mzh0fXDhcq+9XxABjbN0AAAAVALGNvTrp0YwxKNphtIiyWD1k8CePAAABADVNa0SXlowigmu3uWQeMJnk2s1FktefN+9LSXWlRinNsnltYFPHpz8BauBxCLDpSHLEOSxOCl75h4Gl9EW+yu1Y5KqY8AenArt64dl3q8z3DdWdSBngIsbRveWCIn5Ahw3IemklF7wrJOy+WEJZVWn/1MwOVqKVxUNAIGUazvtbgwMZPAANBkM6y1Nb7zZG21XsiSoWAd0oVDdZE5jkAd+kbMloiuUpr+ZkELxX8EG8G6jlWhgbGi5dfmSXHoaKR6NIOsUXT2aCdjot5TzO3r/pD4EHDWAlRZhxVFcGNaFulnPF4m5uffQh0aIfco6vpX5GGG8/oK6PFxxuEEXBir0AAAEBAJsfVpRTYejtaCf2xEpWByHNbx7jIu2JsTzegTQY7h3jWTXTYOQxovYryCi7xPbrlVx58XsfkBJKr+eO20x7hprdRydK37qhOto/qNdjwjTAUVXq0vNdro0npKYx8q690xgMeTe2NBHDcvNulVbwZKCsyrZOisVyzl/LfaQ76hs3d6dpf6ms3s1QQWUh5tM4xB20O9cBlHarZDKdgJFKPQ4NCSYR+gzYAolehkihLaVFLXcL0vlV9R6PuJVkilzdp3eS2riKbVkoE3zpQA/Ya3QkueBNp4pqHkeGvgcQOp57VE4KvnU/N4kOv1NDfD6aARsnRYTVpeBtiPzOl58rhks= davem@sunset

Re: SSH key

[Ian Lance Taylor]

David Miller <davem@davemloft.net> writes:

> Hello, this is for account 'davem' on sourceware.org
>
> It looks like I only had a version 1 key on there.  Could you please
> add the following version 2 key?  I would have updated it myself if
> the site would allow me to :-)
>
> Thanks!
>
> ssh-dss
> AAAAB3NzaC1kc3MAAAEBALZvzYe6K74C6TV56Hgd/Zm/YxE1/LV9nSEws6DI102IwNceTNqTKx3Z0NZJnv838u0VuG3mwOcp96gPojOLfCrxFdNEtaL+O0S39fPQkz16BHt0kKK+5oMroOt3eeW6i9YN+NAekVAxumRxjBNuZX4RrfLmNkpSaSKTw+SgSRq3rYPtfwRFC95n6cgwOlQE9vN1L2pjPzBa/m0vMvJHPt7DfkAGYqBMdUBhH/DSFOqUbNa9fhRSMr5E90jh6hQAU4Gt9iPQvVIT9jyBLXObLT6WwcyBcRStmSTVmmz+D2+4hLOlvfYlSTco1gR3TKWXkc/Mzh0fXDhcq+9XxABjbN0AAAAVALGNvTrp0YwxKNphtIiyWD1k8CePAAABADVNa0SXlowigmu3uWQeMJnk2s1FktefN+9LSXWlRinNsnltYFPHpz8BauBxCLDpSHLEOSxOCl75h4Gl9EW+yu1Y5KqY8AenArt64dl3q8z3DdWdSBngIsbRveWCIn5Ahw3IemklF7wrJOy+WEJZVWn/1MwOVqKVxUNAIGUazvtbgwMZPAANBkM6y1Nb7zZG21XsiSoWAd0oVDdZE5jkAd+kbMloiuUpr+ZkELxX8EG8G6jlWhgbGi5dfmSXHoaKR6NIOsUXT2aCdjot5TzO3r/pD4EHDWAlRZhxVFcGNaFulnPF4m5uffQh0aIfco6vpX5GGG8/oK6PFxxuEEXBir0AAAEBAJsfVpRTYejtaCf2xEpWByHNbx7jIu2JsTzegTQY7h3jWTXTYOQxovYryCi7xPbrlVx58XsfkBJKr+eO20x7hprdRydK37qhOto/qNdjwjTAUVXq0vNdro0npKYx8q690xgMeTe2NBHDcvNulVbwZKCsyrZOisVyzl/LfaQ76hs3d6dpf6ms3s1QQWUh5tM4xB20O9cBlHarZDKdgJFKPQ4NCSYR+gzYAolehkihLaVFLXcL0vlV9R6PuJVkilzdp3eS2riKbVkoE3zpQA/Ya3QkueBNp4pqHkeGvgcQOp57VE4KvnU/N4kOv1NDfD6aARsnRYTVpeBtiPzOl58rhks=
> davem@sunset

As far as I can tell that's the SSH key that's already installed on
sourceware for the davem account.  It's been there since November, 2015.

Ian

Re: SSH key

[Frank Ch. Eigler]

Hi -

> It looks like I only had a version 1 key on there.  Could you please
> add the following version 2 key?  I would have updated it myself if
> the site would allow me to :-)

I am under the impression that a high-bitcount rsa key is more
future-proof than any dsa one.

- FChE

Re: SSH key

[David Miller]

From: Ian Lance Taylor <ian@airs.com>
Date: Tue, 16 Oct 2018 15:41:49 -0700

> David Miller <davem@davemloft.net> writes:
> 
>> Hello, this is for account 'davem' on sourceware.org
>>
>> It looks like I only had a version 1 key on there.  Could you please
>> add the following version 2 key?  I would have updated it myself if
>> the site would allow me to :-)
>>
>> Thanks!
>>
>> ssh-dss
>> AAAAB3NzaC1kc3MAAAEBALZvzYe6K74C6TV56Hgd/Zm/YxE1/LV9nSEws6DI102IwNceTNqTKx3Z0NZJnv838u0VuG3mwOcp96gPojOLfCrxFdNEtaL+O0S39fPQkz16BHt0kKK+5oMroOt3eeW6i9YN+NAekVAxumRxjBNuZX4RrfLmNkpSaSKTw+SgSRq3rYPtfwRFC95n6cgwOlQE9vN1L2pjPzBa/m0vMvJHPt7DfkAGYqBMdUBhH/DSFOqUbNa9fhRSMr5E90jh6hQAU4Gt9iPQvVIT9jyBLXObLT6WwcyBcRStmSTVmmz+D2+4hLOlvfYlSTco1gR3TKWXkc/Mzh0fXDhcq+9XxABjbN0AAAAVALGNvTrp0YwxKNphtIiyWD1k8CePAAABADVNa0SXlowigmu3uWQeMJnk2s1FktefN+9LSXWlRinNsnltYFPHpz8BauBxCLDpSHLEOSxOCl75h4Gl9EW+yu1Y5KqY8AenArt64dl3q8z3DdWdSBngIsbRveWCIn5Ahw3IemklF7wrJOy+WEJZVWn/1MwOVqKVxUNAIGUazvtbgwMZPAANBkM6y1Nb7zZG21XsiSoWAd0oVDdZE5jkAd+kbMloiuUpr+ZkELxX8EG8G6jlWhgbGi5dfmSXHoaKR6NIOsUXT2aCdjot5TzO3r/pD4EHDWAlRZhxVFcGNaFulnPF4m5uffQh0aIfco6vpX5GGG8/oK6PFxxuEEXBir0AAAEBAJsfVpRTYejtaCf2xEpWByHNbx7jIu2JsTzegTQY7h3jWTXTYOQxovYryCi7xPbrlVx58XsfkBJKr+eO20x7hprdRydK37qhOto/qNdjwjTAUVXq0vNdro0npKYx8q690xgMeTe2NBHDcvNulVbwZKCsyrZOisVyzl/LfaQ76hs3d6dpf6ms3s1QQWUh5tM4xB20O9cBlHarZDKdgJFKPQ4NCSYR+gzYAolehkihLaVFLXcL0vlV9R6PuJVkilzdp3eS2riKbVkoE3zpQA/Ya3QkueBNp4pqHkeGvgcQOp57VE4KvnU/N4kOv1NDfD6aARsnRYTVpeBtiPzOl58rhks=
>> davem@sunset
> 
> As far as I can tell that's the SSH key that's already installed on
> sourceware for the davem account.  It's been there since November, 2015.

Hmmm:

[davem@apc-ap8641-3a-d11c GLIBC]$ git clone davem@sourceware.org:/git/glibc.git
Cloning into 'glibc'...
davem@sourceware.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
[davem@apc-ap8641-3a-d11c GLIBC]$ head ~/.ssh/id_dsa.pub 
ssh-dss AAAAB3NzaC1kc3MAAAEBALZvzYe6K74C6TV56Hgd/Zm/YxE1/LV9nSEws6DI102IwNceTNqTKx3Z0NZJnv838u0VuG3mwOcp96gPojOLfCrxFdNEtaL+O0S39fPQkz16BHt0kKK+5oMroOt3eeW6i9YN+NAekVAxumRxjBNuZX4RrfLmNkpSaSKTw+SgSRq3rYPtfwRFC95n6cgwOlQE9vN1L2pjPzBa/m0vMvJHPt7DfkAGYqBMdUBhH/DSFOqUbNa9fhRSMr5E90jh6hQAU4Gt9iPQvVIT9jyBLXObLT6WwcyBcRStmSTVmmz+D2+4hLOlvfYlSTco1gR3TKWXkc/Mzh0fXDhcq+9XxABjbN0AAAAVALGNvTrp0YwxKNphtIiyWD1k8CePAAABADVNa0SXlowigmu3uWQeMJnk2s1FktefN+9LSXWlRinNsnltYFPHpz8BauBxCLDpSHLEOSxOCl75h4Gl9EW+yu1Y5KqY8AenArt64dl3q8z3DdWdSBngIsbRveWCIn5Ahw3IemklF7wrJOy+WEJZVWn/1MwOVqKVxUNAIGUazvtbgwMZPAANBkM6y1Nb7zZG21XsiSoWAd0oVDdZE5jkAd+kbMloiuUpr+ZkELxX8EG8G6jlWhgbGi5dfmSXHoaKR6NIOsUXT2aCdjot5TzO3r/pD4EHDWAlRZhxVFcGNaFulnPF4m5uffQh0aIfco6vpX5GGG8/oK6PFxxuEEXBir0AAAEBAJsfVpRTYejtaCf2xEpWByHNbx7jIu2JsTzegTQY7h3jWTXTYOQxovYryCi7xPbrlVx58XsfkBJKr+eO20x7hprdRydK37qhOto/qNdjwjTAUVXq0vNdro0npKYx8q690xgMeTe2NBHDcvNulVbwZKCsyrZOisVyzl/LfaQ76hs3d6dpf6ms3s1QQWUh5tM4xB20O9cBlHarZDKdgJFKPQ4NCSYR+gzYAolehkihLaVFLXcL0vlV9R6PuJVkilzdp3eS2riKbVkoE3zpQA/Ya3QkueBNp4pqHkeGvgcQOp57VE4KvnU/N4kOv1NDfD6aARsnRYTVpeBtiPzOl58rhks= davem@sunset
[davem@apc-ap8641-3a-d11c GLIBC]$ ls -l ~/.ssh/id_dsa
-rw-------. 1 davem davem 1264 Jun 20  2011 /home/davem/.ssh/id_dsa

Something's not right....

Re: SSH key

[David Miller]

From: David Miller <davem@davemloft.net>
Date: Tue, 16 Oct 2018 16:17:55 -0700 (PDT)

> Something's not right....

Ok, it's this:

debug1: Skipping ssh-dss key /home/davem/.ssh/id_dsa - not in PubkeyAcceptedKeyTypes

So I have to generate a different kind of key?

Re: ssh key

[Jonathan Larmour]

Janus Weil wrote:
> Hello,
> 
> I have accidentally nuked my ssh key for accessing gcc.gnu.org. Would
> it be possible to set up a new one (my new key is attached). Sorry for
> the inconvenience.

Done.

Jifl

ssh key

[Janus Weil]

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

Hello,

I have accidentally nuked my ssh key for accessing gcc.gnu.org. Would
it be possible to set up a new one (my new key is attached). Sorry for
the inconvenience.

Best regards,
Janus Weil

[-- Attachment #2: id_dsa.pub --]
[-- Type: application/octet-stream, Size: 605 bytes --]

ssh-dss AAAAB3NzaC1kc3MAAACBAJGPchoupSQi4C8vN5VzjQ2xDHZIVIOKW6gy10NGrXQNPhFAxr28lM/T92IMJrXA2nm1NCwaXxPhbPXPiIqnYHHyiEMq6hKLN9c5rB8ZqhREdsgUFSHey/zRz56aN+Mvfl7cz/328whZonoaiR06CfPE+vgqxn0q88ZkaRTP5HZ1AAAAFQDSKc/wuyLbSlz6i/qRr0eHQsUWxQAAAIBMZQz82WupY8VeM9l/zZg5DuU8f22qFuvqFAwRtTgwJJIkfh2f9YLIWF28xFXIuEtqLuMxeA+gcbY4ffAa9oYogESIa7zlg3ImVBg8x4uW9uq2hKSQrJqhqU0EH3jKpAsRmHPoMfmI4HepKT81hUCWsanLffmiAvcA2hjEP3t8QgAAAIB+FnngOx00UXcd2JZhFk6XXJMg83EFyvYTh6gSHoR/CKe904SwXx92z2+R5K/NdHUA7x9TDCDRE8HvuLAwQ+0WfiLdlpPzUS1AqWwxk2MG0cZd6zYw36xFOSFmfJ6eDgcix3yTZghZ/bGeNvmqk3TjTYGAf2AXwMMgvtKDQOWImw== jweil@fb07-jlap

Re: ssh key

[Alexandre Oliva]

On Aug 10, 2004, "Frank Ch. Eigler" <fche@redhat.com> wrote:

> Hi -
> On Tue, Aug 10, 2004 at 02:14:16PM -0300, Alexandre Oliva wrote:
>> [...]  I'm just thinking it might be reasonable to have, as
>> part of the sign-up procedure, a gpg pubkey registration, and demand
>> such requests to be signed with the corresponding privkey.

> But how would that solve the typical problem that appears here, which
> is that people lose their old ssh private keys (due to change of hardware
> or fatfingering rm or whatever)?  Files in $HOME/.gnupg are not much more
> likely to survive than $HOME/.ssh.

Well...  You're supposed to keep the GPG key revocation certificate in
permanent storage, and you might as well have the GPG private key
itself saved somewhere.  Sure it's not bullet-proof, and we may have
to handle exceptions, but those would not be the rule.

In this one case, it was not about a lost key, it was about requesting
an additional key.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

Re: ssh key

[Frank Ch. Eigler]

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

Hi -

On Tue, Aug 10, 2004 at 02:14:16PM -0300, Alexandre Oliva wrote:
> [...]  I'm just thinking it might be reasonable to have, as
> part of the sign-up procedure, a gpg pubkey registration, and demand
> such requests to be signed with the corresponding privkey.

But how would that solve the typical problem that appears here, which
is that people lose their old ssh private keys (due to change of hardware
or fatfingering rm or whatever)?  Files in $HOME/.gnupg are not much more
likely to survive than $HOME/.ssh.

- FChE

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

Re: ssh key

[Alexandre Oliva]

On Aug  9, 2004, Christopher Faylor <me@cgf.cx> wrote:

> On Mon, Aug 09, 2004 at 04:37:43AM -0300, Alexandre Oliva wrote:
>> On Aug  7, 2004, Christopher Faylor <me@cgf.cx> wrote:
>>> On Sat, Aug 07, 2004 at 12:02:40PM -0400, James A.  Morrison wrote:
>>>> I would like the following ssh key added for my access to the GCC
>>>> repository.  My usersname is phython.
>> 
>>> I've added the key.  You should be all set.
>> 
>> Am I the only one who thinks `hey, could you grant this key access to
>> my account' e-mail requests should get some additional form of
>> verification than simply hoping they weren't forged by a random third
>> party trying to get unwarranted access to s.r.c?

> Since he only has CVS access and the email headers seemed to check out,
> I didn't think there was great harm in satisfying the request.

Oh, absolutely.  I'm just thinking it might be reasonable to have, as
part of the sign-up procedure, a gpg pubkey registration, and demand
such requests to be signed with the corresponding privkey.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

Re: ssh key

[Christopher Faylor]

On Mon, Aug 09, 2004 at 04:37:43AM -0300, Alexandre Oliva wrote:
>On Aug  7, 2004, Christopher Faylor <me@cgf.cx> wrote:
>>On Sat, Aug 07, 2004 at 12:02:40PM -0400, James A.  Morrison wrote:
>>>I would like the following ssh key added for my access to the GCC
>>>repository.  My usersname is phython.
>
>>I've added the key.  You should be all set.
>
>Am I the only one who thinks `hey, could you grant this key access to
>my account' e-mail requests should get some additional form of
>verification than simply hoping they weren't forged by a random third
>party trying to get unwarranted access to s.r.c?

Since he only has CVS access and the email headers seemed to check out,
I didn't think there was great harm in satisfying the request.

Re: ssh key

[Alexandre Oliva]

On Aug  7, 2004, Christopher Faylor <me@cgf.cx> wrote:

> On Sat, Aug 07, 2004 at 12:02:40PM -0400, James A. Morrison wrote:
>> I would like the following ssh key added for my access to the GCC repository.
>> My usersname is phython.

> I've added the key.  You should be all set.

Am I the only one who thinks `hey, could you grant this key access to
my account' e-mail requests should get some additional form of
verification than simply hoping they weren't forged by a random third
party trying to get unwarranted access to s.r.c?

BTW, could I please have the attached ssh key added to my
.ssh/authorized_keys?  My login on s.r.c is r00t  :-) :-)

Attachment intentionally omitted.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

Re: ssh key

[Christopher Faylor]

On Sat, Aug 07, 2004 at 12:02:40PM -0400, James A. Morrison wrote:
>  I would like the following ssh key added for my access to the GCC repository.
>My usersname is phython.

I've added the key.  You should be all set.

cgf

ssh key

[James A. Morrison]

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


 Hi,

  I would like the following ssh key added for my access to the GCC repository.
My usersname is phython.

-- 
Thanks,
Jim

http://www.student.cs.uwaterloo.ca/~ja2morri/
http://phython.blogspot.com
http://open.nit.ca/wiki/?page=jim


[-- Attachment #2: RSA public key --]
[-- Type: application/octet-stream, Size: 254 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAqkgdAz3MTQwbr3+Yoi/NF8PsQTnmxulkSxlGXThuZk7J0N5VgmAwQneW2NYcleLureuwAF0Wn2/UrTm66gYOob6tvq6m7Ak1Jtq6+vJ6EQB+KvnMlIAcN0X/4L4G7NRmmSezOLNOVHkmg8XTwvg1Dtn82OUdh0+i3QB+1hhG/ic= jamesmorrison@James-Morrisons-Computer.local