Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 439 of 808  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1562   Thu Dec 22 01:17:12 2005 Question PJ Meyerpjm@pjmeyer.orgQuestion 2.6New docs?
Just looked at change log for 2.6
was wondering where the documentation for the new additions/changes is/are.
  66881   Wed Aug 25 02:49:44 2010 Question Owen LaGardeolagarde@gmail.comQuestionLinux2.7.8honor "user" field in the Apache SSL request object or environment variables in SSL process groups?

Will elog defer user identification and authorization to the ssl engine of a *local* Apache proxy?  I'd like to try elog in a site that requires the service port positively authenticate and identify users via smartcard certificate ID.  Per SOP they have Apache+mod_ssl setting SSLUserName=SSL_CLIENT_S_DN_CN which sets both the SSL request object's "user" field and the REMOTE_USER environment var relative to the mod_ssl's session's process group leader.  Users auth with Apache's mod_ssl as a single-signon replacement for web apps which have traditional native, internal user accounts/passwords, but those passwords are subsumed by the Apache/smartcard/mod_ssl setup.  The web apps define internal accounts matching the users' cert IDs but do not allow any management of the [unused] passwords.  Can elog do this?

  69843   Fri Dec 6 09:39:44 2024 Warning Olivier MARTINamande.olive@yahoo.frQuestionLinux3.1.5Probleme TLS
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?

  69848   Mon Dec 9 10:23:32 2024 Reply Olivier MARTINamande.olive@yahoo.frQuestionLinux3.1.5Re: Probleme TLS

Thanks,

Does email notification from a Gmail address work? It is noted that port 465 must be used for SSL use? Is this correct :


SMTP host : smtp.gmail.com

SMTP port = 465

SMTP username = monadresse@gmail.com

And, should I enter the password attached to my Gmail email and where?

Thanks in advance.

 

Stefan Ritt wrote:

TSL is not implemented in ELOG. Maybe I find time some day to do that, but if we have any volunteers in our community who could help me with that I would appreciate.

Stefan

Olivier MARTIN wrote:
Hello,
I would like to notify by email as soon as an entry is created or modified.
I declared my SMTP which uses TLS security.
The following error message appears : Erreur d'envoi de mail via "smtp.xxxx.xxx.xxx.fr": 5.7.0 Must issue a STARTTLS command first
Is there a solution ?

 

 

  67032   Wed Mar 23 10:01:01 2011 Warning Olivier CallotOlivier.Callot@cern.chBug reportLinux2.9.0Mail are no longer sent from the logged in user in 2.9.0

We upgraded to Elog 2.9.0-2402 and since then mails sent by Elog when posting an item are from the default account, not from the logged in user's mail address.

The configuration is, for the mail part :

Default Email From = Olivier.Callot@cern.ch

Use Email Subject = ELOG Computing Operations - $Subject ($Site - $System - $Production number)

 

Thanks for telling me which flag/option I have to set to restore the proper mail 'From:' field.

  67047   Wed Apr 13 10:51:34 2011 Angy Olivier CallotOlivier.Callot@cern.chBug reportAll2.9.0Self Register = 3 doesn't work any longer

With the recent Elog 2.9.0 rev 2412 the Self Register = 3 option doesn't work as expected: The user is immediately allowed to login. This is not what this option was doing, which is to wait for an approval by the administrator. Can this behaviour be restored, or should I change the value of the Self Register flag? Thanks

  67050   Fri Apr 15 11:49:43 2011 Reply Olivier CallotOlivier.Callot@cern.chBug reportAll2.9.0Re: Self Register = 3 doesn't work any longer

Stefan Ritt wrote:

Olivier Callot wrote:

With the recent Elog 2.9.0 rev 2412 the Self Register = 3 option doesn't work as expected: The user is immediately allowed to login. This is not what this option was doing, which is to wait for an approval by the administrator. Can this behaviour be restored, or should I change the value of the Self Register flag? Thanks

Are you sure about that (maybe used an older revision of elogd where this indeed was a problem?). The current V2.9.0-2412 gives me this:

 Capture004.png

If I then log in as the admin user, I see the configuration of the new user, but the account is not activated:

Capture005.png

So the user cannot log in. The config file is:

 

[global]
port = 8080
password file = passwd
smtp host = mail.psi.ch
Self register = 3
Admin user = stefan

[demo1]
Attributes = Project, Category


Can you double check?
 

 

 HI Stefan,

I tried again and confirm the version number. I never got this pannel saying that my request will be processed by an adminstrator. Maybe the installation was incomplete? Is this pannel outside the standard src files?  I receive the mail as administrator, but the accout is already valid BEFORE I validate it.

This was working in previous versions, i.e. the entry was not created at all. And login wasn't possible.

We went back to 2.8.0 as the server is regularly crashing with 2.9.0 and we have to keep it alive for our running experiment. We are trying to isolate and reproduce the problem...

  67066   Tue May 17 13:19:03 2011 Reply Olivier CallotOlivier.Callot@cern.chBug reportAll2.9.0Re: Self Register = 3 doesn't work any longer

Stefan Ritt wrote:

Olivier Callot wrote:

 

I tried again and confirm the version number. I never got this pannel saying that my request will be processed by an adminstrator. Maybe the installation was incomplete? Is this pannel outside the standard src files?  I receive the mail as administrator, but the accout is already valid BEFORE I validate it.

This was working in previous versions, i.e. the entry was not created at all. And login wasn't possible.

We went back to 2.8.0 as the server is regularly crashing with 2.9.0 and we have to keep it alive for our running experiment. We are trying to isolate and reproduce the problem...

Try to use the simple config file, and see what happens there. Maybe it's a config option you use differently in the experiment. If you identify the config option which triggers the problem, I can probably reproduce it and fix it. Concerning crashes of 2.9.0: We have it running stably for our experiments, that's why I released it. But there are major changes since 2.8.0, mainly the Kerberos authentification (actually people from CERN asked for that). So it could be that in your case there are problems I don't see. In that case you have to test with which options in the config file the problems start. If elogd crashes, a stack dump would maybe also be helpful for me.

 Dear Stefan, after a long time I managed to get a test setup. The line that creates the misbehaviour is

Guest Menu Commands      = List, Find, Login, Help

which seems inocuous! But with this line a user with inactive account can login without validation. Without this line I get also the proper web page indicating that the account has to be activated when I register as new user.

Another little annoyance: When a user is prevented from login ("The account is currently deactivated") there is NO WAY to login, as any action with Elog tries to use the (non activated) username and password. I can't get back the login page!

Thanks

ELOG V3.1.5-3fb85fa6