Quoting "Douglas A. Tutty" :
> Problem: in your analogy, there is some limit to the number of bad guys
I would have thought this is further evidence of the analogy not being too bad.
You are relying on secrecy - if that is blown, you're screwed across the board
- all four ambassadors. So for virtualisation, you are relying on the separate
application domains being partitioned off from each other - and if that is
blown, you're screwed across the board again. In both cases, the failure could
be malicious (bad guy tortures the maid for information / hacker gets into
system) or accidental (toxic leak on subway / some interaction between guest
process and host triggers previously undiscovered bug.)
But instead of going all James Bond-ish - I could have said is having all your
eggs in one basket more secure?
| Andreas Gruenbacher | Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
| Alan Cox | Re: [patch 7/8] fdmap v2 - implement sys_socket2 |
| Jens Axboe | Re: regression: CD burning (k3b) went broke |
| Paul E. McKenney | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
git: | |
| KOSAKI Motohiro | [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | [GIT]: Networking |
| Alexey Dobriyan | [PATCH 09/33] netns ct: per-netns /proc/net/nf_conntrack, /proc/net/stat/nf_conntr... |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
