| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1201
|
Sat Jun 18 23:14:51 2005 |
 | Paul Paquette | paquettep@gmail.com | Question | Windows | V2.5.4 | prevent CVS and XML exports |
Hello All and Happy Father's Day,
How do I prevent Anonymous Users from exporting the Data when using the search funtion?
Thank You
Paul |
|
1202
|
Sun Jun 19 20:50:16 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V2.5.4 | Re: prevent CVS and XML exports |
| Paul Paquette wrote: | Hello All and Happy Father's Day,
How do I prevent Anonymous Users from exporting the Data when using the search funtion?
Thank You
Paul |
By not allowing anonymous access at all. The CVS and XML exports do not contain more information than anonymous users can see on the web page, so there is no reason to prevent it. Anybody could view all pages anonymously (if guest access is allowed) and reconstruct the CVS data easily. |
|
1204
|
Mon Jun 20 09:56:28 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Question | Windows | V2.5.4 | Re: prevent CVS and XML exports |
| Stefan Ritt wrote: |
| Paul Paquette wrote: | Hello All and Happy Father's Day,
How do I prevent Anonymous Users from exporting the Data when using the search funtion?
Thank You
Paul |
By not allowing anonymous access at all. The CVS and XML exports do not contain more information than anonymous users can see on the web page, so there is no reason to prevent it. Anybody could view all pages anonymously (if guest access is allowed) and reconstruct the CVS data easily. |
You are obviously talking about CSV (Comma Separated Values), and not CVS (Cuncurrent Verioning System)..  |
|
1209
|
Wed Jun 22 18:34:18 2005 |
| Gerfried Kumbartzki | kum@physics.rutgers.edu | Question | Linux | 2.6.0 | Re: Cloning |
Thank you for the suggestions; I commented the read and write passwd in elogd.cfg out and only then I was able to clone
(elogd -v -C http://laptop:8080) the logbook to the new server.
But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running.
I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out.
Sync works fine from the RedHat linux laptop (rpm installed), but crashes the elogd on the alpha Linux machine (compiled from src) most of the time. elogd hast to be restarted and the sync had not finished.
So for now I settled to do the synchronize only from the laptop but have to remove the read passwd each time. That is tolerable but not
convenient.
Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window
pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog.
I think I have to learn more about the whole user and passwd protection schema.
Thanks again
Gerfried |
|
1214
|
Fri Jun 24 21:24:55 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.0 | Re: Cloning |
| Gerfried Kumbartzki wrote: | But this is only part of the story. The logbook on the labtop is owned by the
default user elog and default group elog, that is needed to start up the elogd. Only a user "elog" can do the cloning, unless temporarily the owner ship in /usr/local/elog is changed. I made it work by temporarily changing the owner ship on both machines, did the cloning, changed back to owner elog, started elogd and all was running. |
The /usr/local/elog files should be owned by user elog on both machines, and both elogd daemons should be started under user elog. Since only the two elogd daemons communicate with each other during synchronization, that should be fine. Only after the initial cloning (which you presumably do under your own user account), you have to do a "chmod" to change ownership of all files to uid/gid "elog/elog".
| Gerfried Kumbartzki wrote: | | I setup synchronizing and here too it works only if the read passwd in elogd.cfg is commented out. |
As I said, the read password is not really supported for synchronization. It is there historically, from the times when there was no user level password access. If you use synchronization, you should use that authentication (by putting a "password file = ..." into your config.
| Gerfried Kumbartzki wrote: | | Here I have another question: My Elog is passwd protected, encrypted passwd in elogd.cfg (read and write). When connecting to the elog the window pops up asking for a user name and the passwd. I donot remember exactly, what was done to set name and passwd. But I find it "strange" that the user name can be anything as long as the passwd is right to access the ELog. I think I have to learn more about the whole user and passwd protection schema. |
If you switch to user level password access, this problem goes away as well.
- Stefan |
|
1221
|
Sun Jul 3 03:48:12 2005 |
| John Habermann | john.habermann@wilderness.org.au | Question | Linux | 2.5.9+r167 | changing the default to plain text rather than elcode |
Hi
I just shifted our elogs to a new server and in the process upgraded to the latest debian version which is 2.5.9+r1674-1. I am just wondering how to change the default for the text body area from "elcode" to plain text? I can't see anything in the admin configuration syntax guide and the HTML default = 2 option no longer seems to work.
Also is there anything in particular that you have to do to get the elcode editor to work. Although the elcode buttons appear highlighting text and clicking on them doesn't actually do anything although it works fine in my browser when using these elog forums. I don't get any errors in mozilla but trying it in IE under cxoffice gives an "error on page" message in the bottom of the browser.
Thanks
John |
|
1228
|
Tue Jul 5 23:06:12 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.9+r167 | Re: changing the default to plain text rather than elcode |
| John Habermann wrote: | | I just shifted our elogs to a new server and in the process upgraded to the latest debian version which is 2.5.9+r1674-1. I am just wondering how to change the default for the text body area from "elcode" to plain text? I can't see anything in the admin configuration syntax guide and the HTML default = 2 option no longer seems to work. |
The HTML default option has been replaced by the Default encoding option, with which one can set the default encoding style to plain text (Default encoding = 1).
| John Habermann wrote: | | Also is there anything in particular that you have to do to get the elcode editor to work. Although the elcode buttons appear highlighting text and clicking on them doesn't actually do anything although it works fine in my browser when using these elog forums. I don't get any errors in mozilla but trying it in IE under cxoffice gives an "error on page" message in the bottom of the browser. |
The ELCode editor requires the JavaScript file elcode.js to be present in the scripts directory under your elog root directory. Future installations will handle this correctly. |
|
1230
|
Thu Jul 7 02:41:40 2005 |
| Tim Fowler | timfowler1@gmail.com | Question | Linux | 2.5.9+r167 | Re: changing the default to plain text rather than elcode |
| Stefan Ritt wrote: |
| John Habermann wrote: | | I just shifted our elogs to a new server and in the process upgraded to the latest debian version which is 2.5.9+r1674-1. I am just wondering how to change the default for the text body area from "elcode" to plain text? I can't see anything in the admin configuration syntax guide and the HTML default = 2 option no longer seems to work. |
The HTML default option has been replaced by the Default encoding option, with which one can set the default encoding style to plain text (Default encoding = 1).
| John Habermann wrote: | | Also is there anything in particular that you have to do to get the elcode editor to work. Although the elcode buttons appear highlighting text and clicking on them doesn't actually do anything although it works fine in my browser when using these elog forums. I don't get any errors in mozilla but trying it in IE under cxoffice gives an "error on page" message in the bottom of the browser. |
The ELCode editor requires the JavaScript file elcode.js to be present in the scripts directory under your elog root directory. Future installations will handle this correctly. |
The installation did not include scripts directory. Where can I download the elcode.js file? |