Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 1 of 718  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  69152   Sat May 23 16:15:38 2020 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi Frank,

Good bit of detective work. 
To me it suggests that something as yet undetermined
  
  69151   Fri May 22 21:03:05 2020 Reply Frank Baptistacaffeinejazz@gmail.comQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi David,

Well, you've made some very
interesting observations, and raised some
  
  69150   Tue May 12 15:53:17 2020 Question Rich Loringrloring@bnl.govQuestionLinux3.1.4How to prevent file path leaks on a 404 pageHello,

We used the Elog RPM binary installation
method to install Elog. Our security scanners
  
  Draft   Tue May 12 15:47:33 2020  Rich Loringrloring@bnl.govQuestionLinux3.1.4How to prevent file path leaks on a 404 pageHello,

We used the Elog RPM binary installation
method to install Elog. Our security scanners
  
  69148   Mon May 4 14:55:53 2020 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi Frank,

There are two interesting points
about the log file. 
  
  69147   Sun May 3 22:43:12 2020 Reply Frank Baptistacaffeinejazz@gmail.comQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi David,

Thanks for the quick response! 
Well, I'd have to say that the sequence
 200428a.log 
  69146   Sun May 3 18:05:32 2020 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindowsV3.1.4-80633baRe: Record ID corruptionHi,

I've had problems in the past
due to a dodgy pointer creating branches
  
  69145   Sun May 3 15:58:24 2020 Question Frank Baptistacaffeinejazz@gmail.comQuestionWindowsV3.1.4-80633baRecord ID corruptionHi all,

I've encountered an occasional
problem that seems to be exacerbated by having
  
ELOG V3.1.4-80633ba