Tracker Registry Data

From Higher Intellect wiki
Jump to: navigation, search

This is the UDP datagram sent by the Hotline Server, to
register itself on a tracker.



(tracker registry version #)
00000000: 00 01                                               ..

(port, example is 4000)
00000000:       0F A0                                           . 

(users online at this server)
00000000:             00 01                                       ..

(reserved?)
00000000:                   00 00                                   ..

(server identification number)
00000000:                         FD 6C 59 95                         ýlY•

(server name)
00000000:                                     0C 56 69 72                 .Vir
00000010: 74 75 61 6C 46 54 50 2F 78                          tualFTP/x

(description)
00000010:                            51 A5 A5 20 50 6F 77              Q¥¥ Pow
00000020: 65 72 42 6F 74 20 A5 A5 20 20 42 61 63 6B 20 6F     erBot ¥¥  Back o
00000030: 6E 20 69 6E 74 65 72 6D 69 74 74 65 6E 74 20 62     n intermittent b
00000040: 61 73 69 73 2C 20 6D 61 6A 6F 72 20 68 61 72 64     asis, major hard
00000050: 77 61 72 65 20 72 65 76 61 6D 70 20 69 6E 20 70     ware revamp in p
00000060: 72 6F 67 72 65 73 73 2E 2E 2E 20                    rogress... 

(tracker password)
00000060:                                  0B 46 56 69 74                .Virt
00000070: 75 61 6C 46 54 50 37                                ualFTP7         



Note: the "server identification number" appears to be a four byte
number generated at random when you run the server for the very
first time.  It does NOT appear to be based on the registration
codes for the server.  Its use seems to be to uniquely identify
the server to the tracker, so that it can replace an existing
entry in the tracker list even if all demographics change. (name,
description, and of course IP)   Whatever its intent, this number
DOES uniquely identify a server, and does not change over time.
It is stored in the prefs file for the server.  To change it, you
will either have to trash your prefs and reconfigure again, or
go into the prefs file and alter it by hand.

Note also that the IP is NOT sent, just the port.  It is therefore
not possible to spoof a server tracker request without also
spoofing your internet IP. (the tracker gets the server IP
address by looking at the UDP socket)  Seeing as UDP does not
require a pipe, this would be considerably easier to do than
anything using TCP/IP, so it is still not entirely secure.


- Virtual1


Share your opinion