Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 116 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 115, 116, 117 ... 804, 805, 806   Next  
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  1194   Wed Jun 15 18:59:23 2005 Reply Charles DuncanCharles@YorkU.CAQuestionLinux Re: Moving eLog from Server to Server...

Charles Duncan wrote:

Charles Duncan wrote:

Quote:

Stefan Ritt wrote:

Charles Duncan wrote:
I am moving my eLog system from one server to another.
I moved all my log books, my /etc/elog.conf, and /usr/share/elog/elog.pwd file. Did I miss anything?
The Logbooks come up fine on the eLog list, but when I try to access them I get invalid user name...
Do I have to do some sort of conversion to move the pwd file from one server to another?
Or should I try using the sync command for the move? does sync also move the pwd file??


Of course you have to start elogd after you copied all files over, but I presume you did that. The
password file itself does not need any conversion, it should work on both hosts fine. Cloning an elog logbook
(via the "-C <url>") flag, does copy the password file if you enter "yes" to the according question. Have you
checked the file permission of the password file? Maybe the user name elogd is running under has no read access
to it.


I reinstalled elog on the new server and ran the clone (via the "-C <url>"), wow that is really slick. But unfortunately my passwords and user data were not transfered. I did say 'Y' when prompted to transfer the password info.

I think my problem is that one server is running 2.5.9 (or 2.6.0 beta, unstable, Debian) and my new server is running 2.5.5.3 (stable, UBUNTU).

Are the password files not compatible between the 2 versions?

All my logbook entries appear to be there in full.

btw: I am back leveling to 2.5.5.3 because I lose my last column on every log book view.


I wanted to add that the elog.pwd file did transfer when I used the "elogd -C <url>" command, but the passwords and accounts were not recognized. Also I edited my elog.conf file to contain the absolute address of my elog.pwd file.


I fixed it... I merely backed out of the XML format of the elog.pwd and reverted to common passwd format. Everyone can log in now... great product.
  1195   Thu Jun 16 22:37:06 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.9Re: reverse sort option does not work for quick filter
I finally found some time to fix this problem. The fix is under CVS.
  1197   Fri Jun 17 22:08:28 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Cloning

Gerfried Kumbartzki wrote:
The elogd.cfg has a read and write passwd set. Any user can access the logbook, read and write after providing the proper user id and password.


This might be your problem. Try to temporarily remove the read and write password from you config file, then do the cloning, then put it back. Cloning works with a passowd file, but I haven't tested it with read/write passwords.


Gerfried Kumbartzki wrote:
Beside missing the real stuff everything ends up in the users home directory. I would like it in the general area (/usr/local/elog for instance).


The cloning works in the current directory. So just go to /usr/local/elog and start "elogd -C ..." from there. Alternatively, copy your whole /usr/local/elog tree to the server manually. The "Synchronize" button then works again only with a password file. You need a "Mirror user = xxx" option in that case.
  1198   Fri Jun 17 22:33:29 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.9Re: elog crashes when admin tries to register new users

Heiko Scheit wrote:
The following appended after the base (!) URL results in a segmentation fault
?cmd=Activate&new_user_name=test1&new_full_name=Test1

It works fine, if a specific logbook is given. So
http://my.ho.st/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is not OK, while
http://my.ho.st/myLogBook/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is OK.


Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes Crying

I tried to fix this and committed the changes to CVS. Can you try with that version?
  1202   Sun Jun 19 20:50:16 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows V2.5.4Re: 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 Reply Emiliano GabrielliAlberT@SuperAlberT.itQuestionWindows V2.5.4Re: 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).. Smile
  1206   Tue Jun 21 19:24:58 2005 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.9Re: elog crashes when admin tries to register new users

Quote:

Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes Crying

I tried to fix this and committed the changes to CVS. Can you try with that version?


Not really, unless you have a fixed 2.5.9 version. Version 2.6 has
way too many new features, which I don't want at the moment. Or is
there a config option to get the old behavior?

I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.

Maybe you should consider supporting two branches, say 'stable' (2.5.9
currently) and 'experimental' (2.6 currently)? For 'stable' only
severe bugs and security issues are fixed and in 'experimental' new
features are introduced. What do you say?

For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook.
  1207   Tue Jun 21 19:38:06 2005 Reply Heiko Scheith.scheit@mpi-hd.mpg.deBug reportLinux2.5.9email flagged as spam

Heiko Scheit wrote:

I also saw that the format of the email notification has changed. As
I have scripts (bash, akw, procmail) that depend on this format I
would need much more time than I currently have to actually test
everything.


By the way, the emails I get from the forum are now all flagged as
spam. SpamAssassin is used and Spam-score header is

X-Spam-Score: 4.875 (****) ADDRESS_IN_SUBJECT, BAYES_00,HTML_40_50,
HTML_IMAGE_ONLY_24, HTML_MESSAGE, MIME_HEADER_CTYPE_ONLY,
MIME_HTML_ONLY, MSGID_FROM_MTA_HEADER, MSGID_FROM_MTA_ID,
NO_REAL_NAME, SPF_FAIL, SPF_HELO_PASS, TO_MALFORMED

Maybe you can see what the problem is.
Goto page Previous  1, 2, 3 ... 115, 116, 117 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6