DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Encrypted is obsolete

 16 Replies
 4 Subscribed to this topic
 28 Subscribed to this forum
Sort:
Page 2 of 2 << < 12
Author
Messages
Growing Member
Posts: 47
Growing Member

Thanks Sebastian.

Sounds like there is scope there for a utility to convert all encrypted password into a hash.  If DNN already checks both, seems like a logical thing to do when DNN detects a change in the web.config from encrypted>hashed.

This would improve the security of the platform I reckon.  Does anyone know if such a thing exists, or perhaps a 3rd-party tool?

Veteran Member
Posts: 546
Veteran Member
MVP
MVP
You're an MVP!
AFAIR DNN Corp. wrote such a Utility to migrate their own website years ago, but it was not ready to be released for the public. The easiest Workaround would be a SQL script, which sets the flag for requiring Password reset for all users upon next login.
Advanced Member
Posts: 159
Advanced Member
MVP
MVP
You're an MVP!
I'm not aware of any freely available mechanism to do this. Unfortunately, I don't think Sebastian's easy workaround will be effective. As far as I recall, once a password is marked as encrypted, it continues to be encrypted even if the setting is changed. Only new accounts get hashed passwords once the main setting is changed to encrypted. There will need to be some process running on the web server to decrypt each password and update them to the hashed format.
Veteran Member
Posts: 546
Veteran Member
MVP
MVP
You're an MVP!

Of course, the password remains encrypted, until the user updates it. If DNN password format is set to "hashed", the new password would be stored as hashed value.

Veteran Member
Posts: 1182
Veteran Member
MVP
MVP
You're an MVP!
Posted By Sebastian Leupold on 06 Sep 2019 11:43 AM

Of course, the password remains encrypted, until the user updates it. If DNN password format is set to "hashed", the new password would be stored as hashed value.

I could not reproduce this. I tried to change the password for a user who had PasswordFormat=2 in the aspnet_membership table, and after the change, it still was 2. I created a new user, and the password format is 1 for this user. So changing the password does not "upgrade" the password format.

Happy DNNing!
Michael

 

 

Michael Tobisch
DNN★MVP

DNN Connect
Veteran Member
Posts: 546
Veteran Member
MVP
MVP
You're an MVP!
Maikl,
when updating the password, DNN uses the format value from web.config, not the current membership entry.
Veteran Member
Posts: 1182
Veteran Member
MVP
MVP
You're an MVP!
Sebastian,

I could not reproduce that. The password is still encrypted and not hashed after changing it (the value of the field PasswordFormat is still 2). Only new users get the PasswordFormat 1 (hashed).

Happy DNNing!
Michael

Michael Tobisch
DNN★MVP

DNN Connect
Page 2 of 2 << < 12

These Forums are for the discussion of the open source CMS DNN platform and ecosystem.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved