Quote:
Originally Posted by xXExiledXx
The SecurityNo is set in the SecurityNo table in telecaster. For mine telecaster was all set up i only needed 2 things to make it work.
This smp in your Auth database.
-- start of dbo.smp_check_security
CREATE PROCEDURE [dbo].[smp_check_security]
@IN_ACCOUNT VARCHAR(60),
@IN_SECURITY VARCHAR(60)
AS
SET NOCOUNT ON
IF @IN_ACCOUNT LIKE '@%' AND CONVERT( VARBINARY, @IN_SECURITY ) = CONVERT( VARBINARY, '0000000' ) AND EXISTS ( SELECT * FROM Account WHERE account = @IN_ACCOUNT )
BEGIN
SELECT @IN_ACCOUNT AS account;
END
ELSE
BEGIN
--SELECT account FROM tb_account WHERE account = @IN_ACCOUNT AND LEN( jumin ) = 14 AND SUBSTRING( jumin, 8, 7 ) = @IN_SECURITY
SELECT account FROM Account WHERE account = @IN_ACCOUNT AND password = @IN_SECURITY --LEN( password ) = 14 AND SUBSTRING( jumin, 8, 7 ) = @IN_SECURITY
END
-- end of dbo.smp_check_security
GO
And set this value in ur authserver.opt
N db.auth.use_md5_for_security_no:1
And SecurityNo should work.
|
I have tried all kinds of different ways.
With Auth emu
Not sure if this works in the auth emu but I used the auth emu queries for SecurityNo
N db.auth.use_md5_for_security_no:1
sql.db_securitynocheck.param.account:1
sql.db_securitynocheck.param.security_no:2
sql.db_securitynocheck.query:{CALL smp_check_security(?, ?)}
1. Plain text entry in SecurityNo
2. MD5 entry in SecurityNo
3. MD5 with 2011 salt entry in SecurityNo
Regular Princess Aurora for 9.1
1. Plain text entry in SecurityNo
N db.auth.use_md5_for_security_no:0
2. MD5 entry in SecurityNo
N db.auth.use_md5_for_security_no:1
3. MD5 with 2011 salt entry in SecurityNo
N db.auth.use_md5_for_security_no:1
No mater which way I try it always returns that my password is incorrect.
I don't need it anyway I was just trying to help Thund22222