[osiris-devel] removing features

[Alexei_Roudnev]

Q. is not _to stay or to remove_. Unfortunately,  osiris interface today is
a mixture of primitive 'command line' technology (which is difficult to use
even for configuration) and primitive WEB interface which can only show list
of changes. A huge number of possible options stays behind, because osiris
as a system is excellent, with excellent design , good scanning agent, great
simplicity. But I can not:
- see report of the system status - servers, date of change, number of
changes, sheduled scans, last scan time, etc...
- browse old database, for example, see list of files (sizes, dates, owners)
before change (for forencic purpose, for example);
- deliver every day ops (approvals, adding new servers, changing e-mail and
schedule) to tier-1 person (again, because of primitive interface).

On the other hand, I do agree - merging http server and osirismd server is
dangerous, and does not aloow to expand it easily (I mean - expand web
interface).

So, if you want to remove http daemon from osirismd (which is not crazy
idea - it have it's own reasons), we need some way to write simple web
add-ons first, then rewrite existing functionality on somethimg like cgi or
php or python, then remove http functionality.

Other way is to adapt http interface for everything, so simplifying
administrative interface. But it can require more complicated http parser,
this is correct.

Alexei Roudnev

----- Original Message ----- 
From: "Brian Wotring" <brian at shmoo.com>
To: "Osiris Developers" <osiris-devel at lists.shmoo.com>
Sent: Thursday, November 11, 2004 7:28 PM
Subject: Re: [osiris-devel] removing features


>
> I received a lot more response from others offline, all objecting to the
> removal of this feature;  I guess it stays.
>
> I'm glad I asked.  Thanks for the feedback :)
>
> Alexei_Roudnev wrote:
> > Problem 1 - there is not way to create CGI for osiris console.
> > Problem 2 - such CGI will be highly system dependent and will reproduce
> > existing (in osirismd) functionality - what for?
> >
> > For reports, I agree with such approach - osiris can generate static web
> > files, available by standard web server.
> >
> > PS. Notice, that 90% of modern tools use web access, and most of them
just
> > implements primitive web server inside.
> >
> > ----- Original Message ----- 
> > From: "Spike Ilacqua" <spike at indra.com>
> > To: "Osiris Developers" <osiris-devel at lists.shmoo.com>
> > Cc: <brian at shmoo.com>
> > Sent: Thursday, November 11, 2004 4:07 PM
> > Subject: Re: [osiris-devel] removing features
> >
> >
> >
> >>Personally I use the CLI interface, but I think Alexei does have a valid
> >>point, your average user is going to prefer a pretty Web interface.
> >>
> >>That said, I don't think the management console should be a Web server.
> >>    Let Web servers be Web servers, and Osiris be Osiris.  Create a CGI
> >>that can be installed on an existing Web server.  That way you don't
> >>have to be writting HTTP code and if the user can't get to the Web
> >>server, than it's a problem with the Web server, not Osiris.
> >>
> >>->Spike
> >>_______________________________________________
> >>osiris-devel mailing list
> >>osiris-devel at lists.shmoo.com
> >>https://lists.shmoo.com/mailman/listinfo/osiris-devel
> >>
> >
> >
> > _______________________________________________
> > osiris-devel mailing list
> > osiris-devel at lists.shmoo.com
> > https://lists.shmoo.com/mailman/listinfo/osiris-devel
> >
>
> _______________________________________________
> osiris-devel mailing list
> osiris-devel at lists.shmoo.com
> https://lists.shmoo.com/mailman/listinfo/osiris-devel
>