

Well yeah, duh.


Well yeah, duh.


Opening ports is also trivial. You don’t generally need a dedicated IP if you keep a connection running but YMMV. And you don’t need a domain - just remember the IP. This is only for a few weeks.


Setting up ssh is nearly trivial. And saying it’s “less secure” doesn’t mean it’s insecure.
It’s the primary access point for thousands of systems and for good reason. It’s “good enough” for your little homelab.


Jesus… Just port forward 22 to your system and ssh in directly.


Just use ssh and be sure to disable remote root access and require key based authentication. If it’s good enough for aws, azure, etc. then it’s good enough for what you want.
You’ll want to read up on port forwarding and pick a remote gui tool. “No machine” works very well for x11, but rdp is supported by some wayland displays. Vnc is the old workhorse.


Why? It sounds fine to me. OpenSSH is the standard for secure remote access. And port forwarding works great.


OpenSSH is one of the most secure applications in the world. It’s fine to expose it to the Internet. Just be sure you have excellent passwords or don’t allow password auth.
That happens here too, it’s just easier when you make AI disclosure a scarlet letter.