Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 256 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  2301   Thu Aug 2 12:24:26 2007 Reply Stefan Rittstefan.ritt@psi.chInfoWindows2.6.5Re: WYSIWYG (What you see is what you get)

An Thai wrote:
I have just found an open source for WYSIWYG text editor named FCKeditor at http://www.fckeditor.net/. It looks great. The download Zip-file for this tool is only 1 MB.


I had a look and it just looks great. I will certainly add support for this editor, but I have to fix a few things, like inserting of images and the preview feature need modifications of FCKeditor. So stay tuned.
  340   Thu May 15 13:37:48 2003 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: WIshlist Additional
> Is it possible to make the logbook summary screen sort differently

I fixed that problem. The new version 2.3.7 released today contains the fix.
  626   Wed Jul 28 21:29:28 2004 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.5.3Re: WISHLIST: Type <attribute> = user
Acknowledged. Added your vote to the wishlist.
  632   Wed Jul 28 22:08:16 2004 Agree Steve Jonessteve.jones@freescale.comRequestAll2.5.3Re: WISHLIST: Type <attribute> = user
> Acknowledged. Added your vote to the wishlist.

Thanks!
  65934   Thu Jul 24 11:28:30 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows Re: WINDOWS binaries with latest fixes.

Franck C wrote:

Hi,

When the WINDOWS binaries with the latest bug fixes will be available on the download page ?

Have a nice day

 Whenever you ask for it 

I made you an elog274-1.exe containing revision 2118.

  69484   Thu Mar 3 16:49:40 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fRe: Vulnerability?
The CVEs you refer to are very old and have been fixed a long time ago.

Please refer to:
https://www.tenable.com/security/research/tra-2019-53

This report states that all the reported problems are fixed as of ELOG 3.1.4-283534d or later.

Note that the elog git history does not refer to these CVEs because
they were fixed before the CVE number was assigned, per "Disclosure Timeline"
in the above document. The relevant commits are listed under "Additional References".

K.O.
  69485   Fri Mar 4 08:51:24 2022 Reply Alessandro Petrolinialessandro.petrolini@cern.chQuestionWindows3.1.4-a04faf9fRe: Vulnerability?
Ok, many many thanks!
I will pass the info to my sysadmin.
Best Regards.

> The CVEs you refer to are very old and have been fixed a long time ago.
> 
> Please refer to:
> https://www.tenable.com/security/research/tra-2019-53
> 
> This report states that all the reported problems are fixed as of ELOG 3.1.4-283534d or later.
> 
> Note that the elog git history does not refer to these CVEs because
> they were fixed before the CVE number was assigned, per "Disclosure Timeline"
> in the above document. The relevant commits are listed under "Additional References".
> 
> K.O.
  69486   Sun Mar 6 09:00:33 2022 Reply Alessandro Petrolinialessandro.petrolini@cern.chQuestionWindows3.1.4-a04faf9fRe: Vulnerability?
> Ok, many many thanks!
> I will pass the info to my sysadmin.
> Best Regards.
> 
> > The CVEs you refer to are very old and have been fixed a long time ago.
> > 
> > Please refer to:
> > https://www.tenable.com/security/research/tra-2019-53
> > 
> > This report states that all the reported problems are fixed as of ELOG 3.1.4-283534d or later.
> > 
> > Note that the elog git history does not refer to these CVEs because
> > they were fixed before the CVE number was assigned, per "Disclosure Timeline"
> > in the above document. The relevant commits are listed under "Additional References".
> > 
> > K.O.

Am I wrong that the windows executable version on the site is dated 2018? 3.1.4-2?
ELOG V3.1.5-3fb85fa6