Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 711 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  834   Tue Dec 7 01:18:14 2004 Smile Steve Allenns@elogicsystems.comInfoAll2.5.5-2Re: external authentication possible?> > > In order to avoid having to remember
multiple usernames/passwords for
> > > different systems, is it possible for
  
  833   Mon Dec 6 22:48:19 2004 Reply Steve Jonessteve.jones@freescale.comInfoAll2.5.5-2Re: external authentication possible?> > In order to avoid having to remember multiple
usernames/passwords for
> > different systems, is it possible for
  
  832   Mon Dec 6 21:48:19 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.5.5-2Re: back button does not work> hi
> the back button/liunk does not work
> if i click on an entry and then back, it
  
  831   Mon Dec 6 21:22:20 2004 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.5.5-2Re: external authentication possible?> In order to avoid having to remember multiple
usernames/passwords for
> different systems, is it possible for ELOG
  
  830   Mon Dec 6 20:05:58 2004 Question PJ Meyerpjm@pjmeyer.orgBug reportWindows Login/Password request appears twiceHave set up 3 top level groups, each with
their own password file.
Ever since users have to 'login' twice to
  
  828   Mon Dec 6 17:42:59 2004 Entry Guenter NowakGuenter.Nowqak@t-systems.atBug reportAll2.5.5-2back button does not workhi
the back button/liunk does not work
if i click on an entry and then back, it
  
  827   Mon Dec 6 02:34:32 2004 Question Steve Allenns@elogicsystems.comQuestionAll2.5.5-2external authentication possible?In order to avoid having to remember multiple
usernames/passwords for
different systems, is it possible for ELOG
  
  822   Sun Dec 5 13:09:12 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.5.5-1Re: ELOG-Server crashes after date entry'Date' attributes can only be between 1970
and 2037, since I use internally the
unix time format. I added a test so future
  
ELOG V3.1.5-3fb85fa6