> > There is a ton of evidence both in computing and outside of it whichOn the contrary because I know it is not secure I would a) Insure it b) Not waste vast amounts of money on a useless expensive lock c) Make sure the bike looked not worth stealing d) Take the saddle with me (or the software versions of that a) Keep backups b) Not waste vast amounts of money on bogus security software c) Keep the system looking uninteresting d) Encrypt the data) Yes and its very clear from the things said by politicians that if the computer software people don't do this soon, the legislators will make very sure they do by stripping away all the techniques used to hide from liability for failure. Absolutely - but those layers should do whatever they do *right* and really do it, whether they are complex whole system controls like SELinux or simple network security tools. Alan -
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| holzheu | Re: [RFC/PATCH] Documentation of kernel messages |
| FUJITA Tomonori | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 13/37] dccp: Deprecate Ack Ratio sysctl |
| Arjan van de Ven | Re: [GIT]: Networking |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
