Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 383 of 808  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject Text Attachments
  69404   Mon Oct 25 13:34:06 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4 Re: Too many open files - issue?The code segements you show are from the
command line tool elog.c, not the server
elogd.c. The tool is called to submit a new
  
  69408   Tue Nov 2 12:07:46 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxelog-3.1.4-2Re: results of security scanThe elgod.c progarm itself is rather weak
in SSL, since I just don't have time
to catch up with the latest SSL enhancements.
  
  69423   Wed Nov 24 08:38:33 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.3-7933898Re: Display edit timeCreat an attribute "last edit"
and set it to the last edit time. Something
like this:
  
  69427   Wed Dec 1 13:05:14 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: Unclear how to use the command line tool /usr/bin/elogPlease issue the elog command with an added
"-v" flag and post the output here.

Stefan
  
  69432   Tue Dec 7 14:46:16 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: Unclear how to use the command line tool /usr/bin/elogIf you use HTTPS, you have to connect to
port 443 of your server, using the "-p"
option.
  
  69434   Tue Dec 7 17:50:37 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: Unclear how to use the command line tool /usr/bin/elogThe reply from the server

Response received:
  
  69437   Wed Dec 8 10:59:58 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: Unclear how to use the command line tool /usr/bin/elogOk, you Apache listes on two ports. On
port 80 with HTTP and on port 443 with HTTPS.
If you connect to port 80, there is no fowarding
  
  69440   Wed Dec 8 13:19:55 2021 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.4Re: Unclear how to use the command line tool /usr/bin/elogThat reply indicates that the login was
not successful. So something went wrong with
the authentication. You can try to switch
  
ELOG V3.1.5-3fb85fa6