Update documentation

Author: g3force

README.md

@@ -100,6 +100,10 @@ Active connections to teams are shown as an icon in the team overview.
 #### The controller crashes on start. What can I do?
 Try deleting the `state-store.json.stream` file in the working directory. It may got corrupted.
 
+#### How can I use TLS?
+Generate a new `server.crt` for the game-controller with [tools/newX509KeyPair.sh](./tools/newX509KeyPair.sh).
+See instructions for the client part in the reference clients mentioned above.
+
 ## Integration into your own framework
 The game-controller can easily be integrated into your own AI framework, if you do not want to implement your own controller for testing purposes.
 

cmd/ssl-auto-ref-client/README.md

@@ -5,7 +5,7 @@ This folder contains a sample client that connects to the autoRef interface of t
 ## Protocol
 The communication is established with a bidirectional TCP connection. Messages are encoded with [Protocol Buffers](https://developers.google.com/protocol-buffers/). Each message is preceded by an uvarint containing the message size in bytes, see https://cwiki.apache.org/confluence/display/GEODE/Delimiting+Protobuf+Messages for details.
 
-The .proto files can be found [here](../../pkg/refproto).
+The .proto files can be found in [../../proto](../../proto).
 
 The default port is `10007`. The IP to connect to can be determined using the multicast referee messages.
 

cmd/ssl-team-client/README.md

@@ -5,7 +5,7 @@ This folder contains a sample client that connects to the team interface of the
 ## Protocol
 The communication is established with a bidirectional TCP connection. Messages are encoded with [Protocol Buffers](https://developers.google.com/protocol-buffers/). Each message is preceded by an uvarint containing the message size in bytes, see https://cwiki.apache.org/confluence/display/GEODE/Delimiting+Protobuf+Messages for details.
 
-The .proto files can be found [here](../../pkg/refproto).
+The .proto files can be found in [../../proto](../../proto).
 
 The default port is `10008` for plain connections and 10108 for TLS encrypted connections. The IP to connect to can be determined using the multicast referee messages.