Jump to content

Talk:Optimal asymmetric encryption padding

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Untitled

I don't know too much about this subject, so I can't expand it, maybe someone else can? Maybe after I finish my paper about RSA :) 13:32, 6 October 2005 (UTC) — Preceding unsigned comment added by 80.100.146.218 (talkcontribs)

Hmm, yeah, what I don't get is: If this is a block cypher, how come the recipient can read the message after decrypting it with private RSA key? Is the y of the trapdoor-function submitted within the encrypted content? - 62.206.74.26 09:57, 2 January 2006 (UTC)[reply]

SVG by Inkscape seems to loose the arrow ends on lines. That's annoying. --Ozga (talk) 18:18, 5 March 2008 (UTC)[reply]

Requested move

The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review. No further edits should be made to this section.

The result of the move request was: No consensus to move. This has been listed here for ages now, and the request for evidence that a violation of WP:NCCAPS is justified has not been met. (non-admin closure)  — Amakuru (talk) 23:02, 27 November 2013 (UTC)[reply]



Optimal asymmetric encryption paddingOptimal Asymmetric Encryption PaddingOptimal Asymmetric Encryption Padding – This is a very specific implementation of optimal asymmetric encryption padding and it's even capitalized in the article text itself Relisted. BDD (talk) 17:37, 14 November 2013 (UTC) Olathe (talk) 14:50, 2 November 2013 (UTC)[reply]

The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page or in a move review. No further edits should be made to this section.

Update the OAEP standardization covered by this page.

The OAEP standard indicated by this page (PKCSv1.5, I believe) is outdated and replaced by the PKCSv2.2 standard. The page should update to reflect this. The new standard allows for authentication using a secret string, prefixes with 0x00 (which affords some message>modulus protection), and has the nonce and padded message portions reversed, among other changes. See the link below for details. [1] 100.2.188.182 (talk) 05:48, 3 February 2022 (UTC)[reply]

References

  1. ^ "PKCS #1: RSA Cryptography Specifications Version 2.2". {{cite journal}}: Cite journal requires |journal= (help)