ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 231 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 230, 231, 232 ... 804, 805, 806 Next

Author Email down

Wed Apr 15 09:26:37 2009

Re: Long cookie content is not handled properly.

Simon Patton wrote:

I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.

In 2.7.5 the code was:

    for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )
        if (i < (int) sizeof(cookie)-1)
            cookie[i++] = *p++;

While in 2.7.6 is became:

    for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n';)
        if (i < (int) sizeof(cookie) - 1)
            cookie[i++] = *p++;
        else
            break;

This leaves 'p' pointing to the middle of the cookie's content and I can not see that this is corrected in the loop (sorry if I've missed that).

The solution I used to patch 2.7.5 was the following:

    for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; ++p)
        if (i < (int) sizeof(cookie)-1)
            cookie[i++] = *p;

which simply truncates the contents of the cookie (which is assumed not to be an elogd cookie) but leaves 'p' in the right place to extract the next one.

You're absolutely right about that. I incorporated your patch into revision #2192.

66316

Wed Apr 15 09:51:35 2009

Re: Multi Logook Login

Hal Proctor wrote:

Grant Jeffcote wrote:

Hal Proctor wrote:

We have two logbooks, each with a different list of users.

The logbooks are open to all network users for read only.

A user with Write permisions logs into his designated logbook.

He then decides to view the other logbook, the one he does not have write permissions to by clicking on the tab to the other logbook.

He is immediately logged out of the logbook he has write permissions to.

He did not close his browser session, only clicked on the other logbook tab.

Is there Any way to keep that person logged into the logbook he has rights to without having the "keep me logged in Checkbox"?

Just like this site has Forum, Config Examples, etc.

Once you select another tab they are logged out of their logbook they just logged in to.

Have a look at this thread Hal, worked well for me: Link

thanks Grant, but I dont see the solution. your last entry still states users being logged out when switching logbooks.

Are you suggesting that every user within our orginization needs to be on the deny list of logbook1 if they have rights to logook2?

Can you try the following:

Put your "password file = xxx" option from the [global] section in elogd.cfg into each individual logook, remove it from [global]
Remove all cookies from your browser
Try again to log in to the individual logbooks

The login is handled through cookies. Once you log in, you get two cookies unm (for user name) and upwd (for user password). Each cookie contains a "path" which controls to which URL the browser sends that cookie. If you "password file = xxx" statement is under [global], then "path=/", meaning the cookie is sent for all logbooks. This confuses you if you have different rights for different logooks. If "password file = xxx" is however in each individual loogbooks configuration, then you get "path=/<lobook>". You can check that by inspecting your browser's cookies. In that case the login name and password cookies are only sent to the URL for that specific logbook. I have not tested that extensively (different browsers, with/without Apache proxy), but if it works reliably, I will put this into the documentation.

66318

Wed Apr 15 12:56:18 2009

Re: ROptions value changed in the edit page

> When ROptions items contain the same substring and this substring is also an ROptions item (ex: notdone, 
> done), the value of the entry could change in the edit page. 
> It depends on the item order in the config file. 
> 
> If Options is used (instead of ROptions), it works as expected.
> 
> Is it a bug?
> 
> 
> Examples : 
> 
> #Insert "notdone" as new entry. When you try to edit the entry, the displayed value is "done".
> 
> [test_bad]
> Attributes = Author, Category
> ROptions Category = notdone, done
> 
> #No problem if you change the item order 
> 
> [test_good]
> Attributes = Author, Category
> ROptions Category = done, notdone

Thanks for reporting this bug. I fixed it in SVN revisoin 2193.

66321

Thu Apr 16 08:34:03 2009

Re: Config so that users can delete only their own entries?

Dennis Seitz wrote:

I've tried

Deny_Delete = All
Allow Delete = $author

and just
Allow Delete = $author

But either users can delete anyone's entries, or they can't delete any entries.

Am I missing something? If not, can you add the capability to allow users to delete, but only their own entries?

Thanks as usual for a great piece of code!

You cannot put $author into any Allow or Deny option, only explicit login names (not "full" names). What you want however is

Restrict Edit = 1

which lets only the original author either delete or edit entries. If you use that option, you probably want as well

Preset Author = $long_name
Preset on reply Author = $long_name
Preset on duplicate Author = $long_name
Locked Attributes = Author

So a user cannot pretend to be somebody else. You also need a valid "admin user = ..." statement. Note that the admin user always can delete/edit entries. If no admin user is defined, everybody has automatically admin rights, so Restrict Edit has no effect.

66328

Fri Apr 24 09:03:05 2009

Re: Is there a way to import old log messages

Joseph Le wrote:

I update my elog from version 2.7.5 to 2.7.6 and mistakenly replace configuration file. so i have to reconfigure everything from ground up. when my elog back online, old log messages are not show up. is there a way to import old log messages from old log book to new one.

thanks

You don't have to import old log book messages, they should be shown automatically (as long as you don't overwrite your configuration file mistakenly). If you had a different logbook name (not "demo") your files will still be there under c:\Program Files\ELOG\logbooks\<logbook name>. Just add the proper name in elogd.cfg, restart elogd and you will see your old messages.

66329

Fri Apr 24 12:25:16 2009

Re: mail to localhost?

Mike wrote:

Nevermind!

What was your problem (maybe others could benefit from this information...) ???

66331

Tue Apr 28 07:53:37 2009

Re: Error: Failed dependencies:

Rob Snihur wrote:

Carl Shirey wrote:

Stefan Ritt wrote:

Carl Shirey wrote:

I went to upgrade to the new version of elog I receive a error message that is.

error: Failed dependencies:
	libssl.so.6 is needed by elog-2.7.5-1.i386
	rtld(GNU_HASH) is needed by elog-2.7.5-1.i386

Do I need these dependencies for elog to work? If I do need them where do I get them for Suse 10.2.

Thank you for any help.

Carl

Starting from 2.7.5, elog needs libssl for any https:// connection. Just install the RPM like you install any other RPM. Now I'm not familar with SUSE, but I found links like that:

http://lenz.homelinux.org/RPMs/

from where you can obtain RPMs. You might have to adjust your YaST installation sources. The package you need should be named opensll-xxx where xxx is some number.

Thank you

I will look into it.

Carl

Hi,

I just tried to install the latest elog on linux Fedora 10. I also get an error saying that libssl.so.6 is needed.

But I already have libssl.so.7 installed. Should I also install libssl.so.6 ?

thx,

-rob

[snihur@nunllap01 ~]$ rpm -qa | grep ssl
qca-ossl-2.0.0-0.4.beta3.fc10.i386
openssl-0.9.8g-12.fc10.i686
docbook-style-dsssl-1.79-5.fc9.noarch
nss_compat_ossl-0.9.4-2.fc10.i386
openssl-devel-0.9.8g-12.fc10.i386
[snihur@nunllap01 ~]$ rpm -q --provides openssl
config(openssl) = 0.9.8g-12.fc10
lib4758cca.so
libaep.so
libatalla.so
libchil.so
libcrypto.so.7
libcswift.so
libgmp.so
libnuron.so
libssl.so.7
libsureware.so
libubsec.so
openssl = 0.9.8g-12.fc10
openssl(x86-32) = 0.9.8g-12.fc10

The RPM system is a bit picky about which version is required. I believe you have to install libssl.so.7 or compile elog from the sources, which is very simple.

66333

Wed Apr 29 07:52:57 2009

Re: elogd runs by a user but not by root

Dongwook Jang wrote:

Hi,

I really don't understand why elogd cannot run by root but it runs by a user.

I've put elog deamon in /etc/init.d. So it didn't bring up, but it runs if I run it by user interactively.

Thanks,

Dongwook

That's a security issue. If elogd runs under a user and gets hacked, the hacker obtains just the user rights, which can be limited. If it runs under root, the hacker will automatically get root rights, which is bad. Technically, there is no reason why elogd cannot be run as root. Just put

Usr = root

Grp = root

into elogd.cfg.

Goto page Previous 1, 2, 3 ... 230, 231, 232 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6