[SAC] [OSGeo] #2663: Get access to osgeo7-*

[OSGeo]

#2663: Get access to osgeo7-*
---------------------------+------------------------
 Reporter:  jsanz          |       Owner:  sac@…
     Type:  task           |      Status:  new
 Priority:  normal         |   Milestone:  Unplanned
Component:  Systems Admin  |  Resolution:
 Keywords:                 |
---------------------------+------------------------

Comment (by robe):

 Replying to [comment:2 jsanz]:

 > Done, I've added my public key on that form. I waited a day but I still
 get a `permission denied` error.

 The change takes effect immediately so you don't need to wait.
 I do see the key now on your ldap account and confirmed it matches what
 you have in osgeo6 second key aside from linebreaks and spaces which
 shouldn't matter as the ldap one is chunked on mine too and I don't have a
 authorized_keys in my hop home drive and can get in with my account.

 I've manually added the key to your home drive on hop.osgeo7.osgeo.org to
 rule out any weird whitespace issues.

 If that still doesn't work perhaps your issue is the one described below.

 https://dev.to/bowmanjd/upgrade-ssh-client-keys-and-remote-servers-after-
 fedora-33-s-new-crypto-policy-47ag

 Here:
 https://wiki.osgeo.org/wiki/SAC_Service_Status#Accessing_osgeo7_containers_via_ssh

 {{{
 Troubleshooting: In case of "Permission denied (publickey)." after an
 update to a modern openSSH version, it might well be that your ssh key
 (RSH key) is disabled in your client in favour of more modern cyphers.

 Ugly workaround: add one line `PubkeyAcceptedKeyTypes ...` in
 `.ssh/config`, to re-enable RSA keys for now (consider to generate a new
 key):

  vim .ssh/config
  ...
  Host *
     ...
     PubkeyAcceptedKeyTypes +ssh-rsa

 }}}

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2663#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.