summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKrzysztof Jackiewicz <k.jackiewicz@samsung.com>2016-08-18 08:29:39 +0200
committerKrzysztof Jackiewicz <k.jackiewicz@samsung.com>2016-08-22 10:40:42 +0200
commit8d70b1ac7f9084bfade4d6fc2126b74887a15e27 (patch)
tree78fd161920d97ba3b169a5be7e8de45433316a2d
parent0e594530adaaf13491176fed6c72fa2df40020b6 (diff)
downloadyaca-8d70b1ac7f9084bfade4d6fc2126b74887a15e27.tar.gz
yaca-8d70b1ac7f9084bfade4d6fc2126b74887a15e27.tar.bz2
yaca-8d70b1ac7f9084bfade4d6fc2126b74887a15e27.zip
Removed rsa padding TODO
RSA_NO_PADDING can be used when message length exactly matches the length of the asymmetric key. As for now no digest can produce matching output so only plain asymmetric operation without digest supports it. RSA_SSLV23_PADDING can be used in asymmetric encryption only. Change-Id: I9f4b84086bf150994f5eb5cc270203cf8834b683
-rw-r--r--src/sign.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/src/sign.c b/src/sign.c
index 2e5fe25..4233c98 100644
--- a/src/sign.c
+++ b/src/sign.c
@@ -131,8 +131,6 @@ int set_sign_property(yaca_context_h ctx,
padding = *(yaca_padding_e *)(value);
- // TODO: investigate whether it's possible to set
- // RSA_NO_PADDING or RSA_SSLV23_PADDING in some cases
switch (padding) {
case YACA_PADDING_X931:
pad = RSA_X931_PADDING;