shell exec not working, posted by Emiliano Gabrielli on Mon Jun 6 12:25:53 2005
|
It seems that, since Fri 2005-06-03, 12:50 almost, the shell exec feature is not invoked anymore.
the -x flag is present in the command line and the elog.cfg Parameters are present both for edit and for insert..
I'm not disabling shell exec by the checkbox
the dummy-level log in syslog does not show *anything* about shell exec. |
|
Re: shell exec not working, posted by Emiliano Gabrielli on Mon Jun 6 12:43:48 2005
|
| Emiliano Gabrielli wrote: | It seems that, since Fri 2005-06-03, 12:50 almost, the shell exec feature is not invoked anymore.
the -x flag is present in the command line and the elog.cfg Parameters are present both for edit and for insert..
I'm not disabling shell exec by the checkbox
the dummy-level log in syslog does not show *anything* about shell exec. |
oh my @#[#@ .. sorry stefan, my bad ... for some reason the make_thumbs script was not +x ..
Is it possible to check the executability of the script in elog and eventually tell about this in syslog ?  |
password encryption, posted by Alex H on Fri May 20 14:40:12 2005 
|
Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
|
Re: password encryption, posted by Stefan Ritt on Fri May 27 14:48:05 2005
|
| Alex H wrote: | Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
Unfortunately there is no real way around that. If a password is entered into a text box, it is always transferred in plain text (which means that in security-sensive installations one should always use SSL together with elog). I encrypt it on the server side and do an immediate redirect which "hided" the plain password, but if your connection is slow, you might see it for a moment. Unless nobody has a clever idea of how to prevent this, we're out of luck. |
Re: password encryption, posted by Alex H on Mon May 30 10:01:14 2005
|
| Stefan Ritt wrote: |
| Alex H wrote: | Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
Unfortunately there is no real way around that. If a password is entered into a text box, it is always transferred in plain text (which means that in security-sensive installations one should always use SSL together with elog). I encrypt it on the server side and do an immediate redirect which "hided" the plain password, but if your connection is slow, you might see it for a moment. Unless nobody has a clever idea of how to prevent this, we're out of luck. |
Oki Thanks for the answer  .
Alex |
Re: password encryption, posted by Gary Clayson on Mon May 30 19:18:34 2005
|
Hello Alex and Stefan,
I know of only one way to "hide" the text of the status bar in a web browser;
use JavaScript - specifically the status method (as in the following example):
<!-- the following goes in the body of the document, perhaps in a link. -->
<!-- sample link -->
<a href="javascript://place link url here"
onMouseOver="window.status='Status Bar Text Goes Here'; return true">Link Text Here</a>
<!-- place the following script in the head of the document -->
<script language="JavaScript" type="text/javascript"><!--
window.defaultStatus="Default Status Bar Text Here";
--></script>
Of course the above only works in those browsers that support javascripting,
but it is one way to hide the actual text of links from the user.
Hopefully this helps you!
Gary Clayson
| Alex H wrote: | Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
|
|
Re: password encryption, posted by Emiliano Gabrielli on Mon May 30 19:56:01 2005
|
| Gary Clayson wrote: | Hello Alex and Stefan,
I know of only one way to "hide" the text of the status bar in a web browser;
use JavaScript - specifically the status method (as in the following example):
<!-- the following goes in the body of the document, perhaps in a link. -->
<!-- sample link -->
<a href="javascript://place link url here"
onMouseOver="window.status='Status Bar Text Goes Here'; return true">Link Text Here</a>
<!-- place the following script in the head of the document -->
<script language="JavaScript" type="text/javascript"><!--
window.defaultStatus="Default Status Bar Text Here";
--></script>
Of course the above only works in those browsers that support javascripting,
but it is one way to hide the actual text of links from the user.
Hopefully this helps you!
Gary Clayson
| Alex H wrote: | Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
|
I don't have double checked .. but .. why we need to pass the sensible information in the Query String ??
Are you sure that putting it in an hidden field (and eventualli using a GET methon in the <form>-tag) can't be a solution? |
|
Re: password encryption, posted by Stefan Ritt on Mon May 30 20:16:11 2005
|
| Emiliano Gabrielli wrote: |
I don't have double checked .. but .. why we need to pass the sensible information in the Query String ??
Are you sure that putting it in an hidden field (and eventualli using a GET methon in the <form>-tag) can't be a solution? |
Hidden means only these fields are not shown in the form, but they are added to the URL in the same way as non-hidden fields. But I got another idea: I will try to use a POST form instead of the GET form. Using the POST method, fields are attached to the request and not present in the URL. Hope this will work. When I find some time to work on it I will let you know. |
Re: password encryption, posted by Alex H on Tue May 31 09:07:37 2005
|
| Thanks Stefan 8) |
|
Re: password encryption, posted by Stefan Ritt on Sat Jun 4 14:00:17 2005
|
| Alex H wrote: | I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
I switched the login page to the HTTP "POST" method, where arguments are not passed in the URL.
The new version is under CVS. Can you try if the behaviour is better now? I upgraded also the ELOG forum, so you can try there as well. |
|
Logbook locking issue, posted by Steve Jones on Tue May 17 21:38:36 2005
|
Stefan, any ideas on this problem?
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
|
Re: Logbook locking issue, posted by Steve Jones on Wed Jun 1 16:14:22 2005
|
| Steve Jones wrote: | Stefan, any ideas on this problem?
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
Hmmm, I don't seem to be seeing any responses - is email being generated? |
|
Re: Logbook locking issue, posted by Stefan Ritt on Wed Jun 1 16:33:54 2005
|
Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.
| Steve Jones wrote: | Stefan, any ideas on this problem?
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
|
Re: Logbook locking issue, posted by Steve Jones on Wed Jun 1 21:00:01 2005
|
| Steve Jones wrote: | Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself?
| Stefan Ritt wrote: | Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.
| Steve Jones wrote: | Stefan, any ideas on this problem?
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
|
|
|
Re: Logbook locking issue, posted by Stefan Ritt on Sat Jun 4 13:06:08 2005
|
| Steve Jones wrote: | | Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself? |
I would recommend to remove the Restrict edit time = 0.5 temporarily from your config file, then edit this entry, the clicking Back instead of Submit (since you don't really want to edit the entry). This removes the lock, and you can re-enable the Restrict edit time = 0.5 in the config file.
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
I fixed this problem and committed it to CVS. It will be contained in the next release. |
Incorrect Display, posted by David Spindler on Sat May 21 15:05:23 2005
|
I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me upload the screen captures. On the main screen, for example, my field contents for "Route" appear in the "Text" field. But when on the specific entry screen, these field contents are in the correct field. I will be glad to eamil the screen captures, if anyone wants.
I am running Firefox 1.0.3 (same results with IE 6, BTW), on a WinXP OS (sorry fellows, but I am still in process of learning Linux, so I have not tried this version of elog on it, yet), on a Gateway 2.2 GHZ, 1 GB RAM PC.
BTW, I love elog and have it running at work. It is being used extensively. |
|
Re: Incorrect Display, posted by David Spindler on Sat May 21 15:23:08 2005
|
| David Spindler wrote: | I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me upload the screen captures. On the main screen, for example, my field contents for "Route" appear in the "Text" field. But when on the specific entry screen, these field contents are in the correct field. I will be glad to eamil the screen captures, if anyone wants.
I am running Firefox 1.0.3 (same results with IE 6, BTW), on a WinXP OS (sorry fellows, but I am still in process of learning Linux, so I have not tried this version of elog on it, yet), on a Gateway 2.2 GHZ, 1 GB RAM PC.
BTW, I love elog and have it running at work. It is being used extensively. |
I guess it did upload. Here is the other screen capture.
BTW, I received the following message upon submitting my last post:
| Quote: | | "Error sending Email via "mailsend.psi.ch": malformed address: <>" |
|
|
Re: Incorrect Display, posted by David Spindler on Mon May 23 17:47:24 2005
|
Never mind. I figured it out. I used two fields (date and time) that are automatically placed in elog. It messed up the spacing, altough what was puzzling was that it displayed correctly on the entry itself, but not the list. Anyway, I renamed the date and time to another name and it is ok.
Thanks, anyway. Keep up the good work.
| David Spindler wrote: |
| David Spindler wrote: | I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me upload the screen captures. On the main screen, for example, my field contents for "Route" appear in the "Text" field. But when on the specific entry screen, these field contents are in the correct field. I will be glad to eamil the screen captures, if anyone wants.
I am running Firefox 1.0.3 (same results with IE 6, BTW), on a WinXP OS (sorry fellows, but I am still in process of learning Linux, so I have not tried this version of elog on it, yet), on a Gateway 2.2 GHZ, 1 GB RAM PC.
BTW, I love elog and have it running at work. It is being used extensively. |
I guess it did upload. Here is the other screen capture.
BTW, I received the following message upon submitting my last post:
| Quote: | | "Error sending Email via "mailsend.psi.ch": malformed address: <>" |
|
|
|
Re: Incorrect Display, posted by Geoffrey Carman on Fri Jun 3 17:34:44 2005
|
| David Spindler wrote: |
BTW, I love elog and have it running at work. It is being used extensively. |
We just did the 2.60 beta upgrade, and now our pre-existing logbooks, with a
List Display = Name, Author, Date for example will only show the first two fields.
It seems like Elog is dropping the last attribute in the List Display line.
We can 'fix' it by making it say:
List Display = Name, Author, Date, Date
so that it drops the second Date, but that is a bad workaround.
Anyone else seeing this?
Elog 2.60 beta on Linux, Firefox 1.04 as the client. Or IE fully patched on WinXP SP2.
PS: Love Elog at work here too! Truly has made our documentation way better. And RSS feeds of the logbooks is just wonderful. |
|
Re: Incorrect Display, posted by Emiliano Gabrielli on Fri Jun 3 18:02:25 2005
|
| Geoffrey Carman wrote: |
| David Spindler wrote: |
BTW, I love elog and have it running at work. It is being used extensively. |
We just did the 2.60 beta upgrade, and now our pre-existing logbooks, with a
List Display = Name, Author, Date for example will only show the first two fields.
It seems like Elog is dropping the last attribute in the List Display line.
We can 'fix' it by making it say:
List Display = Name, Author, Date, Date
so that it drops the second Date, but that is a bad workaround.
Anyone else seeing this?
Elog 2.60 beta on Linux, Firefox 1.04 as the client. Or IE fully patched on WinXP SP2.
PS: Love Elog at work here too! Truly has made our documentation way better. And RSS feeds of the logbooks is just wonderful. |
I just reported it to Stefan last week ... it's the "pippo-bug" I called it this way becouse you can put anything you want as garbage Attribute to go around the bug .. I temporary corrected my elogs configs addig a ", pippo" to every "List Display" line ... |
|
Re: Incorrect Display, posted by Stefan Ritt on Sat Jun 4 10:59:52 2005
|
I finally found some time to fix the pippo-bug  .
It had to do with the request that one can turn on and off the summary lines of the text body in Guest list display. So if this option does not contain Text, the text summary is not shown for guest access, but only for registered access. This modification had the side effect that one column was dropped on the non-guest access. |
|
Problem with auto-increment attribute, posted by Andy on Tue May 24 20:32:08 2005
|
I have a very strange problem with auto-increment attribute. Here is a part of my configuration:
Attributes = Access ID, Harvest Date, Access, Species, PI, Submission date, Stain, Comments
Preset Access ID = MI-05-%03d
Type Harvest date = date
Type Submission date = date
I tried to add new entry, and it's Access ID is MI-05-001. But when I'm adding another entries,
there Access ID is MI-05-006
I found only one mention of using increment in documentation.
What I'm doing wrong? |
|
error message from this forum, posted by Heiko Scheit on Wed May 18 14:20:23 2005
|
Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
|
Re: error message from this forum, posted by Stefan Ritt on Wed May 18 19:52:41 2005
|
| Heiko Scheit wrote: | Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
Sombody used an invalid formed email address, like user<at>domain<dot>com, on which the SMTP server complained. I would like to note here that the email addresses registered in this forum are not published in any way, so there is no risk to get spam from that (except the normal elog notifications, which can be turned off easily). |
post box question, posted by damon nettles on Sat May 7 17:51:22 2005
|
is there any way to get a larger text box to type in when making a new post?
the default box is rather small and you have to scroll up and down when
making a new post or editing an existing one.
once the post is submitted, the display goes to a larger box, but the text
only takes up the left side of the page. seems the only way to get it to go
all the way to the right is to make everything html and submit it that way.
can the normal text look like the html does without submitting it as html? |
|
Re: post box question, posted by Stefan Ritt on Mon May 9 11:30:07 2005
|
> is there any way to get a larger text box to type in when making a new post?
> the default box is rather small and you have to scroll up and down when
> making a new post or editing an existing one.
Message width = <number of characters>
Message height = <number of lines>
> can the normal text look like the html does without submitting it as html?
No. |
|
Re: post box question, posted by damon nettles on Thu May 12 18:32:18 2005
|
> > is there any way to get a larger text box to type in when making a new post?
> > the default box is rather small and you have to scroll up and down when
> > making a new post or editing an existing one.
>
> Message width = <number of characters>
> Message height = <number of lines>
>
> > can the normal text look like the html does without submitting it as html?
>
> No.
thanks stefan. it looks like it was right in front of my face the whole time (on
the elogd.cfg syntax page). but, somehow i missed it. |
|
elogd crashes on log out, posted by Kevin Robinder on Wed Apr 27 21:27:25 2005
|
Since updating to version 2.5.8 we have been having problems with the elogd
service crashing whenever anyone attempts to log out. We are using stunnel
4.09 on a Win 2k system.
When someone tries to log out of e-log from their desktop the machine
hosting the service throws an error popup wanting to report to Microsoft.
The error signature has the following information:
szAppName: elogd.exe
szAppVer: 0.0.0.0
szModName: elogd.exe
szMidVer: 0.0.0.0
offset: 0003586a
Clicking to get the technical information it wants to send it shows these
two file names:
C:\DocumentsandSettings\krobinde\LOCALS~1\temp\WER6F.tmp.dir00
\elogd.exe.mdmp
C:\DocumentsandSettings\krobinde\LOCALS~1\temp\WER6F.tmp.dir00\appcompat.txt
Let me know if there is any further information you need. |
|
Re: elogd crashes on log out, posted by Stefan Ritt on Fri Apr 29 21:30:26 2005
|
It's hard to tell the problem from what you report. Have you tried the latest
release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
some problems with the password file in 2.5.8 versions prior to patch level 6. |
|
Re: elogd crashes on log out, posted by Kevin Robinder on Sat Apr 30 19:10:22 2005
|
> It's hard to tell the problem from what you report. Have you tried the latest
> release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
> some problems with the password file in 2.5.8 versions prior to patch level 6.
Yes, I am up to date with the latest version (2.5.8-6).
What other information can I provide that might assist in diagnosing this? |
|
Re: elogd crashes on log out, posted by Stefan Ritt on Mon May 2 09:33:51 2005
|
> What other information can I provide that might assist in diagnosing this?
Please send me your elogd.cfg configuration file. |
|
Re: elogd crashes on log out, posted by Matt B on Fri May 6 18:41:04 2005
|
> > What other information can I provide that might assist in diagnosing this?
>
> Please send me your elogd.cfg configuration file.
Stefan - I am having the exact same problem as outlined here. I sent you an
email with a somewhat complicated config file. Attached to this message is a
much simpler one.
With this file, if you remove the B5 server (remove it from top group a2, and
remove the [b5] entry) the crash does not happen. If the B5 server (or any
additional server) is in the file, then the problem occurs.
For me, there are 3 places where the crash happens:
- on logout
- when an invalid username/password is used to login
- when you login to A1, then try to go to A2
This is happening on elog v2.5.9-1 (built May 2, 2005, 12:17:18 revision 1.642)
I have tried on windows 2000 and 2003 servers, and it seems to happen on both of
them.
Matt |
|
Re: elogd crashes on log out, posted by Matt B on Fri May 6 20:32:49 2005
|
Another quick update on this, it looks like the bug was introduced in version
2.5.8-2 built Mar 30 2005, 11:04:33, revision 1.611
version 2.5.8-1 built Mar 21 2005, 17:28:54, revision 1.592 does not exhibit the
behavior.
Matt |
|
Re: elogd crashes on log out, posted by Stefan Ritt on Mon May 9 13:12:26 2005
|
> Since updating to version 2.5.8 we have been having problems with the elogd
> service crashing whenever anyone attempts to log out. We are using stunnel
> 4.09 on a Win 2k system.
This problem has finally been identified and fixed. Please download the newest
version 2.5.9-2 which contains this fix. |
|
Re: elogd crashes on log out, posted by Kevin Robinder on Wed May 11 21:39:12 2005
|
> > Since updating to version 2.5.8 we have been having problems with the elogd
> > service crashing whenever anyone attempts to log out. We are using stunnel
> > 4.09 on a Win 2k system.
>
> This problem has finally been identified and fixed. Please download the newest
> version 2.5.9-2 which contains this fix.
I will get right on this. Thank you for your efforts! |
|
|
ELOG V3.1.5-3fb85fa6 |