Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Is There A Way to Cature Or Verify SQL Login Passwords Expand / Collapse
Author
Message
Posted Wednesday, February 20, 2013 12:37 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 12:05 PM
Points: 892, Visits: 1,559
We have an outside vendor who is using a SQL Server Login & Password we created so I already know the password. What I'd like to be able to do is verify if that is the password they are using when they try to connect. Why not just ask them to verify the password? Because the vendor swears they are using the right password and yet they can't connect but we can using the exact same name & password.

The password contains a lower case letter L which is easy to confuse for a number 1 and so I believe that they are using the wrong characters in the password but I have no way to verify it and they swear they are not. I can see via my SQL Logs that they are attempting to connect and failing (password error) but I don't see away to verify the password they are actually using. Is there a way to do this even if its hashing the password and then comparing that to a hashed or encrypted value. I know you can use sp_help_Revlogin to create the DCL necessary to re-create a login with the same password without knowing that password so I thought that perhaps the same could be applied when trying to capture login info as users connect.


Thanks


Kindest Regards,

Just say No to Facebook!
Post #1422250
Posted Wednesday, February 20, 2013 1:18 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 5:35 PM
Points: 866, Visits: 7,470
You could always change the password to what you think they are using and have them try it again. If it works, you have your answer.



And then again, I might be wrong ...
David Webb
Post #1422277
Posted Wednesday, February 20, 2013 4:31 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 12:05 PM
Points: 892, Visits: 1,559
David Webb-200187 (2/20/2013)
You could always change the password to what you think they are using and have them try it again. If it works, you have your answer.


I actually gave some thought to doing that but then I loose the ability to say "Nothings has changed" betwen when they could not get connected and when they coudl.

This has cost me a lot of reasearch hours, hours that were wasted simply because some web/it admin was unwiling to believe that maybe, just maybe there was something in his setup that was not updated and therefore the roblem was clearly on my end as the DBG (Database Guy).

Thanks


BTW - Since I first posted this has been reoslved and what do you know they magically started getting connected with no changes being made on the DB side. Of course no on is admiting to any incorrect passwords or other login info.


Kindest Regards,

Just say No to Facebook!
Post #1422352
Posted Wednesday, February 20, 2013 4:46 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 5:35 PM
Points: 866, Visits: 7,470
I'm glad it got resolved. Because those passwords don't travel in clear text anywhere that I know of, you might have to get a sniffer and compare the successful and unsuccessful login packets. The password hashes sent from the client might be the same, but I'd confirm that from two succesful clients before I'd bet the farm on it.



And then again, I might be wrong ...
David Webb
Post #1422354
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse