Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

SSH has included file encryption for a few versions now, and iirc supports yubikeys — probably would be more useful a backend than age.


sort by: page size:

I'm not sure if they will support those yet. I could never get SSH working well, whereas SSH with U2F works perfectly (and they do support that). I'm guessing they will add GPG key integration, as once the key can perform crypto operations, it's just a matter of host software.

And they support keys -- Although it seems the primary way to use them is by putting your keys into your 'Downloads' folder, which isn't exactly ideal.

Looks like this will eventually replace the inbuilt ssh supplied with crosh (Chromium OS shell)


Here's half an answer: Kerberos.

Which SSH does support, btw.


Another way I'm feeling old... I remember back when OpenSSH was just a plucky upstart implementation of SSH.

Hmm. The lack of any kind of user-accessible local filesystem is one thing that makes me not prefer iOS.

But it's a real puzzler: is this really a brand new implementation of the ssh protocol? I know I'd feel a LOT better knowing that it used OpenSSH.


Cool. Looks like Userify.com (SSH Key management) will support yet another platform sometime next year.

(disclaimer: I work there.)


Do we need a replacement for SSH? The OpenSSH team is doing an amazing work. Besides making the tool as secure as possible, they are also improving the protocol. The recently added support for encrypt-then-MAC modes is a great step forward.

Also any proprietary/ancient SSH implementation only supporting RSA that you'll find in all kinds of boxes.

If you wanted OpenPGP to protect SSH, you should consider upgrading clients and servers to a modern OpenSSH which can just speak FIDO (which this and other recent Yubikeys support)

I meant the protocol, not the program. A secure shell is still useful, but the old protocol is like a unix neckbeard that doesn't wanna learn containers. (And while we're on the subject, SSHD should support an HTTPS port and either serve a javascript client or accept websocket connections, because it is 2023 and that's what everyone wants anyway)

Thanks! It doesn’t look very promising! SSH is already PQ-secure.

Yes, because it’s underpinned by SSH it’s secure.

The authors consider it feature complete hence the lack of updates.


It's usually not a full replacement. SSH for macOS has some integration built in that current OpenSSH does not have, like Keychain integration.

I agree - the killer advantage of SSH is that OpenSSH is very, very good.

Yes, but that would either be a fork of OpenSSH, private or open source (both are possible since it's BSD-licensed), or a different SSH server (which Github is of course free to use, since the protocol is standardized and their scale absolutely justifies any efforts in protecting their SSH host key). But GPs comment was about OpenSSH.

Edit: Apparently OpenSSH's sshd also supports the SSH agent protocol for host keys, and ssh-agent does support PKCS#11 – so I stand corrected!


It's still the only SSH client I know that can change most of its settings during an existing session, especially in a cross-platform way (it is available for Linux). Good software indeed.

pam_yubico yes.

You can also use this to secure SSHD on servers by delegating to PAM with keyboard-interactive.

I'm waiting for U2F OpenSSH support to trickle down to stable distros but in the meantime pam_yubico is pretty damn good... not to mention you don't have to worry about terminal support since it relies on the yubikey OTP emulating a keyboard.


If you just want ssh it's even easier to use u2f/fido now since it's built into openssh.

If it’s good enough for ssh, it’s good enough for everything. Widespread Passkey support can’t come soon enough.
next

Legal | privacy