

I’ve read the article and I couldn’t see any implication of Seagate. I’m not saying anything about your story, shame on Seagate, but I don’t see what that has to do with the scandal in the article.
I’ve read the article and I couldn’t see any implication of Seagate. I’m not saying anything about your story, shame on Seagate, but I don’t see what that has to do with the scandal in the article.
With Wireguard there’s really no reason.
Well, that’s kinda of a personal choice. If somebody needs to have services accessible by someone else besides him, that service can’t be behind a VPN (let’s face the truth: we know that we can’t ask all out relatives and friends to use a VPN).
No no, what I meant is that if I connect to your server without the certificate installed don’t I just get the warning and I can still get through?
I don’t know much about certificates, but doesn’t that just alert the browser that the certificate is not trusted and you can decide if keep going or not?
I’ve never virtualized OpenWRT, but with hardware passthrough I don’t see why it shouldn’t work.
I use SMTP2GO (with my own domain) with the free plan (1000 email per month) that’s way over a selfhoster needs.