Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 435 of 808  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  66327   Tue Apr 21 22:13:26 2009 Disagree Andreas Wilkewilke4all@hotmail.deQuestionWindows2.7.5-2130Mirror Server Funktion

Ich möchte meine "lokale" ELOG Installation mit einem Server in der Firma synchronisieren.

Dazu habe ich in der entfernten Firewall ein Portmapping auf den ELOG Server in der Firma eingerichtet.

Wenn ich von meiner "lokalen" Maschine im Browser  http://meinedomain.dyndns.xx:PORT aufrufe, kann ich auf den ELOG Server zugreifen.

Ich habe in meiner "lokalen" Installation in der Section [global] den Mirror-Server = http://meinedomain.dyndns.xx:PORT angeben.

Beim Synchornisieren bekomme ich jedoch den Hinweis "Fehler beim Zugriff auf entfertes Logbuch".......


 

  66326   Tue Apr 21 20:32:10 2009 Reply Hal Proctorhproctor@mpm.comQuestionWindows2.7.5Re: Multi Logook Login RESOLVED

Stefan Ritt wrote:

 

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.

 This worked for us just fine!  thanks!

  66325   Tue Apr 21 16:29:23 2009 Question Joseph Lejosephle9@gmail.comQuestionWindows2.7.6Is there a way to import old log messages

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

  66324   Sat Apr 18 02:49:42 2009 Question Mikemike@raghuexim.comBug reportLinux2.7.6-2191"Forgot Password?" link not working?

I have my site running under apache. I don't have a /elog/ directory.

for example most would do http://www.example.com/elog/ to visit elog

but my site loads at http://www.example.com/

The site is private so it's password protected. Everything works fine except

if I click the "Forgot Password" link it does nothing.

but if I go to one of the log books...

http://www.example.com/open/

The forgot password link works.

Is there anyway to fix this? I have nothing else running on the server, it's dedicated to only ELOG.

That's why I don't want to have it running under /elog/ in the url.

  66323   Sat Apr 18 00:33:53 2009 Reply Dennis Seitzdseitz@berkeley.eduQuestionAll2.7.5Re: Config so that users can delete only their own entries?
Thanks for reminding me of that, it will do fine. A suggestion: Separate Restrict Edit into Restrict Edit and Restrict Delete or some functional equivalent. Then we have the choice to restrict one or the other or both. Is that worth doing?


Stefan Ritt wrote:

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.
  66322   Fri Apr 17 22:44:58 2009 Idea Mikemike@raghuexim.comQuestionLinux2.7.6-219mail to localhost?

Initially I thought you had to specify a port number after localhost for emailing.

As it turns out just putting "localhost" as the email server in the elog config

file works just fine. We have a strange problem where our elog server is running.

our outgoing mail has to be routed through port 465 and SSL. I had to set up

postfix and stunnel to handle this arrangement.

  66321   Thu Apr 16 08:34:03 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.5Re: 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.
  66320   Wed Apr 15 17:57:19 2009 Question Dennis Seitzdenseitz@comcast.netQuestionAll2.7.5Config so that users can delete only their own entries?
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!
ELOG V3.1.5-3fb85fa6