From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,af0c6ea85f3ed92d X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.226.10 with SMTP id ro10mr6452747pbc.6.1328994913212; Sat, 11 Feb 2012 13:15:13 -0800 (PST) Path: wr5ni13622pbc.0!nntp.google.com!news2.google.com!postnews.google.com!m2g2000vbc.googlegroups.com!not-for-mail From: Maciej Sobczak Newsgroups: comp.lang.ada Subject: Re: Arbitrary Sandbox Date: Sat, 11 Feb 2012 13:15:12 -0800 (PST) Organization: http://groups.google.com Message-ID: References: <8e83f2be-c6e9-4b0b-b53c-d50fe70d01e1@pq6g2000pbc.googlegroups.com> <702c5d55-ff96-486c-bff9-93aa273f6217@i18g2000yqf.googlegroups.com> NNTP-Posting-Host: 95.49.186.187 Mime-Version: 1.0 X-Trace: posting.google.com 1328994913 22640 127.0.0.1 (11 Feb 2012 21:15:13 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sat, 11 Feb 2012 21:15:13 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: m2g2000vbc.googlegroups.com; posting-host=95.49.186.187; posting-account=bMuEOQoAAACUUr_ghL3RBIi5neBZ5w_S User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HUALESNKRC X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13,gzip(gfe) Content-Type: text/plain; charset=ISO-8859-1 Date: 2012-02-11T13:15:12-08:00 List-Id: On 11 Lut, 12:39, "Dmitry A. Kazakov" wrote: > I wonder when (maybe already) the malware will start to target specifically > virtualization software. That would not be any different from a malware that targets separate physical machines. This of course exists already, but the advantage of a virtual machine is that it can be protected by means that are outside of it. For example, a virtual machine can be put behind a firewall that is outside of the virtual machine (and is therefore unreachable from inside of it) instead of relying on a firewall that is part of the sandboxed system. I count it as an added security. Of course, a virtual machine is a software and can have its own bugs. Whether they can be exploited by a contained (sandboxed) software is another story - but such speculations are true about any software tools, including compilers themselves. We have to trust something and I think that VM-based sandbox is safer than no sandbox at all. -- Maciej Sobczak * http://www.msobczak.com * http://www.inspirel.com