diff --git a/doc/adminguide.html b/doc/adminguide.html index 13ce8696..6d9951d6 100755 --- a/doc/adminguide.html +++ b/doc/adminguide.html @@ -293,7 +293,9 @@ Logbook dir in the elogd.cfg description

Although the elogd program does not support secure connections over SSL directly, it is still possible to access elogd -securely using one of the following methods: +securely using one of the following methods. It is recommented to run elog +through an HTTPS proxy to avoid exposing elog passwords to clear text sniffing +attacks.

Using Apache:

@@ -306,7 +308,33 @@ before on this page on how to run elogd under Apache. Once configured correctly, elogd can be accessed via http://your.host and via https://your.host simultaneously.

-For detailed step-by-step instructions please read the +The redirection statement has to be changed to + + + +and following has to be added to the section "VirtualHOst ...:443 in +/etc/httpd/conf.d/ssl.conf: + +
+# Proxy setup for Elog
+<Proxy *>
+Order deny,allow
+Allow from all
+</Proxy>
+ProxyPass /elog/ http://host.where.elogd.is.running:8080/
+ProxyPassReverse /elog/ http://host.where.elogd.is.running:8080/
+
+ +Then, following URL statement has to be written to elogd.cfg: + +
+URL = https://your.host.domain/elog
+
+ +There is a more detailed step-by-step instructions at the contributions section.

Using ssh:

@@ -351,9 +379,10 @@ details. 
URL = https://your.host.name/
Note the https at the beginning of the URL, which is - mandatory. Once you use the https URL, elog won't work correctly when - accessed not through stunnel via http://.., since any - redirection would always bring you back to https://...).

+ mandatory. Once you use the https URL, elog won't work + correctly when accessed not through stunnel via + http://.., since any redirection would always bring you + back to https://...).

  • Connect to your logbook with a browser which supports SSL via:

    @@ -371,10 +400,16 @@ This reveals any potential error.

    • For the technically curious :

    -The concept of ELOG is very simple. The logbook functionality is implemented by a single daemon program, elogd, which is written in C. It contains an integrated +The concept of ELOG is very simple. The logbook functionality is +implemented by a single daemon program, elogd, which +is written in C. It contains an integrated Web server, which does not serve files like standard Web servers, but reads logbook entries from its database and formats them into HTML. Since -only forms and tables are used, no Java or Javascript is necessary, which makes the logbook display very fast. The system does not use any images on purpose to reduce the amount of data to be transferred. Since the ELOG daemon contains its own http server, no additional server like Apache is required. +only forms and tables are used, no Java or Javascript is necessary, which +makes the logbook display very fast. The system does not use any images on +purpose to reduce the amount of data to be transferred. Since the ELOG +daemon contains its own http server, no additional server like +Apache is required.

    The "database" in which ELOG saves its entries is in plain ASCII format. One file is created for each day in the form YYMMDDa.log