| 14 Mar 2026 |
 m1cr0man | how does this happen? Like is there cert authorities that let you do it OOB? | 01:29:52 |
 hexa | security.acme.defaults.email = "foo" -> "bar" | 01:36:13 |
| hexa | then we register a new account I guess | 01:36:24 |
| hexa | but the regular quiet renews ask for ari and that raises that error | 01:36:41 |
| hexa | for existing certificates that were created under the foo account | 01:36:52 |
 emily | LE don't even store emails any more, right? | 01:37:29 |
| emily | so the email value is just … changing the hash of the account but not anything about the data that actually gets retained on their end? | 01:37:55 |
| hexa | they don't, but other acme providers might | 01:39:33 |
| hexa | a hash change registers a new account, right? | 01:39:49 |
| hexa | so we have certs in store that don't belong to the new account and therefore fail renewal | 01:40:12 |
| emily | right | 01:42:36 |
| emily | I mean… it might make sense to warn if an email is set / omit it from the hash for LE servers, say | 01:43:08 |
| emily | but that is its own migration separate | 01:43:23 |
| 26 May 2021 |
|  @grahamc:nixos.org set the history visibility to "world_readable". | 20:36:34 |
| @grahamc:nixos.org changed the room name to "" from "". | 20:36:34 |
|  Server Stats Discoverer (traveler bot) joined the room. | 20:36:42 |
| @grahamc:nixos.org invited m1cr0man. | 20:36:47 |
| @grahamc:nixos.orgchanged room power levels. | 20:36:52 |
| m1cr0man joined the room. | 20:37:09 |
|  Dandellion joined the room. | 20:38:19 |
| emily joined the room. | 20:43:31 |
| hexa joined the room. | 20:44:30 |
| m1cr0man set the room topic to "Another day, another cert renewal". | 20:46:02 |
|  Matrix Traveler (bot) joined the room. | 20:51:53 |
|  sumner joined the room. | 21:00:03 |
|  andi- joined the room. | 21:03:46 |
|  immae joined the room. | 21:13:02 |
|  hax404 joined the room. | 22:17:28 |
|  l3af joined the room. | 22:39:21 |
| 28 May 2021 |
|  pinage404 joined the room. | 11:07:44 |
