doplneni drobnosti; uprava formatovani; oprava kreklepu

src/warden-client/doc/README.cesnet

 +-------------------------------------+
-| README.cesnet - Warden Client 1.0.0 |
+| README.cesnet - Warden Client 1.1.0 |
+|				      |
 | CESNET Specifics                    |
 +-------------------------------------+
 
@@ -7,9 +8,11 @@ Content
 
  A. Overall Information
  B. Registration
- C. Configuration
- D. Testing
- E. Authors of this document
+ C. Description tags
+ D. Types of events
+ E. Configuration
+ F. Testing
+ G. Authors of this document
 
 --------------------------------------------------------------------------------
 A. Overall Information
@@ -23,19 +26,19 @@ A. Overall Information
 
  2. Version
 
-    1.0.0 (2011-11-16)
+    1.1.0 (2011-11-16) - DOPLNIT
 
 --------------------------------------------------------------------------------
 B. Registration
 
     Client attempting to communicate with CESNET Warden server must be
     registered. Registration is currently provided by Tomas Plesnik at
-    address plesnik@ics.muni.cz and following information is needed:
+    mail address plesnik@ics.muni.cz and following information is needed:
 
     * For sender client:
       - hostname of the machine, where client runs,
-      - name of the detection service (for example 'ScanDetector'),
       - client type = sender,
+      - name of the detection service (for example 'ScanDetector'),
       - description tags of sent events (see below)
       - CIDR from which client will communicate with Warden server.
 
@@ -75,7 +78,8 @@ notify about such cases).
    Categories list is certainly not complete. Therefore if new client's
    administrator feels that name or type of important feature of his (or
    others) detector is not covered, providers of Warden server are glad to
-discuss it at registration address or at Warden project mailing list. 
+   discuss it at registration address or at Warden project mailing list 
+   (warden@cesnet.cz).
    However, it may or may not be accepted, as aim is to keep the list of
    categories possibly unambiguous, short and usable.
 
@@ -114,11 +118,11 @@ examples.
 --------------------------------------------------------------------------------
 D. Types of events
 
-   Event types purpose is to allow event receivers to filter and/or
-categorise particular events according to attack characteristics. Types are
-loosely chosen as list of common security incidents nowadays observed. List
-is by no means complete, however it was created based on expected use cases
-at receiving places. Possibility of a new type is also open to discussion.
+   Event types purpose is to allow event receivers to filter and/or categorise
+   particular events according to attack characteristics. Types are loosely
+   chosen as list of common security incidents nowadays observed. List is by no
+   means complete, however it was created based on expected use cases at
+   receiving places. Possibility of a new type is also open to discussion.
 
    * portscan - TCP/UDP port scanning/sweeping
    * bruteforce - dictionary/bruteforce attack to services authentication
@@ -153,4 +157,4 @@ G. Authors of this document
     Pavel Kacha     <ph@cesnet.cz>
     Jan Soukal      <soukal@ics.muni.cz>
 
-Copyright (C) 2011 Cesnet z.s.p.o
+Copyright (C) 2011-2012 Cesnet z.s.p.o