[SOLVED] security of your machine when connecting to exposed server via ssh
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.
security of your machine when connecting to exposed server via ssh
if somebody gains control of the server i'm connecting to using ssh (creating a socks tunnel)
does he have access to my machine?
i am behind a router, acting as a firewall, not giving access to ports on my machine from outside the network
how about when forwarding a single port? (port 80), do they still have access?
if somebody gains control of the server i'm connecting to (..) does he have access to my machine?
Controlling the remote host you SSH to or through means the perp in theory controls whatever you execute on, get from or send through that host. Since you only tunnel encrypted SSH traffic through the remote host and don't allow new connections to your LAN machine behind your LAN router / firewall and only use SSH with pubkey auth and your remote host uses a unique password or (better) pass-phrase the risk of the perp finding a way in through that connection is infinitesimal.
since the way ssh works for tunneling is creating another ssh connection from server to host(my machine), doesnt this mean they have access for execution of commands?
Looks like something you could do the groundwork for yourself: create your SSH tunnel (you never listed if you were using a reverse tunnel or not BTW), log in on the remote host, then try to execute commands through your tunnel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.