diff --git a/doc/adminguide.html b/doc/adminguide.html index ff3ee35b..26dde9ec 100755 --- a/doc/adminguide.html +++ b/doc/adminguide.html @@ -283,28 +283,59 @@ Logbook dir in the elogd.cfg description
  Secure Connections HOWTO  

Although the elogd program does not support secure -connections over SSL directly, it is possible to use it together with -stunnel to do so. Three steps are -necessary: +connections over SSL directly, it is still possible to access elogd +securely using one of the following methods: + +

Using stunnel:

+ +To use elogd togethwer with +stunnel, following steps are necessary: +
  1. Start elogd. If another Web server is running on port 80, use a different port.

    -

  2. Install the stunnel program if not already done +
  3. Configure stunnel. This requires the creation of a certificate. See +the manual for +details. +

    +

  4. Start the stunnel program if not already done and start it with: 

    stunnel -d 443 -r your.host.name:80
    Substitute the port 80 if you started elogd on another port. This - causes stunnel to receive requests on the https port 443 and forward them to the elogd port. + causes stunnel to receive requests on the https port 443 and + forward them to the elogd port.

  5. Put the URL under which elogd runs into elogd.cfg:

    URL = https://your.host.name/
  6. Connect to your logbook with a browser which supports SSL via: 

    https://your.host.name/
    +
  7. If you have problems, start stunnel in the foreground mode with +

    + 

    stunnel -f -d 443 -r your.host.name:80
    + +This reveals any potential error.

-Alternatively, elogd can be accessed through a SSH tunnel. + +

Using Apache:

+ +The Apache web server can be used as a proxy +server allowing secure connections. To do so, Apache has to be configured +accordingly and a certificate has to be generated. See some +instuctions +on how to create a certificate, and see Running elogd under Apache +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. See the ELOG Forum for example +via nonsecure and +secure connection.

+ +

Using ssh:

+ +elogd can be accessed through a a SSH tunnel. To do so, open an SSH tunnel like:

diff --git a/doc/wishlist.html b/doc/wishlist.html index f65e9a3c..ee9a9119 100755 --- a/doc/wishlist.html +++ b/doc/wishlist.html @@ -46,6 +46,8 @@ starting at the items with the most votes. You can vote for a feature, or sugges Implement attribute substituions including message id (or change message id display fromat)1 Only display a subset of attributes in edit, entry and list mode1 Change attributes of whole thread, like mark a thread "open" or "closed"1 +Automatic unlocking of entries after a specific time period1 +Make conditional attributes extandable1