PowerConnect 3448 authentication bug

Thanks for reporting this problem.  That's a good catch.  I have notified my group of the problem.  We will try to have it corrected in future releases.  I believe I understand what's happening:

• When you create the user with "username testid password passw" without the privilege level it actually created a user with a default level of 1.
• Then when you run the command "username testid level 15" you actually are not just changing the level but instead you wiped out the password (since you didn't specify one) and changing the permission to level 15.
• The reason you see an encrypted password is because even a "blank" password is encrypted in a way so you see that regardless of whether you created a password or not.  For example, if you had created just a user without password you will still see that user showing up in the configuration with an encrypted password (basically a special encryption that tell the software that the password is in fact blank).

We will also put this information in our release notes.  So in fact, if anyone else is reading this, please make sure you always define the user to include password and user level on one single line.  Do not set the level without specifying password otherwise the password will be blanked.

Thanks again for catching this user interface problem.

Cuong.