The reason that people are going to #2 is that, if you are concerned about
security, that is the optimal way of setting things up. One box, one
task. That is true "separation". In this light, the question of if #3 is
more secure than #1 is truely a moot point. BUT.... To argue that a
VM running a service is more secure than a system running that same service
is rather weak... if the service can be exploited, it can be exploited.
Be it on a (#1) single server also running other stuff or a (#3) VM guest.
Give me root access to a box (from an exploit or an account, don't matter)
and I can crash the bitch. VM... no VM... No matter. If I can crash
one guest, there is a whole lot of code to support that guest that may or
may not behave well. If Theo et al say that the separation that you get
from virtualization isn't all it's cracked up to be, then quite frankly
the brain trust of these people is pretty massive and they don't tend
towards just spewing crap for no reason and the fact that you are arguing
about it doesn't make you look all that smart. Nothing is perfect,
everything fails, everything eventually crumbles.
Let me quote you directly:
near absolute security?
wow... strong words... I think I'll switch today! I don't think anyone
would say those words about even OpenBSD. Thats why we watch for patches
like demented hawks. That's why we have IDS systems on our networks, and
comb through our logs looking for suspicious stuff.
You sir are selling virtual snake oil. Or at least marketing it pretty
hard. Feel free to buy in to your own delusion, but don't ask me to.
(funny, I say the same thing to certian religous types...)
s
Previous message: [thread] [date] [author] Next message: [thread] [date] [author]
Messages in current thread:
Re: About Xen: maybe a reiterative question but .., Stuart VanZee, (Thu Oct 25, 9:08 am)