SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Is There A Way to Cature Or Verify SQL Login Passwords


Is There A Way to Cature Or Verify SQL Login Passwords

Author
Message
YSLGuru
YSLGuru
SSCarpal Tunnel
SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)

Group: General Forum Members
Points: 4356 Visits: 1667
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!
David Webb-CDS
David Webb-CDS
Hall of Fame
Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)

Group: General Forum Members
Points: 3994 Visits: 8586
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
YSLGuru
YSLGuru
SSCarpal Tunnel
SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)SSCarpal Tunnel (4.4K reputation)

Group: General Forum Members
Points: 4356 Visits: 1667
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!
David Webb-CDS
David Webb-CDS
Hall of Fame
Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)

Group: General Forum Members
Points: 3994 Visits: 8586
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search