On 10/24/07, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:(So, I take it that you *don't* lock your bike up, as poor security is worse than none?) While I believe you, I'd love to see references as it doesn't match my day-to-day experience with Win/Mac end-users over the past ten years. I have no trouble believing that. 'Inappropriate risks' nowadays is surfing the web and opening up mail attachments that claim to be movies of dancing bears. I'd argue that users have a reasonable expectation that these are things that should 'just work,' and be safe, much as normal humans have an expectation that their car isn't going to explode when they turn the ignition. Perfect is the enemy of good, or words to that effect, right? My point is that requiring perfection out of a security framework is a bar that's going to be awfully difficult to reach (and when it supposedly has been achieved, as in SELinux, mere mortals find it too troublesome to run with as it's far too difficult to configure). Security can and should be done in layers, and what one may miss, another may catch. Ray -
| Linus Torvalds | Linux 2.6.27-rc5 |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
