i'm pretty sure the way b2evo has done their security is via hashes. Meaning that the passwords get hased and cannot be decrypted, and the security works by comparing the hash of the current password with the one to compare with... Well this is the way most services handle it... Because of this it would not be possible.

You could use the LoginAttempt to store the plain text password (which gets passed as param) in a PluginUserSetting.

But that would require, that you invalidate all user sessions first (could be done by hooking SessionLoaded and see if you have a cleartype PluginUserSetting), so the users have to log in again (and you can catch the raw password) and, of course, the clear password would be stored in the evo_pluginusersettings DB table.

i have no idea what the crap you just said. Is there anyway for you to put that in layman's term or give an example?

We are both saying that it is possible... but it would be 'unsecure'.

And it would be a lot of work for the developer.