Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 794 of 804  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  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

  67258   Tue May 1 17:03:37 2012 Agree Per Erikssonpelle@sm4xiu.euInfoLinuxAnyRe: Compiling Elog for QNAP NAS x86

Per Eriksson wrote:

Hi All,

I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?

Regards,

Per

I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)

Per

  67302   Fri Jul 13 15:12:07 2012 Agree Michael Dannmeyermichael.dannmeyer@solvias.comQuestionWindows2.9.0-2396Re: Problems with Autorization

Stefan Ritt wrote:

Michael Dannmeyer wrote:

Andreas Luedeke wrote:

Michael Dannmeyer wrote:

Hello,

we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg

[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1

So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.

The file is not saved. If I remove the 3 lines the logbook opens without any problems.

I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.

Would you please help solving the File password problem?

[...]

Just two hints:

  • The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
  • The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?

Thank you for the answer, but it didn't solve the problem.

  • I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.
  • The Account which is used to start the Elogd process is local system. System has full right at the logbook directory

 Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.

 

I once had problems with the local system account, so I used my own account to start the service and that worked. For trial, you can also start the elogd.exe program manually (not as a service) in a DOS box and see if it can create the password file. 

 That worked for me. Used an Account instead of local system and everything is OK. Thanks for your help.

  67316   Tue Aug 21 17:16:19 2012 Agree Szu-Ching Pecknerspeckner@nd.eduBug reportLinux2.9.2Re: kerberos authentication

Szu-Ching Peckner wrote:

Szu-Ching Peckner wrote:

Hello, I have

authentication = kerberos

kerberos Realm = xxx

I ran tcpdump and know elogd server did attempt to contact kerberos server. I could run kinit username@realm_name, and klist shows my ticket fine. 

I receive "kerberos error 256: Decrypt integrity check failed. Please check your kerberos configuration" when I entered my password wrong purposely on login page.

I receive "Invalid user name or password!' when I entered my correct password. 

Please advise. 

 

 

I forgot to mention, I also have Password file line in elogd.cfg file. Because without password file line, I wouldn't get login screen. I know my test account is not in the main.pwd file. I believe elogd does go to kerberos server to compare password. I just don't get why I get invalid username and password when I entered correct password, while kerberos error (expected) when I enter wrong password.  

Authentication = Kerberos

Kerberos Realm = xxx

Password file = main.pwd

 It's resolved.  I read the documentation again, and found out my mistake. I didnt have username defined on password file. 

  67324   Wed Aug 29 14:35:45 2012 Agree Szu-Ching Pecknerspeckner@nd.eduQuestionLinuxlatestRe: secure way to allow users create logbook

Stefan Ritt wrote:

Szu-Ching Peckner wrote:

I don't think there is a good secure way so far, but would like to have your opinion. 

If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write to cfg file, but obviously it impose security problem. Is there a good and secure way to allow user to create logbook themselves?

Actually there is no good secure way. What I usually do is to give users admin rights on individual logbooks, then they can change the config of that logbook. Many times adding some attribute is as good as creating new logbooks. Like if you need two logbooks "home" and "work", you can create an attribute "type" and let the type be "home" or "work". With conditional attributes you can make the logbook behave differently for the two values of "type" and get most functionality of two separate logbooks.

- Stefan 

 Thanks, that is good option. 

  67325   Wed Aug 29 17:55:37 2012 Agree Zbigniew Reszelareszelaz@gmail.comQuestionLinuxV2.8.1-235Re: dynamic preset text

Stefan Ritt wrote:

Zbigniew Reszela wrote:

Dear all,

Is it possible to have a dynamic "preset text" option?

I would like to switch the template file depending on the attribute value. (Of course this attribute values will be a fixed list of options, not extandable). 

I see there one difficulty, that: if user already started editing the text body, he could lose this data. But I think that this could be left on user responsibility to take care about it.

Another option could be to always insert the template text on the very beginning of the text body.

Is this feature implemented, or maybe someone have done it by changing the server code?

Cheers

This is possible with conditional attributes. An additional trick would be to not show the text body of an attribute is not selected. This way the user first has to select the attribute, then the text field with the specific preset will show up. The configuration would be something along these lines:

 

Attributes = Type, Subject
Options Type = One{1}, Two{2}, Three{3}
Show text = 0

{1} Preset text = text1
{2} Preset text = text2
{3} Preset text = text3
{1,2,3} Show text = 1

 

Of course you have to supply proper text files text1, text2, text3.

- Stefan

 

 Thanks, it works perfectly!

  67374   Wed Nov 7 12:56:12 2012 Agree Vinícius Ferrãoviniciusferrao@if.ufrj.brRequestLinux2.9.2Support for modern Linux

Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

 

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

 

The second problem is in this line:

 

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

 

The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.

 

After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...

 

And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?

 

Many thanks in advance,

Vinícius Ferrão 

 

PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.

 

 

 

  67404   Mon Dec 17 21:49:54 2012 Agree Hal Proctorhproctor2@gmail.comQuestionWindows2.92Re: Reply HTML

Hal Proctor wrote:

Hal Proctor wrote:

Stefan Ritt wrote:

Hal Proctor wrote:

Any reason why when I click "Reply" to a previous submission that the body is full of HTML code?

See below:

<p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Hal Proctor wrote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;"><p>
<table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;">
<tbody>
<tr>
<td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Quote:</td></tr>
<tr>
<td cellpadding="10px" style="background-color:#FFFFB0;">removed the thing and the other thing....added this and that!</td>
</tr>
</tbody>
</table>
</p><p> </p>
testing reply</td>
</tr>
</tbody>
 

Here is my logbook config:

[Logbook]
Theme = default
Comment = Maintenance Logbook
Attributes = Author, Type, Category, Subject, Shift
Options Type = Repair, Routine, Preventative, Other
Options Category = Emergency, General, Change-Over, Other
Options Shift = 1, 2, 3
Extendable Options = Category
Required Attributes = Author, Type
Page Title = Maint Log - $subject
Reverse sort = 1
Preset Author = $long_name
Preset on reply Author = $long_name
Locked Attributes = Author
Quick filter = Date, Type, Category

I don't see any mistake in the configuration file. Did you switch the "Encoding" from HTML to plain? (Radio buttons at the bottom just below the text window). Is there a problem with your FCKEditor? Do you see the formatting menu bar? 

 I do not get the formatting menu with HTML.  I switched to plain and code still exists.  The only formatting menu I get is when I choose ELCode.   I have no problem with this forum seeing the formatting menu with HTML (although it does take some time to load). 

 Tested it in Chrome and acts the same as IE8 (just much slower)

 It's version issue!!   2.92 does not utilize FCKeditor correctly.  Backed off one version and it works fine!  2.91 is GOOD!

ELOG V3.1.5-3fb85fa6