ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 211 of 801

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6404 Entries

Goto page Previous 1, 2, 3 ... 210, 211, 212 ... 799, 800, 801 Next

Mon Jan 23 10:57:45 2006

Re: redirect errors via apache2

> Since elog 2.6.0 we cannot redirect our elog via apache2.
> 
> in apache2.conf we have (had for a long time):
> Redirect permanent /elog http://elog.oursite.com/elog/
> ProxyPass /elog/ http://elog.oursite.com:8080/
> 
> When visiting the url, this results in:
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET /elog/myelog/.
> 
> After testing we found that ELOG V2.6.0-beta2 works just fine.
> 2.6.0 stable crashes after visiting a redirected url.
> 
> Running on debian sarge

Have you tried 2.6.1. I released it just recently, so I don't know when it will be available for Debian. Have you
checked that your "URL = xxx" statement in the config file is correct? I see above "myelog", while the proxy
passes requests to "elog".

1622

Tue Jan 24 08:11:13 2006

Re: Quicklink does not work for one field

mark james wrote:

Stefan Ritt wrote:

mark james wrote:

I am not so bold as to log this as a bug but one of my Quicklink fields just do not work.

Sorry my late reply, but now I have fixed this problem. The update is under SVN and will be contained in the next release.

Thanks for that. I am now using ver V2.6.1-1622. So I guess that doesn't qualify as a "next release". I wonder if there is anything I could do to work around the issue?

Mark

In fact now the dropdown seems to be working but when I 'tick' an entry, it is not being written to the ascii file.

Can you try V2.6.1-1634? I fixed several issues with ticking entries coming from "MOptions" lists.

1625

Tue Jan 24 22:52:48 2006

Re: Suggestion additional ElCodes

T. Ribbrock wrote:

However, there are two things I'm missing:

Headings
It would be great to have a range of [H1][/H1], [H2][/H2], ... tags that map directly to their HTML counterparts (and have buttons, of course... ). That makes structuring an entry much easier in my opinion (and the output is easier to deal with for tools like html2ps) and I'm really missing those.
Tables
This one is probably more difficult to add, but support for simple tables would be enough. But this is more a "nice to have"...

Yes, I missed tables myself already. The headings I just put into the current SVN version (see this forum for how it works). Tables are a bit harder to implement and will come later. Do you have a proposal for a possible syntax? A 1:1 relation to HTML would look like this:

[tr][th]heading1[/th][th]heading2[/th][/tr] [tr][td]data1[/td][td]data2[/td][/tr]

But that does not look very sexy to me. Maybe somehting like

	heading 1	heading 2	heading 3
	data 1	data 2	data 3

this looks a bit like the "pipe" mode from a Wiki

what do you think?

1627

Wed Jan 25 08:24:28 2006

Re: Access to global configuration in v2.6.1

> Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both
with the
> existing cfg file and with the new cfg.
> Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
> buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.

I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
attached (elog:1627/2). So it's a mystery why it is different in your case...

Attachment 1: elogd.cfg

[global]
port = 8080

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

Attachment 2: Capture.gif

1629

Wed Jan 25 12:10:46 2006

Re: Access to global configuration in v2.6.1

> or maybe browser cookies. 

That rings a bell. If you change user permissions (like password file/no password file/rename logbooks) you might be
fooled by old cookies. Just delete all cookies in your browser and try again.

1632

Thu Jan 26 15:07:11 2006

Re: ELOG v2.6.0 (Linux) crashes while using " Forgot password?"

Dimitrios Tsirigkas wrote:

Is there going to be a fix for that version as well?

A fix is always for all versions, since I have a common code base. Have you tried Version 2.6.1?

1635

Fri Jan 27 13:52:34 2006

Re: Quicklink does not work for one field

mark james wrote:

OK. But where do I get this from? The "latest version of 19 Jan is still 1622.

If you can compile it yourself, you get it from Subversion (see here). Otherwise you have to wait for the next release.

1637

Fri Jan 27 23:18:07 2006

Re: Running elog as ordinnary user

G. Vandemoortele wrote:

I've configured elog with some commands running a shell :

Preset R-Date = $shell(/usr/bin/date +"%Y/%m/%d %H:%S")
; for testing :
Preset $text = $shell(whoami && set)
Preset $text = Some fixed text

That worked well when elog was started by root (and falling to user elog),
but later, I moved all the elog tree to /home/my_name/.elog,
(I'd like to start it only when I'm logged, it's only for personnal data)
changed all the attributes/permissions ($chown -R my_name:my_group .elog)
and none of these commands still works ! I use the -x option to allow
shell substitution.

More surprisingly, even the fixed text doesn't work (???)

First of all, you could use

Preset R-Date = $date

instead of the shell command. Secondly, the command

Preset $text = $shell(whoami && set)

is wrong. Replace it by

Preset text = $shell(whoami && set)

without the "$".

G. Vandemoortele wrote:

By the way, I also seen that it is necessary to set Usr and Grp to "elog"
via the config file even when it's started by root, because otherwise,
you always get the strings 'Falling back to default group "elog"' and
Falling back to default user "elog" in the output of the shell substitutions.

There is a good reason for that. If you run elogd as root, this can open a dangerous hole into your system. If there would be any bug in elog, an attacker could gain root access easily. By falling back to a non-root user, the damage can be minimized. As a precaustion, elog falls back to Usr and Grp "elog" if that setting is missing in the config file.

When you run elog under your user name, this fallback is not necessary. Why you got the message 'Falling back' is a mystery to me. I tried to reproduce that, so I run under a non-root account with following config:

[global]
port = 1234

[demo]
Attributes = Subject
Preset Subject = $shell(date +"%Y/%m/%d %H:%S")

and correctly got the date in the "Subject" field with ELOG V2.6.1-1640.

Goto page Previous 1, 2, 3 ... 210, 211, 212 ... 799, 800, 801 Next

ELOG V3.1.5-3fb85fa6