Tadeusz Struk <tadeusz.struk@xxxxxxxxx> wrote: > > Ummm... Possibly. Is that how it's used? > > > > warthog>git grep pkcs1pad -- Documentation > > warthog1> > > Yes, no docs. Sorry. Can I suggest you at least stick a quick usage summary in the banner comment at the top of the file? > > Anyway, the problem I have with this is that I want to get that knowledge > > out of the asymmetric key in-software public key subtype. It knows "rsa", > > "dsa", "ecdsa", ... because that's all the OIDs tell it. > > Rigth, for now the public_key would need to build the full algorithm string as > follows: > > vsprintf(name, "pkcs1pad(%s, %s)", pkey_algo_name[sig->pkey_algo], > hash_algo_name[sig->pkey_hash_algo]); Does this apply to anything other than RSA? > Do you plan to add more padding schemes later? No plans to, but one never knows. I'm *assuming* that OID_rsaEncryption and OID_sha256WithRSAEncryption, for example, must implicitly specify the padding scheme (RFC4055 suggests I'm right in this assumption). We might have to suppose RSASSA-SSP at some point. > Yes, I can start woring on a subsequent patch based on your changes in > http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-rsa > Is that ok with you? Sure. David -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
