Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 378 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  67116   Tue Sep 6 12:15:54 2011 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsV2.9.0-241Re: Password may not contain blanks

Stefan Ritt wrote:

Terry Shuck wrote:

After setting up email addresses for notifications I noticed that the "Full Name" has part of an email address in it. I've tried several ways to correct this however it keeps sending me to a page that says "Password may not contain blanks" and I've not done anything with the password.

Can you tell me how to correct this issue?

I certainly appreciate your help!!

Terry

 Have you tried deleting and re-creating the account? Otherwise you could stop elogd, edit the password file with a text editor, and restart elogd.

You will not loose your logbook data if you have access rights to the file system where the "elogd" program writes it's data.

The easiest way is to edit there password file directly and then restart "elogd".

But even if you do not dare to edit the files directly, you still can solve the issue from the web interface:

  • Create a new account, e.g. user "admin2"
  • While logged in as "admin", make this user an administrator: go to "Change config file", add "Admin user = admin, admin2"
  • Now log off and then login as "admin2"
  • Check that you can do administration, then remove user "admin"
  • Create a new user "admin" with proper "Full name" and "Email"
  • Now log off and then login as "admin"
  • Check that you can do administration, then remove user "admin2"

That should work. Good luck!

  67118   Wed Sep 7 12:17:44 2011 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.9.0-241Re: Password may not contain blanks

Terry Shuck wrote:

Anyway if I have to wipe out ELOG and start over to have admin capabilities again, do all of my logbooks have to be rewritten? Can I import existing logbooks into a new ELOG?

If you start over, you can just copy the xxyyzza.log files into the new logbook directory and it should be fine. You can also change the config file in your current logbook without starting over. 

  67119   Wed Sep 7 12:37:38 2011 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.9.0-241Re: Password may not contain blanks

Terry Shuck wrote:

Can you tell me how to stop elogd? I've edited that file several times however when I open ELOG in my browser the elogd is back like it was before the edits.

Best is if you edit elgod.cfg or the user configuration from inside the web browser (Click on 'config' on the elog page), then you don't have to restart elogd. If you do have to restart it, go to My Computer/Manage/Services, select elogd, then stop and start the service.

- Stefan

  67120   Wed Sep 7 16:23:01 2011 Agree Terry Shuckterry.shuck@atmosenergy.comQuestionWindowsV2.9.0-241Re: Password may not contain blanks

Andreas Luedeke wrote:

Stefan Ritt wrote:

Terry Shuck wrote:

After setting up email addresses for notifications I noticed that the "Full Name" has part of an email address in it. I've tried several ways to correct this however it keeps sending me to a page that says "Password may not contain blanks" and I've not done anything with the password.

Can you tell me how to correct this issue?

I certainly appreciate your help!!

Terry

 Have you tried deleting and re-creating the account? Otherwise you could stop elogd, edit the password file with a text editor, and restart elogd.

You will not loose your logbook data if you have access rights to the file system where the "elogd" program writes it's data.

The easiest way is to edit there password file directly and then restart "elogd".

But even if you do not dare to edit the files directly, you still can solve the issue from the web interface:

  • Create a new account, e.g. user "admin2"
  • While logged in as "admin", make this user an administrator: go to "Change config file", add "Admin user = admin, admin2"
  • Now log off and then login as "admin2"
  • Check that you can do administration, then remove user "admin"
  • Create a new user "admin" with proper "Full name" and "Email"
  • Now log off and then login as "admin"
  • Check that you can do administration, then remove user "admin2"

That should work. Good luck!

 Fantastic! That worked great. Thanks so much for the help guys!!

Terry

  68648   Fri Jul 21 08:54:03 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsv2 9.2-2475Re: Password Protect Delete

You can allow guests to create entries, but only registered users (Admins) to delete (or edit) entries:

Menu commands = List, New, Edit, Reply, Delete, Find, Config, Logout, Help
Guest menu commands = List, New, Reply, Find, Login, Help

See https://midas.psi.ch/elog/config.html#general for details.

Michael Cianci wrote:

We don't use a password file but would like to password protect (Admin only) the DELETE function in the MENU     Thank You

 

  267   Fri Apr 4 08:58:16 2003 Reply Stefan Rittstefan.ritt@psi.chBug report  Re: Password Problem
> I noticed that when I put in a password such as <test1> a person can login 
> with the password <test2> or any other number at the end.  Is the 
> encryption not able to tell the difference between numbers?  The encrypted 
> passwords even look the same in the password file.  Is this a bug?

This is really strange. Encryption only works on ASCII characters and does 
not distinguish between letters and digits. When I try to reporoduce that, 
the system distinguishes well between "test1" and "test2". The first gives 
encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the different "E" 
and "I". So I have no clue right now what is wrong in your installation. If 
running under Linux, you can compile elogd after adding "-DHAVE_CRYPT" and "-
lcrypt" to the Makefile to use the standard Linux crypt() function, but I 
would rather like to understand what is wrong in your case.

- Stefan
  270   Fri Apr 4 19:49:32 2003 Reply Byroncryogaze@easystreet.comBug report  Re: Password Problem
> > I noticed that when I put in a password such as <test1> a person can 
login 
> > with the password <test2> or any other number at the end.  Is the 
> > encryption not able to tell the difference between numbers?  The 
encrypted 
> > passwords even look the same in the password file.  Is this a bug?
> 
> This is really strange. Encryption only works on ASCII characters and does 
> not distinguish between letters and digits. When I try to reporoduce that, 
> the system distinguishes well between "test1" and "test2". The first gives 
> encrypted "dGVzdDE=" and the second gives "dGVzdDI=", note the 
different "E" 
> and "I". So I have no clue right now what is wrong in your installation. If 
> running under Linux, you can compile elogd after adding "-DHAVE_CRYPT" 
and "-
> lcrypt" to the Makefile to use the standard Linux crypt() function, but I 
> would rather like to understand what is wrong in your case.
> 
> - Stefan

Ok, try it with the passwords <hello1> and <hello2>.  Then when you go to log 
in, put in the password of <hello> with any single number after it and let me 
know if the problem shows up for you because that is the password I was 
using.  When I look at it encrypted in the passwd file they look the same.  I 
also installed the latest version today which is newer than the one I was 
using before and it still does it.  I appreciate your time.

Byron
  272   Mon Apr 7 22:50:17 2003 Reply Stefan Rittstefan.ritt@psi.chBug report  Re: Password Problem
> Ok, try it with the passwords <hello1> and <hello2>.  Then when you go to 
log 
> in, put in the password of <hello> with any single number after it and let 
me 
> know if the problem shows up for you because that is the password I was 
> using.  When I look at it encrypted in the passwd file they look the 
same.  I 
> also installed the latest version today which is newer than the one I was 
> using before and it still does it.  I appreciate your time.

Ok, I finally found the problem: Whenever a password has a length which can 
be divided by three (like 6 or 9), the last two characters are completely 
ignored. This problem will be fixed in version 2.3.5. Is has to be noted 
that all existing passwords with the mentioned length have to be re-entered 
after the upgrade from 2.3.4 to 2.3.5. Since one cannot log in with the old 
password on those cases, a "Forgot password?" links has been added to the 
login screen, which can be used to create a new password and send it to the 
registered email address.
ELOG V3.1.5-3fb85fa6