Mounting SSH does no longer work with latest 1.10.2 release, worked with 1.10.0 - regression? #2581

Open
opened 2015-11-22 18:13:02 +00:00 by Quix0r · 7 comments
Quix0r commented 2015-11-22 18:13:02 +00:00
Owner

Here is a snippet from my config file:

[sftpd]
enabled = true
port = tcp:8022:interface=127.0.0.1
host_pubkey_file = private/ssh_host_rsa_key.pub
host_privkey_file = private/ssh_host_rsa_key
accounts.file = private/accounts

I will attach a twisted.log excerpt soon.

Here is a snippet from my config file: ``` [sftpd] enabled = true port = tcp:8022:interface=127.0.0.1 host_pubkey_file = private/ssh_host_rsa_key.pub host_privkey_file = private/ssh_host_rsa_key accounts.file = private/accounts ``` I will attach a twisted.log excerpt soon.
tahoe-lafs added the
code-frontend-ftp-sftp
normal
defect
unknown
labels 2015-11-22 18:13:02 +00:00
tahoe-lafs added this to the undecided milestone 2015-11-22 18:13:02 +00:00
Quix0r commented 2015-11-22 18:13:30 +00:00
Author
Owner

Attachment tahoe-ssh-problem.txt (3403 bytes) added

twisted.log file - problematic SSH

**Attachment** tahoe-ssh-problem.txt (3403 bytes) added twisted.log file - problematic SSH
Quix0r commented 2015-11-22 18:20:24 +00:00
Author
Owner

Mounting a read-only URI works flawless.

Mounting a read-only URI works flawless.
daira commented 2015-11-22 22:32:24 +00:00
Author
Owner

That's an !ed25519 key that it's failing to recognise. It would not surprise me if Twisted's ssh implementation did not support !ed25519. Can you try with an RSA or ECDSA key?

I'm not sure why a read-only URI would make a difference to the error in the log. What other symptoms are there besides the log entry? Perhaps something else is different in that test?

That's an !ed25519 key that it's failing to recognise. It would not surprise me if Twisted's ssh implementation did not support !ed25519. Can you try with an RSA or ECDSA key? I'm not sure why a read-only URI would make a difference to the error in the log. What other symptoms are there besides the log entry? Perhaps something else is different in that test?
tahoe-lafs added
1.10.1
and removed
unknown
labels 2015-11-22 22:34:51 +00:00
Quix0r commented 2015-11-23 11:56:03 +00:00
Author
Owner

Hello Diara,

which key has been taken here? I have tried to move my ED25519 key out of ~/.ssh/ but no change in the error. I also replaced the key under ~/.tahoe/private/ but still no change.

And maybe you/someone can add 1.10.2 to the list of supported versions?

And thank you for fixing the typo. :)

Hello Diara, which key has been taken here? I have tried to move my ED25519 key out of ~/.ssh/ but no change in the error. I also replaced the key under ~/.tahoe/private/ but still no change. And maybe you/someone can add 1.10.2 to the list of supported versions? And thank you for fixing the typo. :)
daira commented 2015-12-02 03:01:34 +00:00
Author
Owner

When you moved your !Ed25519 key out of ~/.ssh, did the errors in the log change?

When you moved your !Ed25519 key out of ~/.ssh, did the errors in the log change?
tahoe-lafs added
1.10.2
and removed
1.10.1
labels 2015-12-02 03:01:34 +00:00
Quix0r commented 2015-12-28 12:03:51 +00:00
Author
Owner

No, the error remains.

No, the error remains.
Quix0r commented 2015-12-28 12:09:15 +00:00
Author
Owner

1.10.0 has worked flawlessly. I test 1.10.1 now.

Edit: Nope, 1.10.1 is also affected by this bug.

1.10.0 has worked flawlessly. I test 1.10.1 now. Edit: Nope, 1.10.1 is also affected by this bug.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2581
No description provided.