[PATCH] OAEP support

Werner Koch wk at gnupg.org
Tue Jun 30 12:34:09 CEST 2009

On Tue, 30 Jun 2009 05:53, ueno at unixuser.org said:

> The attached patch adds OAEP padding support to libgcrypt.


> - Before encryption/decryption, it reads necessary parameters from
>   `flags'.  For example,
>   (data
>     (flags oaep hash sha1 label "test")
>     (value #11223344556677889900AA#))

I would like to keep the flags list a real flags list without
parameters.  Would anything speak against:

     (flags oaep)
     (hash sha1)
     (label "test")
     (value #11223344556677889900AA#))

I can do this change if you agree.

> - After decryption, it stores the decoded value as a `decoded' token
>   instead of `value', unlike other encodings (`raw' and `pkcs1').  This
>   is for backward compatibility.  For example,
>   (decoded #11223344556677889900AA#)

That is so that the caller can easily see whether OAEP has been used and
that the code needs to be adjusted, right?

I'll look closer at the patch in the next days.



Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.

More information about the Gcrypt-devel mailing list