• 0 Posts
  • 25 Comments
Joined 2 years ago
cake
Cake day: April 10th, 2024

help-circle
  • Oh certificates are so much fun and you have so many options. From fairly easy to mindboggling complex.

    Your current solution is OK if you keep in mind security implications of distributing certs using scripts.

    It is not entirely clear where you do your tls-termination but it sounds like that is the Caddy reverse proxy so that is where your certs should be.

    Placing them in a location like /etc/ssl/example_com/ as fullchain.pem and privkey.pem is probably easiest. Make sure access rights are appropriate. Then point Caddy at them and it should work. I have no experience with Caddy itself though. If Caddy runs in Docker be sure to map the certificates into the container.

    Mind that in this scenario the certificates are only on the Caddy server, connections from the reverse proxy to the services is unencrypted over http. You can’t easily use the LE certificates on the services itself without some ugly split-horizon DNS shenanigans.

    Alternatively you can set up a PKI with certificates for your services behind the reverse-proxy for internal encryption and do public tls termination in the proxy with Let’s Encrypt.













  • It is a nice look into the switch from a perspective of a windows user. But since he is experimenting there is a also a lot of bad choices or wrong information.

    He gripes about things not going smoothly while replacing his whole desktop environment (when was the last time you replaced your explorer.exe?).

    And clamping to old ways of doing things. Which is understandable but would go a lot better with a little bit of guidance. Why force Chrome while Firefox was probably pre-installed or Chromium also works. Using Filezilla while Dolphin can probably do it in an integrated way. Using Notepad++ while Kate probably covers most of his use-cases.

    This doesn’t invalidate his experiences but it does indicate a resistance to switch.

    There is some valid criticisms as well though. The docking station that bugs out or KDE Connect that is confused. We can improve those things, but hardly force Logitech to bring their (horrible) software suite to Linux.

    Maybe he should give it another few weeks to actually feel that while his old ways might not transfer over 1:1 the new ways give him a lot more power.