can we see some code?

[will]

i know this has got to be quite annoying to have all of us so antsy about getting our hands on SM, but I've got a valid question (in my mind anyway).  I've been using YaBB for quite a while, and am now wanting to use it on another site that has an existing user management system which i greatly prefer to YaBB's.  I haven't looked too deeply into merging YaBB into this site, but it isn't looking very easy.  How is user management handled in SM?  is it too much to hope for a PEAR::Auth like interface with some rather generic functions we can override or rewrite?  Is it the same system as YaBBSE?  can you post at least the auth file from SM?  I'm under a bit of pressure from a client to get some boards online, and I need to know if it's worth the effort to mod YaBBSE to work and then transition to SM, or if i need to begin to look elsewhere.

thanks,
will

[will]

lol.. definitely not.  i  just don't want to install YaBB for this client with the intention of moving along to SM when it is available if SM is not going to be compatible with his authentication scheme.

[will]

well how could i possible do that if i dont' know what the SMF authentication scheme is?  if it seems to be better than the one he has in place, then i will likely do that, but I can't make that decision until I know what the SMF scheme is like.

[Metho]

You'll most likely have to wait for [Unknown] to come around and see this as he was the one who wrote the permissions system. Other than that, charter members and devs know about it, but I'd have to say [Unknown] could give you the best and most concise answer.

Methonis

[[Unknown]]

The cookie is pretty much the same as it was with 1.5.4... (this is done for compatibilty.)  serialize(array($ID_MEMBER, md5_hmac($password, 'ys'))) I think.

It's stored in the database as md5_hmac($password, strtolower($username)).  This is done for security.

SSI.php has a "checkPassword" fucntion just for site integration as well.

-[Unknown]