On Sat, 2003-02-15 at 01:58, Buchan Milne wrote: > On 14 Feb 2003, James Sparenberg wrote: > > > Richard, > > > > In order to test what you say I tried what you are doing with msec > > (yes I know the risks but on this box msec makes doing what I have to do > > for testing and development impossible.) I knew that drakxtools had an > > update so I wanted to see what would happen. > > Sorry to jump in here, but please don't make statements like this as fact. > msec doesn't make things impossible, it only enforces what you have told > it to enforce. Either change security levels or configure it. It may take > a few minutes to setup and a little more discipline, but don't blame msec > ... it is a great tool if you spend a little time on it. Use drakperm and > drakesec to customise. >
Buchan, It is a great tool... and it does get in the way of some of the work I have to do. The real point here is that you don't know what it is I'm trying to do, and why it gets in the way. I'm doing a kind of raw security testing. Generic, across a multitude of linux distro's and msec does get in the way of what I do. It is a fact. It is what I do. I can't have a tool coming in during the test and making changes on files as it tends to corrupt the data. Other "nice" tools also get pushed to the side. Such as Tripwire, Snort etc. I need a distro that is reliable. Suse tends to be too far from the norm RH keeps throwing errors that are later found to be in the distro itself, and slackware isn't rpm based (but it does work so it's one of my mules.) Linuxconf is a nice tool to... and I don't install either *grin*. James > Buchan
