Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 141 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Datedown Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  68715   Mon Jan 15 15:56:07 2018 Warning Tim Schelfhouttimpieworks@gmail.comQuestionWindowsELOG V3.1.3-fd7Unsafe browsingHello there,

Can anyone point out to me how
I can avoid the unsafe browsing when accessing
  
  68714   Fri Jan 12 09:54:41 2018 Question Xuan Wuwux@ihep.ac.cnQuestionLinux3.1.3about attachmentHi all,

Some elog users of our site(CSNS)
mentioned some advice about attachment:
  
  68713   Mon Dec 11 13:20:49 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.92.2Re: Tool TipsTooltips on 'ROptions' work since 2007, but
your version 2.9.2 is pre-2007, so you should
consider to upgrade.
  
  68712   Mon Dec 11 13:16:32 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.2-bd7Re: hosts allowHave you set

Resolve host names = 1

in the config file? If it still
  
  68711   Fri Dec 8 19:47:04 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1.2-bd7Re: hosts allowHi Susan,

the documentation
states that you should start elogd with the
-v option from the command line and look
  
  68710   Thu Dec 7 21:54:58 2017 Reply Susan Jamessjames@lbl.govQuestionLinux3.1.2-bd7Re: hosts allowHi All,

We're still having trouble
with hosts.allow and hosts.deny.
  
  68709   Wed Dec 6 13:34:56 2017 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V3.1.2Re: possible DOS vulnerability with negative Content-Length fieldI have fixed this issue in the current
develop branch of elog.

Stefan
  
  68708   Tue Dec 5 15:30:43 2017 Warning Christian Herzogherzog@phys.ethz.chQuestionLinuxELOG V3.1.2possible DOS vulnerability with negative Content-Length fieldHi,

 

a routine scan revealed a possible
  
ELOG V3.1.5-3fb85fa6