Originally created by @oliwel on GitHub (Feb 28, 2024).
The RFC allows a self-signed revoke and as the help says --privkey (-p) path/to/key.pem Use specified private key instead of account key (useful for revocation) I expected this feature is supported.
When I run dehydrated --revoke cert.pem --privkey key.pem the script tries to fetch the account id from the server for the used certificate key which fails for obvious reasons.
Originally created by @oliwel on GitHub (Feb 28, 2024).
The RFC allows a self-signed revoke and as the help says ` --privkey (-p) path/to/key.pem Use specified private key instead of account key (useful for revocation)` I expected this feature is supported.
When I run `dehydrated --revoke cert.pem --privkey key.pem` the script tries to fetch the account id from the server for the used certificate key which fails for obvious reasons.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @oliwel on GitHub (Feb 28, 2024).
The RFC allows a self-signed revoke and as the help says
--privkey (-p) path/to/key.pem Use specified private key instead of account key (useful for revocation)I expected this feature is supported.When I run
dehydrated --revoke cert.pem --privkey key.pemthe script tries to fetch the account id from the server for the used certificate key which fails for obvious reasons.