SAStk / News: Recent posts

I am about to submit one last SAStk Release that will work on Slackware-8.0.
This will basically be a snapshot of the current CVS tree which includes a couple of minor bug fixes.
After that We will begin working on porting SAStk for use on Slackware-8.1.

mRgOBLIN

Due to an error in the pkgmake.sh script our 0.1.3.0 release set the wrong permissions for the systems / directory. This error and the pkmake.sh script have been corrected in this release.

SAStk -- Slackware Administrators Security tool kit.
Some major new features added, SAStk now uses a "Dialog" interface and includes a port of SuSE's seccheck.
This release of SAStk is intended for Slackware 8.0 only.
SAStk.tgz is a Slackware tgz package and is available via the download area or you may check out the "work in progress" version from CVS.

Please Read the release notes for full details.
http://sourceforge.net/project/shownotes.php?release_id=67867... read more

SAStk Update.

Work is currently underway to port SAStk over to Slackware 8.0.
New features will include a Dialog interface and some extra security checking.
The code in CVS is still in the testing phase and should not be run in a production enviroment.
We do however, welcome feedback from those hardy souls willing to test this on an expendable machine.

mRgOBLIN

SAStk-0.1.2.0.tgz -- Slackware Administrators Security tool kit.
This is the Alpha Release 0.1.2.0 -- Mostly a bug fix but does include some extra functionality.
If you are upgrading from 0.1.x we recommend you uninstall your current version and start again.

An SAStk-0.1.2.0.tar.gz package is also available from
ftp://sastk.sourceforge.net/pub/sastk/

mRgOBLIN

SAStk-0.1 is now available in tar.gz format from the SAStk files section.
We also have a Slackware .tgz package and a .shar archive which can be downloaded from
ftp://sastk.sourceforge.net/pub/sastk/
Please read the NOTES and INSTALL docs before running the install script.

mRgOBLIN

The Plan is now located in the DocManager. if you have any comments or suggestions, please send them to myself or to the mailing list (when it becomes available). Feel free to submit anything other documentation that you would like to have available.