Andreas,

Doesn't using the Save Drafts = 0 option result in the old 'Back' button returning (replacing the Delete option) meaning you can revert back to your old (unmodified) version without saving, sure it doesn't save a draft but I'd rather be able to return back and lose the changes I didn't want then mess up an old entry, I guess the back button on the browser could also do what you want?

The issue I had was that entries were being deleted accidently by persons other than those that created them, I reduced the edit time to try and mitigate it but ended up going back to what we had in Ver 2.9.2, a 'Back' button.

Grant

For the time being, I am deeming ELOG 3.1.2 unusable with https (SSL = 1) functionality on my "Debian GNU/Linux 7 (wheezy)" server with "OpenSSL 1.0.1t", due to the described apparent issues with SSL.  Reverting to http (SSL = 0) brings back my ability to upload attachments and synchronize with a remote elogd running on a MacOS laptop.

Interestingly, my records indicate that I suffered a problem with very similar symptoms back in 2011, with version 2.8.0.  The problem at that time, which is acknowledged in the Changelog as "Fixed bug with SSL connection shutdown", got fixed in version 2.9.0.  Perhaps, when the "Replaced insecure SSLv23 with TLSv1 method" change was implemented for version 3.0.0, a similar issue was (re-)introduced?

It would of course be best if this issue were resolvable soon, due to the security vulnerabilities of http versus https.  Thank you in advance for any efforts!

Best regards,

Andreas Warburton

Further to my comment in https://midas.psi.ch/elogs/Forum/68549, if the described synchronization requires attachment(s) to be transferred from my Mac laptop to the Debian linux server (with SSL = 0 set), it fails in all the tests that I tried.

To check whether these problems are linked to the OpenSSL version on the linux server, we also tried building an elogd executable using 1.0.2j instead of 1.0.1t.  This did not appear to change/improve the behaviour.

I'd like to keep using ELOG into the foreseeable future.  Don't hesitate to contact me if you'd like me to beta test any upcoming releases.  I'd appreciate having the earlier mirroring and attachment-handling functionality back again.

Best regards,

Andreas W.

> Hi,
>   I reopen this old thread since I'm having a similar problem.
> 
> I'm running ELOG V3.1.1-0767eb0 on ubuntu with webserver authentication, and I'd like to remove 'active' checkbox as well.
> 
> The problem that we found is that if any user click on the [Set None] button at the bottom of the Config page in order to unsubscribe from all mail notification,
> *all* the checkbox are toggled, not only those for the email notification. And this includes also the "active user" as well.

I can confirm that this bug is present even in this forum and in my current version (ELOG V3.1.3-aded4ae).
And I am positive that this is a bug: it was certainly not the intended behaviour.

Hi,

a routine scan revealed a possible DOS attack vector: sending an invalid POST HTTP request with a negative Content-Length field crashes our elog instance, leading to service unavailability.

thanks,

-Christian

-- 
Dr. Christian Herzog <herzog@phys.ethz.ch>  support: +41 44 633 26 68
IT Services Group, HPT H 8                    voice: +41 44 633 39 50
Department of Physics, ETH Zurich           
8093 Zurich, Switzerland                     http://nic.phys.ethz.ch/

Hello there,

Can anyone point out to me how I can avoid the unsafe browsing when accessing our local ELOG?  
Browsing with chrome and always getting the unsafe browsing page. One has to go through the advanced
button to continue ...

I once had my setup with SSL certificate (local signed, not through the CA) but I somehow cannot get it
to work anymore.   Just create a local certificate and copy the certificates to all browsers that access the ELOG site, no?

Anyway, a small guide would be great.

Dear elog community,

We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing.
I found them in the .log files with attributes

Locked by:
Draft:

But they are not in the list anymore!
The only solution by now is manually remove these two attributes from the file,
but this is terrible.

How can I fix this?

Thanks,
Peter.