Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 348 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  67234   Tue Apr 10 15:35:07 2012 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.1-2444Re: segfault on empty, non-writable passwd file

Achim Dreyer wrote:

 

Segfault when password file is empty and not writable a segmentation fault is generated when a new user tries to register:

 

root#  > passwd

root#  chown root.root passwd

root#  chmod 644 passwd

root#  grep -i usr elogd.cfg

root#


kernel: [515323.672377] elogd[31048]: segfault at 78 ip 00000000004ba780 sp 00007fff03cd2078 error 4 in elogd[400000+dc000]
 

I cannot reproduce this error when running within gdb.

 

Thanks for reporting that bug. I fixed it in SVN revision 2448. 

  67217   Wed Mar 28 04:05:01 2012 Reply rusI ruslan.2008@hotmail.comCommentWindows2.9.1-2435Re: mySQL / SQL synchronisation
> does anybody has interest with a full synchronisation 
> between elog logbook
> on mySQL and SQL database

I am interested!!!
But I don't know how to do that.
  67243   Wed Apr 11 16:32:22 2012 Question Thomas Kleebthomas.kleeb@psi.chQuestionLinux2.9.1-2435SSL

I'm slowly able to see the finish line

Now all I need to do is get SSL to work. My server name is hf-info-elog and I'm not sure what the correct values for Port= and URL= should be.

thank
Tom (the green-horn)

  67244   Wed Apr 11 16:43:37 2012 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.1-2435Re: SSL

Thomas Kleeb wrote:

I'm slowly able to see the finish line

Now all I need to do is get SSL to work. My server name is hf-info-elog and I'm not sure what the correct values for Port= and URL= should be.

thank
Tom (the green-horn)

All you need is a SSL=1 in the config file, then the default port of 443 will be used. The URL is the one seen from outside, like

 

https://hf-info-elog.psi.ch

 

or so. The certificate from the distribution is self-signed and therefore the browser will complain. Go to AIT to obtain an official certificate.

- Stefan

  67249   Sun Apr 15 22:53:41 2012 Question Aldo Saavedraa.saavedra@physics.usyd.edu.auQuestionLinux2.9.1-2435author field in reply
Hi,

I was wondering what is the correct way so that the author field when a reply is made shows the author of the
person making the reply.
In version 2.6, the field was filled correctly but since upgrading to ELOG V2.9.1-2435 due to the ssh problem
the field just keeps the author of the original post.

I have a tried a number of subst on reply Author = $long_name with no luck.

Any ideas?

Cheers,
Aldo
  67252   Wed Apr 18 21:53:26 2012 Reply A. TuttleATuttle@UW.eduQuestionLinux2.9.1-2435Re: author field in reply
Look in https://midas.psi.ch/elog/config.html
--
Fun things to set are:
Preset on first reply <attribute> = <string>
and
Preset on reply <attribute> = <string>
  67264   Mon May 7 13:41:38 2012 Question Roland Gsellroland.gsell@oeaw.ac.atInfoLinux2.9.1-2435Access rights

Hi,

the manual says:

"
There are four ways through which access to a logbook may be controlled:

it may be open for all to read ;
it may require a common "read" password for all users ;
it may require each user to have an individual user account (login name) and password ;
finally, access may be granted or not depending on the address of the workstation you are using.
"

But it doesn't say how to do so or at least I didn't find it.

If I have each user have to log in with an individual accout, can I define which logbooks he can read and/or modify?
If yes, how to do that?

Also, please accept my vote for user groups. We can use that, too.

TIA,
Roland.

  67265   Mon May 7 15:12:24 2012 Reply Stefan Rittstefan.ritt@psi.chInfoLinux2.9.1-2435Re: Access rights

Roland Gsell wrote:

Hi,

the manual says:

"
There are four ways through which access to a logbook may be controlled:

it may be open for all to read ;
it may require a common "read" password for all users ;
it may require each user to have an individual user account (login name) and password ;
finally, access may be granted or not depending on the address of the workstation you are using.
"

But it doesn't say how to do so or at least I didn't find it.

If I have each user have to log in with an individual accout, can I define which logbooks he can read and/or modify?
If yes, how to do that?

Also, please accept my vote for user groups. We can use that, too.

TIA,
Roland.

You haven't found it. Just look here:

http://midas.psi.ch/elog/config.html#access

 

You need Password file and Login user

ELOG V3.1.5-3fb85fa6