About password control
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

About password control

Started by Josecar, 10 April, 2007, 13:56:50

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Josecar

As long as I can see, Ptokax first checks passwords and after that it calls PasswordArrival.  If the pass is bad, user is rejected and nobody knows.

It will be nice that PasswordArrival could control that,  so we can send a message to ops, put escalable timebans, etc.

I was thinking in something like that:

function PasswordArrival(user, Data)
	local s, e, password = string.find(Data,"^$MyPass%s(%S+)|$")
	local pass = frmHub:GetUserPassword(user.sName)

	if password ~= pass then
	    -- Message to ops, warns, disconnect, timeban, etc.
	   return 1
	end
end


Thanks in advance and excuse me if this is my error.




SMF spam blocked by CleanTalk