Implement browser getRandomValues without depending on crypto
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- cryptography
Research direction
Start by reviewing this package's browser getRandomValues implementation and the linked crypto-browserify discussion. Trace how randombytes is selected in browser mode and how the crypto-browserify fallback creates the reported circular dependency. Done means a supported implementation works in the described non-browser JavaScript VM without relying on a native crypto implementation.
Written by the indexing model from the issue text.
Description
This is based on this discussion
TL;DR: I propose having an implementation of getRandomValues that does not depend on a native implementation of crypto.
I am having an issue with bundling my code and running it in a non-browser environment, using modules that depend on crypto, which depends on randombytes' implementation of getRandomValues. If I bundle my code in "browser" mode, I get the error 'Secure random number generation is not supported by this browser.\nUse Chrome, Firefox or Internet Explorer 11'.
If I don't bundle it in browser mode but force browser fallback for crypto-browserify (which is necessary in my use-case, the javascript VM I'm using does not implement crypto), then I get a circular dependency and getRandomBytes is never implemented.
Is it possible to implement it in this package? If not is there any particular reason? And can I help in some way?
- Dominant language
- JavaScript
- Stars
- 102
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from browserify/randombytes
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
browserify/randombytes#40 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
browserify/randombytes#38 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
browserify/randombytes#36 · 2 comments · 6 reactions ·
-
Broken on SSR Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
browserify/randombytes#33 · 2 comments · 1 reaction ·
-
remove phantomjs Open
Difficulty 1/5 Under an hour Newbie friendliness 38/100
browserify/randombytes#26 ·
All issues in browserify/randombytes
Similar issues
-
bug customer-eng Durable Agents Inngest status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-cao#13475 ·
-
[BUG]: "Clear All" in Settings doesn't clear the saved analysis, old data comes back after reload Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
AOSSIE-Org/OrgExplorer#253 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
oxc-project/oxc#26944 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100