Please make it possible in IPB3 to Convert from IPB to VB WITH Passwords being transfered. (Change password structure)

Right now if people convert from IPB to VB there users have to use the FORGOT password feature in order for their account to work again.

Please make the password system so it works with VB when converted.

Thanks.

Vbulletin would have to change stuff in their software. IPB can import the password from vbulletin just fine

You should ask this to Jelsoft, not Invision.

vb store their passwords in a different structure to ipb so they would have to change that make it work with ipb. As for being able to convert from other forums to ipb this has always been a well supported feature.

Well, IPB could fix this by changing how they encrypt their passwords to match vBulletin, but then that would probably break every existing IPB forum, so that's really not an option. Undoubtedly, that would be the same situation vBulletin would be in. The problem is that you can't un-md5 a hash. So if IPB and vBulletin aren't md5'ing passwords the exact same way, you can't unencrypt one software's password hashes to be able to encrypt them in the style the other one uses.

So until the day someone figures out how to un-md5 any hash (which would be a death blow to any kind of security) then IPB's current method is probably the best that can be done.

unless the password is stored in the db in vb as a un md5'd hash as well as the hash but that defeats the entire purpose.

We are capable of "converting" vb's passwords just fine, despite the fact that we (obviously) store them hashed differently. This is not an issue with our software, it is something Jelsoft's team would need to address. I'm afraid we don't intend to change how we hash our passwords at this time.

We are capable of "converting" vb's passwords just fine, despite the fact that we (obviously) store them hashed differently. This is not an issue with our software, it is something Jelsoft's team would need to address. I'm afraid we don't intend to change how we hash our passwords at this time.

yea not till md6 anyways :P.

yea not till md6 anyways :P.

Even if md6 comes out they are not going to change to it because the old passwords would still be in md5.

Its actually not that hard to convert passwords from another format to ours, as long as we know how they generate the passwords. Almost every forum uses different methods, even MD5 can be done differently with salt.

Do you md5 the password, md5 the salt, concatenate the encrypted salt and encrypted pass and then md5 the whole mess or how about just concatenating the plain salt and plain password, then md5 all of it?

On a side note... Why would you want to upgrade to IPB3 to convert to VB? Did you mean convert from VB to IPB3?

Its actually not that hard to convert passwords from another format to ours, as long as we know how they generate the passwords. Almost every forum uses different methods, even MD5 can be done differently with salt.

Do you md5 the password, md5 the salt, concatenate the encrypted salt and encrypted pass and then md5 the whole mess or how about just concatenating the plain salt and plain password, then md5 all of it?

On a side note... Why would you want to upgrade to IPB3 to convert to VB? Did you mean convert from VB to IPB3?

He probably has plans for the VB4 in the long future. but I think he will be so amazed by IPB3 he will not want to convert. :)

He probably has plans for the VB4 in the long future. but I think he will be so amazed by IPB3 he will not want to convert. :)

"vB4" isn't what I'd call it, I just know it's going to be more like "MySpace 2" even the developers are calling it a social network rather than a forum now, I can handle profiles, but the rest is just bleh... so glad I switched... :ermm:

I laughed at the title. Since when is it the manufacturer's responsibility to make sure you'll be ok if you don't like their software and switch to a competitor?

On a side note... Why would you want to upgrade to IPB3 to convert to VB? Did you mean convert from VB to IPB3?

Oh, they probably expect IPS to change IPB so that "vB's convertor can work with it" since Jelsoft insist that ImpEx will never work with IPB because of "the way IPB stores passwords" (ergo, laziness).