RSA SIP #35
RSA SIP #35
Conversation
There was a problem hiding this comment.
The most important part is the specification. We need to write that we have a check that the RSA public key is known to the contract (you implied it in other sections but it should be specified).
Also write down which specific padding scheme should be used (PSS) without "or".
When I read the Specification section it sounds more like some preliminary intro to RSA and crypto. This is not the point of this section. In general I don't think this should be in the SIP.
It should be concise and give clear instructions to the implementor. Usually with pseudo-code but not necessarily.
For example in one line you can write that we use a 2048 bits key with PSS. In another line write that we have to be compliant with standards (and link to NIST) and that would be enough.
sips/rsa_message_authentication.md
Outdated
| The following security and design considerations should be thoroughly addressed: | ||
|
|
||
| 1. Key Length and Security: The security of RSA encryption is highly dependent on the length of the key used. For instance, shorter keys are more vulnerable to brute-force attacks. The [US National Institute of Standard and Technology (NIST)](https://www.nist.gov) approves a minimum of 2048-bit RSA keys. Check the first table of section 1.5 of their [Security Policy](https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp4172.pdf), released in 2023 July, for this reference. | ||
| 2. Padding Schemes: RSA signatures require the use of padding schemes to ensure security. Poorly implemented or outdated padding schemes can expose the system to padding oracle attacks, where an attacker can gain unauthorized access to encrypted data. Employing secure padding schemes, such as PKCS#1 v1.5 or PSS, is essential to prevent these vulnerabilities. |
There was a problem hiding this comment.
write down which exact specific padding scheme is used
|
Great! |
No description provided.