two doors, and neither one is your house.
the netbook dials out, nothing listens at home:
ssh -N -R 0.0.0.0:2323:127.0.0.1:2222 tunnel@vps
the trap sits right there: ssh -R binds the far end to loop...
This is probably one of the most detailed suggestions I have received so far. I appreciate that you considered antiX and the fact that I want to preserve the terminal experience.
The reverse SSH tunnel approach is interesting because it would let my netbook initiate the connection without opening ports on my home router. Running a separate SSH service just for the BBS also makes sense.
My concern is still security though. Even with a reverse tunnel the public VPS would have a connection path to my netbook. If the VPS gets compromised or the BBS has a vulnerability then my other projects and potentially my home network could still be at risk.
There is also the VPS cost. I am trying to find a solution that does not require additional spending.
But I really appreciate the detailed explanation. I am adding this approach to my research list. I would rather spend more time understanding the risks than rush into publishing the BBS.😀
The reverse SSH tunnel approach is interesting because it would let my netbook initiate the connection without opening ports on my home router. Running a separate SSH service just for the BBS also makes sense.
My concern is still security though. Even with a reverse tunnel the public VPS would have a connection path to my netbook. If the VPS gets compromised or the BBS has a vulnerability then my other projects and potentially my home network could still be at risk.
There is also the VPS cost. I am trying to find a solution that does not require additional spending.
But I really appreciate the detailed explanation. I am adding this approach to my research list. I would rather spend more time understanding the risks than rush into publishing the BBS.😀
1
