3 ms·
I find https://wiki.ubuntu.com/UncomplicatedFirewall https://wiki.ubuntu.com/UncomplicatedFirewall to be much friendlier to use when setting up firewalls. The
by nl 13y ago
I find https://wiki.ubuntu.com/UncomplicatedFirewall https://wiki.ubuntu.com/UncomplicatedFirewall to be much friendlier to use when setting up firewalls.
The big problem I have is securing my private keys. I use multiple devices, and haven't found a secure and convenient way to share the keys across devices securely. I'd love ideas..
- Qantourisc 13y agoThe answer is don't: use an unique key for each device. But this doesn't solve the problem you have to connect to each host to reject the lost key. (But you have the same problem with 1 key, so no worse.)
- XorNot 13y agoI fall on the side of an SSH key identifies a person, not a device. That's what host keys are for. What's always been missing though is a decent way to keep track of all the places which might be set to authorize a particular key so you can revoke it if you think it's been compromised (which should mean "is under brute force attack to decrypt it's AES encryption"). I suppose with a DynDNS server and a smartphone app, you could setup a web-page which would allow you to request a URL to download your SSH key securely to new devices but this is kind of the problem: there's just nothing out there which lets you keep a proper eye on how your web-of-trust works for this type of thing.
- oelmekki 13y agoYou shouldn't try to share them, imo, and generate a key for each device. Yes, that may be painful to have to copy 5 public keys on each new server, but the day where, say, your laptop get stolen, you don't have to change the private key on each device : simply remove the laptop one. If you want some kind of centralization, you could only add your keys on a single server, then add this server key on others. You log on first server, then use it to log on others. But that would be dangerous : if the master server crashes, you can't access other servers anymore. Redundancy is good, in that case.
- zokier 13y agoBetter way to reduce the need for copying keys around would be setting up a private CA, and signing the individual keys with it. Of course you need to keep the CA key secure, I'd strongly suggest removable media or preferably a real HSM.
- nl 13y agoCan you explain how this would work? How do I use a private CA to generate(?) keys for ssh authentication?
- nl 13y agoI agree that key-for-each-device is probably best practice. It just doesn't work for me though. I frequently need to log onto servers from new client computers, and the workflow of connect from trusted device, generate new key for new device then use new device just isn't practical. I've spent a lot of time thinking about this. I think the biggest threat to security on my servers is brute forcing of ssh passwords. The best solution for that is key based authentication. (I deploy fail2ban as well though) There is a non-zero threat of my devices being lost/stolen/accessed with my keys on them. So key based authentication is the way to go, but I just can't get around the practical aspects. In the end I often rely on long, random passwords kept in a KeePass database I sync (along with Fail2Ban). I've considered keeping my private keys in that too, and to be honest I think that isn't a terrible solution. It is certainly less than ideal, but probably mildly more secure than my current method (ie: really a private key shared across devices is acting as a very long password)
- colechristensen 13y agoPut a passphrase on your private key and copy it over whatever insecure channel you'd like. ... or use ssh, why wouldn't you use ssh?
- tokenizerrr 13y agoOn Windows I use KeePass 2 [1] with the KeeAgent [2] plugin. The keys will be protected by your master password, and it will act like pageant so most tools will automatically recognize and use the keys. You can configure it to automatically let all applications use the keys, or first prompt you before providing the key to the user. You can keep the database file on an USB stick or even something like dropbox or owncloud [3]. [1] http://keepass.info/index.html http://keepass.info/index.html [2] http://keepass.info/plugins.html#keeagent http://keepass.info/plugins.html#keeagent [3] http://owncloud.org/ http://owncloud.org/
- SpenserJ 13y agoI do the same, and have found it works beautifully. You need my master password, SSH Key, and my SSH Key's password before you can log into my server. And if you somehow manage to get all of that, you need my account password in order to modify any non-user files.
- kolev 13y agoAnother option is ferm (http://ferm.foo-projects.org/ http://ferm.foo-projects.org/).