#Minetest methods windows

private keys are ideally never transferred. generate ssh keypair on client (each client should do these steps.

#Minetest methods windows

( Putty for old windows, built in for linux or osx etc, new windows might have better support).

obtain ssh client for game client machine.

actiate ssh server on pi if not yet done,.

The process when implemented, would look something like this: The ssh tunnel uses strong encryption methods to pass the traffic over the untrusted network ( yours, or perhaps any network for some traffic ). The remote port need not be accessible on the network directly, only ssh ( the game server would listen on localhost). SSH offers a much higher standard of security than most protocols.Ĭonceptually, you execute an ssh client locally on the game client configured to open a local port on the game client, and forwards packet recieved on that port to a remote port on the ssh server. You're already using it to manage your raspberry pi, probably, and if you're not, you might want to (I for one need copy/paste between web and terminal, and I don't want to run gui on pi!). If so, we can probably assume that the connection itself doesn't support much in the way of encryption, but it's likely we can successfully tunnel the connection in any number of ways to add an encryption layer 'between' client and server. So, perhaps you're just a little too paranoid / experienced / virtuous to leave it at that.

Looks like minetest is a game server, so unless you combine its server with other far more sensitive tasks, it's not like there's any dire consequence to unauthorized access.īut that perspective does seem a little naive, doesn't it? If access were to occur, the raspberry pi could probably be compromised, and from there, the IoT devices in the home, other private services, etc are at risk too. Realistically speaking, you can probably assume an internal network is safe enough for inconsequential internal services, if physical and wireless access is adequately controlled. The Raspberry PI is assumed to be internal itself without a public IP or any way to be addressed beyond the local network. You certainly wouldn't want to put an external game server on a network that was also shared by your household. I'm going to assume here that you're intending to serve this internally.