The actual revocation needn't be secure. False revocations are an oxymoron.
The practice around revocations need to be secure of course, but that's more on an engineering problem than a cryptographical.
Can you explain a bit more what you mean by "secure" in the context of "actual revocations"? The oxymoronic nature isn't self-evident enough for me to catch your intended meaning before my first cup of coffee.
Can you explain a bit more what you mean by "secure" in the context of "actual revocations"? The oxymoronic nature isn't self-evident enough for me to catch your intended meaning before my first cup of coffee.