Incorrect password hash generated during user creation #30

New Issue

Closed

opened 2021-08-14 19:58:29 +03:00 by Ghost · 2 comments

Ghost commented

2021-08-14 19:58:29 +03:00

Seems like Unix password hash require changed order of salt inclusion during hash generation.

It's required to test both inclusion from the beginning and at the end, and based on the hash comparison - determine, what hash variant is correct

Seems like Unix password hash require changed order of salt inclusion during hash generation. It's required to test both inclusion from the beginning and at the end, and based on the hash comparison - determine, what hash variant is correct

Ghost added the

Under investigation

Bug

labels 2021-08-14 19:58:29 +03:00

Ghost removed the

Under investigation

label 2021-08-23 07:32:45 +03:00

Ghost added this to the Stable Version Release project 2021-09-14 10:20:15 +03:00

inex commented

2021-12-20 16:37:33 +02:00

Owner

Is this still an issue? Password generation works fine nowdays.

Ghost added the

Fixed

label 2021-12-20 19:17:30 +02:00

Ghost commented

2021-12-20 19:18:28 +02:00

Poster

No, it's not an issue anymore. Hashing has been reauthored to work on backend side instead of mobile application, so now this issue is resolved

inex closed this issue

2021-12-20 19:20:45 +02:00

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: SelfPrivacy/selfprivacy.org.app#30

There is no content yet.