On Fri, Oct 18, 2019 at 11:23 PM wrote:
>
> Frank Beuth writes:
> > On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote:
> > >Virtualisation is not a panacea. I have managed to achieve data loss
> > >through destructi
> > ve actions taken within a "safe" virtualised sandbox.
> >
> >
On Fri, Oct 18, 2019 at 01:20:33PM +0100, cho...@jtan.com wrote:
Frank Beuth writes:
On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote:
>Virtualisation is not a panacea. I have managed to achieve data loss through
destructi
ve actions taken within a "safe" virtualised sandbox.
Raul Miller writes:
> My mental model of computer security often approximates putting a bank
> vault door on a picket fence (and maybe setting up a sniper to stop
> people from climbing over the door).
But in layers. One of them will work right? It's defense^Wobscurity
in depth.
> Doesn't mean
On Fri, Oct 18, 2019 at 8:23 AM wrote:
> That's not to even start on the fact that it's little more than process
> switching and virtual memory on steroids, so the extra seperation on top of
> what the OS already provides is little more than smoke and mirrors.
My mental model of computer
On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote:
Virtualisation is not a panacea. I have managed to achieve data loss through destructive
actions taken within a "safe" virtualised sandbox.
How did you manage that feat?
If the only thing that can demonstrate what a piece of
Frank Beuth writes:
> On Fri, Oct 18, 2019 at 11:54:18AM +0100, cho...@jtan.com wrote:
> >Virtualisation is not a panacea. I have managed to achieve data loss through
> >destructi
> ve actions taken within a "safe" virtualised sandbox.
>
> How did you manage that feat?
Basically assuming "safe"
Shane Lazarus writes:
> Heya
>
> My own experience agrees with you with regards to any system in production.
>
> However, it is also my experience that nothing demonstrates the
> difference between what should happen and what actually occurs better
> than running the code and seeing the aftermath.
Heya
My own experience agrees with you with regards to any system in production.
However, it is also my experience that nothing demonstrates the
difference between what should happen and what actually occurs better
than running the code and seeing the aftermath.
Thankfully, virtualisation makes
With regards to recent discussion, here is a little anecdote that came out of
the 6.5 to 6.6 upgrade.
On one machine I run bitlbee, an IRC:IM gateway. After upgrading all the ports
it left suggestions in the form of copy pasta commands to run to complete the
upgrade process, as it does. One of
9 matches
Mail list logo