What if you have tons of unsaved work opened?
It's just not proper behaviour, when I see a kext (extension) I
suppose that I
can unload it properly. It's like saying this car is safer because since
it can only go backward it drives slower. Yes it might driver slower
but it's in
not way safer. Same thing, it might be good since the "hacker" won't be
able to use your machine, but there are a lot more disadvantages.
On top of that if the hacker can unload the kext that means he has
root access
he can do what ever he wants on your machine. Making it crash isn't
gonna change
much.
Matth.
On 2005-Oct-21, at 10:32 AM, Tom R. no spam wrote:
Hmmmm, looks like a security feature to me. An attacker tries,
and everything comes crashing down. They may damage whatever is
active (tho with journaling, maybe not), but that's it?
On Thu, 20 Oct 2005, LittleSnitch Support wrote:
On Oct 19, 2005, at 21:10, Arno S Hautala wrote:
. . .
unloading the kext in 10.4 results in a system crash. Whether it's
a good idea or not, security wise, to unload the extension, LS
shouldn't crash the system in this manner.
Absolutely. This is a kernel bug in 10.4 (up to 10.4.2). We've
reported this bug to Apple some time ago and rumor has it that this
bug should be fixed in 10.4.3. As you normally don't unload the kext,
I hope this is not really a problem until Apple has fixed this.
_______________________________________________
Littlesnitch-talk mailing list
[email protected]
http://at.obdev.at/mailman/listinfo/littlesnitch-talk
_______________________________________________
Littlesnitch-talk mailing list
[email protected]
http://at.obdev.at/mailman/listinfo/littlesnitch-talk
