Do you know why that would be a positive evolutionary trait? Clearly, if they try to retract it, at some point in the history they must have been able to do so.
Do you know why that would be a positive evolutionary trait? Clearly, if they try to retract it, at some point in the history they must have been able to do so.
Valid reason to bring it back.
Why would it be 200? Imo it should be either 400 or 401.
You’re right, my bad.
OP’s security concern is valid. Different CAs may differ in the challenges used to verify you to be the domain owner. Using something that you could crack may lead to an attacker’s public key being certified instead.
This could for example be the case with HTTPS verification (place a file with a specific content accessible through your URL) if the website has lacking input sanitization and/or creates files with the user’s input at an unfortunate location that collides with the challenge.
This attack vector might be far-fetched, but there can certainly be differences between different signing authorities.
Not quite. Picture an immutable map in your programming language of choice (something like const map). You cannot reassign the map object to a new one, but you totally can change its keys and values.
Do you still need help with docker?
An ee-mail? Do I need to go to the post office for that?
While I believe they really could, that would be really stupid. Is creating a hotspot with your phone suddenly also not allowed? Because that’s all it essentially is.
Yet the review time is exponential with the size.