That's a very roundabout way of saying "fuck you, got mine". Also trying to justify splitting apart families and leaving literal babies in cages to fend for themselves is messed up.
I assume the problem is that most domains don't have DNSSEC. So if you can MITM the SMTP stream you can MITM the DNS request.
Look into vendor.js for patching about:config. I know Arch has one for sure in their package.
I'm also a yearly(-ish) donor and also find it a bit concerning considering they did have a fire in the building 4 years ago. Archive Team have the INTERNETARCHIVE.BAK[0] project. I think they're in need of more disk…
You can issue/renew via DNS. I have a bunch of valid certs for domains that only resolve internally using this method. I believe the plan for wildcard certs is to only support DNS-01 challenges.
They're also fingerprinting every user. I noticed because it caused Firefox to hang for over a minute.
Actually you can run your own FF Sync server.
That's a very roundabout way of saying "fuck you, got mine". Also trying to justify splitting apart families and leaving literal babies in cages to fend for themselves is messed up.
I assume the problem is that most domains don't have DNSSEC. So if you can MITM the SMTP stream you can MITM the DNS request.
Look into vendor.js for patching about:config. I know Arch has one for sure in their package.
I'm also a yearly(-ish) donor and also find it a bit concerning considering they did have a fire in the building 4 years ago. Archive Team have the INTERNETARCHIVE.BAK[0] project. I think they're in need of more disk…
You can issue/renew via DNS. I have a bunch of valid certs for domains that only resolve internally using this method. I believe the plan for wildcard certs is to only support DNS-01 challenges.
They're also fingerprinting every user. I noticed because it caused Firefox to hang for over a minute.
Actually you can run your own FF Sync server.