You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I accidently tried to update a user's password in Snap 0.11.2 with saveUser (user { userPassword = Just (ClearText "...") } )
instead of using the encrypted password.
The JSON backend throws the error "ClearText passwords can't be serialized into JSON" and truncates the users.json file at the location where the encrypted password would have been written.
The text was updated successfully, but these errors were encountered:
Sounds like laziness biting us in the neck here. We need to move that check up to before anything is written to disk.
On Apr 13, 2013, at 6:57 AM, Daniel Lichtenberger [email protected] wrote:
I accidently tried to update a user's password in Snap 0.11.2 with
saveUser (user { userPassword = Just (ClearText "...") } )
instead of using the encrypted password.
The JSON backend throws the error "ClearText passwords can't be serialized into JSON" and truncates the users.json file at the location where the encrypted password would have been written.
—
Reply to this email directly or view it on GitHub.
I accidently tried to update a user's password in Snap 0.11.2 with
saveUser (user { userPassword = Just (ClearText "...") } )
instead of using the encrypted password.
The JSON backend throws the error "ClearText passwords can't be serialized into JSON" and truncates the users.json file at the location where the encrypted password would have been written.
The text was updated successfully, but these errors were encountered: