Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 209 of 796  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  69658   Mon Mar 13 16:16:09 2023 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1.3Re: ssl certificate

I do run elog under:

Usr = elog
Grp = elog

But that does not change the location of my certificates: they are in "/usr/local/elog/ssl".
My guess: you just copied the .pem file to the /ssl directory, but did not rename it to server.crt?
And of course you need to overwrite server.key as well.

Kind Regards
Andreas

Giuseppe Cucinotta wrote:

Hi I'm here again,

According to my conf file I run elog under a specified user and group different from root. So I copied the .pem file I obtained from certbot in /etc/ssl as well as /urs/local/elog/ssl and ssl folder in the user directory (I will call it <user-dir>) but when I launch elog I receive the error that cannot initialize SSL because the old self signed certificate server.crt in <user-dir>/ssl is not found.

I wonder where in elog.cfg or elsewhere is written that <user-dir>/ssl/server.crt must be usedand how to fix it

Thanks

Giuseppe Cucinotta wrote:

Hi Laurent,

thanks very much! Probably I've copied the certificate in the wrong directory. I'll try ASAP

Laurent Jean-Rigaud wrote:

Hi Giuseppe,

The new certificate files should be copy under ssl folder (/usr/local/elog/ssl or /usr/share/elog/ssl by example, closed to templates and script directories) in place of the embedded (autosigned) certificate files enclosed with ELOG source.

It seems that there is no parameter to set a custom path.

SSL = <0 | 1>
Turn on Secure Socket Layer transport. If SSL is on, one can connect via https://... to the elogd daemon. If the URL = directive is used, make sure to use https://... instead of http://... there. The ELOG distribution contains a simple self-signed certificate in the ssl subdirectory. One can replace this certificate and key with a real ceritficate to avoid browser pop-up windows warning about the self-signed certificate. The default for this option is 0.

 

 

Giuseppe Cucinotta wrote:

We obtained a certificate from let's encrypt in order to replace the self signed certificate provided with elog. We copied the new certificates replacing the older server.crt

The problem is that when restarted elog raises an error related to the fact it is looking for server.crt and it doesn't find it anymore.

I searched in elog config file in order to find a way to indicate the new certificate but I didn't find how to manage this issue.

Any suggestion?

 

 

 

 

  69673   Wed Jun 14 21:19:48 2023 Question Leonardo Tacconileonardo.tacconi@unifi.itQuestionWindows3.1.3Nested commands in logbook

Hi everybody,

I am trying to setup my personal ELog, defining attributes and stuff like that. I just tried to make some nested commands but I really could not achieve that. 

The idea is something like this:

Attributes = Author

Options Author = Tizio{1}, Caio{2}, Sempronio{3}

{1} Attributes = Author, Project

{1} Options Project = Proj1{a}, Proj2{b}, Proj3{c}

{a} Attributes = Author, Project, Year

{a} Options Year = 2017, 2019

Anyway, when I select Proj1 nothing really happens. So, is there any way to set up nested commands like in the reported example?

Many thanks in advance!

P.S. Is there any documentation in which are reported all the possible commands that can be used?   

  69674   Sat Jun 17 22:13:01 2023 Idea Andreas Luedekeandreas.luedeke@psi.chQuestionAll3.1.3Re: Nested commands in logbook

Atrributes can only be defined once in a logbook.
But you can select which attributes are shown with the commands:

  • Show Attributes = <list>
    Attributes present in this list are shown in the single entry page. Omitting attributes can make sense for attributes which are automatically derived from other attributes via the Change <attribute> command.
  • Show Attributes Edit = <list>
    The same as Show Attributes, but for the entry form.

Those can be redifined in conditional attribute clauses.

(See https://elog.psi.ch/elog/config.html)

Leonardo Tacconi wrote:

Hi everybody,

I am trying to setup my personal ELog, defining attributes and stuff like that. I just tried to make some nested commands but I really could not achieve that. 

The idea is something like this:

Attributes = Author

Options Author = Tizio{1}, Caio{2}, Sempronio{3}

{1} Attributes = Author, Project

{1} Options Project = Proj1{a}, Proj2{b}, Proj3{c}

{a} Attributes = Author, Project, Year

{a} Options Year = 2017, 2019

Anyway, when I select Proj1 nothing really happens. So, is there any way to set up nested commands like in the reported example?

Many thanks in advance!

P.S. Is there any documentation in which are reported all the possible commands that can be used?   

 

  69707   Thu Nov 2 11:38:36 2023 Question Leonardo Tacconileonardo.tacconi@unifi.itQuestionWindows3.1.3Restricting entries view by user

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

  69708   Thu Nov 2 11:46:42 2023 Reply Stefan RittNo, stefan.ritt@psi.chQuestionWindows3.1.3Re: Restricting entries view by user

No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.

Stefan

Leonardo Tacconi wrote:

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

 

  69709   Tue Nov 7 22:07:24 2023 Reply Matteo Manninithanksmatteo.mannini@unifi.itQuestionLinux3.1.3Re: Restricting entries view by user

Dear Stefan,

thanks to the answer you gave to my colleague. 

Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,

1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks? 

2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?

thanks

 

Matteo

Stefan Ritt wrote:

No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.

Stefan

Leonardo Tacconi wrote:

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

 

 

  69710   Thu Nov 30 14:28:12 2023 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux3.1.3Re: Restricting entries view by user

Keeping the global and individual logbooks in sync is not possible. So indded my proposal is a cumbersome solution in your case. We do have "restrict edit" which lets users only edit their own entries, but we do not have "restrict view". Maye some thought for a future version of elog.

Stefan

Matteo Mannini wrote:

Dear Stefan,

thanks to the answer you gave to my colleague. 

Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,

1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks? 

2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?

thanks

 

Matteo

Stefan Ritt wrote:

No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.

Stefan

Leonardo Tacconi wrote:

Good morning,

I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.

Thank you in advance.

Leonardo

 

 

 

  69749   Tue Feb 27 16:00:43 2024 Question scottshiva.ps@stfc.ac.ukQuestionLinux3.1.3LDAP over password file

Hi Team,

Current configuration

=================

OS: Ubuntu 22.04.4 LTS

ELOG version: elog/jammy,now 3.1.3-1-1build2 amd64 [installed]

Installation method: apt install elog

Configuration file: /etc/elogd.cfg

LOGBOOKDIR= /var/lib/elog/logbooks}
RESOURCEDIR= /usr/share/elog


I had an ELOG server set up in the Windows server which is authenticated using a Password file. Recently, I have migrated the ELOG server to the Ubuntu server. I installed ELOG from the Ubuntu repository (apt install elog) and copied over the logbook and configuration file from the windows server to the new Ubuntu server. In the server, the configuration file was set to /etc/elog.conf by default. I have modified the init file and set the configuration file to /etc/elogd.cfg (this conf file is copied from the Windows server) which includes all the settings. After moving to the Ubuntu server I would like to authenticate users using the password file and LDAP. Could someone help me how to configure LDAP in my installation style?

The global configuration that is found on my installation is as follows:

###################################

; Global settings

Password file = elog.pwd
Self register = 1
Admin user = a, b,c, d, e, Iafdsel

Suppress Email to users = 1
SMTP host = example.com

Time format = %Y-%m-%dT%H:%M:%S
Date format = %Y-%m-%d

Restrict edit time = 2
Restrict edit = 1

Allow HTML = 1
Max content length = 209715200
Save drafts = 0

###################################

 

Should I add the below modification (by editing the necessary fields) to the current configuration? Will that make the LDAP and normal password file work?

############################

  • Enable LDAP authentication in the Makefile by setting USE_LDAP = 1   (I am not sure if I need to do this in my installation style. If yes, how do i do this?)
  • Authentication = LDAP
  • LDAP server = ldap://example.org:389
  • LDAP userbase = ou=People;dc=example,dc=org
  • LDAP login attribute = uid
  • LDAP register = 1

############################
 

Can someone guide me on what changes I need to make for this?

 

Many Thanks,
Scott

ELOG V3.1.5-2eba886