Community AlphaAlpha MUADMINS
RORomână
Autentificare
Pe MuADMINSConfig ScannerÎncarcă zip-ul fișierelor tale: rate-uri, drop-uri, spoturi, limiteDeschidePe MuADMINSÎntâlnește-ne pe DiscordCere ajutor, arată la ce lucrezi și vorbește despre MU cu alți proprietari de servere.Deschide
← Toate soluțiile
Configurarea serveruluiIGCNS9, S12, S16, S17, S18

IGCN WZ_MD5 (PasswordEncryptType 1): fn_md5 fails or XP_MD5_EncodeKeyVal is not found

Scris de MuADMINS pe baza surseiNot verified

IGCN's fn_md5(@data VARCHAR(20), @data2 VARCHAR(10)) RETURNS BINARY(16) does only one thing: EXEC master.dbo.XP_MD5_EncodeKeyVal @data, @data2, @hash OUT (password first, account second). XP_MD5_EncodeKeyVal is an extended procedure that lives in the master database and comes from WZ_MD5_MOD.dll.

  1. Check that it is registered:
SELECT name, dll_name FROM master.sys.extended_procedures WHERE name LIKE 'XP_MD5%';
  1. No row: the DLL ships in Database\3. Extras\MD5 Resources\WZ_MD5_MOD.dll (with an "MD5 Setup.url" link to the IGCN documentation). It is a 32 bit DLL, so it loads only in an x86 SQL Server (2012 or 2014 x86; 2016 and newer are 64 bit only). The standard SQL Server command that registers it, run in master after copying the DLL into the SQL Server Binn folder, is:
USE master;
EXEC sp_addextendedproc 'XP_MD5_EncodeKeyVal', 'WZ_MD5_MOD.dll';
  1. The IGCN documentation also says that for MD5 the database user must own master, and (database chapter) that the collation must be case insensitive.
  2. On a 64 bit SQL Server use PasswordEncryptType 2 (varchar(32)) or 3 (binary(32)) instead: they need no DLL.

Source: IGCN Season 17 Database/1. Full Scripts/MuOnline/MuOnline_MD5.sql (fn_md5) and Database/3. Extras/MD5 Resources/WZ_MD5_MOD.dll (32 bit PE); IGCDS.ini comment "for x86 SQL only, requires WZMD5MOD.dll"; IGCN doc 3.3 as noted in the MuADMINS SQL guide research.

Scris de MuADMINS
Te-a ajutat?

Tot nu merge? Caută în MuGPS Întreabă Asistentul MU

MuADMINS Community Alpha: gratuit, făcut de comunitate, în dezvoltare activă.