ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 117 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 116, 117, 118 ... 804, 805, 806 Next

Wed Jun 22 18:34:18 2005

Gerfried Kumbartzki

kum@physics.rutgers.edu

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

1212

Fri Jun 24 21:02:05 2005

Re: elog crashes when admin tries to register new users

Heiko Scheit wrote:

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?

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?

I think elog is such a small project that supporting several branches makes no sense. You can do this if you have several developers, one taking care of each branch. But as you know I'm alone. But what I can do is the following:

Have a default switch for the Encoding. So if "default encoding = plain", the "plain" radio button is on by default, so people tend to write plain text rather than ELCoded text.
Have either a switch for the email notification, to revert back to the old text format, or have a multipart email message. I saw that outlook sometime does that. One email can contain a "plain" part and an "HTML" part. So you can select in your email reader which one to display. At least thunderbird supports that. But I don't know what your bash scripts say to that, please let me know.

Heiko Scheit wrote:

For me the risk of upgrading to 2.6 now seems to high, as many people
depend on the logbook.

Well, that's why it's called "beta". I first want to make sure that the transition to the new version goes smooth, and nobody's installation gets problems. So the old logbooks should be still readable without any modification, and once I implemented the "dual plain/html" email notification, you should be fine to upgrade. Is that correct?

- Stefan

1213

Fri Jun 24 21:15:14 2005

email flagged as spam

Heiko Scheit wrote:

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.

Apparently the problem is in the HMTL contents of the email message. I use SpamAssassin 3.0.2 and do not get more than three points, that's why I haven't seen that problem before. It looks to me like reverting back to plain text will remove most of the hits, although not all. What happens if you write an HTML email to yourself, is this then flagged as spam, too? The TO_MALFORMED I have no chance, since I send each notification just once, it contains now ~300 email destination addresses. Since I don't want that everyone sees these addresses, I put a dummy "To:" there ("Omit Email to = 1"), but this is then of course a fake "To:" and triggers the spam filter.

1214

Fri Jun 24 21:24:55 2005

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

1215

Fri Jun 24 22:23:50 2005

Re: [BUG] quick filter

Emiliano Gabrielli wrote:

it seems that the select box of quick filters are showing also the "{n}" appended to the Attributes in order to obtain conditional Attributes ...

see the snapshot attached

Fixed in current CVS.

BTW, I would display the date selection calender in a new floating window, not to take away all the precious screen space at the top. Then I would use the same calendar as for the date attributes, not to confuse users with two different styles.

1218

Mon Jun 27 15:16:37 2005

Emiliano Gabrielli

AlberT@SuperAlberT.it

Linux

2.6.0beta2

Re: [BUG] quick filter

Stefan Ritt wrote:

Emiliano Gabrielli wrote:

it seems that the select box of quick filters are showing also the "{n}" appended to the Attributes in order to obtain conditional Attributes ...

see the snapshot attached

Are you sure you really committed it ? Smile

Reguarding the calendar... the picture is just one of my tests .. I started using a popup window, but it makes complicated to do all the job I want.. so my current idea is to implemnet it a a dropdown layer, it will save both the precious space and the functionality..
I don't use the existing style becouse of, in the first popup try, it was to simple .. now I can't use it directly becouse I don't need any popup anymore.. but ok, we can keep the same style of course Smile

1219

Mon Jun 27 15:19:05 2005

Emiliano Gabrielli

AlberT@SuperAlberT.it

Linux

2.6.0beta2

Re: [BUG] quick filter

Emiliano Gabrielli wrote:

Stefan Ritt wrote:

Emiliano Gabrielli wrote:

it seems that the select box of quick filters are showing also the "{n}" appended to the Attributes in order to obtain conditional Attributes ...

see the snapshot attached

uhm... now the drop down menu is composed of only blancs ..

Reguarding the calendar... the picture is just one of my tests .. I started using a popup window, but it makes complicated to do all the job I want.. so my current idea is to implemnet it a a dropdown layer, it will save both the precious space and the functionality..
I don't use the existing style becouse of, in the first popup try, it was to simple .. now I can't use it directly becouse I don't need any popup anymore.. but ok, we can keep the same style of course Smile

1224

Mon Jul 4 22:44:03 2005

Re: [BUG] show only new entries

Emiliano Gabrielli wrote:

Just tested the rev 1.686 .. now the link is displayed, but following the "Show only last" link the "attach=1" setting in the URL I use is removed, not being able to have inline attachment in full view. They are displayed again when turning back to "Show all entries"

I tried to fix this in the current CVS. Can you give it a try?

Goto page Previous 1, 2, 3 ... 116, 117, 118 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6