Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
| JD wrote: |
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
| Stefan Ritt wrote: |
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
| JD wrote: |
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
|
Re: More questions about groups, posted by Stefan Ritt on Thu Apr 21 22:54:46 2005
|
> I am running 2.5.8-3 with the elogd.c 1.632. I have attached the config
> file that I am using. I have a top group "src", with logbooks "SRC
> Analysis" and "SRC Mail" in it. These two logbooks share the same password
> file. If one logs into one, I would like them to be not have to login to
> the other. If I put the password file name under [global src], I get this
> behaviour, but the logbook selection page does not show my graphic or the
> locks by the logbook names (instead it has the Alt text "This logbook
> requires authentication."
Thanks for reporting this bug. I fixed it in the current CVS version. |
|
Re: More questions about groups, posted by Stephen A. Wood on Fri Apr 22 18:16:25 2005
|
> Thanks for reporting this bug. I fixed it in the current CVS version.
I get my Icons and Graphics in the top group now. Thanks for fixing it. |
|
Re: More adventures with SSL, posted by Stefan Ritt on Wed Jul 28 16:38:07 2010
|
| Chuck Brost wrote: |
|
Stefan,
Everything has been working great since we last spoke (Version 2.7.8), until InfoSec decided to change how the Certs were created. Now they come with a little bit of code in the .key file before the Hash.. when I put the new .CRT and .KEY in the SSL folder I am asked on starting Elogd to provide a "PEM PassPhrase". As you can expect, if you do not enter one, or the incorrect one, it does not just turn off SSL, it exits the program. The key begins like this in the new versions:
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,ACF4A8B263EAA51D
(that little encode piece on the end is not the actual one in the key. I am assuming it is a passphrase key so it will know what the right passphrase is that should be entered.
We are assuming that this is the "Install password" they have set up to use to install the certs on all of the IIS servers we have. If that is indeed the case.. Does elog save this passphrase somewhere? does Elog save it in the registry? does it save it encrypted? Or with access security permissions set on the keys? I have a feeling that the answer to most of this is probably "no", but to know where we go from here, that is the place to start.
Thanks
Chuck
|
The pass phrase should not be stored anywhere for security reasons. Actually ELOG cannot stored it encrypted, because strong encryption is a one-way encryption which cannot be reverted, so ELOG would have to store it in plain text, which is not good. Actually all SSL web servers have this problem. See for example:
http://www.akadia.com/services/ssh_test_certificate.html
In Step 3 they tell you how to remove the pass phrase for Apache. The same holds true for ELOG. |
|
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Tue Jan 12 16:10:34 2016
|
Use automatic email notifications or RSS feeds. Read the manual for that.
Stefan
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 08:37:42 2016
|
I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.
Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|
|
Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:27:21 2016
|
Yeah, I found the RSS feed feature, but I could not get ETags/Last-Modified header fields which meant that I'd have to read and parse the entire feed every time. Maybe I made a mistake and they do work, but if not, I think it would make sense to implement as it should save work for both the server and the client.
| Johan Forsberg wrote: |
|
Hi again!
I've another need that you probably already thought of :)
I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).
Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.
Cheers,
Johan
|
|