SphereServer BugTracker - SphereServer |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0002020 | SphereServer | executable - windows build | public | 11-08-11 00:48 | 31-08-11 22:51 |
|
Reporter | Shaklaban | |
Assigned To | ShiryuX | |
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | |
Platform | | OS | | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | 0.56c Nightly | |
Nightly Version | Automated (specify build number) |
Experimental Flags | None |
Option Flags | None |
Internal Build Number | 1478 |
|
Summary | 0002020: Disable CUO Status Request |
Description | People can send the same packet with CUO and retrieve some information about the server (memory usage, items cahracters etc.). I don't want to allow that but it is not possible to disable CUO status request. |
Steps To Reproduce | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
11-08-11 00:48 | Shaklaban | New Issue | |
11-08-11 17:31 | Mirravin | Note Added: 0001215 | |
11-08-11 18:02 | Shaklaban | Note Added: 0001216 | |
27-08-11 14:47 | ShiryuX | Note Added: 0001221 | |
27-08-11 14:47 | ShiryuX | Status | new => resolved |
27-08-11 14:47 | ShiryuX | Fixed in Version | => 0.56c Nightly |
27-08-11 14:47 | ShiryuX | Resolution | open => fixed |
27-08-11 14:47 | ShiryuX | Assigned To | => ShiryuX |
28-08-11 01:39 | Shaklaban | Issue Monitored: Shaklaban | |
28-08-11 01:39 | Shaklaban | Issue End Monitor: Shaklaban | |
28-08-11 01:41 | Shaklaban | Note Added: 0001222 | |
28-08-11 01:41 | Shaklaban | Status | resolved => feedback |
28-08-11 01:41 | Shaklaban | Resolution | fixed => reopened |
28-08-11 01:43 | Shaklaban | Note Edited: 0001222 | bug_revision_view_page.php?bugnote_id=0001222#r404 |
28-08-11 01:43 | Shaklaban | Note Edited: 0001222 | bug_revision_view_page.php?bugnote_id=0001222#r405 |
30-08-11 17:24 | ShiryuX | Note Added: 0001223 | |
31-08-11 18:12 | Shaklaban | Note Added: 0001225 | |
31-08-11 18:12 | Shaklaban | Status | feedback => assigned |
31-08-11 22:51 | ShiryuX | Status | assigned => resolved |
31-08-11 22:51 | ShiryuX | Resolution | reopened => fixed |
Notes |
|
|
What is CUO? :) How to use it? |
|
|
|
|
|
|
It should be fixed in the next automatic build, but I need your feedback, please. |
|
|
(0001222)
|
Shaklaban
|
28-08-11 01:41
(edited on: 28-08-11 01:43) |
|
Changing new settings to 0 block the cuo packets. Showing invalid packet data message for them:
02:40:2:Client connected [Total:2] ('178.63.131.207' 1/1)
02:40:2:Unknown/invalid ping data '0xf1' from 178.63.131.207 (Len: 4)
02:40:2:Client disconnected [Total:1] ('178.63.131.207')
02:40:3:Client connected [Total:2] ('178.63.131.207' 1/1)
02:40:3:Unknown/invalid ping data '0xf1' from 178.63.131.207 (Len: 4)
02:40:3:Client disconnected [Total:1] ('178.63.131.207')
|
|
|
|
I think it's fixed, it should say something like:
'CUO Status request from %s has been rejected' |
|
|
|
yes now fixed, displaying true reason and blocked the request.
19:10:5:Client connected [Total:1] ('178.63.131.207' 2/2)
19:10:5:CUO Status request from 178.63.131.207 has been rejected.
19:10:5:Client disconnected [Total:0] ('178.63.131.207') |
|