head	1.9;
access;
symbols;
locks; strict;
comment	@# @;


1.9
date	99.08.25.01.38.09;	author rkrusty;	state Exp;
branches;
next	1.8;

1.8
date	99.08.25.01.12.41;	author rkrusty;	state Exp;
branches;
next	1.7;

1.7
date	99.08.24.12.11.19;	author rkrusty;	state Exp;
branches;
next	1.6;

1.6
date	99.08.23.22.45.05;	author rkrusty;	state Exp;
branches;
next	1.5;

1.5
date	99.06.16.03.46.24;	author rkrusty;	state Exp;
branches;
next	1.4;

1.4
date	99.06.16.02.02.33;	author rkrusty;	state Exp;
branches;
next	1.3;

1.3
date	99.04.24.18.49.15;	author rkrusty;	state Exp;
branches;
next	1.2;

1.2
date	99.04.19.22.56.36;	author rkrusty;	state Exp;
branches;
next	1.1;

1.1
date	99.04.19.15.36.35;	author rkrusty;	state Exp;
branches;
next	;


desc
@@


1.9
log
@[IEM] Migrating some of the core docs out of the root tree into the docs
subdir.  Basically leaving the README which will point to the docs dir
and the COPYING file. (Updating debian stuff to match)
@
text
@Skattek: Version 0.0.1 (Pre Alpha basically)

REQUIREMENTS
=-=-=-=-=-=-

   * php3 (3.0.12 or newer)
   * phplib 7 
   * Apache w/ SSL (dont' be stupid and not use SSL)
   * SSH (currently not implemented, but eventually)
   * PostgreSQL  (other's soon)
   * Linux (preferablly 2.2.x, but 2.0.x will be supported as well)
   * The Horde module (horde-core for Debian folks) (1.3.0+)


SECURITY ISSUES
=-=-=-=-=-=-=-=

Here is a list of know security issues with this program.  I'm just
starting this so it's going to be small at first.

 *  All users with access to modifying the user database can see each
      other's passwords.  (by viewing page source)


INSTALLATION
=-=-=-=-=-=-

Please see the INSTALL document in to docs directory


STATUS
=-=-=-

8/25/99:

    Basic authentication pieces are done.  There are 3 (currently) levels
of privalages.  User, Admin, Manager.  User is currently ment for log
monitoring and possibly read only status in the rule base.  Admin will
be for maitaining everything except maybe a couple pieces which will
be left for Managers.  I'm still not 100% on all this yet, but I figure
I can always not use one of them.

    Currently this is all being coded for the 1.3.0 development version
of Horde.  There is alot of work to be done.  Migration from the old style
of database management to the new phplib style is going to take alot of 
work.  With authentication out of the way I will be next focusing on
the classes and whatnot for each of the different pieces.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Copyright (c) 1999, Ivan E. Moore II <rkrusty@@tdyc.com>
@


1.8
log
@[IEM] Finishing up authentication pieces.  Currently configured so that
authentication is required.  If you come from the horde link and are
authenticated with the proper access it will dump you into the main page
and not prompt for login (as it should).  Otherwise it kinda looks like
the horde page does currently. Then click on the login button and the
login window will come up.

Also updating the README file with a status update and a brief discription
of current plans for the perms being used for skattek.
@
text
@d25 6
@


1.7
log
@[IEM] Ok.  This is a slur of work I did today while I was supposed to be doing
work for people who pay me. :)

    Currently non working since I forgot the last of the updates at work.

    1>  Updating documentation (install/readme/changelog)
    2>  flattening out lib into src tree.  Removing skattek.lib
    3>  Updating build.pl file so that it will build skattek.lib
    4>  Removing db.lib and it's functions
    5>  Adding in (partial...rest is still at work) phplib based
        authentication.  Actually have it working...woohoo
    6>  html related changes to get it to work with the 1.3.x dev tree
    7>  moving scripts/examples into config/ tree to mirror rest of
        horde modules

Once I get the rest of the auth updates from work into the tree it will
be functional within the 1.3.0 horde dev tree.  (functional as in you
can log in. :)  )   Next step is to build all the database classes and
whatnot for use with phplib...ack...
@
text
@d28 1
a28 1
6/15/99:
d30 12
a41 5
   Currently Skattek is in it's pre-alpha stages.  There is usable code,
   but you can't manage an actualy firewall with it.  User management
   is pretty complete (tho I know there will be more tweaking down the line),
   Object management is functional, and the preliminaries of the firewall
   management pieces are there.
a42 5
   A lot of work still needs to be done for rule base configuration.  Once
   this is done, ie...being able to build a rule set, save it, and recall it,
   the steps needed to build a output file and get it to the destination 
   firewall will be implemented.  At that point we'll deal with the security
   issues with all of that.
@


1.6
log
@[IEM] let's try this again
@
text
@d12 1
a12 1
   * The Horde module (horde-core for Debian folks)
@


1.5
log
@[IEM] Updates
@
text
@d6 2
a7 1
   * php3 (3.0.7 or newer)
a43 1

@


1.4
log
@[IEM] minor tweak
@
text
@d3 2
a4 1
Requirements: (preliminary)
d6 37
a42 7
php3
apache (ssl prefered)
ssh
postgres/mysql/dbm
a Linux box that has a kernel with firewalling and masq support
    (this is not needed for the machine your installing skattek on)
horde
@


1.3
log
@[IEM] minor updates
@
text
@d1 1
a1 2
Skattek:

@


1.2
log
@[IEM] minor tweak to make sure the cvs mailing is working right
@
text
@d8 1
a8 1
sudo/ssh
d10 2
a11 3
kernel with firewalling and masq support
ssh
scp
@


1.1
log
@[IEM] dumping what I've been working on
@
text
@d4 1
a4 1
Requirements:
@

