diafygi / diafygi/webcrypto-examples

Why are RSA APIs marked as "not recommended"?

Open
#50 0 comments 7 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
1.7k
Forks
191
PR merge metrics
No merged PRs in 30d

Description

Hi, thanks for this, this has been my #1 frequently visited website in the last couple of months.

I have a question. When I look at the demo page at https://diafygi.github.io/webcrypto-examples/ I understand why some of them are "not recommended" and colored out as red, but don't understand why all the RSA APIs are marked as "not recommended".

I don't think there's anything wrong with RSA algorithms, in fact some people don't trust ECC algorithms because of a possible NSA backdoor and also the fact that it could be more vulnerable to quantum computing, etc. I think it's all subjective, and I personally plan on using RSA for my application instead of ECC for these reasons. (My application is not resource constrained so don't really need the keys to be short)

I was wondering if I'm seeing this wrong or if there was a reason behind this decision. Thank you!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the demo page linked in the issue and inspect how the RSA APIs are labeled as “not recommended,” then look for the source or documentation that defines those labels. Done means the rationale is clearly documented or the labels are updated to match the project’s stated guidance.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
cryptography, security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.