ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
681
|
Wed Sep 1 22:25:01 2004 |
| Steve Jones | steve.jones@freescale.com | Question | Linux | 2.5.3 | Re: Options Items limits |
> Hello friends,
>
> Exist some form to increase limits of items (100) in the Options List
>
>
>
> Thanks for any help
I believe only through an edit of the C code and a recompile, as the values
are set as constants. I think this might be the line:
#define MAX_N_LIST 100
So, yes, there exists a way and the ease of this way is dependent upon your
comfort level with changing stefan's code. |
696
|
Wed Sep 8 17:39:43 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.4-2 | Re: URL bug in elogd.cfg |
> This problem has been fixed in revision 1.462
Thank you! |
708
|
Fri Sep 24 19:17:52 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.4 | Enhanced "eLog Version" Variable |
Stefan, would it be ok to add the "minor" revision level to the VERSION
constant? I've been doing this after I download source just so I can keep
things straight, you keep cranking out versions ;->
EX:
#define VERSION "2.5.4-4"
BECOMES
#define VERSION "2.5.4-4-1.483" or something like that?
Just a thought.
Thanks |
713
|
Wed Oct 6 06:14:36 2004 |
| Steve Jones | steve.jones@freescale.com | Comment | All | 2.5.4 | Re: Enhanced "eLog Version" Variable |
No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!
> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
>
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
>
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant? I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> >
> > EX:
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> >
> > Just a thought.
> >
> > Thanks |
833
|
Mon Dec 6 22:48:19 2004 |
| Steve Jones | steve.jones@freescale.com | Info | All | 2.5.5-2 | Re: external authentication possible? |
> > In order to avoid having to remember multiple usernames/passwords for
> > different systems, is it possible for ELOG to use external authentication
> > via Active Directory, etc?
>
> Not yet.
I would note that this is a request that comes in fairly frequently, but to
Stephan's credit (and looking back at previous comments) the task of trying to
implement authentication that would *not* be a maintenance nightmare basically
pushes such a request down to the bottom of the list.
The only common denominator that could possibly cover all contingencies would
be LDAP authentication. One way of doing this in a more-or-less universal
fashion is to offload the auth task from eLog itself and place the burden on
Apache. This means figuring out how to get Apache to pass auth info to eLog
when eLog operates behind Apache. In the end, anything that can use LDAP as an
authentication mechanism (like AD) can host eLog - as long as eLog can glom off
of Apache's ability to do the actual authenticating.
For our twiki (source from twiki.org) website, we use the following config:
-- In Apache http.conf
LoadModule auth_ldap_module libexec/auth_ldap.so
AddModule auth_ldap.c
AccessFileName .htaccess
# Twiki
Include /proj/www/twiki/conf/httpd.conf
-- The http.conf in the Twiki directory
<VirtualHost *>
DocumentRoot "/proj/www/twiki/html"
ServerName twiki
ErrorLog error_log
CustomLog access_log combined
<Directory "/proj/www/twiki/html/bin/">
Options +ExecCGI
allow from all
AllowOverride Authconfig FileInfo Indexes Limit Options
</Directory>
<Location /bin>
Options +ExecCGI
AuthType Basic
AuthName CoreID
CustomLog access_log combined
<Directory "/proj/www/twiki/html/bin/">
Options +ExecCGI
allow from all
AllowOverride Authconfig FileInfo Indexes Limit Options
</Directory>
<Location /bin>
Options +ExecCGI
AuthType Basic
AuthName ID
AuthLDAPURL
ldap://ldap.co.com:389/ou=People,ou=Intranet,dc=co,dc=com?uid?sub?(objectClass=*)
require valid-user
allow from all
<Limit OPTIONS>
Order Deny,Allow
Deny from all
</LIMIT>
</Location>
</VirtualHost>
--- Then the DocumentRoot ("/proj/www/twiki/html") has a '.htaccess' file with
the following:
RedirectPermenant / http://twiki.co.com/bin/view.cgi
--- Also in the /bin directory we have:
Redirect http://twiki.sps.mot.com/index.html http://twiki.sps.mot.com/bin/view.cgi
AuthType Basic
AuthName "LDAP Login"
AuthLDAPURL
ldap://ldap.co.com:389/ou=People,ou=Intranet,dc=co,dc=com?uid?sub?(objectClass=*)
SetHandler cgi-script
ErrorDocument 401 /bin/oops.cgi/TWiki/TWikiRegistration?template=oopsauth
<Files ~ "[^/]*\.html$">
SetHandler blabla
allow from all
</Files>
<Files "*">
require valid-user
allow from all
</Files>
-------------------------
Whether this is at all relevant, well . . . . |
849
|
Wed Dec 15 15:42:13 2004 |
| Steve Jones | steve.jones@freescale.com | Comment | All | 2.5.5-2 | Re: external authentication possible? |
> > The only common denominator that could possibly cover all contingencies would
> > be LDAP authentication. One way of doing this in a more-or-less universal
> > fashion is to offload the auth task from eLog itself and place the burden on
> > Apache. This means figuring out how to get Apache to pass auth info to eLog
> > when eLog operates behind Apache. In the end, anything that can use LDAP as an
> > authentication mechanism (like AD) can host eLog - as long as eLog can glom off
> > of Apache's ability to do the actual authenticating.
>
> That sounds to me like a great idea. If anybody gets this working, people would be
> grateful if this could be submitted to the "Contributions" section of this forum.
Ah, you test me! Perhaps I will attempt to dig into this but I may have to leave the
integration up to you, Stefan. Seems that there would be two roads to go:
1> Move away from standalone and start to rely on Apache
2> Continue with the standalone theme and build in LDAP authentication (which could
also give you groups functions as well).
I think I would opt for <2> |
851
|
Thu Dec 16 05:23:54 2004 |
| Steve Jones | steve.jones@freescale.com | Comment | All | 2.5.5-2 | Re: external authentication possible? |
> > Ah, you test me! Perhaps I will attempt to dig into this but I may have to leave the
> > integration up to you, Stefan. Seems that there would be two roads to go:
> > 1> Move away from standalone and start to rely on Apache
> > 2> Continue with the standalone theme and build in LDAP authentication (which could
> > also give you groups functions as well).
> >
> > I think I would opt for <2>
>
> <1> would only make sense if the functionality could be completely implemented inside
> Apache, without (much) modification of elog. Otherwise I agree that <2> would be more
> following the general lines of elog. I was considering to implement PAM (pluggable
> authorization module) support into elog, which is quite easy to implement and gives you
> to power of having LDAP, Kerberos, Unix username, Windows NT Domain and much more. But
> that would them be restricted to elog running under Linux (and Solaris I guess), since
> I'm not aware of a PAM implementation under Windows.
>
> Implementing LDAP directly into elog gives me the problem that we don't use LDAP
> authentication at our institute (it's Kerberos in fact). So I would have to set up my own
> LDAP server for testing, plus we at our institute don't have a direct benefit from that,
> which would make it hard for me to justify to spend time on.
Yes, PAM is highly dependent upon Unix and PAM would work under Solaris just fine. Your
problem lies with Windows - hence my LDAP suggestion.
And LDAP isn't an easy thing to setup, but I bet there is a quick and dirty "test" bench that
could be rigged using OpenLDAP. Like I indicated, I'll see what I can dig up on this front -
but I make no promises wrt delivery time! |
1137
|
Mon May 9 20:23:59 2005 |
| Steve Jones | steve.jones@freescale.com | Question | Linux | Other | 2.5.9 | Version of GCC to use? |
What is the recommended version of gcc to use with elog 2.5.9? I searched
the discussion database but found nothing pertaining to this.
Thanks |