From 4eae7083155e2aefb0f70db80b5687f0a00f2a73 Mon Sep 17 00:00:00 2001 From: hsn <> Date: Tue, 26 Apr 2005 16:55:45 +0000 Subject: [PATCH] *** empty log message *** --- doc/4LAMERZ.TXT | 14 +++++++------- doc/PROTOCOL | 20 ++++++++++---------- 2 files changed, 17 insertions(+), 17 deletions(-) diff --git a/doc/4LAMERZ.TXT b/doc/4LAMERZ.TXT index cdef961..ac149ff 100644 --- a/doc/4LAMERZ.TXT +++ b/doc/4LAMERZ.TXT @@ -25,7 +25,7 @@ Why you need it - stealth operation - few people knows what FSP is -- old proven software with 10 years history +- old proved software with 10 years history - Elite SitEZ has non interrupted operation by lamerz for more than 10 years! - for EliTe only @@ -33,7 +33,7 @@ Why you need it - net adminz do not like it - lamerz can not handle it - bandwidth friendly -- very ressistant to packet loss +- very resistant to packet loss STuFF firSt! @@ -58,7 +58,7 @@ fspd.exe -d c:\your\stuff\to\share -p 53 this number is important. Recommended numbers for stealth operation are: 53, 2090, 137-139, 13, 80, 443 -You can be catched more easily with bad number, so chooze wisely. Remember, +You can be catch more easily with bad number, so chose wisely. Remember, some numbers like 2221, 21, 2000, 2001 are used only by Elite! do not try it at home; bad thingz can hepen. you know. police will certainly take a visit. Lamers can detect you more easily on this ports, so be @@ -70,7 +70,7 @@ You want uploads from users. Of course. You need to setup an upload area. This is easy. In your FSP homedir create subdirectory upload and and create file named -".FSP_OK_ADD" there. Content of this file dosnot matter. Copy your favourite +".FSP_OK_ADD" there. Content of this file doesn't matter. Copy your favorite music into it if you want. Do something nice. Last point is to add upload directory to server invocation arguments: @@ -124,8 +124,8 @@ much better guide - hq version. Try to offer something. 192.168.45.21 108 10.20.30.40 5060 -never try to flood fsp server, this does not work, elite will laugh -at you and cut your accez down. remember, you ar elite, not a kiddie! +never try to flood FSP server, this does not work, elite will laugh +at you and cut your accez down. remember, you are elite, not a kiddie! -----**************------*******************----------************--- @@ -138,7 +138,7 @@ Features included: list of 5 hq quality sitez how to search for new sitez how to make FSP faster - special fsp sites seek tool + special FSP sites seek tool and 3 secret bonuzez !We Do NOT sEnDZ hQ guiDe to LAmeRZ! Prove yourself first. diff --git a/doc/PROTOCOL b/doc/PROTOCOL index e86d2e8..65be154 100644 --- a/doc/PROTOCOL +++ b/doc/PROTOCOL @@ -69,7 +69,7 @@ Transport Minimum FSP packet size (not including size of UDP, IP and link layer headers) is 12 bytes (FSP v2 header only), maximum standard FSP packet size is 12 bytes of FSP v2 header and 1024 bytes of - payload. Server can optionaly accept longer packets, but must not + payload. Server can optionally accept longer packets, but must not send longer packets to client unless specially requested. All servers and clients must support receiving 1024+12 bytes long packets. @@ -92,7 +92,7 @@ Security many people wants it and there were hacked version of FSP with password support floating around. Passwords are transmitted in clear text over network which makes them a weak protection for determined - intruder when transfered over unsecured network. + intruder when transferred over unsecured network. FSP Packet format: HEADER - size = Fixed size 12 bytes. Always present. @@ -136,7 +136,7 @@ checksums when very easy to compute, are sufficient for guarding against random line noise. Note: -IP/UDP packet has its own crc16 checksum, but FSP protocol checksum is +IP/UDP packet has its own CRC16 checksum, but FSP protocol checksum is used as protection against received non FSPv2 UDP packets. KEY @@ -144,8 +144,8 @@ Client's message to server contain a KEY value that is the same as the KEY value of the previous message received from the server. KEY is chosen random by server. -Server uses one KEY per client network address. If multiple fsp clients -on the same host wants access same fsp server at the same time, they +Server uses one KEY per client network address. If multiple FSP clients +on the same host wants access same FSP server at the same time, they must implement some local method of key exchange. If they don't server will serve only one client from host, because other clients do not have valid key. @@ -157,7 +157,7 @@ Server will accept resent message from client with old KEY after 3 seconds. Client MUST wait at least 1 second before resending a message. It is recommended to use initial delay of 1.34 second and after each unsuccessful resend multiply delay time by 1.5. Maximum -delay time is 300 seconds. Recommended maximum delay between resends +delay time is 300 seconds. Recommended maximum delay between resend is 60 seconds. 2. Session @@ -233,7 +233,7 @@ CC_VERSION is recommended. Note - Some fsp servers do not responds to this command, + Some FSP servers do not responds to this command, because this command is used by FSP scanners and servers do not wishes to be detected. @@ -267,11 +267,11 @@ CC_VERSION is recommended. data: directory listing (format follows) xtra data: not used -Directory listing is transfered in similar way as file transfer. +Directory listing is transferred in similar way as file transfer. Directory listing is divided into blocks of equal size, only exception is last block which can be shorter. Default size of directory listing -block is 1024 bytes. Server can use prefered block size sent by client -and split directory listing into blocks with size prefered by client. +block is 1024 bytes. Server can use preferred block size sent by client +and split directory listing into blocks with size preferred by client. Directory blocks can't be split across message boundary and client can't do seeking to any arbitrary offset, which can broke dirblock