ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66239
|
Fri Mar 6 21:51:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.5 | Re: 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 |
| Niall Dooley | Niall_Dooley@inmarsat.com | Request | Windows | 2.7.5 | Email 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 |
| Heinzmann | catman333@web.de | Question | Windows | 2.7.5 | Login 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 |
| Val Schmidt | vschmidt@ldeo.columbia.edu | Question | All | 2.7.5 | Email 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 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 2142 | Re: 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 |
| Niklas | niklas@hoglund.pp.se | Bug report | Linux | 2.7.5 2142 | Re: 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 =)
|
66233
|
Tue Mar 3 12:38:07 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.5-2130 | Re: Idea/Suggestion |
> Hi Stefan,
>
> Must have missed it when the fixed/not fixed thread marking got implimented.
>
> Anyhow, my main point would still apply for where the thread is not yet fixed, but is in one of a number of possible
> states (waiting, panic, work-in-progress....). Clearly you can label the latest entry in a thread with the latest
> status, and icon, but when in collapsed mode, you only see the initial entry. If the latest entry were shown
> (optionally), then one can tell at a glance in the collapsed listings which entry may need direct attention.
If you always mark the whole thread with states (waiting, panic, work-in-progress,...) as described in my last posting,
then you will see this from the thread initial entry as well. If you use icons, then even more. The only disadvantage
is that you have to discipline yourself always modifying the whole thread and not only one entry in that thread. |
66232
|
Tue Mar 3 11:30:01 2009 |
| Adam Blandford | ahb@etw.de | Question | Windows | 2.7.5 | Hiding Comments on the Logbook Selection Page |
Hi
I was just wondering if there was a way that the comments for a logbook could be set to be invisible on the Selection page but then displayed once a user has logged in to a particular logbook?
This is required for security purposes. I want a common login page which shows all logbooks, where the logbook names only have meaning for people who know them but then once logged in the comment provides additional information about that logbook.
Thanks
Adam |