Remote
Posts
Replying to
@kpcyrd@chaos.social
@kpcyrd@chaos.social I think when there's a 1/3rd of the lifetime left is a good rule of thumb for when to start trying to renew. 30 days from expiry for a 90 day cert, 2 days out for a 6 day, etc.
ARI is defined in https://www.rfc-editor.org/rfc/rfc9773.html We have the guts implemented in instant-acme if you want a rust reference, but it's low level and a full fledged client needs to string together the pieces.
Open post
Replying to
@cpu@hachyderm.io
Also you're renewing your certs early, based on some proportion of their total validity period right?
And using ACME, so it's automated and easy to fail-over to a standard's compliant alternative CA, right??
And using ARI so you're informed when you need to re-issue sooner than expected because of a compliance issue, right???
And back-stopping all of the above with monitoring, right????
9
2
0
0
Open post
Reminder that halting issuance is a recommended action during an incident & trustworthy CAs will do it early, until the problem is conclusively identified and remediated.
This happens for both for true "oh-shit" events, and "cross your t's dot your i's" compliance issues and you can't infer which bucket the incident is in just because issuance has stopped.
See
https://wiki.mozilla.org/CA/Responding_To_An_Incident#Immediate_Actions
65
8
48
1
Open post
Replying to
@rustconf@hachyderm.io
@rustconf@hachyderm.io No discount tickets for locals this year? That was a nice perk the last time RustConf was in Montreal :'(
0
0
0
0
Open post
Replying to
@filippo@abyssdomain.expert
@filippo@abyssdomain.expert @dominik@mastodon.honnef.co This is really cool, and a model that I hope catches on! Thanks for blazing a trail for others to follow.
1
0
0
0
Remote instance
hachyderm.io
Open on original server