Max

Thanks :D

Genocide, xinjiang, camps,the, china

(Excellent tankie comment according to science)

We need /c/infuratingasfuck

In that case, you’re better off just using the VPS machine as port forwarding port 443 to your home machine’s wireguard IP address and handle the SSL/TLS termination on the home machine.

This is what I would like to do! I was trying to handle the SSL termination 'automatically' by simply forwarding the connections to 443 of my machine's wireguard IP using nginx, but I did not manage to get it to work. That's when I found that I need to use something like 'stunnel' to handle the SSL termination. But I think that you may be suggesting an even simpler method of using port-forwarding instead of the reverse proxy. I am not sure how to achieve that, I will look into it using these terms.

ssh tunnels

There are so many concepts to learn about! But if the SSH tunnel improves the the available useful bandwidth compared nginx/wireguard, it might be worth looking into it too. Thanks!

Thanks a lot! This is kind of the configuration that I have converged to, with nginx and WireGuard. The last thing I need to set up correctly is for the SSL handshake to occur between the client and my home server, and not between the client and the internet-facing VPS, such that the information remains encrypted and unreadable to the VPS. The two strategies that I have seen can do this is SNI routing with nginx or to use stunnel. I still have not been able to set up either!

That's the next topic then. Thank you

Oh, cool! I have managed to do it with the Wireguard tunnel! I set up a tunnel and use the nginx proxy_pass to redirect through the tunnel. It is pretty nifty that I don't even need to port-forward!

My next step is: in my current configuration, the SSL handshake occurs between the VPS and connecting client. So the VPS has access to everything that goes through... I need to figure out how to hand-shake through the tunnel such that the VPS does not get the SSL keys.

Thanks a lot for your suggestion!

Thanks! Wireguard was suggested as a VPN, and I am currently playing with that.

From what I have learned today, I think that Wireguard Tunnel is what I want!

First I was able to use nginx as a reverse proxy to route the information from my home network through the VPS. But with this approach the client would do the SSL handshake with the VPS, and then the VPS fetches information from my home network via HTTP. Since there is no encryption layer between my VPS and my home network, I suppose that the flow of information between my home server and the VPS is insecure.

Then, I need to establish some form of encrypted connection between my home server and the VPS... And that is where the Wireguard Tunnel comes in! This tunnel allows me to transfer the information with encryption.

I am still reading and setting it up, but yeah, I'm liking this, thanks!

Good luck! I look forward to your healthy grain spawn pics!

Ooh wow, yeah that's a big pressure canner! I work with a smaller pressure cooker - the kind used for preparing meals (a 6L and a 10L, 12 PSI). You probably don't want to use such a big canner for cooking the grains. I would just boil them them in a regular pot instead.

Usually the procedure is separated into the 'hydrating' step and then the 'sterilization' step, because this way you can ensure that the grain is hydrated to the right amount, that it is evenly hydrated, and that the surface is dry. It is possible to mix the dry grains and the right amount of water inside of the jar and then just let the grains hydrate while you pressure cook them. Some people online say that they use this method, but I did not get great results when I tried it.

For the sterilization you really should use that pressure canner. Placing the jars inside the canner and running it at 15 PSI for 90 minutes (after venting for 10 - 15 min) is enough to sterilize grain.

But what you have is indeed a big canner... If you don't want to use it, you can try to simply sterilize by boiling both the grain and the jar. In that case I would not worry about drying the grain at all - the grain would go straight into the jar while both are still hot. Then you have a reasonable chance of not having contaminants. With this procedure you might have grains that are too wet and heat-resistant endospores of bacteria that can survive boiling, so you may get bacterial contamination. But is not a certainty - many times it works fine. Do what's simplest, and if your contamination rate is above the level that you find acceptable then you can take steps to improve your process.