2019-08-24 23:05 CEST

View Issue Details Jump to Notes ] Related Changesets ]
IDProjectCategoryView StatusLast Update
0004881Spring engineGeneralpublic2015-07-04 12:14
Reportersilentwings 
Assigned TojK 
PrioritynormalSeverityfeatureReproducibilityalways
StatusresolvedResolutionfixed 
Product Version99.0+git 
Target VersionFixed in Version 
Summary0004881: users connecting with the wrong spring version recieve no warning message
DescriptionThey simply users connecting with the wrong spring version recieve no warning message - they simply time out. This means people do it without realizing what's wrong.
TagsNo tags attached.
Checked infolog.txt for lua Errors
Attached Files

-Relationships
+Relationships

-Notes

~0014875

abma (administrator)

spring currently silently ignores invalid packets. thats basicly good as this prevents reflection / DDoS attacks. not sure how to probably fix this.

~0014878

silentwings (reporter)

Last edited: 2015-07-04 08:59

View 2 revisions

I'm no network expert, but Spring already doesn't ignore those packets completely - for example it knows which network version the failed connector is trying to use (and repeatedly tells it to everyone ingame!). The host could, in principle, notify the client trying to connect without being vulnerable to DDoS.

~0014879

abma (administrator)

with ignore i mean, that it doesn't send back any packet.

~0014880

jK (developer)

Fix ad00fbcd3ba50c4618886213e5c19e04f6d5717d committed to develop branch: fix 0004881: handle rejected connection attempts, repo: spring changeset id: 5303
+Notes

+Related Changesets

-Issue History
Date Modified Username Field Change
2015-07-03 22:42 silentwings New Issue
2015-07-04 02:08 abma Note Added: 0014875
2015-07-04 02:08 abma Severity minor => feature
2015-07-04 08:51 silentwings Note Added: 0014878
2015-07-04 08:59 silentwings Note Edited: 0014878 View Revisions
2015-07-04 11:51 abma Note Added: 0014879
2015-07-04 12:14 jK Changeset attached => spring develop ad00fbcd
2015-07-04 12:14 jK Note Added: 0014880
2015-07-04 12:14 jK Assigned To => jK
2015-07-04 12:14 jK Status new => resolved
2015-07-04 12:14 jK Resolution open => fixed
+Issue History