Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 152 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6451 Entries 
Goto page Previous  1, 2, 3 ... 151, 152, 153 ... 805, 806, 807   Next  
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  1640   Mon Jan 30 10:21:41 2006 Reply Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chBug reportLinux2.6.0Re: ELOG v2.6.0 (Linux) crashes while using " Forgot password?"

Dimitrios Tsirigkas wrote:
A fix is always for all versions, since I have a common code base. Have you tried Version 2.6.1?


Yep, 2.6.1 works fine. Thanks,
Dimitris
  1642   Mon Jan 30 12:27:08 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: Running ELOG under Apache

Dimitrios Tsirigkas wrote:
Sorry if this has been asked elsewhere and I'm missing it. I want to stop users from accessing my elog by loading the URL: http://mycomputerURL:8080 and only make it accessible through http://mycomputerURL/elog. The end goal would be to use Apache to control access. I followed the instructions under "Running elogd under Apache" in the admin guide, but what that did was simply to redirect browsers trying to load ttp://mycomputerURL/elog to http://mycomputerURL:8080.


If you want to have user-level access control, you need to do that with the config option
Password file = ...

Then, if you have the
URL = http://mycomputerURL/elog

statement in your config file, you get redirected from elogd after each login automatically to that URL. If you physically want to block the 8080 port, you have to do that on the operating system level, like with iptables or ipchains.
  1647   Fri Feb 3 13:10:14 2006 Reply Willem KosterW.Koster@rc.rug.nlQuestionOther2.6.1Re: compiling elog 2.6.1 on solaris platform
[quote="Angus Au"]I came across problem in compiling elog 2.6.1 on solaris platform.

Is there any fix ? I can compile elog 2.6.0 successfully on solaris.[/quote]

There is a fix, we have 2.6.1 running on Solaris.

A colleague of me installed it and did mention something about having to go through the source and adapting the 
makefile. I didn't hear him speak of missing libraries though, I will ask him next week.
  1649   Fri Feb 3 18:25:32 2006 Reply Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chQuestionLinux2.6.1Re: elog allows me to create user "blahblah "
By the way, it is also possible to create a user that doesn't have a password! Shouldn't that be forbidden?

Dimitris
  1650   Mon Feb 6 08:27:40 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionOther2.6.1Re: compiling elog 2.6.1 on solaris platform

Angus Au wrote:
ld: fatal: library -lutil: not found


The util library was added recently because of the new shell substitution functionaly, which requires the forkpty() function call. If you know in which library the forkpty is available on solaris, the makefile could be adjusted accordingly. If the forkpty is not available at all, we have to disable the shell substitution under solaris via conditional compilation.
  1651   Mon Feb 6 12:52:09 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportOther2.6.1Re: [261] problem with month selection
> I have several date-fields defined in my logboek. But when I click the icon and select another month the pop-up 
> window get's filled  with the contants of the logboek instead of the date-selection.

Ups, that problem must have been there for quite some time now. I fixed it in the current SVN version.
  1652   Mon Feb 6 12:54:25 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: elog allows me to create user "blahblah "

Dimitrios Tsirigkas wrote:
By the way, it is also possible to create a user that doesn't have a password! Shouldn't that be forbidden?


Well, some people want that!
  1653   Mon Feb 6 12:58:26 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: elog allows me to create user "blahblah "

Dimitrios Tsirigkas wrote:
I noticed that when I register a username that contains whitespaces (eg "boing "), elog allows me to create the user of that name and updates the password file accordingly. It doesn't log me in, but it gives me no error message either. I also found that if I repeat the process it adds yet another entry in the password file, by the same name "boing ". Is that a bug or is there something wrong with my configuration?


Well, I tell you what is wrong: The form says explicitly (name may not contain blanks) and you did not listen Tongue

I can add a simple check if the name contains blanks, but then some people will come up with other strange characters (@#$%), and I'm not sure which of those gives problems. If you test this carefully and tell me which characters to make forbidden, I will happyly add a simple check.
Goto page Previous  1, 2, 3 ... 151, 152, 153 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6