Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
A buddy of mine travels quite a bit for work. While on the road, he's constantly having to use wifi connections he comes across. Since wifi can be less than secure, I was wondering if the following would help keep his traffic (and passwords) safe-er.
I was considering setting up a linux box on his network that he could SSH into while on an outside wifi connection, then setup a tunnel so all his traffic would be encrypted.
Does this actually help, or would a bad wifi connection just allow a 'badguy' to grab his SSH key and nullify any benefit to the secure tunnel?
If this isn't a good idea, any other suggestions are welcome.
Yes, that would work as long as there is no man-in-the-middle attack. That means he has a public key in the known-hosts file of the mobile device, so that he can tell if traffic is intercepted.
A far more effective strategy would be to use VPN, to create a "tunnel" to the remote system, through which all traffic would pass without any special awareness on the part of any application that wished to use the tunnel. Doesn't matter whether the transport is wireless or wired. "It could be carrier-pigeon," ahh, so to speak, and it would still be secure(d).
You should, of course, secure the VPN connection using individual, unique, password-protected cryptographic keys, issued by the host system. (Do not use "PSK == pre-shared-keys == mere passwords.")
The best form of cryptographic security is the most unobtrusive one. It should require no special awareness, and no special procedures, for its successful employment by any user or application that uses it. "It Just Works.™"ssh, on the other hand, does require special awareness and special procedures, without which communications that were supposed to be secure could be utterly and completely disclosed without the awareness of anyone ... "merely due to, say, the carelessness of the operator."
Always remember that the greatest threat to mechanized security is ... ... human realities. Uh huh. Computers may be mechanical, but we humans are not. "Wea culpa."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.