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 ". |
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 |
|
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' |
|
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 |
|
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:
|
|
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: |
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 |
|
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 |
|
Config: conditional coloring of items when 2 conditions are met (and|or), posted by Tim Schelfhout on Fri Nov 24 08:54:38 2017
|
Hello,
Trying to color an entry log when 2 conditions are met. Tried
Style Result Hired and Administration NOK = background-color:red |
|
Re: Config: conditional coloring of items when 2 conditions are met (and|or), posted by Andreas Luedeke on Mon Nov 27 22:10:22 2017
|
I am not aware that it is forseen to define logical operators in combination with the Style command. How did you get the idea that this should work?
But you should be able to define multiple Style commands, acting on different format parameter.
Tim |
|
Windows 10, posted by Michael Cianci on Fri Nov 24 17:29:49 2017
|
Sorry to bother you with such a simple question, but I am not an IT professional. We just received word that our IT department has plans to update our
system to Windows 10 in 2018. Was wondering if our current version of ELOG was compatable with Windows 10? Thank You Very Much For Your Help. |
|
drop-down list not working, posted by Sara Vanini on Mon Nov 13 12:58:41 2017
|
Hi,
after ubuntu 16 system upgrade, elog version (3.1.1-1-1) on firefox version 56.0+build6-0ubuntu0.16.04.2 , the drop-down menus (Styles, Font,
Size, etc) don't work anymore. |
|
Attribute option "+x" not searcheable, posted by Stefano Lacaprara on Mon Oct 23 11:47:50 2017
|
Dear experts,
I have an elog with an attribute with fixed values, like this:
|
|
Re: Attribute option "+x" not searcheable, posted by Andreas Luedeke on Sat Oct 28 09:12:32 2017
|
Hi Stefano,
you could try to html encode the "+" and "-" sign in the option list
Options Half = +x, -x, both
|
|
Re: Attribute option "+x" not searcheable, posted by Andreas Luedeke on Tue Oct 31 16:56:24 2017
|
Hi Stefano,
I've tested it: it does not work.
Neither in edit nor in list view the HTML encoded characters show correctly.
|
|
Date must be between 1970 and 2037??, posted by Tim Schelfhout on Wed Oct 11 15:55:02 2017
|
Hey there,
Trying to record birthdates in ELOG ... field type being date results in error:
Date must be between 1970 and 2037
Can |
Format Form, posted by Tim Schelfhout on Mon Oct 2 12:55:18 2017 
|
Hello there,
I am trying to format my entry form a little bit more practical and readable. I am struggling with the following:
Numbers should be standard fields of 3 characters and can only be 3 characters wide (doing this by Format Leeftijd=1, css, 3, |
|
Re: Format Form, posted by Stefan Ritt on Mon Oct 2 14:58:32 2017
|
The way and entry form can be customized is kind of limited in elog. You can use "format <attribute> = ..." to request a certain width,
number of allowed characters and special CSS class (which of course you have to define). If you want a complete custom entry form, have a look here: elog:66909 . This requires however writing your own HTML, CSS and JavaScript. |
|
Re: Format Form, posted by Tim Schelfhout on Mon Oct 2 15:20:04 2017
|
Thankx 4 the quick reply Stefan. The link you provided does not work .... could you point me again in the
right direction? Where can I find more info on this ability?
Thankx |
|
Re: Format Form, posted by Stefan Ritt on Mon Oct 2 15:53:39 2017
|
The link does now work in the email, but if you go to the web interface of the forum it does work.
Anyhow, you can go directly to https://midas.psi.ch/elogs/Forum/66909
Stefan |