Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 433 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OSdown ELOG Version Subject Text Attachments
  65937   Wed Jul 30 19:54:28 2008 Entry Alan Stonealstone@fnal.govBug reportLinux2.7.4-2113Exploit Browser Tabs to Make Anonymous EntriesOne of my shifters just managed to make
an anonymous logbook entry even though the
Author attribute is required.
  
  65938   Thu Jul 31 09:25:01 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.4-2113Re: Exploit Browser Tabs to Make Anonymous Entries

    
        
  
  65941   Fri Aug 1 13:47:58 2008 Question Niklaselog@niklas.hoglund.pp.seQuestionLinux2.7.3deadc0deHi,
 
my ELOG sometimes dies with "deadc0de",
  
  65942   Mon Aug 4 09:00:43 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.3Re: deadc0de


   
        
            
  
  65943   Thu Aug 7 10:12:25 2008 Warning T. Ribbrockemgaron@gmx.netQuestionLinux2.7.4-2111Using the command line tool to editI intend to create a script that updates
one of our elog logbooks based on mails it
receives. I was hoping to be able to do this
  
  65946   Fri Aug 8 14:27:03 2008 Reply Yoshio ImaiQuestionLinux2.7.4-2111Re: Using the command line tool to edit[quote=T. Ribbrock][B]NOTE:[/B] I found that
this does [i]not[/i] work if LOGBOOK has
any spaces in it - I would get error messages
  
  65947   Fri Aug 8 14:50:56 2008 Reply T. Ribbrockemgaron+elog@ribbrock.orgQuestionLinux2.7.4-2111Re: Using the command line tool to edit[quote="Yoshio Imai"][quote=T. Ribbrock][B]NOTE:[/B]
I found that this does [i]not[/i] work if
LOGBOOK has any spaces in it - I would get
  
  65949   Mon Aug 11 11:02:18 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.7.4-2111Re: Using the command line tool to edit

    
        
  
ELOG V3.1.5-3fb85fa6