# Migrated password hashes support

**URL:** <https://meta.discourse.org/t/migrated-password-hashes-support/19512>\
**Category:** Plugin\
**Created:** [9월 1, 2014, 5:51오후 UTC](https://meta.discourse.org/t/migrated-password-hashes-support/19512 "2014-09-01T17:51:25Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![michaeld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/michaeld/32/1594_2.png) [@michaeld](https://meta.discourse.org/u/michaeld)\
**Post date:** [9월 8, 2014, 3:42오전 UTC](https://meta.discourse.org/t/migrated-password-hashes-support/19512/10 "2014-09-08T03:42:22Z")

</div>

Yeah, I (of course 😃 ) actually thought about that, but decided not to, for a few reasons:

- this would require naming all those non-standard algorithms, introducing a new kind of semi-standard, which requires more thought that you’d expect. For instance, I would be naming the `md5(md5(pass) + salt)` method `vbulletin` and two months I’d find out that forum X uses the same algorithm, and we would end up with something very counter-intuitive.
- ease of parsing. Your gist had a nasty bug in `salt, password_hash = self.custom_fields['import_pass'].split(':')` because `salt` can contain a colon. I turned them around and used the limit parameter in this case but this made me decide to treat all crypted password strings as an opaque string.

---

_[View the full topic](https://meta.discourse.org/t/migrated-password-hashes-support/19512)._