Ticket #41333

Storage SFTP/SCP not working

오픈 날짜: 2021-01-25 16:46 마지막 업데이트: 2021-01-27 18:44

Reporter:
소유자:
(None)
Status:
Closed
Component:
MileStone:
(None)
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
None
Vote
Score: 1
100.0% (1/1)
0.0% (0/1)

Details

I have already added the ssh keys and now when I am trying to access the storage from the provided code in under the file-storage, it always stays the same. Below are both the outputs:

sftp dev-andi@storage.osdn.net:/storage/groups/p/pe/peux-os dev-andi@storage.osdn.net: Permission denied (publickey). Connection closed. Connection closed

and

sftp dev-andi@storage.osdn.net:/storage/groups/p/pe/peux-os dev-andi@storage.osdn.net: Permission denied (publickey). Connection closed. Connection closed

Any help would be much appreciated. Apologies beforehand if the formatting and component of the ticket is not proper.

Ticket History (3/6 Histories)

2021-01-25 16:46 Updated by: dev-andi
  • New Ticket "Storage SFTP/SCP not working" created
2021-01-26 13:14 Updated by: ishikawa
댓글 올리기
  • After updated a SSH key on the Web UI, it will be take a few minutes for the key to be be applied to the storage server. So if you update the key and access storage server immidiatly, you will see ssh access denied. Please wait a few minutes (about 5 minutes) to use storage access after SSH key update.
  • Please update ssh keys only via Web UI. You can edit SSH key on the shell server but it will be overwrite the data on the DB (it was written via Web UI) after few minuites.
  • We've check your key on the storage server, it was updated at 19:18 JST (10:18 UTC) on Jan 25, 2021. Have you updated the key after create this ticket?
  • Current your SSH key on the storage server finger print is bellow. Please make sure it matches the your client-side key.
256 SHA256:lB9y5rV+cGiDf8fRY3vtAuAxJbAj/61HKVQb+q87iog no comment (ED25519)
  • If the above key is correct and you still can't access to the storage server, there may be something wrong with your client-side configuration. Please run sftp/scp with -v option to output debug log and send/copy the log to this ticket.
sftp -v dev-andi@storage.osdn.net:/storage/groups/p/pe/peux-os
2021-01-26 19:05 Updated by: dev-andi
댓글 올리기

Reply To ishikawa

* After updated a SSH key on the Web UI, it will be take a few minutes for the key to be be applied to the storage server. So if you update the key and access storage server immidiatly, you will see ssh access denied. Please wait a few minutes (about 5 minutes) to use storage access after SSH key update. * Please update ssh keys only via Web UI. You can edit SSH key on the shell server but it will be overwrite the data on the DB (it was written via Web UI) after few minuites. * We've check your key on the storage server, it was updated at 19:18 JST (10:18 UTC) on Jan 25, 2021. Have you updated the key after create this ticket? * Current your SSH key on the storage server finger print is bellow. Please make sure it matches the your client-side key. {{{ 256 SHA256:lB9y5rV+cGiDf8fRY3vtAuAxJbAj/61HKVQb+q87iog no comment (ED25519) }}} * If the above key is correct and you still can't access to the storage server, there may be something wrong with your client-side configuration. Please run sftp/scp with -v option to output debug log and send/copy the log to this ticket. {{{ sftp -v dev-andi@storage.osdn.net:/storage/groups/p/pe/peux-os }}}

Hi Ishikawa-san,

I did tried to check the logs using verbose switch, the problem is ssh authentication to github looks good and also with Sourceforge, but no matter how i try, its fails here. Below is the verbose log:

Executing: program /usr/bin/ssh host storage-in.osdn.net, user dev-andi, command scp -v -t /storage/groups/p/pe/peux-os/
OpenSSH_8.4p1, OpenSSL 1.1.1i  8 Dec 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to storage-in.osdn.net [54.184.171.155] port 22.
debug1: Connection established.
debug1: identity file /home/test/.ssh/id_rsa type 0
debug1: identity file /home/test/.ssh/id_rsa-cert type -1
debug1: identity file /home/test/.ssh/id_dsa type -1
debug1: identity file /home/test/.ssh/id_dsa-cert type -1
debug1: identity file /home/test/.ssh/id_ecdsa type -1
debug1: identity file /home/test/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/test/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/test/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/test/.ssh/id_ed25519 type -1
debug1: identity file /home/test/.ssh/id_ed25519-cert type -1
debug1: identity file /home/test/.ssh/id_ed25519_sk type -1
debug1: identity file /home/test/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/test/.ssh/id_xmss type -1
debug1: identity file /home/test/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.4
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 Debian-10+deb9u7
debug1: match: OpenSSH_7.4p1 Debian-10+deb9u7 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to storage-in.osdn.net:22 as 'dev-andi'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:HZd0QGVac9bA3JjIrIMXPZQG5BCwUnorm798lhfAlTo
debug1: Host 'storage-in.osdn.net' is known and matches the ECDSA host key.
debug1: Found key in /home/test/.ssh/known_hosts:2
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: /home/test/.ssh/id_rsa RSA SHA256:TXEfM7cnpyNCVKPp0V1MiDjgrmtpdL6UuB9s6U4Z1r4
debug1: Will attempt key: /home/test/.ssh/id_dsa 
debug1: Will attempt key: /home/test/.ssh/id_ecdsa 
debug1: Will attempt key: /home/test/.ssh/id_ecdsa_sk 
debug1: Will attempt key: /home/test/.ssh/id_ed25519 
debug1: Will attempt key: /home/test/.ssh/id_ed25519_sk 
debug1: Will attempt key: /home/test/.ssh/id_xmss 
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/test/.ssh/id_rsa RSA SHA256:TXEfM7cnpyNCVKPp0V1MiDjgrmtpdL6UuB9s6U4Z1r4
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/test/.ssh/id_dsa
debug1: Trying private key: /home/test/.ssh/id_ecdsa
debug1: Trying private key: /home/test/.ssh/id_ecdsa_sk
debug1: Trying private key: /home/test/.ssh/id_ed25519
debug1: Trying private key: /home/test/.ssh/id_ed25519_sk
debug1: Trying private key: /home/test/.ssh/id_xmss
debug1: No more authentication methods to try.
dev-andi@storage-in.osdn.net: Permission denied (publickey).
lost connection

NOTE: Though it is not urgent or important to me. It's just that the WEB UI won't let me upload more than 2.3 gigs of file, that's why I tried to use this method. I can always reduce the file-size of the ISO that I am trying to upload anyway.

~ Dev

2021-01-27 10:57 Updated by: ishikawa
댓글 올리기

Sorry, we've found a problem of storage server SSH key update and fixed it. Your ssh key on the storage server has been updated correctly.

https://osdn.net/users/dev-andi/openssh.pubkeys

The key stored for storage access is as same as above URL, please check it. If this key is not the one you want to use, please update it from here (and wait a few minutes to refrect to storage server)

https://osdn.net/account/editsshkeys.php

2021-01-27 18:42 Updated by: dev-andi
댓글 올리기

Reply To ishikawa

Sorry, we've found a problem of storage server SSH key update and fixed it. Your ssh key on the storage server has been updated correctly. https://osdn.net/users/dev-andi/openssh.pubkeys The key stored for storage access is as same as above URL, please check it. If this key is not the one you want to use, please update it from here (and wait a few minutes to refrect to storage server) https://osdn.net/account/editsshkeys.php

Hi Ishikawa-san,

resolved. Thanks. I am now able to get the passphrase prompt. Closing the ticket.

~Dev

(Edited, 2021-01-27 18:44 Updated by: dev-andi)
2021-01-27 18:44 Updated by: dev-andi
  • Status Update from Open to Closed
  • Resolution Update from None to Fixed
댓글 올리기

closing the ticket

Attachment File List

No attachments

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login