On Thursday 30 January 2003 02:58 pm, you wrote:
> Eric & Lynn,
> Are we ready to create a src/config tree in CVS?

We can setup the initial folder, but nothing is ready to commit
at this stage. I think we need to get a solid foundation set, then
myself or Eric can import it to CVS when ready.
More comments below.


> > I am trying to get something like this going for a longer period of time
> > and due to changing concepts, lack of knowledge and the problem of
> > intermittent working on a concept ( and thus changing it ) it isn't a
> > completely  uniform thing.

I understand, I just started back up (remembering exactly where I was
at with it) when I ran out of time last summer. Eric, you beat me to the
start-up post.  ;-)


> > The package is still called weblet.lrp and includes the standard
> > weblet pages.  in the cgi-bin are all the scripts used by the
> > programm. I used uncgi to get the variables back.
> > This is the only programm that might have to be recompiled for
> > uClibc forexample.

Yes, that had been an idea before. With my personal testing, I didn't
have to use 'uncgi' to pass the variables to the CGI, I was successful
with both GET and POST. My problem had been with the permissions
sh-httpd ran under. You can run sh-httpd as root (as you have done) or
use a suid binary to do any system overwriting. The 'su-wrapper' binary
does this and is quite configurable, IIRC, I posted this binary in my
cvs/devel/guitarlynn folder. There were some major buffer-overflow
problems found with this release of 'su-wrapper', but v1.2 is supposed to
be fixed (if you can find it) and I have found a patch as well for it.
Ideally, I would prefer to use/write a suid-c binary instead of running
sh-httpd as root.


> > Attention this programm is for further development. ( I thought it was
> > the right time to share efforts :) )
> > It is NOT A PRODUCTION version.
> > Dangers:
> > - Still running as root  ( change the user for sh-httpd ro root )
> > - Still using get
> > - leaving temporary scripts in /tmp  ( easy to fix)

Absolutely, I'll check it out and see if we can come up with a clear
roadmap. From your earlier diagrams, I believe we are thinking in
the same direction, I'll submit some more refined ideas in a follow-up
post.


> > Problems
> > - Build in the same kind as the original scripts so to change for
> > example the hostname you have to change multiple files. ( an idea to
> > change this exist but the time fails )
> > - Some pages have a relative bad layout.

Hehe, I'm not much of a designer myself, I share your pain. ;-)
I believe Richard A. and Erich had some design/layout things
that were reworked, hopefully we can get something passed 
around and work on the same path in the front-end as well.


> > specialities
> > -Use of a kind of session management. Actually useing the
> > connecting computer IP and a random string.( necessary to prevent
> > page reloading)
> > - highly modular. this proved to be a great advantage. Changes to all
> > sites are much easier to realise.
> > - The option to use the webpage or directly edit the config file.
> > - The use of predefined pages to edit to prevent directory walking.

More ideas in a follow-up

> > ----------------------------------------
> > Questions
> >
> > Anyone willing to contribute. ?

Absolutely!

> > What about a webconfiguration like this. ?

My idea is to create a new back-end and front-end.
I don't believe this will work very well with the bulk
of packages w/o modifications to the packaging and
core system due to lack of predicability in real-life use.


> > Secondary I learned a  lot about shell programming, allthough my
> > style must be a horror for some of you professionals ;)

Well, if it works, the code can always be cleaned up (I hope ;-)
-- 
~Lynn Avants
Linux Embedded Firewall Project developer
http://leaf.sourceforge.net


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

_______________________________________________
leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to