0001911: Verifying account - SphereServer BugTracker

Notes
(0000907) MrSugarCube (administrator) 11-02-11 21:19	Does this affect any particular client version(s)? Are there any messages shown in console when they connect? (there may be something of interest when debug flag 08000 is enabled too (DebugFlags in Sphere.ini))

(0000908) Robert (reporter) 12-02-11 02:41	02:27:DEBUG:Receiving new connection 02:27:DEBUG:Retrieving IP history for '88.x.214.87'. 02:27:DEBUG:Incoming connection from '88.x.214.87' [blocked=0, ttl=300, pings=10, connecting=2, connected=2] 02:27:DEBUG:32:Allocated slot for client (592). 02:27:DEBUG:32:Clearing client state. 02:27:DEBUG:32:Initialising client 02:27:DEBUG:32:Opening network state 02:27:DEBUG:32:Determining async mode 02:27:DEBUG:32:State initialised, registering client instance. 02:27:DEBUG:32:Client successfully initialised. 02:27:DEBUG:31:Receiving new client login handshake. 02:27:DEBUG:31:Client connected with a seed of 0xc0a80102 (new handshake=1, seed length=21, received=83, version=0x600062). 02:27:ERROR:31:Bad Login 9 (The account details entered are invalid (username or password is too short, too long or contains invalid characters). This can sometimes be caused by incorrect/missing encryption keys) 02:27:DEBUG:31:Client being closed by read-thread 02:27:DEBUG:31:Flushing data for client. Client version is 2.0.3, username and password lenghts are ok.

(0000909) Robert (reporter) 12-02-11 02:44	02:36:DEBUG:Receiving new connection 02:36:DEBUG:Retrieving IP history for '88.x.214.87'. 02:36:DEBUG:Incoming connection from '88.x.214.87' [blocked=0, ttl=300, pings=73, connecting=0, connected=0] 02:36:DEBUG:Closing incoming connection [max ip=8, clients max ip=16). 02:36:ERROR:Connection from 88.x.214.87 rejected. 02:36:DEBUG:Receiving new connection 02:36:DEBUG:Retrieving IP history for '88.x.214.87'. 02:36:DEBUG:Incoming connection from '88.x.214.87' [blocked=0, ttl=300, pings=74, connecting=0, connected=0] 02:36:DEBUG:Closing incoming connection [max ip=8, clients max ip=16). 02:36:ERROR:Connection from 88.x.214.87 rejected. It's the only one connection from this ip.

(0000910) MrSugarCube (administrator) 12-02-11 03:40	The first connection looks like it's from a 6.0.6 client (definitely not 2.0.3) and they appear to have entered either: - no password - a password which is too long (30+ characters), or - a password which contains invalid characters (some symbols such as '{', '\|', '}', '~' and newlines are rejected to prevent some exploits). I can't see any other condition that triggers a Bad Login 9 (assuming encryption key is correct). The second connection has exceeded your 'MAXPINGS' setting by trying to connect too often. Assuming there aren't another 70 connection attempts right before then there could be a problem with pings not decaying over time, which I'll look into.

(0000911) MrSugarCube (administrator) 13-02-11 02:08	A fix for MAXPINGS is in the latest automated build (1416+).

(0000920) Robert (reporter) 15-02-11 08:26	Still have same problem 09:19:DEBUG:Receiving new connection 09:19:DEBUG:Retrieving IP history for '91.x.163.209'. 09:19:DEBUG:Incoming connection from '91.x.163.209' [blocked=0, ttl=300, pings=377, connecting=0, connected=0] 09:19:DEBUG:Closing incoming connection [max ip=8, clients max ip=16). 09:19:ERROR:Connection from 91.x.163.209 rejected. 09:20:DEBUG:Receiving new connection 09:20:DEBUG:Retrieving IP history for '91.x.163.209'. 09:20:DEBUG:Incoming connection from '91.x.163.209' [blocked=0, ttl=300, pings=378, connecting=0, connected=0] 09:20:DEBUG:Closing incoming connection [max ip=8, clients max ip=16). 09:20:ERROR:Connection from 91.x.163.209 rejected.

(0000921) MrSugarCube (administrator) 15-02-11 11:00	What are MAXPINGS and NETTTL set to? Is that IP making a connection every minute without leaving some time between attempts?

(0000925) Robert (reporter) 15-02-11 14:19 edited on: 15-02-11 18:37	Sorry i was given wrong information, the log i wrote for a site (www.uoplayer.com) which is recording online player stats. As you said it is making a connection every minute with leaving 60 seconds time between attemps, if i downgrade to 15.01.2011 release there is no problem with this. Real problem, 03:02:DEBUG:Receiving new connection 03:02:DEBUG:Retrieving IP history for '88.x.168.112'. 03:02:DEBUG:Incoming connection from '88.x.168.112' [blocked=0, ttl=297, pings=1, connecting=0, connected=1] 03:02:DEBUG:23:Allocated slot for client (456). 03:02:DEBUG:23:Clearing client state. 03:02:DEBUG:23:Initialising client 03:02:DEBUG:23:Opening network state 03:02:DEBUG:23:Determining async mode 03:02:DEBUG:23:State initialised, registering client instance. 03:02:DEBUG:23:Client successfully initialised. 03:02:DEBUG:23:Receiving old client login handshake. 03:02:DEBUG:23:Client connected with a seed of 0x7f000001 (new handshake=0, seed length=4, received=4, version=0x0). 03:02:DEBUG:20:Client being closed by read-thread 03:02:DEBUG:20:Client being closed by read-thread 03:02:DEBUG:20:Client being closed by write-thread 03:02:DEBUG:20:Client is being cleared since marked to close. 03:02:DEBUG:20:Clearing client state. 03:12:ERROR:Connection from 88.252.168.112 rejected.

(0000926) Robert (reporter) 15-02-11 15:26	I have just sent you the log file url from sphere's main site

(0000931) Robert (reporter) 16-02-11 19:54	i have been running last build for 4 hours, no one has reported this problem yet.

(0000932) Robert (reporter) 17-02-11 00:13	even if i set NetTTL 120 it blocks the sites which recording online players of shards (for example uoplayer.com, this site makes connection in every minute)

(0000933) MrSugarCube (administrator) 17-02-11 02:07	So with the latest build, is it just the IPs that connect every minute for stats that have this problem? I've tweaked the behaviour slightly so that they shouldn't be affected in tomorrow's build. In the meantime you could try reducing NetTTL even further (around 30) or raising MaxPings to a stupidly high value (like 1000000000), although this will effectively disable (or severely reduce) the protection they offer.

(0000943) MrSugarCube (administrator) 21-02-11 01:29	Is this problem still present in the latest builds?

(0000946) Robert (reporter) 24-02-11 11:41 edited on: 24-02-11 12:22	Verifying account issue no longer exists but we are still having trouble with maxpings (i have just set netTTL=30, i will report it again later)

(0000951) Robert (reporter) 27-02-11 00:38	can be marked as resolved

Issue History
Date Modified	Username	Field	Change
11-02-11 13:29	Robert	New Issue
11-02-11 21:19	MrSugarCube	Note Added: 0000907
12-02-11 02:41	Robert	Note Added: 0000908
12-02-11 02:44	Robert	Note Added: 0000909
12-02-11 03:40	MrSugarCube	Note Added: 0000910
13-02-11 02:08	MrSugarCube	Note Added: 0000911
15-02-11 08:26	Robert	Note Added: 0000920
15-02-11 11:00	MrSugarCube	Note Added: 0000921
15-02-11 11:46	Robert	Note Added: 0000922
15-02-11 11:46	Robert	Note View State: 0000922: private
15-02-11 14:01	Robert	Note Deleted: 0000922
15-02-11 14:19	Robert	Note Added: 0000925
15-02-11 14:19	Robert	File Added: test.txt
15-02-11 15:26	Robert	Note Added: 0000926
15-02-11 18:37	Robert	Note Edited: 0000925	View Revisions
16-02-11 19:54	Robert	Note Added: 0000931
17-02-11 00:13	Robert	Note Added: 0000932
17-02-11 02:07	MrSugarCube	Note Added: 0000933
21-02-11 01:29	MrSugarCube	Note Added: 0000943
24-02-11 11:41	Robert	Note Added: 0000946
24-02-11 12:22	Robert	Note Edited: 0000946	View Revisions
27-02-11 00:38	Robert	Note Added: 0000951
13-03-11 23:40	MrSugarCube	Status	new => resolved
13-03-11 23:40	MrSugarCube	Fixed in Version	=> 0.56c Nightly
13-03-11 23:40	MrSugarCube	Resolution	open => fixed
13-03-11 23:40	MrSugarCube	Assigned To	=> MrSugarCube

Relationships