Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 446 of 808  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  66241   Mon Mar 9 17:32:54 2009 Cool Heinzmanncatman333@web.deQuestionWindows2.7.5Re: Login issue

Heinzmann wrote:

Heinzmann wrote:

Hi,

I have found the issue, when I mark at the login page:

Keep me logged in on this computer
for the next 41 days or until I log out

 

I'm not able to login. Only when it is not marked I'm able to login.

How can I diable/hide the part (Keep me logged in on this computer
for the next 41 days or until I log out) from my login page?I

Issue solved: Login expiration = 0

 

 

 

 

 

 

  66240   Mon Mar 9 14:50:03 2009 Reply Heinzmanncatman333@web.deQuestionWindows2.7.5Re: Login issue

Heinzmann wrote:

Hi,

I have found the issue, when I mark at the login page:

Keep me logged in on this computer
for the next 41 days or until I log out

 

I'm not able to login. Only when it is not marked I'm able to login.

How can I diable/hide the part (Keep me logged in on this computer
for the next 41 days or until I log out) from my login page?

 

 

 

 

 

 

  66239   Fri Mar 6 21:51:48 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.5Re: Email authentication with SSL/TLS

 

Val Schmidt wrote:

Hi,

I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.

 

-Val

This is currently not implemented and will probably not implemented in the next time, but it's on my (very long) to-do list.

  66238   Fri Mar 6 13:49:19 2009 Idea Niall DooleyNiall_Dooley@inmarsat.comRequestWindows2.7.5Email recall function similar to what exists say in something like Outlook

Hi,

Is there a way perhaps of implementing an email recall feature into E-Log? In other words, to recall an email before the recipient (s) read the email originating from the e-log. Something perhaps along the lines of what exists in something like Outlook.

Thks in advance.

Regards,

Niall

  66237   Thu Mar 5 23:20:13 2009 Question Heinzmanncatman333@web.deQuestionWindows2.7.5Login issue

Hello,

I have installed the latest elog version from your web site.

My Admin user and my Login user are set in the elog.cfg to use the Self register process within the first login.

The issue is that I get only one time access to my log on the server (XP) and that is direct after the Selfregister process.

If I log out and login to test my admin and user account I will not get access to my server anymore.

My login page stays without any error message.

1 Notebook  XP Client internet explorer http://host ip:8080/demo------> 2nd Notebook XP Server

I have the deleted the cookies after each try.

I have retested later the accounts several times (login/logout) successful with the internet explorer http://host ip:8080/ on the server itself.

 Please could you help me to identify the issue?

 

 

 

 

 

 

  66236   Wed Mar 4 22:47:46 2009 Question Val Schmidtvschmidt@ldeo.columbia.eduQuestionAll2.7.5Email authentication with SSL/TLS

Hi,

I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.

 

-Val

 

ps. sorry for the initial blank post...

  66235   Wed Mar 4 16:41:27 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.5 2142Re: Elogd crashes with: *** stack smashing detected ***
Niklas wrote:

Tried 2178 and I seem to hit some endless loop when I have big cookies. The loop seems to be in this for-loop (from gdb).

I perhaps you should have:

for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )

   if (i < (int) sizeof(cookie)-1)

      cookie[i++] = *p++;

   else
      break;

   cookie[i] = 0;

... Seems to be working for me =)

Yepp, you're right. I applied your change to the distribution code. 

 

  66234   Wed Mar 4 16:32:56 2009 Reply Niklasniklas@hoglund.pp.seBug reportLinux2.7.5 2142Re: Elogd crashes with: *** stack smashing detected ***

Stefan Ritt wrote:

 

Niklas wrote:

Create a list of elog cookies, and store only these as parameters. Examplef:

int process_http_request(const char *request, int i_conn)

{
...
const char *cookie_list[] = { "upwd", "unm", "elmode", "urem", "wpwd", "apwd", "uname", NULL };
...
...
...
         /* store cookie as parameter */
         for(i=0; cookie_list[i]; i++) {
            if(strcmp(cookie_list[i], str) == 0) {
               setparam(str, cookie);
               break;
            }
         }

...

 

I'm not sure if this works, since your test

i < (int) sizeof(cookie)

still will stop parsing cookies if there is one which is too long. So I added your test plus changed the parsing to:

for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )

   if (i < (int) sizeof(cookie)-1)

      cookie[i++] = *p++;

   cookie[i] = 0;

 


The modification is in the curren SVN revision (# 2162). So have a look and check that it works.

Tried 2178 and I seem to hit some endless loop when I have big cookies. The loop seems to be in this for-loop (from gdb).

I perhaps you should have:

for (i = 0; *p && *p != ';' && *p != '\r' && *p != '\n' ; )

   if (i < (int) sizeof(cookie)-1)

      cookie[i++] = *p++;

   else
      break;

   cookie[i] = 0;

... Seems to be working for me =)

 

ELOG V3.1.5-3fb85fa6