2

Closed

Login Fails When EncryptLoginPassword set True in 2.3.9074.18820

description

I installed 2.3.9074.18820 today from scratch and found I was unable to log in. On IE7 there is no error on the client and the log file displays an "Audit: SecurityFailure Longon with username XXX from IP XXX" message. On IE8 there is an error in the javascript "object expected" on the line "password = net_md5(password); // this makes it superchallenged!!" which in generated in the codebehind for the login box usercontrol: https://dasblog.svn.codeplex.com/svn/trunk/source/newtelligence.DasBlog.Web/LoginBox.ascx.cs. Debugging on the client shows net_md5 is undefined.
 
Notably, I have never had dasBlog installed before so I am wondering if the script that defines net_md5 is not being included/executed for first timers? Setting EncryptLoginPassword false (which omits this script) allows me to log in fine. Also, I can login OK from Live Writer regardless.
Closed Apr 28, 2009 at 5:10 AM by tomwatts
This issue is closed, the similar issue reported by Tom Watts is peculiar to his installation also, and not a dasBlog issue.

comments

tomwatts wrote Apr 28, 2009 at 1:27 AM

I don't have time to do much else, but I can confirm this is a real problem with 2.3, in fact it appears the configuration menu application does edit the password regardless of Encription or not. Of course you can edit the file manually i the interim, but not from the dasBlog GUI.
Tom Watts

AlexanderGross wrote Apr 28, 2009 at 1:47 AM

Is https://dasblog.svn.codeplex.com/svn/trunk/source/newtelligence.DasBlog.Web/scripts/md5.js included somewhere in login form (<script> elemtent)? If so, can you download it directly using your browser and wget? What's the file's content type as reported by the server?

whirly wrote Apr 28, 2009 at 3:29 AM

OK I've cracked it. The dasBlog code is fine. The problem was the scripts directory was empty on my server! Why? Because I unzipped from a network share. IE Enhanced Security kicked in and silently (GRRR!) prevented the .js files from being extracted. No error messages, nothing! Copying the zip to the C: drive, unblocking and then extracting fixed the problem. This issue can be closed.