On 5/4/2015 11:42 PM, Tadeusz Struk wrote: > Hi Horia, > On 05/04/2015 06:16 AM, Horia Geantă wrote: >>> int (*sign)(struct pke_request *pkereq); >>>> int (*verify)(struct pke_request *pkereq); >>>> int (*encrypt)(struct pke_request *pkereq); >>>> int (*decrypt)(struct pke_request *pkereq); >> Where would be the proper place for keygen operation? > > This will need to be extended to support keygen. > >> >> AFAICT algorithms currently map to primitives + encoding methods, which >> is not flexible. For e.g. current RSA implementation hardcodes the >> PKCS1-v1_5 encoding method, making it hard to add OAEP(+) etc. >> >> One solution would be to map algorithms to primitives only. Encoding >> methods need to be abstracted somehow, maybe using templates to wrap the >> algorithms. > > So far there is only one rsa implementation in kernel and it is only used > by module signing code. > Later we can add templates or simply one can register "oaep-rsa" algorithm. I am thinking that it would be more logical for "rsa" to represent only the *primitives*, for e.g. RSASP1, RSAVP1, RSAEP, RSADP (in rfc3447 terminology). Then pkcs1_v15(rsa), oaep(rsa), pss(rsa) (i.e. RSAES-PKCS1-v1_5, RSAES-OAEP, RSASSA-PSS encryption and/or signature schemes) would share the primitives implementation, the only thing that would differ being the encoding/padding method. This is similar to symmetric ciphers convention of having the mode defined as a wrapper: we have cbc(aes), ctr(aes), gcm(aes) and not cbc-aes, ctr-aes, gcm-aes. Another thing to consider is that there might be crypto engines which are able to perform only "textbook" rsa. This would allow for the primitives to be offloaded, while the encoding methods would be performed in SW. Thanks, Horia -- 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
