padding/trimming to make like node crypto
- Dominant language
- JavaScript
- Stars
- 28
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
I've been working with des-cbc and des-ede-cbc and I have learnt that the cipher/decipher functions in this library don't work as I expect when compared to node crypto (I'm using v10+).
There is a lot to examine to reproduce the bug, and it is potentially a browserify issue not a des.js issue.
There is a commit linked below where you can see how these differences are worked around. Scroll down to the bottom for the comments on the two .ts files.
Question is, is this des.key, node crypto, or browserify that should "be fixed"? Maybe it is none of the above??
https://github.com/dcdc-io/node-gp/commit/f8b9672f3b5b105b4710c0952b984e83026c8bf1
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the linked commit f8b9672f3b5b105b4710c0952b984e83026c8bf1, especially the comments on its two .ts files, and compare the des-cbc and des-ede-cbc behavior with Node crypto v10+. Reproduce the padding and trimming differences, then determine whether the discrepancy belongs to des.js, Node crypto, or browserify before defining a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100