Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 228 of 796  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6363 Entries 
Goto page Previous  1, 2, 3 ... 227, 228, 229 ... 794, 795, 796   Next  
ID Date Icon Author Author Email Category OSup ELOG Version Subject
  1648   Fri Feb 3 18:15:47 2006 Question Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chQuestionLinux2.6.1elog allows me to create user "blahblah "
Hi,

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?

Cheers,
Dimitris
  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
  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.
  1654   Mon Feb 6 16:27:45 2006 Reply Dimitrios Tsirigkasdimitrios.tsirigkas@cern.chRequestLinux2.6.1Re: elog allows me to create user "blahblah "

Stefan Ritt wrote:

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!


Ok, fair enough. But maybe there could be an optional flag in the configuration that disables blank passwords... I wouldn't want some imposter to start entering stuff under the username of another user, so it would be nice if I could have some way of forcing them to have a password, even if it's a one-letter password.

Thanks,

Dimitris
  1657   Mon Feb 6 16:53:41 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: elog allows me to create user "blahblah "

Dimitrios Tsirigkas wrote:
I wouldn't want some imposter to start entering stuff under the username of another user, so it would be nice if I could have some way of forcing them to have a password, even if it's a one-letter password.


Ok, I added an empty password check. If too many people will complain, I will make it a flag.
  1659   Tue Feb 7 12:58:10 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.1-1637Re: Numbered lists get closed by </ul>

T. Ribbrock wrote:
I just ran into the following problem (and was able to reproduce it in the "demo" logbook on this site):

  • Create a new entry
  • Create a numbered list:
    [LIST=1]
[*] 1st entry
[*] 2nd entry
[/LIST]
  • In the resulting HTML code, the closing statement of that list translates to </ul> instead of </ol>, causing the list to remain open and all following text to be intented by the list indentation. This gets worse when several such lists are used in one document. I'll include an example below.

Numbered list follows:

  1. one
  2. two
  3. three

This text is indented, as the list was not closed properly.

  1. four
  2. five
  3. six

And now we have double indention...


I can't see any double indention there...

But seriously Wink I fixed that problem and updated this elog server already. It's in SVN revison 1653. The code now correctly chooses the proper </ul> or </ol>. What will not work however are nested lists, like an ordered list inside an unordere list, but that's anyhow very uncommon.
  1660   Tue Feb 7 21:02:22 2006 Question Chris Warnerchristopher_warner@dcd.uscourts.govQuestionLinux email problems
When I select to get email notification on new logbook entries I receive this error when entering a new record.

Error sending Email via "xxx.xxx.xxx.xx": Syntax error, parameters in command "MAIL FROM: christopher_warner@xxx.gov SIZE=1985" unrecognized or missing

The user that sent the message was a test account that I set up. I entered the email address in the box provided and I am not sure what may be causing the difficulty.

Any thoughts as to what may be causing this?
Goto page Previous  1, 2, 3 ... 227, 228, 229 ... 794, 795, 796   Next  
ELOG V3.1.5-2eba886