-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP Signatures #170
Comments
Hey! so for information regarding my http-signatures crate, for encoding, it needs a Ring 13.5 RSAKeyPair type, and for decoding it needs a PKCS1 DER encoded Unfortunately, it looks like the only crate in the ecosystem that can generate RSA Keypairs is OpenSSL, which exports to It's likely that when using my crate, you'll need to do some translation, because I think Masto and friends use For Aardwolf, I'm storing keys as I should really put some of this in the http-signatures docs |
@asonix in |
That's a |
You can get that from an |
ACTUALLY I should have created a trait like pub trait IntoVerifyType {
type Error: Fail;
fn into_verify_type(&self) -> Result<Vec<u8>, Self::Error>;
}
impl IntoVerifyType for Rsa {
type Error = ErrorStack;
fn into_verify_type(&self) -> Result<Vec<u8>, Self::Error> {
self.public_key_to_der_pkcs1()
}
} and then it can be extended by consumers of my library, or by others in the future |
Alright, with the CreateKey::from_openssl_rsa(Rsa<Private>, ShaSize)
AsVerifyKey::as_verify_key(&self) // for Rsa<Public> and Rsa<Private> |
Need to implement keypair generation, wire into the
publicKey
field in actors, and actually do the signature stuff (probably with https://github.com/asonix/http-signatures).The text was updated successfully, but these errors were encountered: