« Return to Thread: Using RSAES OAEP with a custom padding parameter

Re: Using RSAES OAEP with a custom padding parameter

by Jeffrey Walton-3 :: Rate this Message:

| View in Thread



On Oct 22, 6:37 am, Charles T <charles...@...> wrote:
> I'm attempting to write a wrapper aroung the API defined for the
> trusted platform module. The Design Principles specification from the
> trusted computing group (http://www.trustedcomputinggroup.org/
> resources/tpm_main_specification) states that when using the
> TPM_ES_RSAESOAEP_SHA1_MGF1 encryption type, that " The OAEP encoding P
> parameter MUST be the 4 character string “TCPA”  ".
>
> I use the following code when performing RSAES_OAEP encryption. How
> can I modify it to set the padding parameter to "TCPA"?
I don't believe modifying the padding after the fact will work well
(if at all).

For this, I believe the best course of action is to provide a
TPM_ES_RSAESOAEP_SHA1_MGF1 class. Then ne TPM padding class probably
should probably look a lot like PK_EncryptionMessageEncodingMethod or
OAEP < H, M >,

See http://www.cryptopp.com/docs/ref/annotated.html,
http://www.cryptopp.com/docs/ref/class_p_k___encryption_message_encoding_method.html
and http://www.cryptopp.com/docs/ref/class_o_a_e_p.html.

jeff

Jeff

--
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscribe@....
More information about Crypto++ and this group is available at http://www.cryptopp.com.

 « Return to Thread: Using RSAES OAEP with a custom padding parameter