v0.6

  - Fixed: default password incompatibilities from config file
  - Added: "client's id" option
  - Lightly Modified: verbose mode
  - Added: temporary listen ports
  - Fixed: bug in printing "client's id"
  - Added: 'dateformat' option to set format of the date in the logs
  - Modified: command line option and config file behaviour
  - Added: logging to a socket
  - Fixed: parsing config file
  - Fixed: major bug in packet buffering
  - Added: several clients-users in one realm
  - Modified: default hostname used by afserver
  - Modified: server listening behaviour (for clients)
  - Fixed: bug in checking options values
  - Modified: verbose mode
  - Modified: client initial connection to server
  - Added: connection time / uptime statistics
  - Added: first version of remote administration (statistics only)
  - Fixed: major bug in remove_client routine
  - Added: 'raclients' option
  - Added: use of automake/autoconf
  - Added: creating ~/.apf directory
  - Modified: the way of creating/managing keys/certificates
  - Added: 'dnslookups' option
  - Modified: usage functions
  - Fixed: no handling of missing 'listen' option after 'newrealm' in config file
  - Added: 'quit' command in remote administration mode
  - Modified: logging error messages during initialization
  - Modified: 'newrealm' changed to 'realm' in config file
  - Added: realm names
  - Modified: connection time / uptime
  - Added: client names / unique numbers
  - Added: user unique numbers
  - Fixed: segmentation fault after 'quit' command

1 files changed, 57 insertions, 0 deletions

diff --git a/doc/afserver_example.conf b/doc/afserver_example.conf
new file mode 100644
index 0000000..2046b03
--- /dev/null
+++ b/doc/afserver_example.conf
@@ -0,0 +1,57 @@
+# This is an example configuration file for active port forwarder
+# Firstly, we have to declare our files with key and certificate
+
+certificate	cacert.pem
+
+# Please note, that we can place only blank characters between words
+
+key		server.rsa
+
+# when we want to log some information, we specify file for lightlog
+# when we want to log everything - we do this by using heavylog option
+
+# type		name of file
+
+lightlog	logfile
+#heavylog	logfile
+
+# we we could also want to use sockets instead of files
+
+# type          port (on localhost)
+
+#lightsocklog   12345
+#heavysocklog   12345
+
+#dateformat %d.%m.%Y %H:%M:%S
+
+# And it's time to create forwarding targets (named realms here)
+
+#realm indicates a new set of commands to a server
+#realmname is optional
+realm my realm
+
+#options        values
+
+#hostname  <yourhostname> #this is the name of the server (used to choose interface)
+listen    50127          #portnumber on which server is listening for users
+manage    50126         #portnumber on which server is listening for afclient
+#users     5           #amount of users we are allowing to connect (>0) (default: 5)
+#timeout   5          #timeout value for the client's connection (>0) (default: 5)
+#clients   1          #number of allowed clients for this realm (>0) (default: 1)
+#usrpcli   $users     #allowed users per client for this realm (>0) (default: $users)
+#climode   1          #strategy used for connecting users with clients (1) (default: 1)
+#proto     tcp       #type of the realm (which protocol it will forward (tcp|udp) (default: tcp)
+#pass   mypassword  #this is a password used for client identification
+#raclients 1         #number of allowed clients in remote administration mode (>0) (default: 1)
+#nossl                #don't use ssl for data transfer
+#nozlib                #don't use zlib
+#baseport               #listenports are temporary and differ for each client
+#dnslookups              #try to obtain dns names of the computers
+#ipv4                   #use ipv4 only
+#ipv6                  #use ipv6 only
+
+# and now the second realm
+
+realm
+listen    50125
+manage    50124