Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

700

I have ran a kluged together thing like this for my homelab for years. Maybe it's time to rebuild.

Archive: https://archive.today/3zlbA

From the post:

>The files that this command generates, cert.key and cert.crt, could be passed to a web server, for example, and it will work fine; that is, all the connections made to that web server will be properly encrypted. The only problem with using this certificate, however, is that our browser doesn’t trust it, because it has not been signed with a certificate authority that the browser trusts.

I have ran a kluged together thing like this for my homelab for years. Maybe it's time to rebuild. Archive: https://archive.today/3zlbA From the post: >>The files that this command generates, cert.key and cert.crt, could be passed to a web server, for example, and it will work fine; that is, all the connections made to that web server will be properly encrypted. The only problem with using this certificate, however, is that our browser doesn’t trust it, because it has not been signed with a certificate authority that the browser trusts.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (2).
[–] • 0 pt

They are mostly for internal use. I have automation that would allow me to push it to all of my internal stuff.

yeah, I know, No real reason for it for most people or even me but it's something that I wanted as a project. You do you though.