Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 43 of 237  Not logged in ELOG logo
icon5.gif   Is there a python3 api to generate logbook entries from python?, posted by markus on Tue Jan 16 09:30:55 2018 

Dear elog community,

I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...

At the moment I am thinking about wrapping the "elog" command line tool.

Is there something usable already out there?

Thanks and regards
Markus

    icon2.gif   Re: Is there a python3 api to generate logbook entries from python?, posted by Stefan Ritt on Tue Jan 16 09:46:04 2018 

There are two options

  • Wrap the "elog" command line tool 
  • Use "curl". Ther is a PycURL library http://pycurl.io/docs/latest/ which can be used, so you don't have to call any command line tool. The usage of curl is described in elog:68597

Stefan

markus wrote:

Dear elog community,

I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...

At the moment I am thinking about wrapping the "elog" command line tool.

Is there something usable already out there?

Thanks and regards
Markus

 

    icon2.gif   Re: Is there a python3 api to generate logbook entries from python?, posted by Andreas Luedeke on Tue Jan 16 10:13:00 2018 

Have a look here: https://github.com/paulscherrerinstitute/py_elog

I haven't tried it myself, but it should allow you to add, reply, edit, delete elog entries from python (>= 3.5) via the http elog interface. It's an anaconda package.

markus wrote:

Dear elog community,

I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...

At the moment I am thinking about wrapping the "elog" command line tool.

Is there something usable already out there?

Thanks and regards
Markus

 

       icon2.gif   Re: Is there a python3 api to generate logbook entries from python?, posted by markus on Wed Jan 24 07:54:47 2018 

Thanks Andreas!
This is more or less exactly what I was looking for...

Regards
Markus

Andreas Luedeke wrote:

Have a look here: https://github.com/paulscherrerinstitute/py_elog

I haven't tried it myself, but it should allow you to add, reply, edit, delete elog entries from python (>= 3.5) via the http elog interface. It's an anaconda package.

markus wrote:

Dear elog community,

I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...

At the moment I am thinking about wrapping the "elog" command line tool.

Is there something usable already out there?

Thanks and regards
Markus

 

 

icon5.gif   Adding New User Failed During Email Send, posted by Jason Moore on Wed Jan 17 18:11:49 2018 

The following error occured during the addition of new user, first time this occured:

"Cannot send email notification to "xxx@xxx.com" Sender address rejected: Domain not found

Please use your browser's back button to go back

 

We are using version 2.7.1-2002. Could this be a version issue? When we loaded the new version, the browser GUI was scrambled and illegible using Microsoft Edge/Explorer and Firefox.

    icon2.gif   Re: Adding New User Failed During Email Send, posted by Stefan Ritt on Wed Jan 17 19:51:49 2018 

This error comes from your email SMTP server, not from elog. It complains about the email address xxx@xxx.com which refers to a nonexisting domain. Just read the message.

Stefan

Jason Moore wrote:

The following error occured during the addition of new user, first time this occured:

"Cannot send email notification to "xxx@xxx.com" Sender address rejected: Domain not found

Please use your browser's back button to go back

 

We are using version 2.7.1-2002. Could this be a version issue? When we loaded the new version, the browser GUI was scrambled and illegible using Microsoft Edge/Explorer and Firefox.

 

icon1.gif   Drop down order, posted by Alan Grant on Mon Jan 15 16:46:58 2018 

Can you please make a change to have the Quick Filter ComboBox controls reference the field type for ordering purposes?

For example, if attribute Lot Number is Type Numeric then the ComboBox should be listed in numerical order instead of alphanumeric (eg: 1,2,3,11,21 vs 1,11,2,21,3).

Best Regards.

icon4.gif   Unsafe browsing, posted by Tim Schelfhout on Mon Jan 15 15:56:07 2018 

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.

    icon2.gif   Re: Unsafe browsing, posted by Stefan Ritt on Mon Jan 15 16:27:19 2018 

Safety is getting more and more an issue these days. Normal browsers don't accept self-signed certificates any more. One possibility is to get a certificate from https://letsencrypt.org/

Stefan

Tim Schelfhout wrote:

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.

 

icon5.gif   about attachment, posted by Xuan Wu on Fri Jan 12 09:54:41 2018 

Hi all,

Some elog users of our site(CSNS) mentioned some advice about attachment:

1.Can imagemagick create thumbnail for .bmp file now?

2.Can re-sort the attachments after attachments uploaded by dragging or clicking up/down arrow or anything except deleting and re-upload attachment again?

3.Can add some description under the thumbnail of uploaded attachment? I've suggested them adding the description to the name of attchment or writing the detail in the text area. They are seem not very satisfied with this solution.

Any advice and suggestion will be appreciated.

Cheers

icon6.gif   Tool Tips, posted by Grant Jeffcote on Sun Nov 26 22:15:34 2006 
Hi Stefan,

Is there a way to add a 'Tool Tips' to individual 'Options' similar to that currently available for Attributes? I have several checkboxes under an attribute for predefined email groups and would like to see if I can make the recipient list viewable via a mouse hover using the 'Tool tip' feature.
If not possible can it be added to the wishlist?

Many thx.
    icon2.gif   Re: Tool Tips, posted by Stefan Ritt on Tue Nov 28 10:20:12 2006 

Grant Jeffcote wrote:
Hi Stefan,

Is there a way to add a 'Tool Tips' to individual 'Options' similar to that currently available for Attributes? I have several checkboxes under an attribute for predefined email groups and would like to see if I can make the recipient list viewable via a mouse hover using the 'Tool tip' feature.
If not possible can it be added to the wishlist?


Ok, I implemented this. It is in revision 1760 and will be contained in the next release.
       icon2.gif   Re: Tool Tips, posted by Grant Jeffcote on Tue Nov 28 10:25:08 2006 

Stefan Ritt wrote:

Grant Jeffcote wrote:
Hi Stefan,

Is there a way to add a 'Tool Tips' to individual 'Options' similar to that currently available for Attributes? I have several checkboxes under an attribute for predefined email groups and would like to see if I can make the recipient list viewable via a mouse hover using the 'Tool tip' feature.
If not possible can it be added to the wishlist?


Ok, I implemented this. It is in revision 1760 and will be contained in the next release.


That's really great, thank you so much.
What will the configuration line be?
          icon2.gif   Re: Tool Tips, posted by Stefan Ritt on Tue Nov 28 10:26:33 2006 

Grant Jeffcote wrote:
What will the configuration line be?


If you have
MOptions item = value_1, value_2

you can do a
Tooltip value_1 = text
             icon2.gif   Re: Tool Tips, posted by Grant Jeffcote on Tue Nov 28 22:12:13 2006 

Stefan Ritt wrote:

Grant Jeffcote wrote:
What will the configuration line be?


If you have
MOptions item = value_1, value_2

you can do a
Tooltip value_1 = text


Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?
                icon2.gif   Re: Tool Tips, posted by Stefan Ritt on Wed Nov 29 13:42:14 2006 

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:
What will the configuration line be?


If you have
MOptions item = value_1, value_2

you can do a
Tooltip value_1 = text


Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?


ELOG itself has a limit of 256 characters, but that can be changed easily. I found that Mozilla Firefox only showed 70 characters and then three dots ("..."), while Internet Explorer showed all 256 characters, wrapping words if necessary. So it strongly depends on the browser.
                   icon2.gif   Re: Tool Tips, posted by Grant Jeffcote on Wed Nov 29 22:44:15 2006 

Stefan Ritt wrote:

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:
What will the configuration line be?


If you have
MOptions item = value_1, value_2

you can do a
Tooltip value_1 = text


Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?


ELOG itself has a limit of 256 characters, but that can be changed easily. I found that Mozilla Firefox only showed 70 characters and then three dots ("..."), while Internet Explorer showed all 256 characters, wrapping words if necessary. So it strongly depends on the browser.



Thanks, we use Internet Explorer in service but I tested using Mozilla (hence above).
I'd really like to be able change the limit to more than 256 characters, is this simply a configuration parameter or a code change?
                      icon2.gif   Re: Tool Tips, posted by Stefan Ritt on Thu Nov 30 20:49:56 2006 

Grant Jeffcote wrote:
Thanks, we use Internet Explorer in service but I tested using Mozilla (hence above).
I'd really like to be able change the limit to more than 256 characters, is this simply a configuration parameter or a code change?


It is a code change. I increased it to 10000 chars in revision 1766, it will be contained in the next release.
                         icon2.gif   Re: Tool Tips, posted by Grant Jeffcote on Thu Nov 30 22:07:31 2006 

Stefan Ritt wrote:

Grant Jeffcote wrote:
Thanks, we use Internet Explorer in service but I tested using Mozilla (hence above).
I'd really like to be able change the limit to more than 256 characters, is this simply a configuration parameter or a code change?


It is a code change. I increased it to 10000 chars in revision 1766, it will be contained in the next release.


Thx Stefan, I can write a book in there now! ;o))
                   icon2.gif   Re: Tool Tips, posted by Grant Jeffcote on Tue Feb 6 18:04:54 2007 

Stefan Ritt wrote:

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:
What will the configuration line be?


If you have
MOptions item = value_1, value_2

you can do a
Tooltip value_1 = text


Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?


ELOG itself has a limit of 256 characters, but that can be changed easily. I found that Mozilla Firefox only showed 70 characters and then three dots ("..."), while Internet Explorer showed all 256 characters, wrapping words if necessary. So it strongly depends on the browser.


Hi Stefan,

Many thanks for implementing this feature, it is very useful and works very well, I can't seem to get the Tooltips to show up using the 'ROptions' (radio buttons) though? Could you check if it is available for this please?

Thx
                      icon2.gif   Re: Tool Tips, posted by Stefan Ritt on Tue Feb 6 19:56:05 2007 

Grant Jeffcote wrote:
I can't seem to get the Tooltips to show up using the 'ROptions' (radio buttons) though? Could you check if it is available for this please?


Did I tell that it also works with 'ROptions' ??? It does not! I implemented this just now in revision 1788. The fix will be contained in the next release.
                         icon14.gif   Re: Tool Tips, posted by Grant Jeffcote on Tue Feb 6 21:46:59 2007 

Stefan Ritt wrote:

Grant Jeffcote wrote:
I can't seem to get the Tooltips to show up using the 'ROptions' (radio buttons) though? Could you check if it is available for this please?


Did I tell that it also works with 'ROptions' ??? It does not! I implemented this just now in revision 1788. The fix will be contained in the next release.


Sorry, just checking. Happy
Many thanks Stefan Big grin
                         icon5.gif   Re: Tool Tips, posted by Grant Jeffcote on Thu Nov 23 12:51:51 2017 
Stefan, I know this request was a long time ago on an older version of E-Log (which we are still using) but can you tell me if Tooltips on Radio Buttons was ever implemented, it's not working on our version (2.92.2)?
Working as it should on MOptions?


Stefan Ritt wrote:

Grant Jeffcote wrote:
I can't seem to get the Tooltips to show up using the 'ROptions' (radio buttons) though? Could you check if it is available for this please?


Did I tell that it also works with 'ROptions' ??? It does not! I implemented this just now in revision 1788. The fix will be contained in the next release.
                            icon2.gif   Re: Tool Tips, posted by Stefan Ritt on Mon Dec 11 13:20:49 2017 
Tooltips on 'ROptions' work since 2007, but your version 2.9.2 is pre-2007, so you should consider to upgrade.

Stefan


Grant Jeffcote wrote:
Stefan, I know this request was a long time ago on an older version of E-Log (which we are still using) but can you tell me if Tooltips on Radio Buttons was ever implemented, it's not working on our version (2.92.2)?
Working as it should on MOptions?


Stefan Ritt wrote:

Grant Jeffcote wrote:
I can't seem to get the Tooltips to show up using the 'ROptions' (radio buttons) though? Could you check if it is available for this please?


Did I tell that it also works with 'ROptions' ??? It does not! I implemented this just now in revision 1788. The fix will be contained in the next release.
icon5.gif   hosts allow, posted by Susan James on Fri Nov 17 18:58:52 2017 

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

 

 

    icon2.gif   Re: hosts allow, posted by Andreas Luedeke on Sat Nov 18 19:36:57 2017 

Hi Susan,

according to the documentation you need to add "Hosts deny = All" in addition to the "Hosts allow" command.
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#access).
Cheers
Andreas
  • Hosts allow = <list>
  • Hosts deny = <list>

These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like 123.213. (note the trailing '.') or .mit.edu, or the word All. The following rules are applied:

  • Access will be granted when a host matches a pattern in "hosts allow".
  • Otherwise, access will be denied when a host matches a pattern in "hosts deny".
  • Otherwise, access will be granted.

These rules are applied before any password is checked. To debug problems, start elogd with the "-v" flag, in which case the rule checking is printed on the screen.

 

Susan James wrote:

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

 

 

 

       icon2.gif   Re: hosts allow, posted by Susan James on Tue Nov 21 01:27:06 2017 

thanks for your quick reply.

the configuration is still not working.  See my entry below which denies everyone.

I've tried many different combinations of 'hosts allow and hosts deny'

we want to restrict all our logbooks to only domain lbl.gov

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov
 

Can you help?

 

Andreas Luedeke wrote:

Hi Susan,

according to the documentation you need to add "Hosts deny = All" in addition to the "Hosts allow" command.
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#access).
Cheers
Andreas
  • Hosts allow = <list>
  • Hosts deny = <list>

These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like 123.213. (note the trailing '.') or .mit.edu, or the word All. The following rules are applied:

  • Access will be granted when a host matches a pattern in "hosts allow".
  • Otherwise, access will be denied when a host matches a pattern in "hosts deny".
  • Otherwise, access will be granted.

These rules are applied before any password is checked. To debug problems, start elogd with the "-v" flag, in which case the rule checking is printed on the screen.

 

Susan James wrote:

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

 

 

 

 

          icon2.gif   Re: hosts allow, posted by Susan James on Thu Dec 7 21:54:58 2017 

Hi All,

We're still having trouble with hosts.allow and hosts.deny.

We're trying to allow all of our domain  lbl.gov to the access list

for our logbooks.  But the combination below is not working.

==========================

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov

========================
Can someone help?

Susan James wrote:

thanks for your quick reply.

the configuration is still not working.  See my entry below which denies everyone.

I've tried many different combinations of 'hosts allow and hosts deny'

we want to restrict all our logbooks to only domain lbl.gov

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov
 

Can you help?

 

Andreas Luedeke wrote:

Hi Susan,

according to the documentation you need to add "Hosts deny = All" in addition to the "Hosts allow" command.
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#access).
Cheers
Andreas
  • Hosts allow = <list>
  • Hosts deny = <list>

These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like 123.213. (note the trailing '.') or .mit.edu, or the word All. The following rules are applied:

  • Access will be granted when a host matches a pattern in "hosts allow".
  • Otherwise, access will be denied when a host matches a pattern in "hosts deny".
  • Otherwise, access will be granted.

These rules are applied before any password is checked. To debug problems, start elogd with the "-v" flag, in which case the rule checking is printed on the screen.

 

Susan James wrote:

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

 

 

 

 

 

             icon2.gif   Re: hosts allow, posted by Andreas Luedeke on Fri Dec 8 19:47:04 2017 
Hi Susan,
the documentation states that you should start elogd with the -v option from the command line and look at the output. Did you try this?
You might post the output here to get further help.
Cheers
Andreas
Susan James wrote:

Hi All,

We're still having trouble with hosts.allow and hosts.deny.

We're trying to allow all of our domain  lbl.gov to the access list

for our logbooks.  But the combination below is not working.

==========================

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov

========================
Can someone help?

Susan James wrote:

thanks for your quick reply.

the configuration is still not working.  See my entry below which denies everyone.

I've tried many different combinations of 'hosts allow and hosts deny'

we want to restrict all our logbooks to only domain lbl.gov

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov
 

Can you help?

 

Andreas Luedeke wrote:

Hi Susan,

according to the documentation you need to add "Hosts deny = All" in addition to the "Hosts allow" command.
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#access).
Cheers
Andreas
  • Hosts allow = <list>
  • Hosts deny = <list>

These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like 123.213. (note the trailing '.') or .mit.edu, or the word All. The following rules are applied:

  • Access will be granted when a host matches a pattern in "hosts allow".
  • Otherwise, access will be denied when a host matches a pattern in "hosts deny".
  • Otherwise, access will be granted.

These rules are applied before any password is checked. To debug problems, start elogd with the "-v" flag, in which case the rule checking is printed on the screen.

 

Susan James wrote:

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

 

 

 

 

 

 

                icon2.gif   Re: hosts allow, posted by Stefan Ritt on Mon Dec 11 13:16:32 2017 

Have you set

Resolve host names = 1

in the config file? If it still does not work, run "elogd -v" from the terminal and watch the output. You should see someting like:

Remote host "mpc1865.psi.ch" matches "ALL" in "Hosts deny". Access denied.
Remote host "mpc1865.psi.ch" matches ".lbl.gov" in "Hosts allow". Access granted.

 

Regards,
Stefan

Andreas Luedeke wrote:
Hi Susan,
the documentation states that you should start elogd with the -v option from the command line and look at the output. Did you try this?
You might post the output here to get further help.
Cheers
Andreas
Susan James wrote:

Hi All,

We're still having trouble with hosts.allow and hosts.deny.

We're trying to allow all of our domain  lbl.gov to the access list

for our logbooks.  But the combination below is not working.

==========================

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov

========================
Can someone help?

Susan James wrote:

thanks for your quick reply.

the configuration is still not working.  See my entry below which denies everyone.

I've tried many different combinations of 'hosts allow and hosts deny'

we want to restrict all our logbooks to only domain lbl.gov

[ below denies ALL ]

Hosts allow = .lbl.gov
Hosts deny = ALL

[ below denies ALL ]

Hosts deny = ALL

Hosts allow = .lbl.gov
 

Can you help?

 

Andreas Luedeke wrote:

Hi Susan,

according to the documentation you need to add "Hosts deny = All" in addition to the "Hosts allow" command.
Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#access).
Cheers
Andreas
  • Hosts allow = <list>
  • Hosts deny = <list>

These two settings can be used to restrict the access to the logbook to certain computers. It is similar to the UNIX hosts.allow and hosts.deny files. The list can consist of individual host names or IP numbers, subnet masks like 123.213. (note the trailing '.') or .mit.edu, or the word All. The following rules are applied:

  • Access will be granted when a host matches a pattern in "hosts allow".
  • Otherwise, access will be denied when a host matches a pattern in "hosts deny".
  • Otherwise, access will be granted.

These rules are applied before any password is checked. To debug problems, start elogd with the "-v" flag, in which case the rule checking is printed on the screen.

 

Susan James wrote:

I'm trying to wrap our elog instance to our company domain which is lbl.gov

I add this entry below (without quotes) to elogd.cfg and it's not working.  the world can see our logbooks

" Hosts Allow = *.lbl.gov ".

can someone help?

 

 

 

 

 

 

 

icon4.gif   possible DOS vulnerability with negative Content-Length field, posted by Christian Herzog on Tue Dec 5 15:30:43 2017 

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/

 

    icon2.gif   Re: possible DOS vulnerability with negative Content-Length field, posted by Stefan Ritt on Wed Dec 6 13:34:56 2017 

I have fixed this issue in the current develop branch of elog.

Stefan

Christian Herzog wrote:

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/

 

 

ELOG V3.1.5-3fb85fa6