Max Suraev

See https://github.com/djcb/mu/issues/545 for corresponding discussion.

> Since ssh is such a non-trivial tool, it might be worth mentioning a workaround after encrypting. This isn't a workaround - it's a security hole which completely defeats the...

> Disagree. Disable passwords of course. If you're smart enough to use arch linux, you'll know ed25519. Huh? What does passwords or ECC have to do with this? Do you...

> This repo needs a code of conduct. Which should absolutely forbid giving public security advice which might put users in danger.

> remember they're already encrypted with passphrase What exactly makes you think that? Remember, we're talking about "authorized_keys" file for SSH. This isn't a trade-off. You either protect highly sensitive...

I did before opening this bug. That's a nice starting point but it does not cover all what's described in this issue. Read the issue description.

Confirmed with clisp 2.49 on ubuntu 13.10

All the abovementioned tickets are closed - perhaps it's time to removed the 'blocked' label?

Is there particular sourcehut repo(s) worth keeping eye on for new developments?

> But I think its install procedure should be simplified/industrialized/packaged to make it easier to enforce its usage in a team. I second this - having .deb package for example...