hashpass | A simple password manager with a twist | Identity Management library

There's too much hashing here.

When registering a user you store the unhashed user name and the password hashed with password_hash()

When logging in you use the unhashed user name to recover the hashed password for that user, then use password_verify() to compare the unhashed password the user has given you with the hashed password you stored.

password_hash() adds a random salt to the password and stores the salt and the generated hash in the resulting string. Even if you hash the same password twice you'll get a different result each time.

You should really look at the documentation page that describes inserting on belongsTo relations.

In the first example you are simply creating a user record. In the second one, if you say the user id is null, it is probably because the value of newIdUserEntry was null (have you debugged that?) or maybe the field name is not matching what you declared in the model.

Anyway, I think the doc page I mentioned has exactly what you need!

I'm pretty sure this is happening because your handler continues after sending a response, therefore attempting to modify a response after it's already been sent.

Keep in mind, it could be how you are using the loginUser function. If you wouldn't mind updating your question showing us how you are using it, that would be super helpful!

There are a couple things that come to mind; 1. You may need to add a return statement somewhere, like on line 10/11 for example 2. You could also wrap the code after the first if statement inside an else statement to see if that changes things.

At the end of the day, I'm pretty sure your code is continuing after sending a response, which is why you see that error.

Using your own hash function for authentication isn't as straight forward as implementing a custom hash function and dropping it in place.

The entire process is more involved.

First, you need to create a Hasher class that implements Illuminate\Contracts\Hashing\Hasher interface.

The image url needs point to a location where the image is served by the backend. You probably don't see the image when you navigate to http://localhost:3000/user/account/frontend/public/uploads/1621968408663.jpg because it doesn't exist at that location.

First, localhost:3000 is your frontend so you need to change that to point to your backend: localhost:5000.

Second, you're serving the uploads folder at the /uploads route so everything inside that folder will be available at http://localhost:5000/uploads/.... Therefore you should see the image if you navigate to http://localhost:5000/uploads/1621968408663.jpg.

So we need to go from:

http://localhost:3000/user/account/frontend/public/uploads/1621968408663.jpg

to:

http://localhost:5000/uploads/1621968408663.jpg.

When you save the user in userRoutes.js you set User.path to req.file.path which ends up being uploads/1621968408663.jpg. So far so good.

In AccountPage.js you set image source with which is essentially . This is where things go wrong. Since this is a relative url, the string is appended to URL on the current page.

To fix the issue, change the image source to:

first of all you can't upload image like this because you send regular http request if you want to send iamge you need to follow this steps

in the frontend you need to send the request with form data for more info read this blog from mdn what is formData mdn you can do something like that with axios append all of the req body to the formData and add it to the axios add multipart/form-data header

Use https://www.npmjs.com/package/nedb-promise

so you can use await for database queries and you can change your code like this -

The problem is that you take input of user for chosen account password then you append splitter and random generated password then '/n'. After that you encrypt this var using fernet. This method will work to view your first password since with first password you read and decrypt whole file but not with multiple encrypted passwords since each var encryption is unique (having different IV) which means that to decrypt all the passwords you will need a way to signal the end of an encrypted password and beginning of another encrypted password so that you pass to ferent the correct ciphertext with correct margins. This can be done by simply adding --END OF PASSWORD-- after each encryption write to password file. Then during reading of passwords you can just split pass file on these margins and pass result to fernet.

NOTE: dont use this code as your password manager since although you encrypt your passwords you are leaving your master password in mykey.key unencrypted which makes this totally useless.

I would console.log the new password hash getting saved to the database and then console.log the hash when you try to log back in (in step 3). See whether they're the same or not.

Then have a look at these lines in particular:

1. In POST /userlogin request handler: