And standing in line for the privilege to spend it.

Looks more like a randomly generated password.

Maybe add this line to your post?

Sukko is an open source Android app for creating widgets for home and lock screens.

The maintainers of the big web browsers have pretty strict rules for CAs in this list. If any one of them gets caught issuing only one certificate maliciously, they are out of business.

And all CAs are required to publish each certificate in multiple public, cryptographically signed ledgers.

Sure, there is a history of CAs issuing certificates to people that shouldn’t have them (e.g. for espionage), but that is almost impossible now.

For 3 more months or so, you can’t buy them in april 2026 anymore

Short lifespans are also great when domains change their owner. With a 3 year lifespan, the old owner could possibly still read traffic for a few more years.

When the lifespan ist just 30-90 days, that risk is significatly reduced.

No, these are completely separate issues.

• CRL: protect against certificates that have their private key compromised
• CT: protect against incompetent or malicious Certificate Authorities.

This is just one example why we have certificate transparency. Revocation wouldn’t be useful if it isn’t even known which certificates need revocation.

The National Informatics Centre (NIC) of India, a subordinate CA of the Indian Controller of Certifying Authorities (India CCA), issues rogue certificates for Google and Yahoo domains. NIC claims that their issuance process was compromised and that only four certificates were misissued. However, Google is aware of misissued certificates not reported by NIC, so it can only be assumed that the scope of the breach is unknown.

Source

There are some nameserver providers that have an API.

When you register a domain, you can choose which nameserver you like. There are nameservers that work with certbot, choose one that does.

The only disadvantage I see is that all my personal subdomains (e.g. immich.name.com and jellyfin) are forever stored in a public location. I wouldn’t call it a privacy nightmare, yet it isn’t optimal.

There are two workarounds:

• do not use public certificates
• use wildcard certificates only

The best approach for securing our CA system is the “certificate transparency log”. All issued certificates must be stored in separate, public location. Browsers do not accept certificates that are not there.

This makes it impossible for malicious actors to silently create certificates. They would leave traces.

The allowed transmit power can vary by country, but I doubt any phone will use 1000mW for it’s mobile hotapot.

Because 2.4 GHz has a better range.

6 GHz really makes sense for a hotspot. Typically, both devices will be quite near. And 6 GHz has plenty of channels available for optimal performance.

I think its a completely different use case. MobaXterm is a fancy ssh/rdp tool with some extra features, while rustdesk is an alternative to teamviewer or anydesk - tools for remote support.

Disclaimer: I haven’t used rustdesk yet, I have no need for this use case.

IIRC, you need to “clean flash”.

Yes, that is exactly what I meant.

Personally, I would try to avoid publishing nginx proxy manager’s management web ui to the general public.

Please don’t confuse the nginx proxy manager (npm) with the node.js packet manager (npm). The latter is frequently in the news regarding security vulnerabilities.

There is no content in this post.

@taher12@lemdro.id I see this is your first post, welcome here :) If you need help, feel free to ask.

For selfhosting, I would advise against installing a desktop environment and rather suggest to install a server version without GUI.