Mounting SSH does no longer work with latest 1.10.2 release, worked with 1.10.0 - regression? #2581
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2581
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Here is a snippet from my config file:
I will attach a twisted.log excerpt soon.
Attachment tahoe-ssh-problem.txt (3403 bytes) added
twisted.log file - problematic SSH
Mounting a read-only URI works flawless.
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?
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. :)
When you moved your !Ed25519 key out of ~/.ssh, did the errors in the log change?
No, the error remains.
1.10.0 has worked flawlessly. I test 1.10.1 now.
Edit: Nope, 1.10.1 is also affected by this bug.