Keys with passphrases for SFTP #1039
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1039
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?
Currently ssh keys with passphareses raise following exception:
twisted.conch.ssh.keys.EncryptedKeyError: encrypted key with no passphrase
Twisted has support for passphrases but currently there is no way in Tahoe-LAFS to acquire the passphrase from user.
The solution for now is just to generate keys without a passphrase~~, even though source:docs/frontends/FTP-and-SFTP.txt suggests otherwise~~.
FTP-and-SFTP.txt doesn't actually suggest otherwise, but I can see how [the current wording]source:docs/frontends/FTP-and-SFTP.txt#L28 could be confusing (it is actually referring to user passwords, not the passphrase of the server private key).
Server-side keys don't generally have passphrases. When they do, things like sshd can't start up by themselves. The usual linux distributions creates passphraseless keys in /etc/ssh/ssh_host_dsa_key at install time.
I think it's perfectly fine to have Tahoe's SFTP server refuse to use passphrase'd server keys. And yeah, the docs should encourage this by showing an example of running 'ssh-keygen' without providing a passphrase.
Milestone 1.7 to make the docs clear that this isn't supported; then we can decide whether to leave the ticket open or wontfix it.
Attachment sftp-and-ftp-doc.dpatch (57063 bytes) added
FTP-and-SFTP.txt: remove description of public key format that is not actually implemented. Document that SFTP does not support server private keys with passphrases, and that FTP cannot list directories containing mutable files.
Attachment sftp-and-ftp-doc-known-issues.dpatch (57796 bytes) added
Update to previous patch adding a 'Known Issues' section
The updated patch looks good to me; I like the known issues section.
Doc patches applied in changeset:e05c6c2c7d25db66 and changeset:29a9059c94eef955.
Demoting this to minor; I have no plans to support server-side keys with passphrases, and there's lots more important stuff to do.