NodeGoat icon indicating copy to clipboard operation
NodeGoat copied to clipboard

Migration to bcrypt

Open UlisesGascon opened this issue 6 years ago • 14 comments

Context

  • This is part of release-1.5 #148
  • MEDIUM priority task

Tasks

  • [ ] Remove dependency bcrypt-nodejs in package.json
  • [ ] Add dependency bcrypt in package.json
  • [ ] Migrate file app/data/user-dao.js to bcrypt
  • [ ] Validate the instalation with the local test
  • [ ] Add and submit the changes in package-lock.json
  • [ ] Add the primary dependency list to the readme.md
  • [ ] Check that the npm tasks are working as expected
  • [ ] Update the readme.md with the extra relevant info (if needed)

Assignation

  • This tasks is open for assignation, just claim it (as reply to this) and submit your PR ;-)

Important

UlisesGascon avatar Aug 06 '19 06:08 UlisesGascon

Hi all! As i want to get more into FOSS I stumbled upon this project again and saw this issue. I would claim it for now and would be glad to provide the PR by the end of this week, if it's okay? :)

If so, i'll do the migration from bcrypt-nodejs to bcrypt.

PeterWunderlich avatar Sep 23 '19 16:09 PeterWunderlich

@PeterWunderlich thank you for your interest in contributing to the project. Yes, you are very welcome to make the PR. I have assigned it to you 👍

ckarande avatar Sep 28 '19 22:09 ckarande

Thank you, @PeterWunderlich! :-)

UlisesGascon avatar Sep 30 '19 13:09 UlisesGascon

Hey @ckarande & @UlisesGascon, the migration is finished from my part but i have 2 final questions regarding the tasks:

  1. Add the primary dependency list to the readme.md: Shall i add a list of the dependencies (devDependencies exlucded) with a short explanation to the README.md? I would add the list before the "How to Setup Your Copy of NodeGoat" chapter.
  2. I've run into a few problems on my Windows machine executing the npm scripts, as "NODE_ENV" is not a known command for my OS. Usually i use cross-env for convenience. Do you want me to add this, do you have any other suggestions or did I use something wrong? Maybe this could become a new issue? :)

As I'm finished i would create a PR heading to the "OWASP:release-1.5" branch or do you want me to merge elsewhere?

Thanks for your help. :)

PeterWunderlich avatar Oct 01 '19 07:10 PeterWunderlich

Hi @PeterWunderlich!

  1. Don't worry about the README.md dependencies. I will include an script that will autodocument that part for us.

  2. Feel free to add cross-env to add support for windows users.

  3. PR to OWASP:release-1.5 is perfect 👍

Thanks a lot for your support!

UlisesGascon avatar Jan 27 '20 06:01 UlisesGascon

It looks like this task is already assigned and has not been implemented. Would you like me to take it on instead?

jantaylor avatar Jun 02 '21 21:06 jantaylor

@jantaylor sure, feel free to take over.

PeterWunderlich avatar Jun 04 '21 06:06 PeterWunderlich

@PeterWunderlich I've submitted the PR if you want to look it over and give your review. @UlisesGascon, the PR is ready for your review as well.

jantaylor avatar Jun 07 '21 04:06 jantaylor

Hi, I would like to work on this issue if the above PR has not been approved yet.

All that need to be done is to migrate from the deprecated bcrypt-nodejs to bcrypt and to validate the installation with the local tests.

snowkluster avatar Mar 06 '23 11:03 snowkluster

I've pinged Jan in the original PR. Let's see if he is able to follow-up first.

lirantal avatar Mar 06 '23 11:03 lirantal

I've pinged Jan in the original PR. Let's see if he is able to follow-up first.

Ok

snowkluster avatar Mar 06 '23 11:03 snowkluster

Is it alright if I open a PR as I think, I have fixed this issue as well as issue #271 and ran "npm run precommit" and fixed all those errors.

snowkluster avatar Mar 06 '23 14:03 snowkluster

Are there any updates about the PR

snowkluster avatar Mar 07 '23 16:03 snowkluster

@snow-kluster I haven't gotten any indication that the maintainers wanted to merge my PR #237.

jantaylor avatar Mar 07 '23 16:03 jantaylor