[Release] WZ_MD5_MOD for SQL Server x64 by xakumm

[xakumm]

Extended Stored Procedure for create and check WZ MD5 Hash on x64 systems.

1. Copy the 'WZ_MD5_MOD_x64.dll' in C:\Program Files\Microsoft SQL Server\MSSQL\Binn\
2. Run this script "Install WZ_MD5_MOD_x64.sql"
3. Run script "Test.sql" [optional]
4. Enjoy!

Download WZ_MD5_MOD x64 + fix

[MentaL]

[pquintal]

Excelent xakum, very useful!!!

[ianvalls90]

Simply awesome.

[jhesociety]

thanks.. :)

[Mulegend]

This already posted 4 o 5 years ago..

[xakumm]

This already posted 4 o 5 years ago..

what are you talking about? I made it 9 months ago and released just now.
if there is another version of this library for SQL Server x64 - show it me.

[pquintal]

I search for this on net one month ago, no results, this not exist in another place, only exist for x86 systems

[navossoc]

what are you talking about? I made it 9 months ago and released just now.
if there is another version of this library for SQL Server x64 - show it me.

Well, maybe it exists, but is not public...

Test script

-- XP_MD5_EncodeKeyVal

SET NOCOUNT ON


DECLARE @login1 char(10), @pass1 char(10), @Hash1 binary(16)
set @login1 = 'login'
set @pass1 = 'pass'


EXEC master.dbo.XP_MD5_EncodeKeyVal @login1, @pass1, @Hash1 OUT


---------------------------------------------------------------------


DECLARE @login1n nchar(10), @pass1n nchar(10), @Hash1n binary(16)
set @login1n = N'login'
set @pass1n = N'pass'


EXEC master.dbo.XP_MD5_EncodeKeyVal @login1n, @pass1n, @Hash1n OUT


---------------------------------------------------------------------


DECLARE @LogiN2 varchar(10), @pass2 varchar(10), @Hash2 binary(16)
set @LogiN2 = 'login'
set @pass2 = 'pass'


EXEC master.dbo.XP_MD5_EncodeKeyVal @LogiN2, @pass2, @Hash2 OUT


---------------------------------------------------------------------


DECLARE @LogiN2n nvarchar(10), @pass2n nvarchar(10), @Hash2n binary(16)
set @LogiN2n = N'login'
set @pass2n = N'pass'


EXEC master.dbo.XP_MD5_EncodeKeyVal @LogiN2n, @pass2n, @Hash2n OUT


---------------------------------------------------------------------


declare @Hash3 binary(16)
EXEC master.dbo.XP_MD5_EncodeKeyVal 'login', 'pass', @Hash3 OUT


---------------------------------------------------------------------


declare @Hash3n binary(16)
EXEC master.dbo.XP_MD5_EncodeKeyVal N'login', N'pass', @Hash3n OUT


---------------------------------------------------------------------


select @Hash1 as 'char', @Hash1n as 'nchar'
select @Hash2 as 'varchar', @Hash2n as 'nvarchar' 
select @Hash3 as 'literal', @Hash3n as 'nliteral'

Your DLL

char                               nchar
---------------------------------- ----------------------------------
0x49192D0074BA77460E1AC359D3DDEABA 0x36B759A7F6A79F205FE9271ACB1722F8


varchar                            nvarchar
---------------------------------- ----------------------------------
0x2450781554F7806EC1A4DE67E7A762C4 0x406800C0B012934AD1CA13562EEC3F2B


literal                            nliteral
---------------------------------- ----------------------------------
0x2450781554F7806EC1A4DE67E7A762C4 0x406800C0B012934AD1CA13562EEC3F2B

Original x86

char                               nchar
---------------------------------- ----------------------------------
0x49192D0074BA77460E1AC359D3DDEABA 0xABEF31793325B11D7DBBF98C8F3C2794


varchar                            nvarchar
---------------------------------- ----------------------------------
0x2450781554F7806EC1A4DE67E7A762C4 0xEA4C79D5CF04F00860937968F60C7EFC


literal                            nliteral
---------------------------------- ----------------------------------
0x19522F64C31DD4CB2DA20AADC2CE924D 0x2A6985F2ECB9C4F4B37439125F7B4C4E

[wolfulus]

the one that I have matches original x86 results too. this one seems to be fk up.. be careful migrating your server to SQL Server x64 using this dll.

[xakumm]

navossoc, wolfulus,
you should use only varchar (or char), because the use unicode is a big mistake and unsafe - for password guessing need only the first character ( check it: )

DECLARE @btInStr0 NVARCHAR(10), @btInStr1 NVARCHAR(10), @btInStr2 NVARCHAR(10)
DECLARE @btInStrIndex	NVARCHAR(10)
DECLARE	@btOutVal	BINARY(16)
set @btInStr0 = N'password'
set @btInStr1 = N'pass'
set @btInStr2 = N'p'
set @btInStrIndex = N'login'
EXEC master..XP_MD5_EncodeKeyVal @btInStr0, @btInStrIndex, @btOutVal OUT
print @btOutVal
EXEC master..XP_MD5_EncodeKeyVal @btInStr1, @btInStrIndex, @btOutVal OUT
print @btOutVal
EXEC master..XP_MD5_EncodeKeyVal @btInStr2, @btInStrIndex, @btOutVal OUT
print @btOutVal

/* result: 
	0x124C67DED6D675FE458137B70BBDC41E
	0x124C67DED6D675FE458137B70BBDC41E
	0x124C67DED6D675FE458137B70BBDC41E */

I changed the library (download from first post), what would the outcome was in the original library x86, but my dll already correctly worked with varchar.

[navossoc]

navossoc, wolfulus,
you should use only varchar (or char), because the use unicode is a big mistake and unsafe - for password guessing need only the first character ( check it: )

DECLARE @btInStr0 NVARCHAR(10), @btInStr1 NVARCHAR(10), @btInStr2 NVARCHAR(10)
DECLARE @btInStrIndex    NVARCHAR(10)
DECLARE    @btOutVal    BINARY(16)
set @btInStr0 = N'password'
set @btInStr1 = N'pass'
set @btInStr2 = N'p'
set @btInStrIndex = N'login'
EXEC master..XP_MD5_EncodeKeyVal @btInStr0, @btInStrIndex, @btOutVal OUT
print @btOutVal
EXEC master..XP_MD5_EncodeKeyVal @btInStr1, @btInStrIndex, @btOutVal OUT
print @btOutVal
EXEC master..XP_MD5_EncodeKeyVal @btInStr2, @btInStrIndex, @btOutVal OUT
print @btOutVal

/* result: 
    0x124C67DED6D675FE458137B70BBDC41E
    0x124C67DED6D675FE458137B70BBDC41E
    0x124C67DED6D675FE458137B70BBDC41E */

I changed the library (download from first post), what would the outcome was in the original library x86, but my dll already correctly worked with varchar.

TBH, i really don't care about it or even use it...

It just don't mimic the original behavior, so it's broken in my opinion, but now seems you have fixed it...

[]'s

[perez4all]

Thanks! Man! Thanks! I'd been seaching foor this like 3 days.

[jhesociety]

repost but not bad :)) btw ty

[MaskARRA]

Please help I have this error. but I already paste the WZ_MD5_MOD_x64.dll

DBCC cannot free the DLL "WZ_MD5_MOD_x64.dll". The DLL is not loaded.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Msg 17750, Level 16, State 0, Procedure XP_MD5_EncodeKeyVal, Line 1
Could not load the DLL WZ_MD5_MOD_x64.dll, or one of the DLLs it references. Reason: 193(%1 is not a valid Win32 application.).

Edit: by the way Im using 32bit

[navossoc]

Please help I have this error. but I already paste the WZ_MD5_MOD_x64.dll

DBCC cannot free the DLL "WZ_MD5_MOD_x64.dll". The DLL is not loaded.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Msg 17750, Level 16, State 0, Procedure XP_MD5_EncodeKeyVal, Line 1
Could not load the DLL WZ_MD5_MOD_x64.dll, or one of the DLLs it references. Reason: 193(%1 is not a valid Win32 application.).

Edit: by the way Im using 32bit

If are you using a sql server 32 bits, why want you use this DLL?
Just use the original one...

[]'s