Technology

59116 readers

3397 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

192

Sysadmins slam Apple’s SSL/TLS cert lifespan cuts (www.theregister.com)

submitted 2 weeks ago by misk@sopuli.xyz to c/technology@lemmy.world

82 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] sugar_in_your_tea@sh.itjust.works 2 points 2 weeks ago

Exactly. My "special case" took a little more care, but it works completely fine. Here's my setup:

TCP proxy at edge -> wireguard tunnel using SNI to route to the right service
reverse proxy that handles all TLS for all services on its device (renewals and crypto)
HTTP services behind a firewall that only communicate w/ proxy

I have my router configured to resolve DNS to #2, so I don't need to hit the WAN to access local services over TLS, and it uses the exact same cert as WAN traffic and the browser is happy.

This is about as exotic as I can think of, and it still works just fine for TLS renewals, and it's 100% automated. I do need to leave HTTP open (it only serves acme endpoints, so whatever), but I could also close that down and have the renewal process open that temporarily if needed.

The only special case I can think of is a device that rarely turns on, which is incredibly rare these days (you'd generally have an always-on gateway that uses self-signed certs or something for those devices that stay off).