From publicity-bounces@lists.xenproject.org Wed Oct 01 10:00:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Oct 2014 10:00:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZGhj-0003Ya-FG; Wed, 01 Oct 2014 10:00:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZGhh-0003YR-7v for publicity@lists.xenproject.org; Wed, 01 Oct 2014 10:00:13 +0000 Received: from [85.158.137.68:24747] by server-1.bemta-3.messagelabs.com id 15/3C-30185-CA0DB245; Wed, 01 Oct 2014 10:00:12 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1412157608!10783134!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11048 invoked from network); 1 Oct 2014 10:00:09 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 1 Oct 2014 10:00:09 -0000 Received: by mail-wi0-f170.google.com with SMTP id hi2so143045wib.3 for ; Wed, 01 Oct 2014 03:00:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yJip7uOy50qz3Fb/T3pANXYy/SjaF0wbd76OCqwU3NE=; b=vJG3gdDvC/DgocGY17oZHL4XinvX2W8cUok3jEes/L0rNhUMlvaVvvUtGrgprWcV11 8++Njy69KCYGZoRu/J8Zv/JQXSPpnZYsPXkpxU3NjacSVFMd9f5bokz77bH0M9UY3CI4 1nxKhuev50iQlJmfg0eEk987FYVMMW5vCb+X+FR8nFODCmdK7SqSahuj1vxRbF1LSsEY xH2sEmAz6uVTre7YJVIU17xKu29sYfo0nuydZYCzvuHA7Kkvp4rhyZpzSk0s18+pQGpH Xz5DyXx6OEXHHbRBVdKXZvqjzu3LSY+sfyQhacIg9BD7XtSF7Q18qzTr+JrSGXNe2PRW R+OA== X-Received: by 10.180.96.161 with SMTP id dt1mr12756713wib.1.1412157608645; Wed, 01 Oct 2014 03:00:08 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id q5sm561606wja.49.2014.10.01.03.00.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Oct 2014 03:00:07 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <542AE2FE.2070807@eu.citrix.com> Date: Wed, 1 Oct 2014 11:00:05 +0100 Message-Id: <4F100AC9-4B9F-44AF-89E6-7BF0B0C8C012@gmail.com> References: <542AE2FE.2070807@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: "kbsingh@karan.org" , "publicity@lists.xenproject.org" Subject: Re: [Publicity] FOSDEM talk on CentOS SIGs X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org I think this is good. I would appreciate KB=92s perspective. I think it is = likely that the talk will be rejected though (or bounced to the distro devr= oom) It=92s not normally a topic for the main track Lars On 30 Sep 2014, at 18:06, George Dunlap wrote: > Below is a draft of my submission to FOSDEM for a main track talk on Cent= OS SIGs. Let me know what you think -- the deadline for submission is tomo= rrow. > = > Peace, > -George > = > = > = > * CentOS SIGs: Community packages on an immutable core > = > CentOS is a "distribution" with a rather unique description: it is a free= (gratis) clone of a commercially-supported distribution with all the brand= ing removed. Being Probably say Linux =93distribution" > enterprise-grade distribution means solid, well-tested, and slow-moving; = but it also means not having the latest functionality. It also means havin= g a small enough I would take out slow-moving as it duplicates what you say afterwards It also means used twice > feature set to provide commercial support in a viable manner: and that ty= pically means choosing one technology and sticking with it. > = > But what if you wanted your entire system to be solid, well-tested, and s= low-moving, *except* for one particular package or program? Or what if you= really wanted an How about =93=85 solid and well-tested and add the latest functionality for= one particular =85=94 > enterprise system, but wanted to use one of the alternate technoloies tha= t were not selected? > = > This is where CentOS SIGs come in. The new CentOS is still at its core a= clone of an upstream enterprise distribution. But having had success with= the Xen4CentOS project, which provided a version of Xen to run on CentOS 6= , they have now generalized the process. > = > This talk will talk about CentOS SIGs, and compare and contrast them to o= ther community distro development models like Fedora, OpenSuSE, Debian, Ubu= ntu, and so forth. I would also add: we will also share lessons from the CentOS Virt SIG, in w= hich a number of virtualisation and related technologies such as Xen, oVirt= , Docker and others collaborate Regards Lars _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Wed Oct 01 10:00:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 01 Oct 2014 10:00:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZGhj-0003Ya-FG; Wed, 01 Oct 2014 10:00:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZGhh-0003YR-7v for publicity@lists.xenproject.org; Wed, 01 Oct 2014 10:00:13 +0000 Received: from [85.158.137.68:24747] by server-1.bemta-3.messagelabs.com id 15/3C-30185-CA0DB245; Wed, 01 Oct 2014 10:00:12 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1412157608!10783134!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11048 invoked from network); 1 Oct 2014 10:00:09 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-10.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 1 Oct 2014 10:00:09 -0000 Received: by mail-wi0-f170.google.com with SMTP id hi2so143045wib.3 for ; Wed, 01 Oct 2014 03:00:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yJip7uOy50qz3Fb/T3pANXYy/SjaF0wbd76OCqwU3NE=; b=vJG3gdDvC/DgocGY17oZHL4XinvX2W8cUok3jEes/L0rNhUMlvaVvvUtGrgprWcV11 8++Njy69KCYGZoRu/J8Zv/JQXSPpnZYsPXkpxU3NjacSVFMd9f5bokz77bH0M9UY3CI4 1nxKhuev50iQlJmfg0eEk987FYVMMW5vCb+X+FR8nFODCmdK7SqSahuj1vxRbF1LSsEY xH2sEmAz6uVTre7YJVIU17xKu29sYfo0nuydZYCzvuHA7Kkvp4rhyZpzSk0s18+pQGpH Xz5DyXx6OEXHHbRBVdKXZvqjzu3LSY+sfyQhacIg9BD7XtSF7Q18qzTr+JrSGXNe2PRW R+OA== X-Received: by 10.180.96.161 with SMTP id dt1mr12756713wib.1.1412157608645; Wed, 01 Oct 2014 03:00:08 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id q5sm561606wja.49.2014.10.01.03.00.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Oct 2014 03:00:07 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <542AE2FE.2070807@eu.citrix.com> Date: Wed, 1 Oct 2014 11:00:05 +0100 Message-Id: <4F100AC9-4B9F-44AF-89E6-7BF0B0C8C012@gmail.com> References: <542AE2FE.2070807@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: "kbsingh@karan.org" , "publicity@lists.xenproject.org" Subject: Re: [Publicity] FOSDEM talk on CentOS SIGs X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org I think this is good. I would appreciate KB=92s perspective. I think it is = likely that the talk will be rejected though (or bounced to the distro devr= oom) It=92s not normally a topic for the main track Lars On 30 Sep 2014, at 18:06, George Dunlap wrote: > Below is a draft of my submission to FOSDEM for a main track talk on Cent= OS SIGs. Let me know what you think -- the deadline for submission is tomo= rrow. > = > Peace, > -George > = > = > = > * CentOS SIGs: Community packages on an immutable core > = > CentOS is a "distribution" with a rather unique description: it is a free= (gratis) clone of a commercially-supported distribution with all the brand= ing removed. Being Probably say Linux =93distribution" > enterprise-grade distribution means solid, well-tested, and slow-moving; = but it also means not having the latest functionality. It also means havin= g a small enough I would take out slow-moving as it duplicates what you say afterwards It also means used twice > feature set to provide commercial support in a viable manner: and that ty= pically means choosing one technology and sticking with it. > = > But what if you wanted your entire system to be solid, well-tested, and s= low-moving, *except* for one particular package or program? Or what if you= really wanted an How about =93=85 solid and well-tested and add the latest functionality for= one particular =85=94 > enterprise system, but wanted to use one of the alternate technoloies tha= t were not selected? > = > This is where CentOS SIGs come in. The new CentOS is still at its core a= clone of an upstream enterprise distribution. But having had success with= the Xen4CentOS project, which provided a version of Xen to run on CentOS 6= , they have now generalized the process. > = > This talk will talk about CentOS SIGs, and compare and contrast them to o= ther community distro development models like Fedora, OpenSuSE, Debian, Ubu= ntu, and so forth. I would also add: we will also share lessons from the CentOS Virt SIG, in w= hich a number of virtualisation and related technologies such as Xen, oVirt= , Docker and others collaborate Regards Lars _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 14:49:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 14:49:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZhhP-0001jq-6a; Thu, 02 Oct 2014 14:49:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZhhN-0001jg-PO for publicity@lists.xenproject.org; Thu, 02 Oct 2014 14:49:41 +0000 Received: from [85.158.139.211:2165] by server-6.bemta-5.messagelabs.com id E4/C3-06284-5066D245; Thu, 02 Oct 2014 14:49:41 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1412261378!11681206!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19431 invoked from network); 2 Oct 2014 14:49:40 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 14:49:40 -0000 X-IronPort-AV: E=Sophos;i="5.04,638,1406592000"; d="scan'208";a="177505094" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 10:49:08 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZhgq-0005ox-J2; Thu, 02 Oct 2014 15:49:08 +0100 Message-ID: <542D65BE.8000604@eu.citrix.com> Date: Thu, 2 Oct 2014 15:48:30 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , Andrew Halley X-DLP: MIA1 Subject: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Hey all, Below is a more technical draft blog post in response to the recent media flurry about XSA-108. If you've updated your blog logins you can also preview the post here: https://blog.xenproject.org/?p=10093&preview=true Let me know if you have any feedback! -George XSA-108: Not the disaster you're looking for There has an unusual amount of media attention to XSA-108, whose embargo period ended Wednesday -- far more than any of the previous 107 vulnerabilities the Xen Project has reported. It began when a blogger noticed that Amazon was telling customers it would be rebooting VMs in certain regions before a specific date -- a date which happened to coincide with the release of XSA-108. He conjectured that the reboots had something to do with that, and further conjectured that, because of the major impact to customers of rebooting, that it must be something very big and important, similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon confirmed that the reboots had to do with XSA-108, but could say nothing else because of the security embargo. Unfortunately, because of the nature of embargoes, nobody with any actual knowledge of the vulnerability was allowed to say anything about it, and so the media was entirely free to speculate without any actual facts getting in the way. Now that the embargo has lifted, we can talk in detail about the vulnerability; and I'm afraid that people looking for another Shell Shock or Heartbleed are going to be disappointed.

What is the vulnerability?

XSA-108 has to do with the emulation of a piece of hardware called an x2apic. x2apic is an interrupt controller: it allows the operating system to control when and how and where urgent messages from outside the chip, and from other cores within the same chip, are delivered. Interrupt controllers occupy a rather awkward position in the architecture. They are fairly complicated to implement in hardware; which is why they are not yet implemented by Intel's VT hardware. (This may change in the future.) But they are far too performance critical for Xen to pass emulation off to qemu, as it does with virtual disks or virtual networks. This means that they must be emulated within Xen. The actual vulnerability, like most vulnerabilities, is pretty simple. Xen implements 256 x2apic registers. These registers are stored in a buffer big enough to hold exactly 256 registers. However, the limit check for reading these registers was erroneosly set to 1024. What this means is that, without the fix, if you read x2apic registers 0-255, you'll get the correct emulated value from the register buffer; but if you read x2apic registers 256-1023, Xen will copy hypervisor memory from directly afterwards into the guest. So what this bug gives you is the ability to read (and only read) the 12k [1] of memory directly adjacent to where Xen is storing the first 256 registers (and no other area of memory). The fix simply corrects the limit check to 256. The emulated x2apic functionality was introduced in Xen 4.1, so previous versions of Xen are not affected. Neither are PV guests, since Xen does not provide them with any emulated hardware.

The impact

If this seems like a relatively minor issue, that's because it is. The most likely scenario is that that 12k of memory contains other Xen data structures which contain no important information. There is, however, a small chance that this memory might contain memory from another VM; and a small chance that this memory might contain sensitive information, like passwords, encryption keys, or other private data. Nonetheless, this is a security issue, and the XenProject takes all potential security issues very seriously, no matter how minor. We have a mature process in place to notify cloud providers, distributions, and software providers so that they can have a fix in place before publicly disclosing any vulnerability. Applying security patches proactively, even though there's very low risk that anyone might have their secret data leaked because of it, is a conscientious and diligient thing to do. We're glad to see that so many cloud providers using Xen are demonstrating how seriously they take protecting customer data. But it is by no means a disaster. Those looking for a major scandal like Heartbleed and Shellshocker will be disappointed. [1] You may see this reported elsewhere as 3k; saying either 3k or 12k is simplifiying the truth in different ways. The MSR data is laid out as a 16-byte structure, of which only the first four bytes (one 32-bit word) can be read by this vulnerability. So the actual amount of data which is exposed is 3k, but it's spread out in 4-byte chunks across 12k of memory. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 14:49:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 14:49:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZhhP-0001jq-6a; Thu, 02 Oct 2014 14:49:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZhhN-0001jg-PO for publicity@lists.xenproject.org; Thu, 02 Oct 2014 14:49:41 +0000 Received: from [85.158.139.211:2165] by server-6.bemta-5.messagelabs.com id E4/C3-06284-5066D245; Thu, 02 Oct 2014 14:49:41 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1412261378!11681206!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19431 invoked from network); 2 Oct 2014 14:49:40 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 14:49:40 -0000 X-IronPort-AV: E=Sophos;i="5.04,638,1406592000"; d="scan'208";a="177505094" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 10:49:08 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZhgq-0005ox-J2; Thu, 02 Oct 2014 15:49:08 +0100 Message-ID: <542D65BE.8000604@eu.citrix.com> Date: Thu, 2 Oct 2014 15:48:30 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , Andrew Halley X-DLP: MIA1 Subject: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Hey all, Below is a more technical draft blog post in response to the recent media flurry about XSA-108. If you've updated your blog logins you can also preview the post here: https://blog.xenproject.org/?p=10093&preview=true Let me know if you have any feedback! -George XSA-108: Not the disaster you're looking for There has an unusual amount of media attention to XSA-108, whose embargo period ended Wednesday -- far more than any of the previous 107 vulnerabilities the Xen Project has reported. It began when a blogger noticed that Amazon was telling customers it would be rebooting VMs in certain regions before a specific date -- a date which happened to coincide with the release of XSA-108. He conjectured that the reboots had something to do with that, and further conjectured that, because of the major impact to customers of rebooting, that it must be something very big and important, similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon confirmed that the reboots had to do with XSA-108, but could say nothing else because of the security embargo. Unfortunately, because of the nature of embargoes, nobody with any actual knowledge of the vulnerability was allowed to say anything about it, and so the media was entirely free to speculate without any actual facts getting in the way. Now that the embargo has lifted, we can talk in detail about the vulnerability; and I'm afraid that people looking for another Shell Shock or Heartbleed are going to be disappointed.

What is the vulnerability?

XSA-108 has to do with the emulation of a piece of hardware called an x2apic. x2apic is an interrupt controller: it allows the operating system to control when and how and where urgent messages from outside the chip, and from other cores within the same chip, are delivered. Interrupt controllers occupy a rather awkward position in the architecture. They are fairly complicated to implement in hardware; which is why they are not yet implemented by Intel's VT hardware. (This may change in the future.) But they are far too performance critical for Xen to pass emulation off to qemu, as it does with virtual disks or virtual networks. This means that they must be emulated within Xen. The actual vulnerability, like most vulnerabilities, is pretty simple. Xen implements 256 x2apic registers. These registers are stored in a buffer big enough to hold exactly 256 registers. However, the limit check for reading these registers was erroneosly set to 1024. What this means is that, without the fix, if you read x2apic registers 0-255, you'll get the correct emulated value from the register buffer; but if you read x2apic registers 256-1023, Xen will copy hypervisor memory from directly afterwards into the guest. So what this bug gives you is the ability to read (and only read) the 12k [1] of memory directly adjacent to where Xen is storing the first 256 registers (and no other area of memory). The fix simply corrects the limit check to 256. The emulated x2apic functionality was introduced in Xen 4.1, so previous versions of Xen are not affected. Neither are PV guests, since Xen does not provide them with any emulated hardware.

The impact

If this seems like a relatively minor issue, that's because it is. The most likely scenario is that that 12k of memory contains other Xen data structures which contain no important information. There is, however, a small chance that this memory might contain memory from another VM; and a small chance that this memory might contain sensitive information, like passwords, encryption keys, or other private data. Nonetheless, this is a security issue, and the XenProject takes all potential security issues very seriously, no matter how minor. We have a mature process in place to notify cloud providers, distributions, and software providers so that they can have a fix in place before publicly disclosing any vulnerability. Applying security patches proactively, even though there's very low risk that anyone might have their secret data leaked because of it, is a conscientious and diligient thing to do. We're glad to see that so many cloud providers using Xen are demonstrating how seriously they take protecting customer data. But it is by no means a disaster. Those looking for a major scandal like Heartbleed and Shellshocker will be disappointed. [1] You may see this reported elsewhere as 3k; saying either 3k or 12k is simplifiying the truth in different ways. The MSR data is laid out as a 16-byte structure, of which only the first four bytes (one 32-bit word) can be read by this vulnerability. So the actual amount of data which is exposed is 3k, but it's spread out in 4-byte chunks across 12k of memory. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:38:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:38:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiSw-0004S0-5g; Thu, 02 Oct 2014 15:38:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiSu-0004Rv-OW for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:38:48 +0000 Received: from [85.158.143.35:5488] by server-1.bemta-4.messagelabs.com id 6B/85-05872-8817D245; Thu, 02 Oct 2014 15:38:48 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1412264326!13423764!1 X-Originating-IP: [141.146.126.69] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuNjkgPT4gMjc3MjE4\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28068 invoked from network); 2 Oct 2014 15:38:47 -0000 Received: from aserp1040.oracle.com (HELO aserp1040.oracle.com) (141.146.126.69) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2014 15:38:47 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s92Fcc9M002675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Oct 2014 15:38:39 GMT Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s92Fcb13023827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Oct 2014 15:38:38 GMT Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id s92FcaSH023775; Thu, 2 Oct 2014 15:38:37 GMT Received: from laptop.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 02 Oct 2014 08:38:36 -0700 Received: by laptop.dumpdata.com (Postfix, from userid 1000) id 9D3BAEA892; Thu, 2 Oct 2014 11:38:35 -0400 (EDT) Date: Thu, 2 Oct 2014 11:38:35 -0400 From: Konrad Rzeszutek Wilk To: George Dunlap Message-ID: <20141002153835.GF32249@laptop.dumpdata.com> References: <542D65BE.8000604@eu.citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <542D65BE.8000604@eu.citrix.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On Thu, Oct 02, 2014 at 03:48:30PM +0100, George Dunlap wrote: > Hey all, > > Below is a more technical draft blog post in response to the recent media > flurry about XSA-108. If you've updated your blog logins you can also > preview the post here: https://blog.xenproject.org/?p=10093&preview=true > > Let me know if you have any feedback! You might want to add that Linux guests that run in HVM mode don't enable x2APIC mode at all - as they end up using the PVHVM route which ends up using events. This does affect 'true' HVM guests. > > -George > > XSA-108: Not the disaster you're looking for > > There has an unusual amount of media attention to XSA-108, whose embargo > period ended Wednesday -- far more than any of the previous 107 > vulnerabilities the Xen Project has reported. It began when a blogger > noticed that Amazon was telling customers it would be rebooting VMs in > certain regions before a specific date -- a date which happened to coincide > with the release of XSA-108. He conjectured that the reboots had something > to do with that, and further conjectured that, because of the major impact > to customers of rebooting, that it must be something very big and important, > similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon > confirmed that the reboots had to do with XSA-108, but could say nothing > else because of the security embargo. > > Unfortunately, because of the nature of embargoes, nobody with any actual > knowledge of the vulnerability was allowed to say anything about it, and so > the media was entirely free to speculate without any actual facts getting in > the way. > > Now that the embargo has lifted, we can talk in detail about the > vulnerability; and I'm afraid that people looking for another Shell Shock or > Heartbleed are going to be disappointed. > >

What is the vulnerability?

> > XSA-108 has to do with the emulation of a piece of hardware called an > x2apic. x2apic is an interrupt controller: it allows the operating system x2APIC > to control when and how and where urgent messages from outside the chip, and > from other cores within the same chip, are delivered. > > Interrupt controllers occupy a rather awkward position in the architecture. > They are fairly complicated to implement in hardware; which is why they are > not yet implemented by Intel's VT hardware. (This may change in the future.) > But they are far too performance critical for Xen to pass emulation off to > qemu, as it does with virtual disks or virtual networks. This means that QEMU > they must be emulated within Xen. > > The actual vulnerability, like most vulnerabilities, is pretty simple. Xen > implements 256 x2apic registers. These registers are stored in a buffer big > enough to hold exactly 256 registers. However, the limit check for reading > these registers was erroneosly set to 1024. > > What this means is that, without the fix, if you read x2apic registers > 0-255, you'll get the correct emulated value from the register buffer; but > if you read x2apic registers 256-1023, Xen will copy hypervisor memory from > directly afterwards into the guest. > > So what this bug gives you is the ability to read (and only read) the 12k > [1] of memory directly adjacent to where Xen is storing the first 256 > registers (and no other area of memory). > > The fix simply corrects the limit check to 256. > > The emulated x2apic functionality was introduced in Xen 4.1, so previous > versions of Xen are not affected. Neither are PV guests, since Xen does not > provide them with any emulated hardware. > >

The impact

> > If this seems like a relatively minor issue, that's because it is. The most > likely scenario is that that 12k of memory contains other Xen data > structures which contain no important information. There is, however, a > small chance that this memory might contain memory from another VM; > and a small chance that this memory might contain sensitive > information, like passwords, encryption keys, or other private data. > > Nonetheless, this is a security issue, and the XenProject takes all > potential security issues very seriously, no matter how minor. We have a > mature process in > place to notify cloud providers, distributions, and software providers so > that they can have a fix in place before publicly disclosing any > vulnerability. > > Applying security patches proactively, even though there's very low risk > that anyone might have their secret data leaked because of it, is a > conscientious and diligient thing to do. We're glad to see that so many > cloud providers using Xen are demonstrating how seriously they take > protecting customer data. > > But it is by no means a disaster. Those looking for a major scandal like > Heartbleed and Shellshocker will be disappointed. > > > [1] You may see this reported elsewhere as 3k; saying either 3k or 12k is > simplifiying the truth in different ways. The MSR data is laid out as a > 16-byte structure, of which only the first four bytes (one 32-bit word) can > be read by this vulnerability. So the actual amount of data which is > exposed is 3k, but it's spread out in 4-byte chunks across 12k of memory. > > > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:38:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:38:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiSw-0004S0-5g; Thu, 02 Oct 2014 15:38:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiSu-0004Rv-OW for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:38:48 +0000 Received: from [85.158.143.35:5488] by server-1.bemta-4.messagelabs.com id 6B/85-05872-8817D245; Thu, 02 Oct 2014 15:38:48 +0000 X-Env-Sender: konrad.wilk@oracle.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1412264326!13423764!1 X-Originating-IP: [141.146.126.69] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTQxLjE0Ni4xMjYuNjkgPT4gMjc3MjE4\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28068 invoked from network); 2 Oct 2014 15:38:47 -0000 Received: from aserp1040.oracle.com (HELO aserp1040.oracle.com) (141.146.126.69) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2014 15:38:47 -0000 Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s92Fcc9M002675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 2 Oct 2014 15:38:39 GMT Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet22.oracle.com (8.14.5+Sun/8.14.5) with ESMTP id s92Fcb13023827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Oct 2014 15:38:38 GMT Received: from abhmp0008.oracle.com (abhmp0008.oracle.com [141.146.116.14]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id s92FcaSH023775; Thu, 2 Oct 2014 15:38:37 GMT Received: from laptop.dumpdata.com (/50.195.21.189) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 02 Oct 2014 08:38:36 -0700 Received: by laptop.dumpdata.com (Postfix, from userid 1000) id 9D3BAEA892; Thu, 2 Oct 2014 11:38:35 -0400 (EDT) Date: Thu, 2 Oct 2014 11:38:35 -0400 From: Konrad Rzeszutek Wilk To: George Dunlap Message-ID: <20141002153835.GF32249@laptop.dumpdata.com> References: <542D65BE.8000604@eu.citrix.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <542D65BE.8000604@eu.citrix.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On Thu, Oct 02, 2014 at 03:48:30PM +0100, George Dunlap wrote: > Hey all, > > Below is a more technical draft blog post in response to the recent media > flurry about XSA-108. If you've updated your blog logins you can also > preview the post here: https://blog.xenproject.org/?p=10093&preview=true > > Let me know if you have any feedback! You might want to add that Linux guests that run in HVM mode don't enable x2APIC mode at all - as they end up using the PVHVM route which ends up using events. This does affect 'true' HVM guests. > > -George > > XSA-108: Not the disaster you're looking for > > There has an unusual amount of media attention to XSA-108, whose embargo > period ended Wednesday -- far more than any of the previous 107 > vulnerabilities the Xen Project has reported. It began when a blogger > noticed that Amazon was telling customers it would be rebooting VMs in > certain regions before a specific date -- a date which happened to coincide > with the release of XSA-108. He conjectured that the reboots had something > to do with that, and further conjectured that, because of the major impact > to customers of rebooting, that it must be something very big and important, > similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon > confirmed that the reboots had to do with XSA-108, but could say nothing > else because of the security embargo. > > Unfortunately, because of the nature of embargoes, nobody with any actual > knowledge of the vulnerability was allowed to say anything about it, and so > the media was entirely free to speculate without any actual facts getting in > the way. > > Now that the embargo has lifted, we can talk in detail about the > vulnerability; and I'm afraid that people looking for another Shell Shock or > Heartbleed are going to be disappointed. > >

What is the vulnerability?

> > XSA-108 has to do with the emulation of a piece of hardware called an > x2apic. x2apic is an interrupt controller: it allows the operating system x2APIC > to control when and how and where urgent messages from outside the chip, and > from other cores within the same chip, are delivered. > > Interrupt controllers occupy a rather awkward position in the architecture. > They are fairly complicated to implement in hardware; which is why they are > not yet implemented by Intel's VT hardware. (This may change in the future.) > But they are far too performance critical for Xen to pass emulation off to > qemu, as it does with virtual disks or virtual networks. This means that QEMU > they must be emulated within Xen. > > The actual vulnerability, like most vulnerabilities, is pretty simple. Xen > implements 256 x2apic registers. These registers are stored in a buffer big > enough to hold exactly 256 registers. However, the limit check for reading > these registers was erroneosly set to 1024. > > What this means is that, without the fix, if you read x2apic registers > 0-255, you'll get the correct emulated value from the register buffer; but > if you read x2apic registers 256-1023, Xen will copy hypervisor memory from > directly afterwards into the guest. > > So what this bug gives you is the ability to read (and only read) the 12k > [1] of memory directly adjacent to where Xen is storing the first 256 > registers (and no other area of memory). > > The fix simply corrects the limit check to 256. > > The emulated x2apic functionality was introduced in Xen 4.1, so previous > versions of Xen are not affected. Neither are PV guests, since Xen does not > provide them with any emulated hardware. > >

The impact

> > If this seems like a relatively minor issue, that's because it is. The most > likely scenario is that that 12k of memory contains other Xen data > structures which contain no important information. There is, however, a > small chance that this memory might contain memory from another VM; > and a small chance that this memory might contain sensitive > information, like passwords, encryption keys, or other private data. > > Nonetheless, this is a security issue, and the XenProject takes all > potential security issues very seriously, no matter how minor. We have a > mature process in > place to notify cloud providers, distributions, and software providers so > that they can have a fix in place before publicly disclosing any > vulnerability. > > Applying security patches proactively, even though there's very low risk > that anyone might have their secret data leaked because of it, is a > conscientious and diligient thing to do. We're glad to see that so many > cloud providers using Xen are demonstrating how seriously they take > protecting customer data. > > But it is by no means a disaster. Those looking for a major scandal like > Heartbleed and Shellshocker will be disappointed. > > > [1] You may see this reported elsewhere as 3k; saying either 3k or 12k is > simplifiying the truth in different ways. The MSR data is laid out as a > 16-byte structure, of which only the first four bytes (one 32-bit word) can > be read by this vulnerability. So the actual amount of data which is > exposed is 3k, but it's spread out in 4-byte chunks across 12k of memory. > > > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:41:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:41:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiVB-0004UZ-Cf; Thu, 02 Oct 2014 15:41:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiVA-0004UU-PD for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:41:08 +0000 Received: from [85.158.139.211:39335] by server-11.bemta-5.messagelabs.com id 1E/62-11011-3127D245; Thu, 02 Oct 2014 15:41:07 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1412264465!11665682!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10884 invoked from network); 2 Oct 2014 15:41:07 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 15:41:07 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="178598691" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 11:41:03 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZiV5-0006Ya-Ld; Thu, 02 Oct 2014 16:41:03 +0100 Message-ID: <542D71E9.5060505@eu.citrix.com> Date: Thu, 2 Oct 2014 16:40:25 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> In-Reply-To: <20141002153835.GF32249@laptop.dumpdata.com> X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 10/02/2014 04:38 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Oct 02, 2014 at 03:48:30PM +0100, George Dunlap wrote: >> Hey all, >> >> Below is a more technical draft blog post in response to the recent media >> flurry about XSA-108. If you've updated your blog logins you can also >> preview the post here: https://blog.xenproject.org/?p=10093&preview=true >> >> Let me know if you have any feedback! > You might want to add that Linux guests that run in HVM mode don't enable > x2APIC mode at all - as they end up using the PVHVM route which ends up > using events. > > This does affect 'true' HVM guests. But you could only exploit this if you have control of the guest OS; and if you have that, you can enable the x2APIC, right? > >> -George >> >> XSA-108: Not the disaster you're looking for >> >> There has an unusual amount of media attention to XSA-108, whose embargo >> period ended Wednesday -- far more than any of the previous 107 >> vulnerabilities the Xen Project has reported. It began when a blogger >> noticed that Amazon was telling customers it would be rebooting VMs in >> certain regions before a specific date -- a date which happened to coincide >> with the release of XSA-108. He conjectured that the reboots had something >> to do with that, and further conjectured that, because of the major impact >> to customers of rebooting, that it must be something very big and important, >> similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon >> confirmed that the reboots had to do with XSA-108, but could say nothing >> else because of the security embargo. >> >> Unfortunately, because of the nature of embargoes, nobody with any actual >> knowledge of the vulnerability was allowed to say anything about it, and so >> the media was entirely free to speculate without any actual facts getting in >> the way. >> >> Now that the embargo has lifted, we can talk in detail about the >> vulnerability; and I'm afraid that people looking for another Shell Shock or >> Heartbleed are going to be disappointed. >> >>

What is the vulnerability?

>> >> XSA-108 has to do with the emulation of a piece of hardware called an >> x2apic. x2apic is an interrupt controller: it allows the operating system > x2APIC > >> to control when and how and where urgent messages from outside the chip, and >> from other cores within the same chip, are delivered. >> >> Interrupt controllers occupy a rather awkward position in the architecture. >> They are fairly complicated to implement in hardware; which is why they are >> not yet implemented by Intel's VT hardware. (This may change in the future.) >> But they are far too performance critical for Xen to pass emulation off to >> qemu, as it does with virtual disks or virtual networks. This means that > QEMU Do I have to? :-) I think it looks much nicer as "qemu"... -George _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:41:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:41:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiVB-0004UZ-Cf; Thu, 02 Oct 2014 15:41:09 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZiVA-0004UU-PD for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:41:08 +0000 Received: from [85.158.139.211:39335] by server-11.bemta-5.messagelabs.com id 1E/62-11011-3127D245; Thu, 02 Oct 2014 15:41:07 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1412264465!11665682!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10884 invoked from network); 2 Oct 2014 15:41:07 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 15:41:07 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="178598691" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 11:41:03 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZiV5-0006Ya-Ld; Thu, 02 Oct 2014 16:41:03 +0100 Message-ID: <542D71E9.5060505@eu.citrix.com> Date: Thu, 2 Oct 2014 16:40:25 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> In-Reply-To: <20141002153835.GF32249@laptop.dumpdata.com> X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 10/02/2014 04:38 PM, Konrad Rzeszutek Wilk wrote: > On Thu, Oct 02, 2014 at 03:48:30PM +0100, George Dunlap wrote: >> Hey all, >> >> Below is a more technical draft blog post in response to the recent media >> flurry about XSA-108. If you've updated your blog logins you can also >> preview the post here: https://blog.xenproject.org/?p=10093&preview=true >> >> Let me know if you have any feedback! > You might want to add that Linux guests that run in HVM mode don't enable > x2APIC mode at all - as they end up using the PVHVM route which ends up > using events. > > This does affect 'true' HVM guests. But you could only exploit this if you have control of the guest OS; and if you have that, you can enable the x2APIC, right? > >> -George >> >> XSA-108: Not the disaster you're looking for >> >> There has an unusual amount of media attention to XSA-108, whose embargo >> period ended Wednesday -- far more than any of the previous 107 >> vulnerabilities the Xen Project has reported. It began when a blogger >> noticed that Amazon was telling customers it would be rebooting VMs in >> certain regions before a specific date -- a date which happened to coincide >> with the release of XSA-108. He conjectured that the reboots had something >> to do with that, and further conjectured that, because of the major impact >> to customers of rebooting, that it must be something very big and important, >> similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon >> confirmed that the reboots had to do with XSA-108, but could say nothing >> else because of the security embargo. >> >> Unfortunately, because of the nature of embargoes, nobody with any actual >> knowledge of the vulnerability was allowed to say anything about it, and so >> the media was entirely free to speculate without any actual facts getting in >> the way. >> >> Now that the embargo has lifted, we can talk in detail about the >> vulnerability; and I'm afraid that people looking for another Shell Shock or >> Heartbleed are going to be disappointed. >> >>

What is the vulnerability?

>> >> XSA-108 has to do with the emulation of a piece of hardware called an >> x2apic. x2apic is an interrupt controller: it allows the operating system > x2APIC > >> to control when and how and where urgent messages from outside the chip, and >> from other cores within the same chip, are delivered. >> >> Interrupt controllers occupy a rather awkward position in the architecture. >> They are fairly complicated to implement in hardware; which is why they are >> not yet implemented by Intel's VT hardware. (This may change in the future.) >> But they are far too performance critical for Xen to pass emulation off to >> qemu, as it does with virtual disks or virtual networks. This means that > QEMU Do I have to? :-) I think it looks much nicer as "qemu"... -George _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:56:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:56:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZikE-0005Hf-4s; Thu, 02 Oct 2014 15:56:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZikC-0005HZ-SO for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:56:40 +0000 Received: from [85.158.143.35:13853] by server-1.bemta-4.messagelabs.com id 25/E2-05872-8B57D245; Thu, 02 Oct 2014 15:56:40 +0000 X-Env-Sender: Stefano.Stabellini@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1412265398!13519334!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25423 invoked from network); 2 Oct 2014 15:56:39 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 15:56:39 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="177535431" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 11:54:11 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZihm-0006ks-Vx; Thu, 02 Oct 2014 16:54:10 +0100 Date: Thu, 2 Oct 2014 16:52:03 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: George Dunlap In-Reply-To: <542D71E9.5060505@eu.citrix.com> Message-ID: References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> <542D71E9.5060505@eu.citrix.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On Thu, 2 Oct 2014, George Dunlap wrote: > > > to control when and how and where urgent messages from outside the chip, > > > and > > > from other cores within the same chip, are delivered. > > > > > > Interrupt controllers occupy a rather awkward position in the > > > architecture. > > > They are fairly complicated to implement in hardware; which is why they > > > are > > > not yet implemented by Intel's VT hardware. (This may change in the > > > future.) > > > But they are far too performance critical for Xen to pass emulation off to > > > qemu, as it does with virtual disks or virtual networks. This means that > > QEMU > > Do I have to? :-) I think it looks much nicer as "qemu"... It's a few years now that they have started enforcing the name of the project as "QEMU" everywhere. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:56:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:56:42 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZikE-0005Hf-4s; Thu, 02 Oct 2014 15:56:42 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZikC-0005HZ-SO for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:56:40 +0000 Received: from [85.158.143.35:13853] by server-1.bemta-4.messagelabs.com id 25/E2-05872-8B57D245; Thu, 02 Oct 2014 15:56:40 +0000 X-Env-Sender: Stefano.Stabellini@citrix.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1412265398!13519334!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25423 invoked from network); 2 Oct 2014 15:56:39 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 15:56:39 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="177535431" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 11:54:11 -0400 Received: from kaball.uk.xensource.com ([10.80.2.59]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZihm-0006ks-Vx; Thu, 02 Oct 2014 16:54:10 +0100 Date: Thu, 2 Oct 2014 16:52:03 +0100 From: Stefano Stabellini X-X-Sender: sstabellini@kaball.uk.xensource.com To: George Dunlap In-Reply-To: <542D71E9.5060505@eu.citrix.com> Message-ID: References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> <542D71E9.5060505@eu.citrix.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On Thu, 2 Oct 2014, George Dunlap wrote: > > > to control when and how and where urgent messages from outside the chip, > > > and > > > from other cores within the same chip, are delivered. > > > > > > Interrupt controllers occupy a rather awkward position in the > > > architecture. > > > They are fairly complicated to implement in hardware; which is why they > > > are > > > not yet implemented by Intel's VT hardware. (This may change in the > > > future.) > > > But they are far too performance critical for Xen to pass emulation off to > > > qemu, as it does with virtual disks or virtual networks. This means that > > QEMU > > Do I have to? :-) I think it looks much nicer as "qemu"... It's a few years now that they have started enforcing the name of the project as "QEMU" everywhere. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:59:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:59:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZimZ-0005NZ-Ok; Thu, 02 Oct 2014 15:59:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZimV-0005NJ-RC for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:59:06 +0000 Received: from [85.158.139.211:62507] by server-14.bemta-5.messagelabs.com id E1/4E-12422-7467D245; Thu, 02 Oct 2014 15:59:03 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1412265539!8784836!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 637 invoked from network); 2 Oct 2014 15:59:02 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 15:59:02 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="177536419" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 11:56:26 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZijy-0006n9-E2; Thu, 02 Oct 2014 16:56:26 +0100 Message-ID: <542D7584.5030204@eu.citrix.com> Date: Thu, 2 Oct 2014 16:55:48 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Stefano Stabellini References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> <542D71E9.5060505@eu.citrix.com> In-Reply-To: X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 10/02/2014 04:52 PM, Stefano Stabellini wrote: > On Thu, 2 Oct 2014, George Dunlap wrote: >>>> to control when and how and where urgent messages from outside the chip, >>>> and >>>> from other cores within the same chip, are delivered. >>>> >>>> Interrupt controllers occupy a rather awkward position in the >>>> architecture. >>>> They are fairly complicated to implement in hardware; which is why they >>>> are >>>> not yet implemented by Intel's VT hardware. (This may change in the >>>> future.) >>>> But they are far too performance critical for Xen to pass emulation off to >>>> qemu, as it does with virtual disks or virtual networks. This means that >>> QEMU >> Do I have to? :-) I think it looks much nicer as "qemu"... > It's a few years now that they have started enforcing the name of the > project as "QEMU" everywhere. *sigh* Very well... -G _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 15:59:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 15:59:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZimZ-0005NZ-Ok; Thu, 02 Oct 2014 15:59:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZimV-0005NJ-RC for publicity@lists.xenproject.org; Thu, 02 Oct 2014 15:59:06 +0000 Received: from [85.158.139.211:62507] by server-14.bemta-5.messagelabs.com id E1/4E-12422-7467D245; Thu, 02 Oct 2014 15:59:03 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1412265539!8784836!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 637 invoked from network); 2 Oct 2014 15:59:02 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 15:59:02 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="177536419" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 11:56:26 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZijy-0006n9-E2; Thu, 02 Oct 2014 16:56:26 +0100 Message-ID: <542D7584.5030204@eu.citrix.com> Date: Thu, 2 Oct 2014 16:55:48 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Stefano Stabellini References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> <542D71E9.5060505@eu.citrix.com> In-Reply-To: X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 10/02/2014 04:52 PM, Stefano Stabellini wrote: > On Thu, 2 Oct 2014, George Dunlap wrote: >>>> to control when and how and where urgent messages from outside the chip, >>>> and >>>> from other cores within the same chip, are delivered. >>>> >>>> Interrupt controllers occupy a rather awkward position in the >>>> architecture. >>>> They are fairly complicated to implement in hardware; which is why they >>>> are >>>> not yet implemented by Intel's VT hardware. (This may change in the >>>> future.) >>>> But they are far too performance critical for Xen to pass emulation off to >>>> qemu, as it does with virtual disks or virtual networks. This means that >>> QEMU >> Do I have to? :-) I think it looks much nicer as "qemu"... > It's a few years now that they have started enforcing the name of the > project as "QEMU" everywhere. *sigh* Very well... -G _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 16:01:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 16:01:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZioU-0005rP-Ug; Thu, 02 Oct 2014 16:01:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZioU-0005rJ-0M for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:01:06 +0000 Received: from [85.158.139.211:32930] by server-9.bemta-5.messagelabs.com id 0E/8C-20744-1C67D245; Thu, 02 Oct 2014 16:01:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1412265664!7555391!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28853 invoked from network); 2 Oct 2014 16:01:04 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2014 16:01:04 -0000 Received: from [192.168.15.34] (no-dns-yet.demon.co.uk [62.49.66.12]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id e5ec3bae; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 2 Oct 2014 17:02:41 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <542D65BE.8000604@eu.citrix.com> Date: Thu, 2 Oct 2014 17:00:59 +0100 Message-Id: <9F0C1689-5FFB-43A5-B111-9FA752AEAE1F@recoil.org> References: <542D65BE.8000604@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 15:48, George Dunlap wrote: > There has an unusual amount of media attention to XSA-108, whose embargo period ended Wednesday -- far more than any of the previous 107 vulnerabilities the Xen Project has reported. Great post -- it might be worth putting the 107 previous vulnerabilities in a causal context; e.g. "far more than any of the previous 107 vulnerabilities the Xen Project has reported over the previous decade." or else "107" seems like an awfully large number :-) -anil _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 16:01:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 16:01:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZioU-0005rP-Ug; Thu, 02 Oct 2014 16:01:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZioU-0005rJ-0M for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:01:06 +0000 Received: from [85.158.139.211:32930] by server-9.bemta-5.messagelabs.com id 0E/8C-20744-1C67D245; Thu, 02 Oct 2014 16:01:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1412265664!7555391!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28853 invoked from network); 2 Oct 2014 16:01:04 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2014 16:01:04 -0000 Received: from [192.168.15.34] (no-dns-yet.demon.co.uk [62.49.66.12]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id e5ec3bae; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 2 Oct 2014 17:02:41 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <542D65BE.8000604@eu.citrix.com> Date: Thu, 2 Oct 2014 17:00:59 +0100 Message-Id: <9F0C1689-5FFB-43A5-B111-9FA752AEAE1F@recoil.org> References: <542D65BE.8000604@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 15:48, George Dunlap wrote: > There has an unusual amount of media attention to XSA-108, whose embargo period ended Wednesday -- far more than any of the previous 107 vulnerabilities the Xen Project has reported. Great post -- it might be worth putting the 107 previous vulnerabilities in a causal context; e.g. "far more than any of the previous 107 vulnerabilities the Xen Project has reported over the previous decade." or else "107" seems like an awfully large number :-) -anil _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 16:17:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 16:17:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZj4g-0006Vn-63; Thu, 02 Oct 2014 16:17:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZj4f-0006Vi-A5 for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:17:49 +0000 Received: from [85.158.137.68:29600] by server-9.bemta-3.messagelabs.com id 86/FE-30790-CAA7D245; Thu, 02 Oct 2014 16:17:48 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1412266666!11175296!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23304 invoked from network); 2 Oct 2014 16:17:48 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 16:17:48 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="177546164" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 12:15:48 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZj2i-00074B-DB; Thu, 02 Oct 2014 17:15:48 +0100 Message-ID: <542D7A0E.2090605@eu.citrix.com> Date: Thu, 2 Oct 2014 17:15:10 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Anil Madhavapeddy References: <542D65BE.8000604@eu.citrix.com> <9F0C1689-5FFB-43A5-B111-9FA752AEAE1F@recoil.org> In-Reply-To: <9F0C1689-5FFB-43A5-B111-9FA752AEAE1F@recoil.org> X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 10/02/2014 05:00 PM, Anil Madhavapeddy wrote: > On 2 Oct 2014, at 15:48, George Dunlap wrote: > >> There has an unusual amount of media attention to XSA-108, whose embargo period ended Wednesday -- far more than any of the previous 107 vulnerabilities the Xen Project has reported. > Great post -- it might be worth putting the 107 previous vulnerabilities in a causal context; e.g. > > "far more than any of the previous 107 vulnerabilities the Xen Project has reported over the previous decade." > > or else "107" seems like an awfully large number :-) Well XSA-1 was in 2011, 3.5 years ago. :-) I agree, that number out of context could be misinterpreted; I'll see what I can do to reword that. -George _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 16:17:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 16:17:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZj4g-0006Vn-63; Thu, 02 Oct 2014 16:17:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZj4f-0006Vi-A5 for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:17:49 +0000 Received: from [85.158.137.68:29600] by server-9.bemta-3.messagelabs.com id 86/FE-30790-CAA7D245; Thu, 02 Oct 2014 16:17:48 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1412266666!11175296!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23304 invoked from network); 2 Oct 2014 16:17:48 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 16:17:48 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="177546164" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 12:15:48 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZj2i-00074B-DB; Thu, 02 Oct 2014 17:15:48 +0100 Message-ID: <542D7A0E.2090605@eu.citrix.com> Date: Thu, 2 Oct 2014 17:15:10 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Anil Madhavapeddy References: <542D65BE.8000604@eu.citrix.com> <9F0C1689-5FFB-43A5-B111-9FA752AEAE1F@recoil.org> In-Reply-To: <9F0C1689-5FFB-43A5-B111-9FA752AEAE1F@recoil.org> X-DLP: MIA1 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 10/02/2014 05:00 PM, Anil Madhavapeddy wrote: > On 2 Oct 2014, at 15:48, George Dunlap wrote: > >> There has an unusual amount of media attention to XSA-108, whose embargo period ended Wednesday -- far more than any of the previous 107 vulnerabilities the Xen Project has reported. > Great post -- it might be worth putting the 107 previous vulnerabilities in a causal context; e.g. > > "far more than any of the previous 107 vulnerabilities the Xen Project has reported over the previous decade." > > or else "107" seems like an awfully large number :-) Well XSA-1 was in 2011, 3.5 years ago. :-) I agree, that number out of context could be misinterpreted; I'll see what I can do to reword that. -George _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 16:27:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 16:27:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjDc-0006sN-L1; Thu, 02 Oct 2014 16:27:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjDa-0006s9-6C for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:27:02 +0000 Received: from [85.158.139.211:24487] by server-15.bemta-5.messagelabs.com id B4/4B-12002-5DC7D245; Thu, 02 Oct 2014 16:27:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1412267220!8316667!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12139 invoked from network); 2 Oct 2014 16:27:01 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2014 16:27:01 -0000 Received: from [192.168.15.34] (no-dns-yet.demon.co.uk [62.49.66.12]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 3e228bed; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 2 Oct 2014 17:28:38 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <20141002153835.GF32249@laptop.dumpdata.com> Date: Thu, 2 Oct 2014 17:26:56 +0100 Message-Id: <728470F7-3D4A-44F5-875A-50693228CC2A@recoil.org> References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> To: Konrad Rzeszutek Wilk X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 16:38, Konrad Rzeszutek Wilk wrote: > On Thu, Oct 02, 2014 at 03:48:30PM +0100, George Dunlap wrote: >> Hey all, >> >> Below is a more technical draft blog post in response to the recent media >> flurry about XSA-108. If you've updated your blog logins you can also >> preview the post here: https://blog.xenproject.org/?p=10093&preview=true >> >> Let me know if you have any feedback! > > You might want to add that Linux guests that run in HVM mode don't enable > x2APIC mode at all - as they end up using the PVHVM route which ends up > using events. > > This does affect 'true' HVM guests. This is pretty confusing -- I've seen quite a few people asking if the vulnerability affected PVH guests, which is distinct from Linux activating PV mode when running inside a HVM container, and also distinct from a Windows HVM guest without PV drivers. Perhaps throwing a bit more explanation in about the various HVM boot modes would help allay some of that confusion, or just explicitly having a table with common guest OSs, what modes they use, and if they're affected or not. Rackspace, for example, expose this terminology to their users by giving you the option of booting an Ubuntu PV or PVH guest as separate templates. I have no idea why they do that since I'm not aware of any application compatibility that's enabled by running in PVH mode -- it seems like a hosting decision rather than one that the user should care about. -anil _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 16:27:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 16:27:04 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjDc-0006sN-L1; Thu, 02 Oct 2014 16:27:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjDa-0006s9-6C for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:27:02 +0000 Received: from [85.158.139.211:24487] by server-15.bemta-5.messagelabs.com id B4/4B-12002-5DC7D245; Thu, 02 Oct 2014 16:27:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1412267220!8316667!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12139 invoked from network); 2 Oct 2014 16:27:01 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Oct 2014 16:27:01 -0000 Received: from [192.168.15.34] (no-dns-yet.demon.co.uk [62.49.66.12]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 3e228bed; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 2 Oct 2014 17:28:38 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <20141002153835.GF32249@laptop.dumpdata.com> Date: Thu, 2 Oct 2014 17:26:56 +0100 Message-Id: <728470F7-3D4A-44F5-875A-50693228CC2A@recoil.org> References: <542D65BE.8000604@eu.citrix.com> <20141002153835.GF32249@laptop.dumpdata.com> To: Konrad Rzeszutek Wilk X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 16:38, Konrad Rzeszutek Wilk wrote: > On Thu, Oct 02, 2014 at 03:48:30PM +0100, George Dunlap wrote: >> Hey all, >> >> Below is a more technical draft blog post in response to the recent media >> flurry about XSA-108. If you've updated your blog logins you can also >> preview the post here: https://blog.xenproject.org/?p=10093&preview=true >> >> Let me know if you have any feedback! > > You might want to add that Linux guests that run in HVM mode don't enable > x2APIC mode at all - as they end up using the PVHVM route which ends up > using events. > > This does affect 'true' HVM guests. This is pretty confusing -- I've seen quite a few people asking if the vulnerability affected PVH guests, which is distinct from Linux activating PV mode when running inside a HVM container, and also distinct from a Windows HVM guest without PV drivers. Perhaps throwing a bit more explanation in about the various HVM boot modes would help allay some of that confusion, or just explicitly having a table with common guest OSs, what modes they use, and if they're affected or not. Rackspace, for example, expose this terminology to their users by giving you the option of booting an Ubuntu PV or PVH guest as separate templates. I have no idea why they do that since I'm not aware of any application compatibility that's enabled by running in PVH mode -- it seems like a hosting decision rather than one that the user should care about. -anil _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:10:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:10:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjtM-0000ID-DC; Thu, 02 Oct 2014 17:10:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjtK-0000HE-RD for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:10:10 +0000 Received: from [85.158.137.68:57633] by server-17.bemta-3.messagelabs.com id 57/C5-01689-2F68D245; Thu, 02 Oct 2014 17:10:10 +0000 X-Env-Sender: Ian.Jackson@citrix.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1412269808!11181217!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27984 invoked from network); 2 Oct 2014 17:10:09 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:10:09 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="178635188" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 13:10:07 -0400 Received: from mariner.uk.xensource.com ([10.80.2.22]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZjtG-0007np-Lq; Thu, 02 Oct 2014 18:10:06 +0100 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.80) (envelope-from ) id 1XZjtG-0007ER-E1; Thu, 02 Oct 2014 18:10:06 +0100 From: Ian Jackson MIME-Version: 1.0 Message-ID: <21549.34542.272159.795058@mariner.uk.xensource.com> Date: Thu, 2 Oct 2014 18:10:06 +0100 To: George Dunlap In-Reply-To: <542D65BE.8000604@eu.citrix.com> References: <542D65BE.8000604@eu.citrix.com> X-Mailer: VM 8.1.0 under 23.4.1 (i486-pc-linux-gnu) X-DLP: MIA2 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org George Dunlap writes ("[Publicity] Draft technical blog post"): > Below is a more technical draft blog post in response to the recent > media flurry about XSA-108. If you've updated your blog logins you can > also preview the post here: > https://blog.xenproject.org/?p=10093&preview=true Thanks. I think this is an excellent blog post. Ian. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:10:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:10:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjtM-0000ID-DC; Thu, 02 Oct 2014 17:10:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZjtK-0000HE-RD for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:10:10 +0000 Received: from [85.158.137.68:57633] by server-17.bemta-3.messagelabs.com id 57/C5-01689-2F68D245; Thu, 02 Oct 2014 17:10:10 +0000 X-Env-Sender: Ian.Jackson@citrix.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1412269808!11181217!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27984 invoked from network); 2 Oct 2014 17:10:09 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:10:09 -0000 X-IronPort-AV: E=Sophos;i="5.04,639,1406592000"; d="scan'208";a="178635188" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 13:10:07 -0400 Received: from mariner.uk.xensource.com ([10.80.2.22]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZjtG-0007np-Lq; Thu, 02 Oct 2014 18:10:06 +0100 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.80) (envelope-from ) id 1XZjtG-0007ER-E1; Thu, 02 Oct 2014 18:10:06 +0100 From: Ian Jackson MIME-Version: 1.0 Message-ID: <21549.34542.272159.795058@mariner.uk.xensource.com> Date: Thu, 2 Oct 2014 18:10:06 +0100 To: George Dunlap In-Reply-To: <542D65BE.8000604@eu.citrix.com> References: <542D65BE.8000604@eu.citrix.com> X-Mailer: VM 8.1.0 under 23.4.1 (i486-pc-linux-gnu) X-DLP: MIA2 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org George Dunlap writes ("[Publicity] Draft technical blog post"): > Below is a more technical draft blog post in response to the recent > media flurry about XSA-108. If you've updated your blog logins you can > also preview the post here: > https://blog.xenproject.org/?p=10093&preview=true Thanks. I think this is an excellent blog post. Ian. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:34:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:34:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkGO-0000sF-MC; Thu, 02 Oct 2014 17:34:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkGN-0000sA-Dv for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:33:59 +0000 Received: from [85.158.139.211:48074] by server-6.bemta-5.messagelabs.com id DC/04-06284-68C8D245; Thu, 02 Oct 2014 17:33:58 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1412271236!4096194!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10311 invoked from network); 2 Oct 2014 17:33:58 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:33:58 -0000 X-IronPort-AV: E=Sophos;i="5.04,640,1406592000"; d="scan'208";a="177578815" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 13:33:54 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZkGH-00087P-W6; Thu, 02 Oct 2014 18:33:53 +0100 Message-ID: <542D8C5B.7020506@eu.citrix.com> Date: Thu, 2 Oct 2014 18:33:15 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , Andrew Halley References: <542D65BE.8000604@eu.citrix.com> In-Reply-To: <542D65BE.8000604@eu.citrix.com> X-DLP: MIA2 Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Thanks everyone for your comments (both here and on IRC). I've posted an updated draft, and included one inline below. In line with Lars' advice, I'm going to wait until tomorrow morning for more comments before pulling the trigger. Peace, -George XSA-108: Not the vulnerability you're looking for There has an unusual amount of media attention to XSA-108 during the embargo period (which ended Wednesday) -- far more than any of the previous security issues the Xen Project has reported. It began when a blogger complained that Amazon was telling customers it would be rebooting VMs in certain regions before a specific date. Other media outlets picked it up and noticed that the date happened to coincide with the release of XSA-108, and conjectured that the reboots had something to do with that. Soon others were conjecturing that, because of the major impact to customers of rebooting, that it must be something very big and important, similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon confirmed that the reboots had to do with XSA-108, but could say nothing else because of the security embargo. Unfortunately, because of the nature of embargoes, nobody with any actual knowledge of the vulnerability was allowed to say anything about it, and so the media was entirely free to speculate without any additional information to ground the discussion in reality. Now that the embargo has lifted, we can talk in detail about the vulnerability; and I'm afraid that people looking for another Shell Shock or Heartbleed are going to be disappointed. No catchy name for this one.

What is the vulnerability?

XSA-108 has to do with the emulation of a piece of hardware called an x2APIC. x2APIC is an interrupt controller: it allows the operating system to control when and how and where urgent messages from outside the chip, and from other cores within the same chip, are delivered. Interrupt controllers occupy a rather awkward position in the architecture. They are fairly complicated to implement in hardware; which is why they are not implemented in earlier generations of Intel hardware. (They have been implemented in hardware since the Ivy Bridge architecture came out in mid-2012.) But they are far too performance critical for Xen to pass emulation off to QEMU, as it does with virtual disks or virtual networks. This means that they must be emulated within Xen. The actual vulnerability, like most vulnerabilities, is pretty simple. Xen implements 256 x2APIC registers. These registers are stored in a buffer big enough to hold exactly 256 registers. However, the limit check for reading these registers was erroneosly set to 1024. What this means is that, without the fix, if you read x2APIC registers 0-255, you'll get the correct emulated value from the register buffer; but if you read x2APIC registers 256-1023, Xen will read memory from directly after the register buffer. If that memory is not mapped, Xen will crash; if it is mapped, it will copy it to the guest. So what this bug gives you is the ability to read (and only read) the 12k [1] of memory directly adjacent to where Xen is storing the first 256 registers (and no other area of memory). The fix simply corrects the limit check to 256. The emulated x2APIC functionality was introduced in Xen 4.1, so previous versions of Xen are not affected. Neither are PV guests, since Xen does not provide them with any emulated hardware. Unfortunately, the presence of VT support emulating the x2APIC, available on newer processors, doesn't mitigate the issue: it only implements the 64 registers actually used by real hardware at the moment, leaving Xen to emulate the rest of the registers. If you access registers above 64, it will trap to Xen, and Xen will emulate access to them, allowing you to trigger the bug.

The impact

If this seems like a relatively minor issue, that's because it is. The most likely scenario is that that 12k of memory contains other Xen data structures which contain no important information. There is, however, a chance that this memory might contain memory from another VM; and a chance that this memory might contain sensitive information, like passwords, encryption keys, or other private data. Nonetheless, this is a security issue, and the XenProject takes all potential security issues very seriously, no matter how minor. We have a mature process in place to notify cloud providers, distributions, and software providers so that they can have a fix in place before publicly disclosing any vulnerability. Applying security patches proactively, even though there's very low risk that anyone might have their secret data leaked because of it, is a conscientious and diligient thing to do. We're glad to see that so many cloud providers using Xen are demonstrating how seriously they take protecting customer data. But it is by no means a disaster. Those looking for a juicy vulnerability like Heartbleed and Shell Shock will be disappointed. [1] You may see this reported elsewhere as 3k; saying either 3k or 12k is simplifiying the truth in different ways. The MSR data is laid out as a 16-byte structure, of which only the first four bytes (one 32-bit word) can be read by this vulnerability. So the actual amount of data which is exposed is 3k, but it's spread out in 4-byte chunks across 12k of memory. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:34:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:34:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkGO-0000sF-MC; Thu, 02 Oct 2014 17:34:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkGN-0000sA-Dv for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:33:59 +0000 Received: from [85.158.139.211:48074] by server-6.bemta-5.messagelabs.com id DC/04-06284-68C8D245; Thu, 02 Oct 2014 17:33:58 +0000 X-Env-Sender: George.Dunlap@citrix.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1412271236!4096194!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10311 invoked from network); 2 Oct 2014 17:33:58 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:33:58 -0000 X-IronPort-AV: E=Sophos;i="5.04,640,1406592000"; d="scan'208";a="177578815" Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.3.181.6; Thu, 2 Oct 2014 13:33:54 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1XZkGH-00087P-W6; Thu, 02 Oct 2014 18:33:53 +0100 Message-ID: <542D8C5B.7020506@eu.citrix.com> Date: Thu, 2 Oct 2014 18:33:15 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: "publicity@lists.xenproject.org" , Andrew Halley References: <542D65BE.8000604@eu.citrix.com> In-Reply-To: <542D65BE.8000604@eu.citrix.com> X-DLP: MIA2 Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Thanks everyone for your comments (both here and on IRC). I've posted an updated draft, and included one inline below. In line with Lars' advice, I'm going to wait until tomorrow morning for more comments before pulling the trigger. Peace, -George XSA-108: Not the vulnerability you're looking for There has an unusual amount of media attention to XSA-108 during the embargo period (which ended Wednesday) -- far more than any of the previous security issues the Xen Project has reported. It began when a blogger complained that Amazon was telling customers it would be rebooting VMs in certain regions before a specific date. Other media outlets picked it up and noticed that the date happened to coincide with the release of XSA-108, and conjectured that the reboots had something to do with that. Soon others were conjecturing that, because of the major impact to customers of rebooting, that it must be something very big and important, similar to the recent Heartbleed and Shell Shock vulnerabilities. Amazon confirmed that the reboots had to do with XSA-108, but could say nothing else because of the security embargo. Unfortunately, because of the nature of embargoes, nobody with any actual knowledge of the vulnerability was allowed to say anything about it, and so the media was entirely free to speculate without any additional information to ground the discussion in reality. Now that the embargo has lifted, we can talk in detail about the vulnerability; and I'm afraid that people looking for another Shell Shock or Heartbleed are going to be disappointed. No catchy name for this one.

What is the vulnerability?

XSA-108 has to do with the emulation of a piece of hardware called an x2APIC. x2APIC is an interrupt controller: it allows the operating system to control when and how and where urgent messages from outside the chip, and from other cores within the same chip, are delivered. Interrupt controllers occupy a rather awkward position in the architecture. They are fairly complicated to implement in hardware; which is why they are not implemented in earlier generations of Intel hardware. (They have been implemented in hardware since the Ivy Bridge architecture came out in mid-2012.) But they are far too performance critical for Xen to pass emulation off to QEMU, as it does with virtual disks or virtual networks. This means that they must be emulated within Xen. The actual vulnerability, like most vulnerabilities, is pretty simple. Xen implements 256 x2APIC registers. These registers are stored in a buffer big enough to hold exactly 256 registers. However, the limit check for reading these registers was erroneosly set to 1024. What this means is that, without the fix, if you read x2APIC registers 0-255, you'll get the correct emulated value from the register buffer; but if you read x2APIC registers 256-1023, Xen will read memory from directly after the register buffer. If that memory is not mapped, Xen will crash; if it is mapped, it will copy it to the guest. So what this bug gives you is the ability to read (and only read) the 12k [1] of memory directly adjacent to where Xen is storing the first 256 registers (and no other area of memory). The fix simply corrects the limit check to 256. The emulated x2APIC functionality was introduced in Xen 4.1, so previous versions of Xen are not affected. Neither are PV guests, since Xen does not provide them with any emulated hardware. Unfortunately, the presence of VT support emulating the x2APIC, available on newer processors, doesn't mitigate the issue: it only implements the 64 registers actually used by real hardware at the moment, leaving Xen to emulate the rest of the registers. If you access registers above 64, it will trap to Xen, and Xen will emulate access to them, allowing you to trigger the bug.

The impact

If this seems like a relatively minor issue, that's because it is. The most likely scenario is that that 12k of memory contains other Xen data structures which contain no important information. There is, however, a chance that this memory might contain memory from another VM; and a chance that this memory might contain sensitive information, like passwords, encryption keys, or other private data. Nonetheless, this is a security issue, and the XenProject takes all potential security issues very seriously, no matter how minor. We have a mature process in place to notify cloud providers, distributions, and software providers so that they can have a fix in place before publicly disclosing any vulnerability. Applying security patches proactively, even though there's very low risk that anyone might have their secret data leaked because of it, is a conscientious and diligient thing to do. We're glad to see that so many cloud providers using Xen are demonstrating how seriously they take protecting customer data. But it is by no means a disaster. Those looking for a juicy vulnerability like Heartbleed and Shell Shock will be disappointed. [1] You may see this reported elsewhere as 3k; saying either 3k or 12k is simplifiying the truth in different ways. The MSR data is laid out as a 16-byte structure, of which only the first four bytes (one 32-bit word) can be read by this vulnerability. So the actual amount of data which is exposed is 3k, but it's spread out in 4-byte chunks across 12k of memory. _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:36:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:36:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkIl-0000tD-Tc; Thu, 02 Oct 2014 17:36:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkIl-0000t8-65 for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:36:27 +0000 Received: from [193.109.254.147:27341] by server-5.bemta-14.messagelabs.com id E8/FA-28255-A1D8D245; Thu, 02 Oct 2014 17:36:26 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1412271385!13058913!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5801 invoked from network); 2 Oct 2014 17:36:25 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:36:25 -0000 Received: by mail-wi0-f171.google.com with SMTP id em10so2199069wid.10 for ; Thu, 02 Oct 2014 10:36:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YUJeNpk7/g3+pAatFV3WKqikUkXFHG4YaDL2q3s1oaA=; b=s60LiFZnqpqptTtt3C3CookpvwgRMG7fEqw7MuKTyjVFMcmbtVL2kId3MQonSmTMuA 20ZzkzzWqwJZMZ/euJiqqSNvXZDp1DTckD+IQaiRF+DrPY0OEanXYyuyfp3SuXMDeoZy MCD2PFHBeUMgsxSv37JYt6076+l63/ilpCChMt3RHdJmKgt1C/oQ2O03ic/29du0tpO0 Q6AFgWpQ43DfZU1JmpyjfgCW1W3+vv2BvOOhtU9kLnQ10Yqpd4TUomqx05O4dOGA0igT Y24en3hOyLJW+yXLhQHWLNESmBMU1x4y8+vf/Urx8Sir9B2nRxtI5zBdkuN+0oCYOfpF 883w== X-Received: by 10.194.133.135 with SMTP id pc7mr492350wjb.54.1412271385520; Thu, 02 Oct 2014 10:36:25 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id t8sm1932544wib.8.2014.10.02.10.36.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 10:36:24 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <21549.34542.272159.795058@mariner.uk.xensource.com> Date: Thu, 2 Oct 2014 18:36:20 +0100 Message-Id: References: <542D65BE.8000604@eu.citrix.com> <21549.34542.272159.795058@mariner.uk.xensource.com> To: Ian Jackson X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 18:10, Ian Jackson wrote: > George Dunlap writes ("[Publicity] Draft technical blog post"): >> Below is a more technical draft blog post in response to the recent = >> media flurry about XSA-108. If you've updated your blog logins you can = >> also preview the post here: = >> https://blog.xenproject.org/?p=3D10093&preview=3Dtrue > = > Thanks. I think this is an excellent blog post. > = > Ian. I think this is an excellent post also. In one place you use =93XenProject= =94 instead of =93Xen Project=94. That=92s all I noticed Regards Lars _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:36:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:36:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkIl-0000tD-Tc; Thu, 02 Oct 2014 17:36:27 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkIl-0000t8-65 for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:36:27 +0000 Received: from [193.109.254.147:27341] by server-5.bemta-14.messagelabs.com id E8/FA-28255-A1D8D245; Thu, 02 Oct 2014 17:36:26 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1412271385!13058913!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5801 invoked from network); 2 Oct 2014 17:36:25 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:36:25 -0000 Received: by mail-wi0-f171.google.com with SMTP id em10so2199069wid.10 for ; Thu, 02 Oct 2014 10:36:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YUJeNpk7/g3+pAatFV3WKqikUkXFHG4YaDL2q3s1oaA=; b=s60LiFZnqpqptTtt3C3CookpvwgRMG7fEqw7MuKTyjVFMcmbtVL2kId3MQonSmTMuA 20ZzkzzWqwJZMZ/euJiqqSNvXZDp1DTckD+IQaiRF+DrPY0OEanXYyuyfp3SuXMDeoZy MCD2PFHBeUMgsxSv37JYt6076+l63/ilpCChMt3RHdJmKgt1C/oQ2O03ic/29du0tpO0 Q6AFgWpQ43DfZU1JmpyjfgCW1W3+vv2BvOOhtU9kLnQ10Yqpd4TUomqx05O4dOGA0igT Y24en3hOyLJW+yXLhQHWLNESmBMU1x4y8+vf/Urx8Sir9B2nRxtI5zBdkuN+0oCYOfpF 883w== X-Received: by 10.194.133.135 with SMTP id pc7mr492350wjb.54.1412271385520; Thu, 02 Oct 2014 10:36:25 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id t8sm1932544wib.8.2014.10.02.10.36.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 10:36:24 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <21549.34542.272159.795058@mariner.uk.xensource.com> Date: Thu, 2 Oct 2014 18:36:20 +0100 Message-Id: References: <542D65BE.8000604@eu.citrix.com> <21549.34542.272159.795058@mariner.uk.xensource.com> To: Ian Jackson X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 18:10, Ian Jackson wrote: > George Dunlap writes ("[Publicity] Draft technical blog post"): >> Below is a more technical draft blog post in response to the recent = >> media flurry about XSA-108. If you've updated your blog logins you can = >> also preview the post here: = >> https://blog.xenproject.org/?p=3D10093&preview=3Dtrue > = > Thanks. I think this is an excellent blog post. > = > Ian. I think this is an excellent post also. In one place you use =93XenProject= =94 instead of =93Xen Project=94. That=92s all I noticed Regards Lars _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:38:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:38:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkKV-0000uC-4B; Thu, 02 Oct 2014 17:38:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkKT-0000u7-TZ for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:38:14 +0000 Received: from [85.158.137.68:16303] by server-15.bemta-3.messagelabs.com id 19/07-01573-58D8D245; Thu, 02 Oct 2014 17:38:13 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1412271492!11167840!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28876 invoked from network); 2 Oct 2014 17:38:12 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:38:12 -0000 Received: by mail-wg0-f52.google.com with SMTP id a1so3717799wgh.35 for ; Thu, 02 Oct 2014 10:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=InnxZeVJBqbQN1EzOFox5cFhIybU4rLgYqefYN0L24M=; b=R87ATyGlDvFOnBW+ejfz7rzLlwrumJqcGGqVNik2lEZjTVI2unIoeGbK8hTzy0IwVi LnZV9Giy4InuQv6z4SbNL0Eqzz2hg+RjH1e/BekvfD/OPOSiUqVEiX8nNYBib2j6STGe 9S/o3VNhCO4ihuEMm5tOpUFV9MRV8UjVmgSmuRppjOfGRI8WNRnGuj1j7CzVFCZ4UKuZ Tgpvp2aFO+LiJDNyeTfQ49HFlqq0nsrYz6givYp3jsaJFqqDpEq7kTU4/elRnM3hpan0 fIyWM67gt0hwR5xbo8KrMdJpnc0WGBsf1d9lHDXP69u9O/+8bwbt2TgusxlwVCF3I01G INug== X-Received: by 10.180.39.44 with SMTP id m12mr6052154wik.25.1412271492240; Thu, 02 Oct 2014 10:38:12 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id x6sm1974110wif.0.2014.10.02.10.38.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 10:38:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <542D8C5B.7020506@eu.citrix.com> Date: Thu, 2 Oct 2014 18:38:09 +0100 Message-Id: <9B6D7BBE-123D-4E21-8AFE-96A214AF0F50@gmail.com> References: <542D65BE.8000604@eu.citrix.com> <542D8C5B.7020506@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 18:33, George Dunlap wrote: > Thanks everyone for your comments (both here and on IRC). > > I've posted an updated draft, and included one inline below. In line with Lars' advice, I'm going to wait until tomorrow morning for more comments before pulling the trigger. The reason for the advice is timing : posts made from 9-12 UK time are more likely to be read Lars _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:38:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:38:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkKV-0000uC-4B; Thu, 02 Oct 2014 17:38:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkKT-0000u7-TZ for publicity@lists.xenproject.org; Thu, 02 Oct 2014 17:38:14 +0000 Received: from [85.158.137.68:16303] by server-15.bemta-3.messagelabs.com id 19/07-01573-58D8D245; Thu, 02 Oct 2014 17:38:13 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1412271492!11167840!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28876 invoked from network); 2 Oct 2014 17:38:12 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 17:38:12 -0000 Received: by mail-wg0-f52.google.com with SMTP id a1so3717799wgh.35 for ; Thu, 02 Oct 2014 10:38:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=InnxZeVJBqbQN1EzOFox5cFhIybU4rLgYqefYN0L24M=; b=R87ATyGlDvFOnBW+ejfz7rzLlwrumJqcGGqVNik2lEZjTVI2unIoeGbK8hTzy0IwVi LnZV9Giy4InuQv6z4SbNL0Eqzz2hg+RjH1e/BekvfD/OPOSiUqVEiX8nNYBib2j6STGe 9S/o3VNhCO4ihuEMm5tOpUFV9MRV8UjVmgSmuRppjOfGRI8WNRnGuj1j7CzVFCZ4UKuZ Tgpvp2aFO+LiJDNyeTfQ49HFlqq0nsrYz6givYp3jsaJFqqDpEq7kTU4/elRnM3hpan0 fIyWM67gt0hwR5xbo8KrMdJpnc0WGBsf1d9lHDXP69u9O/+8bwbt2TgusxlwVCF3I01G INug== X-Received: by 10.180.39.44 with SMTP id m12mr6052154wik.25.1412271492240; Thu, 02 Oct 2014 10:38:12 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id x6sm1974110wif.0.2014.10.02.10.38.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 10:38:11 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <542D8C5B.7020506@eu.citrix.com> Date: Thu, 2 Oct 2014 18:38:09 +0100 Message-Id: <9B6D7BBE-123D-4E21-8AFE-96A214AF0F50@gmail.com> References: <542D65BE.8000604@eu.citrix.com> <542D8C5B.7020506@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org On 2 Oct 2014, at 18:33, George Dunlap wrote: > Thanks everyone for your comments (both here and on IRC). > > I've posted an updated draft, and included one inline below. In line with Lars' advice, I'm going to wait until tomorrow morning for more comments before pulling the trigger. The reason for the advice is timing : posts made from 9-12 UK time are more likely to be read Lars _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:40:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:40:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkMs-00012u-BE; Thu, 02 Oct 2014 17:40:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XYcUk-0008HE-Fj for publicity@lists.xenproject.org; Mon, 29 Sep 2014 15:04:10 +0000 Received: from [85.158.139.211:43699] by server-5.bemta-5.messagelabs.com id E7/0F-11546-9E479245; Mon, 29 Sep 2014 15:04:09 +0000 X-Env-Sender: tjones@techtarget.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1412003047!8032756!1 X-Originating-IP: [12.191.12.14] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4066 invoked from network); 29 Sep 2014 15:04:08 -0000 Received: from mailfilter-n.techtarget.com (HELO mailfilter-n.techtarget.com) (12.191.12.14) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Sep 2014 15:04:08 -0000 Received: from pps.filterd (mailfilter-n.techtarget.com [127.0.0.1]) by mailfilter-n.techtarget.com (8.14.5/8.14.5) with SMTP id s8TF3UZ5009313 for ; Mon, 29 Sep 2014 08:04:07 -0700 Received: from mailma11.office.techtarget.com ([10.68.1.9]) by mailfilter-n.techtarget.com with ESMTP id 1pppdgvdcf-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Sep 2014 08:04:07 -0700 Received: from MAILMA13.office.techtarget.com (10.68.1.13) by Mailma11.office.techtarget.com (10.68.1.9) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 29 Sep 2014 11:04:02 -0400 Received: from MAILMA13.office.techtarget.com ([fe80::e05b:1ec8:6cb3:32cb]) by Mailma13.office.techtarget.com ([fe80::e05b:1ec8:6cb3:32cb%17]) with mapi id 15.00.0847.030; Mon, 29 Sep 2014 11:04:06 -0400 From: "Jones, Trevor" To: "publicity@lists.xenproject.org" Thread-Topic: cloud reboot Thread-Index: Ac/b9biQGsRRt8DgSiq/M33EVFa72g== Date: Mon, 29 Sep 2014 15:04:06 +0000 Message-ID: <20bc1d91762d4918a71a44e57c177e66@Mailma13.office.techtarget.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.68.1.20] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-09-29_03:2014-09-29, 2014-09-29, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409290143 X-Mailman-Approved-At: Thu, 02 Oct 2014 17:40:41 +0000 Subject: [Publicity] cloud reboot X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0880451360727156337==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============0880451360727156337== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_" --_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm a reporter working on a story about Rackspace and AWS and the reboots d= ue to issues with Xen hypervisors. Is there someone I could speak with on y= our end that could help explain what the issue is? My deadline is 5 p.m. ET today. Best, Trevor Trevor Jones News Writer Data Center and Virtualization Media Group Office: 617-431-9816 Mobile: 518-852-2295 Twitter: @tjonesTT AIM: tjones@techtarget.com TechTarget 275 Grove Street Newton, MA 02466 --_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m a reporter working on a story about Racksp= ace and AWS and the reboots due to issues with Xen hypervisors. Is there so= meone I could speak with on your end that could help explain what the issue= is?

 

My deadline is 5 p.m. ET today.

 

Best,

Trevor

 

Trevor Jones

News Writer

Data Center and Virtualization Media = Group

 

Office: 617-431-9816

Mobile: 518-852-2295

Twitter: @tjonesTT<= /p>

AIM: tjones@techtarget.com=

 

TechTarget

275 Grove Street

Newton, MA 02466

 

--_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_-- --===============0880451360727156337== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============0880451360727156337==-- From publicity-bounces@lists.xenproject.org Thu Oct 02 17:40:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:40:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkMs-00012y-Ck; Thu, 02 Oct 2014 17:40:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZj8K-0006ks-7U for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:21:36 +0000 Received: from [193.109.254.147:53243] by server-9.bemta-14.messagelabs.com id D5/88-31535-F8B7D245; Thu, 02 Oct 2014 16:21:35 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1412266894!12939315!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1206 invoked from network); 2 Oct 2014 16:21:34 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 16:21:34 -0000 Received: by mail-wg0-f43.google.com with SMTP id m15so799900wgh.2 for ; Thu, 02 Oct 2014 09:21:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zV7LLJiJk18zCHO3cUve5KJhzIhMA7borze640dLuBY=; b=KfmkzDW9mpZBd5u3MB34hKhT4whueAy5KKA176/CB2BQcqOCelpNxEG6R/TAg2UBSx mUb92/2TMyyc45DarS/Cz3qL9WwX0DU2aXGXcVr+WSiL7MYafOxUwNWQsUGpboD6bNzx oAYbqxfOh9C7OMCONDYxQLRCpftAjYdPMhHfGwTzH+eF6RqYBL+OMAGy/eF2LyLktic3 nAK4NUad9qadLTtroT9LlT5PqZePyMYm88UZuv7qFUXqv+vh3+bJOKBCiRD6mocIAnv+ qWXNF/bh3OJI/Cp4AssDqehLacdSGhFsCjT9CnM4kLYr/1TcfzNVyxspU3AeR4sxyNWc Qsbg== MIME-Version: 1.0 X-Received: by 10.194.80.71 with SMTP id p7mr74134176wjx.35.1412266893979; Thu, 02 Oct 2014 09:21:33 -0700 (PDT) Received: by 10.216.52.6 with HTTP; Thu, 2 Oct 2014 09:21:33 -0700 (PDT) In-Reply-To: <542D65BE.8000604@eu.citrix.com> References: <542D65BE.8000604@eu.citrix.com> Date: Thu, 2 Oct 2014 17:21:33 +0100 X-Google-Sender-Auth: 5QjwD2CpZNtE2Cyn4G2prQTq7o4 Message-ID: From: Richard Mortier To: George Dunlap X-Mailman-Approved-At: Thu, 02 Oct 2014 17:40:41 +0000 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org one minor comment... On 2 October 2014 15:48, George Dunlap wrote: >... > What this means is that, without the fix, if you read x2apic registers > 0-255, you'll get the correct emulated value from the register buffer; but > if you read x2apic registers 256-1023, Xen will copy hypervisor memory from > directly afterwards into the guest. "directly afterwards" reads oddly -- could bind as memory directly after register 1023 in that sentence i think. "...memory directly following x2APIC register 255" or something? -- Richard Mortier mort@cantab.net _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:40:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:40:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkMs-00012y-Ck; Thu, 02 Oct 2014 17:40:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZj8K-0006ks-7U for publicity@lists.xenproject.org; Thu, 02 Oct 2014 16:21:36 +0000 Received: from [193.109.254.147:53243] by server-9.bemta-14.messagelabs.com id D5/88-31535-F8B7D245; Thu, 02 Oct 2014 16:21:35 +0000 X-Env-Sender: richard.mortier@gmail.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1412266894!12939315!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1206 invoked from network); 2 Oct 2014 16:21:34 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 16:21:34 -0000 Received: by mail-wg0-f43.google.com with SMTP id m15so799900wgh.2 for ; Thu, 02 Oct 2014 09:21:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=zV7LLJiJk18zCHO3cUve5KJhzIhMA7borze640dLuBY=; b=KfmkzDW9mpZBd5u3MB34hKhT4whueAy5KKA176/CB2BQcqOCelpNxEG6R/TAg2UBSx mUb92/2TMyyc45DarS/Cz3qL9WwX0DU2aXGXcVr+WSiL7MYafOxUwNWQsUGpboD6bNzx oAYbqxfOh9C7OMCONDYxQLRCpftAjYdPMhHfGwTzH+eF6RqYBL+OMAGy/eF2LyLktic3 nAK4NUad9qadLTtroT9LlT5PqZePyMYm88UZuv7qFUXqv+vh3+bJOKBCiRD6mocIAnv+ qWXNF/bh3OJI/Cp4AssDqehLacdSGhFsCjT9CnM4kLYr/1TcfzNVyxspU3AeR4sxyNWc Qsbg== MIME-Version: 1.0 X-Received: by 10.194.80.71 with SMTP id p7mr74134176wjx.35.1412266893979; Thu, 02 Oct 2014 09:21:33 -0700 (PDT) Received: by 10.216.52.6 with HTTP; Thu, 2 Oct 2014 09:21:33 -0700 (PDT) In-Reply-To: <542D65BE.8000604@eu.citrix.com> References: <542D65BE.8000604@eu.citrix.com> Date: Thu, 2 Oct 2014 17:21:33 +0100 X-Google-Sender-Auth: 5QjwD2CpZNtE2Cyn4G2prQTq7o4 Message-ID: From: Richard Mortier To: George Dunlap X-Mailman-Approved-At: Thu, 02 Oct 2014 17:40:41 +0000 Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org one minor comment... On 2 October 2014 15:48, George Dunlap wrote: >... > What this means is that, without the fix, if you read x2apic registers > 0-255, you'll get the correct emulated value from the register buffer; but > if you read x2apic registers 256-1023, Xen will copy hypervisor memory from > directly afterwards into the guest. "directly afterwards" reads oddly -- could bind as memory directly after register 1023 in that sentence i think. "...memory directly following x2APIC register 255" or something? -- Richard Mortier mort@cantab.net _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 02 17:40:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 17:40:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkMs-00012u-BE; Thu, 02 Oct 2014 17:40:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XYcUk-0008HE-Fj for publicity@lists.xenproject.org; Mon, 29 Sep 2014 15:04:10 +0000 Received: from [85.158.139.211:43699] by server-5.bemta-5.messagelabs.com id E7/0F-11546-9E479245; Mon, 29 Sep 2014 15:04:09 +0000 X-Env-Sender: tjones@techtarget.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1412003047!8032756!1 X-Originating-IP: [12.191.12.14] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4066 invoked from network); 29 Sep 2014 15:04:08 -0000 Received: from mailfilter-n.techtarget.com (HELO mailfilter-n.techtarget.com) (12.191.12.14) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Sep 2014 15:04:08 -0000 Received: from pps.filterd (mailfilter-n.techtarget.com [127.0.0.1]) by mailfilter-n.techtarget.com (8.14.5/8.14.5) with SMTP id s8TF3UZ5009313 for ; Mon, 29 Sep 2014 08:04:07 -0700 Received: from mailma11.office.techtarget.com ([10.68.1.9]) by mailfilter-n.techtarget.com with ESMTP id 1pppdgvdcf-1 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Mon, 29 Sep 2014 08:04:07 -0700 Received: from MAILMA13.office.techtarget.com (10.68.1.13) by Mailma11.office.techtarget.com (10.68.1.9) with Microsoft SMTP Server (TLS) id 15.0.847.32; Mon, 29 Sep 2014 11:04:02 -0400 Received: from MAILMA13.office.techtarget.com ([fe80::e05b:1ec8:6cb3:32cb]) by Mailma13.office.techtarget.com ([fe80::e05b:1ec8:6cb3:32cb%17]) with mapi id 15.00.0847.030; Mon, 29 Sep 2014 11:04:06 -0400 From: "Jones, Trevor" To: "publicity@lists.xenproject.org" Thread-Topic: cloud reboot Thread-Index: Ac/b9biQGsRRt8DgSiq/M33EVFa72g== Date: Mon, 29 Sep 2014 15:04:06 +0000 Message-ID: <20bc1d91762d4918a71a44e57c177e66@Mailma13.office.techtarget.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.68.1.20] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.28, 0.0.0000 definitions=2014-09-29_03:2014-09-29, 2014-09-29, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1409290143 X-Mailman-Approved-At: Thu, 02 Oct 2014 17:40:41 +0000 Subject: [Publicity] cloud reboot X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0880451360727156337==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============0880451360727156337== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_" --_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I'm a reporter working on a story about Rackspace and AWS and the reboots d= ue to issues with Xen hypervisors. Is there someone I could speak with on y= our end that could help explain what the issue is? My deadline is 5 p.m. ET today. Best, Trevor Trevor Jones News Writer Data Center and Virtualization Media Group Office: 617-431-9816 Mobile: 518-852-2295 Twitter: @tjonesTT AIM: tjones@techtarget.com TechTarget 275 Grove Street Newton, MA 02466 --_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m a reporter working on a story about Racksp= ace and AWS and the reboots due to issues with Xen hypervisors. Is there so= meone I could speak with on your end that could help explain what the issue= is?

 

My deadline is 5 p.m. ET today.

 

Best,

Trevor

 

Trevor Jones

News Writer

Data Center and Virtualization Media = Group

 

Office: 617-431-9816

Mobile: 518-852-2295

Twitter: @tjonesTT<= /p>

AIM: tjones@techtarget.com=

 

TechTarget

275 Grove Street

Newton, MA 02466

 

--_000_20bc1d91762d4918a71a44e57c177e66Mailma13officetechtarge_-- --===============0880451360727156337== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============0880451360727156337==-- From publicity-bounces@lists.xenproject.org Thu Oct 02 18:12:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 18:12:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkrR-000216-1s; Thu, 02 Oct 2014 18:12:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkrQ-000211-Jx for publicity@lists.xenproject.org; Thu, 02 Oct 2014 18:12:16 +0000 Received: from [85.158.143.35:62137] by server-3.bemta-4.messagelabs.com id C0/56-06192-F759D245; Thu, 02 Oct 2014 18:12:15 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1412273533!13450681!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_10_20,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6019 invoked from network); 2 Oct 2014 18:12:13 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 18:12:13 -0000 Received: by mail-wg0-f52.google.com with SMTP id a1so3904223wgh.11 for ; Thu, 02 Oct 2014 11:12:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=HTuvR3myBN+/YH8yezhP9+Cvc2c/lqV2+QX2xVxgEQY=; b=cyfUxQz+qj8TUKZ67ewzoDyARwystl2SKeHOtBP5+ap8C6q1oGrOc+sH5Mk9+UKMzf W/AbiY+WA/IJ39tP5zJCAuiDrrnSbCs7P/FNKWUYa7+rtn8MlBsn57SGDAIyxLtKZBUl +sG3Z5Xvo6q/apfvtWAEplUfITRFHaYKQkUnRcxZQXKzDw2cNDvZelyREIJrxzKV9Glu eOa4Hpp8E8FKKeYJpxVv5GFIxqSW1b3e4PLoYpQhNPYF5tAKKTwhSFJ/n7RIgaH1zCoP ZWfCYYt2eMlErLl6p0aSE4mvQoMH1jBqvFIRs647Vm50oS4wrYjxbuqKQL+BmClgiOwm j7jw== X-Received: by 10.194.94.165 with SMTP id dd5mr473788wjb.75.1412273533061; Thu, 02 Oct 2014 11:12:13 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id v9sm5381034wjy.14.2014.10.02.11.12.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 11:12:12 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <542D8C5B.7020506@eu.citrix.com> Date: Thu, 2 Oct 2014 19:12:09 +0100 Message-Id: <76A058F8-FFD8-45FE-8155-3162EFF77C6B@gmail.com> References: <542D65BE.8000604@eu.citrix.com> <542D8C5B.7020506@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4693258012744114000==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============4693258012744114000== Content-Type: multipart/alternative; boundary="Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36" --Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii George, just came across = http://labs.bromium.com/2014/10/01/musings-on-the-recent-xen-security-advi= sories/ - not sure whether relevant Lars On 2 Oct 2014, at 18:33, George Dunlap = wrote: > Thanks everyone for your comments (both here and on IRC). >=20 > I've posted an updated draft, and included one inline below. In line = with Lars' advice, I'm going to wait until tomorrow morning for more = comments before pulling the trigger. >=20 > Peace, > -George >=20 >=20 > XSA-108: Not the vulnerability you're looking for >=20 > There has an unusual amount of media attention to XSA-108 during the = embargo period (which ended Wednesday) -- far more than any of the = previous security issues the Xen Project has reported. It began when a = blogger complained that Amazon was telling customers it would be = rebooting VMs in certain regions before a specific date. Other media = outlets picked it up and noticed that the date happened to coincide with = the release of XSA-108, and conjectured that the reboots had something = to do with that. Soon others were conjecturing that, because of the = major impact to customers of rebooting, that it must be something very = big and important, similar to the recent Heartbleed and Shell Shock = vulnerabilities. Amazon confirmed that the reboots had to do with = XSA-108, but could say nothing else because of the security embargo. >=20 > Unfortunately, because of the nature of embargoes, nobody with any = actual knowledge of the vulnerability was allowed to say anything about = it, and so the media was entirely free to speculate without any = additional information to ground the discussion in reality. >=20 > Now that the embargo has lifted, we can talk in detail about the = vulnerability; and I'm afraid that people looking for another Shell = Shock or Heartbleed are going to be disappointed. No catchy name for = this one. >=20 > >=20 >

What is the vulnerability?

>=20 > XSA-108 has to do with the emulation of a piece of hardware called an = x2APIC. x2APIC is an = interrupt controller: it allows the operating system to control when and = how and where urgent messages from outside the chip, and from other = cores within the same chip, are delivered. >=20 > Interrupt controllers occupy a rather awkward position in the = architecture. They are fairly complicated to implement in hardware; = which is why they are not implemented in earlier generations of Intel = hardware. (They have been implemented in hardware since the Ivy = Bridge architecture came out in mid-2012.) But they are far too = performance critical for Xen to pass emulation off to QEMU, as it does = with virtual disks or virtual networks. This means that they must be = emulated within Xen. >=20 > The actual vulnerability, like most vulnerabilities, is pretty simple. = Xen implements 256 x2APIC registers. These registers are stored in a = buffer big enough to hold exactly 256 registers. However, the limit = check for reading these registers was erroneosly set to 1024. >=20 > What this means is that, without the fix, if you read x2APIC registers = 0-255, you'll get the correct emulated value from the register buffer; = but if you read x2APIC registers 256-1023, Xen will read memory from = directly after the register buffer. If that memory is not mapped, Xen = will crash; if it is mapped, it will copy it to the guest. >=20 > So what this bug gives you is the ability to read (and only read) the = 12k [1] of memory directly adjacent to where Xen is storing the first = 256 registers (and no other area of memory). >=20 > The fix simply corrects the limit check to 256. >=20 > The emulated x2APIC functionality was introduced in Xen 4.1, so = previous versions of Xen are not affected. Neither are PV guests, since = Xen does not provide them with any emulated hardware. >=20 > Unfortunately, the presence of VT support emulating the x2APIC, = available on newer processors, doesn't mitigate the issue: it only = implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers. If you access = registers above 64, it will trap to Xen, and Xen will emulate access to = them, allowing you to trigger the bug. >=20 >

The impact

>=20 > If this seems like a relatively minor issue, that's because it is. The = most likely scenario is that that 12k of memory contains other Xen data = structures which contain no important information. There is, however, a = chance that this memory might contain memory from another VM; and = a chance that this memory might contain sensitive information, = like passwords, encryption keys, or other private data. >=20 > Nonetheless, this is a security issue, and the XenProject takes = all potential security issues very seriously, no matter how minor. We = have a mature process in = place to notify cloud providers, distributions, and software providers = so that they can have a fix in place before publicly disclosing any = vulnerability. >=20 > Applying security patches proactively, even though there's very low = risk that anyone might have their secret data leaked because of it, is a = conscientious and diligient thing to do. We're glad to see that so many = cloud providers using Xen are demonstrating how seriously they take = protecting customer data. >=20 > But it is by no means a disaster. Those looking for a juicy = vulnerability like Heartbleed and Shell Shock will be disappointed. >=20 >=20 > [1] You may see this reported elsewhere as 3k; saying either 3k or 12k = is simplifiying the truth in different ways. The MSR data is laid out = as a 16-byte structure, of which only the first four bytes (one 32-bit = word) can be read by this vulnerability. So the actual amount of data = which is exposed is 3k, but it's spread out in 4-byte chunks across 12k = of memory. >=20 >=20 > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii George, just came across http://labs.bromium.com/2014/10/01/musings-on-the-recent-= xen-security-advisories/ - not sure whether = relevant
Lars

On 2 Oct 2014, at 18:33, George = Dunlap <george.dunlap@eu.citrix.com> wrote:

Thanks everyone for your comments (both here and on = IRC).

I've posted an updated draft, and included one inline = below.  In line with Lars' advice, I'm going to wait until tomorrow = morning for more comments before pulling the trigger.

Peace,
= -George


XSA-108: Not the vulnerability you're looking = for

There has an unusual amount of media attention to XSA-108 = during the embargo period (which ended Wednesday) -- far more than any = of the previous security issues the Xen Project has reported.  It = began when a blogger complained that Amazon was telling customers it = would be rebooting VMs in certain regions before a specific date. =  Other media outlets picked it up and noticed that the date = happened to coincide with the release of XSA-108, and conjectured that = the reboots had something to do with that.  Soon others were = conjecturing that, because of the major impact to customers of = rebooting, that it must be something very big and important, similar to = the recent Heartbleed and Shell Shock vulnerabilities.  Amazon = confirmed that the reboots had to do with XSA-108, but could say nothing = else because of the security embargo.

Unfortunately, because of = the nature of embargoes, nobody with any actual knowledge of the = vulnerability was allowed to say anything about it, and so the media was = entirely free to speculate without any additional information to ground = the discussion in reality.

Now that the embargo has lifted, we = can talk in detail about the vulnerability; and I'm afraid that people = looking for another Shell Shock or Heartbleed are going to be = disappointed.  No catchy name for this = one.

<!--more-->

<h1>What is the = vulnerability?</h1>

XSA-108 has to do with the emulation of = a piece of hardware called an <a href=3Dhttp://www.intel.com/content/w= ww/us/en/architecture-and-technology/64-architecture-x2apic-specification.= html>x2APIC</a>. x2APIC is an interrupt controller: it = allows the operating system to control when and how and where urgent = messages from outside the chip, and from other cores within the same = chip, are delivered.

Interrupt controllers occupy a rather = awkward position in the architecture.  They are fairly complicated = to implement in hardware; which is why they are not implemented in = earlier generations of Intel hardware.  (They have been implemented = in hardware since the <a h= ttp://en.wikipedia.org/wiki/Ivy_Bridge_%28microarchitecture%29>Ivy = Bridge</a> architecture came out in mid-2012.)  But they are = far too performance critical for Xen to pass emulation off to QEMU, as = it does with virtual disks or virtual networks.  This means that = they must be emulated within Xen.

The actual vulnerability, like = most vulnerabilities, is pretty simple.  Xen implements 256 x2APIC = registers.  These registers are stored in a buffer big enough to = hold exactly 256 registers. However, the limit check for reading these = registers was erroneosly set to 1024.

What this means is that, = without the fix, if you read x2APIC registers 0-255, you'll get the = correct emulated value from the register buffer; but if you read x2APIC = registers 256-1023, Xen will read memory from directly after the = register buffer.  If that memory is not mapped, Xen will crash; if = it is mapped, it will copy it to the guest.

So what this bug = gives you is the ability to read (and only read) the 12k [1] of memory = directly adjacent to where Xen is storing the first 256 registers (and = no other area of memory).

The fix simply corrects the limit check = to 256.

The emulated x2APIC functionality was introduced in Xen = 4.1, so previous versions of Xen are not affected.  Neither are PV = guests, since Xen does not provide them with any emulated = hardware.

Unfortunately, the presence of VT support emulating the = x2APIC, available on newer processors, doesn't mitigate the issue: it = only implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers.  If you = access registers above 64, it will trap to Xen, and Xen will emulate = access to them, allowing you to trigger the bug.

<h1>The = impact</h1>

If this seems like a relatively minor issue, = that's because it is. The most likely scenario is that that 12k of = memory contains other Xen data structures which contain no important = information.  There is, however, a <i>chance</i> that = this memory might contain memory from another VM; and a = <i>chance</i> that this memory might contain sensitive = information, like passwords, encryption keys, or other private = data.

Nonetheless, this <i>is</i> a security issue, = and the XenProject takes all potential security issues very seriously, = no matter how minor.  We have a mature <a href=3Dhttp://www.xenproj= ect.org/security-policy.html>process</a> in place to notify = cloud providers, distributions, and software providers so that they can = have a fix in place before publicly disclosing any = vulnerability.

Applying security patches proactively, even though = there's very low risk that anyone might have their secret data leaked = because of it, is a conscientious and diligient thing to do.  We're = glad to see that so many cloud providers using Xen are demonstrating how = seriously they take protecting customer data.

But it is by no = means a disaster.  Those looking for a juicy vulnerability like = Heartbleed and Shell Shock will be disappointed.


[1] You may = see this reported elsewhere as 3k; saying either 3k or 12k is = simplifiying the truth in different ways.  The MSR data is laid out = as a 16-byte structure, of which only the first four bytes (one 32-bit = word) can be read by this vulnerability.  So the actual amount of = data which is exposed is 3k, but it's spread out in 4-byte chunks across = 12k of = memory.


_______________________________________________
Publ= icity mailing list
Publicity@lists.xenproject.= org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity<= br>

= --Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36-- --===============4693258012744114000== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============4693258012744114000==-- From publicity-bounces@lists.xenproject.org Thu Oct 02 18:12:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 02 Oct 2014 18:12:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkrR-000216-1s; Thu, 02 Oct 2014 18:12:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZkrQ-000211-Jx for publicity@lists.xenproject.org; Thu, 02 Oct 2014 18:12:16 +0000 Received: from [85.158.143.35:62137] by server-3.bemta-4.messagelabs.com id C0/56-06192-F759D245; Thu, 02 Oct 2014 18:12:15 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1412273533!13450681!1 X-Originating-IP: [74.125.82.52] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_10_20,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6019 invoked from network); 2 Oct 2014 18:12:13 -0000 Received: from mail-wg0-f52.google.com (HELO mail-wg0-f52.google.com) (74.125.82.52) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Oct 2014 18:12:13 -0000 Received: by mail-wg0-f52.google.com with SMTP id a1so3904223wgh.11 for ; Thu, 02 Oct 2014 11:12:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=HTuvR3myBN+/YH8yezhP9+Cvc2c/lqV2+QX2xVxgEQY=; b=cyfUxQz+qj8TUKZ67ewzoDyARwystl2SKeHOtBP5+ap8C6q1oGrOc+sH5Mk9+UKMzf W/AbiY+WA/IJ39tP5zJCAuiDrrnSbCs7P/FNKWUYa7+rtn8MlBsn57SGDAIyxLtKZBUl +sG3Z5Xvo6q/apfvtWAEplUfITRFHaYKQkUnRcxZQXKzDw2cNDvZelyREIJrxzKV9Glu eOa4Hpp8E8FKKeYJpxVv5GFIxqSW1b3e4PLoYpQhNPYF5tAKKTwhSFJ/n7RIgaH1zCoP ZWfCYYt2eMlErLl6p0aSE4mvQoMH1jBqvFIRs647Vm50oS4wrYjxbuqKQL+BmClgiOwm j7jw== X-Received: by 10.194.94.165 with SMTP id dd5mr473788wjb.75.1412273533061; Thu, 02 Oct 2014 11:12:13 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id v9sm5381034wjy.14.2014.10.02.11.12.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Oct 2014 11:12:12 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <542D8C5B.7020506@eu.citrix.com> Date: Thu, 2 Oct 2014 19:12:09 +0100 Message-Id: <76A058F8-FFD8-45FE-8155-3162EFF77C6B@gmail.com> References: <542D65BE.8000604@eu.citrix.com> <542D8C5B.7020506@eu.citrix.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4693258012744114000==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============4693258012744114000== Content-Type: multipart/alternative; boundary="Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36" --Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii George, just came across = http://labs.bromium.com/2014/10/01/musings-on-the-recent-xen-security-advi= sories/ - not sure whether relevant Lars On 2 Oct 2014, at 18:33, George Dunlap = wrote: > Thanks everyone for your comments (both here and on IRC). >=20 > I've posted an updated draft, and included one inline below. In line = with Lars' advice, I'm going to wait until tomorrow morning for more = comments before pulling the trigger. >=20 > Peace, > -George >=20 >=20 > XSA-108: Not the vulnerability you're looking for >=20 > There has an unusual amount of media attention to XSA-108 during the = embargo period (which ended Wednesday) -- far more than any of the = previous security issues the Xen Project has reported. It began when a = blogger complained that Amazon was telling customers it would be = rebooting VMs in certain regions before a specific date. Other media = outlets picked it up and noticed that the date happened to coincide with = the release of XSA-108, and conjectured that the reboots had something = to do with that. Soon others were conjecturing that, because of the = major impact to customers of rebooting, that it must be something very = big and important, similar to the recent Heartbleed and Shell Shock = vulnerabilities. Amazon confirmed that the reboots had to do with = XSA-108, but could say nothing else because of the security embargo. >=20 > Unfortunately, because of the nature of embargoes, nobody with any = actual knowledge of the vulnerability was allowed to say anything about = it, and so the media was entirely free to speculate without any = additional information to ground the discussion in reality. >=20 > Now that the embargo has lifted, we can talk in detail about the = vulnerability; and I'm afraid that people looking for another Shell = Shock or Heartbleed are going to be disappointed. No catchy name for = this one. >=20 > >=20 >

What is the vulnerability?

>=20 > XSA-108 has to do with the emulation of a piece of hardware called an = x2APIC. x2APIC is an = interrupt controller: it allows the operating system to control when and = how and where urgent messages from outside the chip, and from other = cores within the same chip, are delivered. >=20 > Interrupt controllers occupy a rather awkward position in the = architecture. They are fairly complicated to implement in hardware; = which is why they are not implemented in earlier generations of Intel = hardware. (They have been implemented in hardware since the Ivy = Bridge architecture came out in mid-2012.) But they are far too = performance critical for Xen to pass emulation off to QEMU, as it does = with virtual disks or virtual networks. This means that they must be = emulated within Xen. >=20 > The actual vulnerability, like most vulnerabilities, is pretty simple. = Xen implements 256 x2APIC registers. These registers are stored in a = buffer big enough to hold exactly 256 registers. However, the limit = check for reading these registers was erroneosly set to 1024. >=20 > What this means is that, without the fix, if you read x2APIC registers = 0-255, you'll get the correct emulated value from the register buffer; = but if you read x2APIC registers 256-1023, Xen will read memory from = directly after the register buffer. If that memory is not mapped, Xen = will crash; if it is mapped, it will copy it to the guest. >=20 > So what this bug gives you is the ability to read (and only read) the = 12k [1] of memory directly adjacent to where Xen is storing the first = 256 registers (and no other area of memory). >=20 > The fix simply corrects the limit check to 256. >=20 > The emulated x2APIC functionality was introduced in Xen 4.1, so = previous versions of Xen are not affected. Neither are PV guests, since = Xen does not provide them with any emulated hardware. >=20 > Unfortunately, the presence of VT support emulating the x2APIC, = available on newer processors, doesn't mitigate the issue: it only = implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers. If you access = registers above 64, it will trap to Xen, and Xen will emulate access to = them, allowing you to trigger the bug. >=20 >

The impact

>=20 > If this seems like a relatively minor issue, that's because it is. The = most likely scenario is that that 12k of memory contains other Xen data = structures which contain no important information. There is, however, a = chance that this memory might contain memory from another VM; and = a chance that this memory might contain sensitive information, = like passwords, encryption keys, or other private data. >=20 > Nonetheless, this is a security issue, and the XenProject takes = all potential security issues very seriously, no matter how minor. We = have a mature process in = place to notify cloud providers, distributions, and software providers = so that they can have a fix in place before publicly disclosing any = vulnerability. >=20 > Applying security patches proactively, even though there's very low = risk that anyone might have their secret data leaked because of it, is a = conscientious and diligient thing to do. We're glad to see that so many = cloud providers using Xen are demonstrating how seriously they take = protecting customer data. >=20 > But it is by no means a disaster. Those looking for a juicy = vulnerability like Heartbleed and Shell Shock will be disappointed. >=20 >=20 > [1] You may see this reported elsewhere as 3k; saying either 3k or 12k = is simplifiying the truth in different ways. The MSR data is laid out = as a 16-byte structure, of which only the first four bytes (one 32-bit = word) can be read by this vulnerability. So the actual amount of data = which is exposed is 3k, but it's spread out in 4-byte chunks across 12k = of memory. >=20 >=20 > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii George, just came across http://labs.bromium.com/2014/10/01/musings-on-the-recent-= xen-security-advisories/ - not sure whether = relevant
Lars

On 2 Oct 2014, at 18:33, George = Dunlap <george.dunlap@eu.citrix.com> wrote:

Thanks everyone for your comments (both here and on = IRC).

I've posted an updated draft, and included one inline = below.  In line with Lars' advice, I'm going to wait until tomorrow = morning for more comments before pulling the trigger.

Peace,
= -George


XSA-108: Not the vulnerability you're looking = for

There has an unusual amount of media attention to XSA-108 = during the embargo period (which ended Wednesday) -- far more than any = of the previous security issues the Xen Project has reported.  It = began when a blogger complained that Amazon was telling customers it = would be rebooting VMs in certain regions before a specific date. =  Other media outlets picked it up and noticed that the date = happened to coincide with the release of XSA-108, and conjectured that = the reboots had something to do with that.  Soon others were = conjecturing that, because of the major impact to customers of = rebooting, that it must be something very big and important, similar to = the recent Heartbleed and Shell Shock vulnerabilities.  Amazon = confirmed that the reboots had to do with XSA-108, but could say nothing = else because of the security embargo.

Unfortunately, because of = the nature of embargoes, nobody with any actual knowledge of the = vulnerability was allowed to say anything about it, and so the media was = entirely free to speculate without any additional information to ground = the discussion in reality.

Now that the embargo has lifted, we = can talk in detail about the vulnerability; and I'm afraid that people = looking for another Shell Shock or Heartbleed are going to be = disappointed.  No catchy name for this = one.

<!--more-->

<h1>What is the = vulnerability?</h1>

XSA-108 has to do with the emulation of = a piece of hardware called an <a href=3Dhttp://www.intel.com/content/w= ww/us/en/architecture-and-technology/64-architecture-x2apic-specification.= html>x2APIC</a>. x2APIC is an interrupt controller: it = allows the operating system to control when and how and where urgent = messages from outside the chip, and from other cores within the same = chip, are delivered.

Interrupt controllers occupy a rather = awkward position in the architecture.  They are fairly complicated = to implement in hardware; which is why they are not implemented in = earlier generations of Intel hardware.  (They have been implemented = in hardware since the <a h= ttp://en.wikipedia.org/wiki/Ivy_Bridge_%28microarchitecture%29>Ivy = Bridge</a> architecture came out in mid-2012.)  But they are = far too performance critical for Xen to pass emulation off to QEMU, as = it does with virtual disks or virtual networks.  This means that = they must be emulated within Xen.

The actual vulnerability, like = most vulnerabilities, is pretty simple.  Xen implements 256 x2APIC = registers.  These registers are stored in a buffer big enough to = hold exactly 256 registers. However, the limit check for reading these = registers was erroneosly set to 1024.

What this means is that, = without the fix, if you read x2APIC registers 0-255, you'll get the = correct emulated value from the register buffer; but if you read x2APIC = registers 256-1023, Xen will read memory from directly after the = register buffer.  If that memory is not mapped, Xen will crash; if = it is mapped, it will copy it to the guest.

So what this bug = gives you is the ability to read (and only read) the 12k [1] of memory = directly adjacent to where Xen is storing the first 256 registers (and = no other area of memory).

The fix simply corrects the limit check = to 256.

The emulated x2APIC functionality was introduced in Xen = 4.1, so previous versions of Xen are not affected.  Neither are PV = guests, since Xen does not provide them with any emulated = hardware.

Unfortunately, the presence of VT support emulating the = x2APIC, available on newer processors, doesn't mitigate the issue: it = only implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers.  If you = access registers above 64, it will trap to Xen, and Xen will emulate = access to them, allowing you to trigger the bug.

<h1>The = impact</h1>

If this seems like a relatively minor issue, = that's because it is. The most likely scenario is that that 12k of = memory contains other Xen data structures which contain no important = information.  There is, however, a <i>chance</i> that = this memory might contain memory from another VM; and a = <i>chance</i> that this memory might contain sensitive = information, like passwords, encryption keys, or other private = data.

Nonetheless, this <i>is</i> a security issue, = and the XenProject takes all potential security issues very seriously, = no matter how minor.  We have a mature <a href=3Dhttp://www.xenproj= ect.org/security-policy.html>process</a> in place to notify = cloud providers, distributions, and software providers so that they can = have a fix in place before publicly disclosing any = vulnerability.

Applying security patches proactively, even though = there's very low risk that anyone might have their secret data leaked = because of it, is a conscientious and diligient thing to do.  We're = glad to see that so many cloud providers using Xen are demonstrating how = seriously they take protecting customer data.

But it is by no = means a disaster.  Those looking for a juicy vulnerability like = Heartbleed and Shell Shock will be disappointed.


[1] You may = see this reported elsewhere as 3k; saying either 3k or 12k is = simplifiying the truth in different ways.  The MSR data is laid out = as a 16-byte structure, of which only the first four bytes (one 32-bit = word) can be read by this vulnerability.  So the actual amount of = data which is exposed is 3k, but it's spread out in 4-byte chunks across = 12k of = memory.


_______________________________________________
Publ= icity mailing list
Publicity@lists.xenproject.= org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity<= br>

= --Apple-Mail=_9F2FE0E5-B207-410B-B81F-F67A8AF4BA36-- --===============4693258012744114000== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============4693258012744114000==-- From publicity-bounces@lists.xenproject.org Fri Oct 03 10:03:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Oct 2014 10:03:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZzhe-0005ju-3j; Fri, 03 Oct 2014 10:03:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZzhd-0005jp-66 for publicity@lists.xenproject.org; Fri, 03 Oct 2014 10:03:09 +0000 Received: from [85.158.139.211:10001] by server-12.bemta-5.messagelabs.com id 4A/12-22251-C547E245; Fri, 03 Oct 2014 10:03:08 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1412330586!11807208!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31209 invoked from network); 3 Oct 2014 10:03:06 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Oct 2014 10:03:06 -0000 Received: by mail-wi0-f182.google.com with SMTP id n3so1583315wiv.9 for ; Fri, 03 Oct 2014 03:03:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=sgvc4yRKzzxI7EIwpQd+pbj1Dcgy9RiA34G5/VNFWSE=; b=fMfc1ZrujZcc6uSGeJnZ0W2lHjBpym7MYMjPqXqKlisTRd6oxwtANnCC5cv3vO89ak 7WfCjfA9vOYvR71265wIPPOEPmOLx3rgk/+a2HxtjCy4eUsAyrPYrxi4zKfp53tR41PZ qbpcL7ywsX4qkJ8FD6kUc0tYWO+GXcFMjoPmDif9jvYXTplDjkmGNJuUb5byDf7JBq0G jdA41lbBOWsAmDEQSqhzjn9rXDWeVVNEzEHYyFSW9H9Qqmx+igDLTDNENNyLSLRQhR9y y8sahPSBQkYBVU6sgDAeta1MQVSlbwObwMeXCnye7GJ4ynqVg0L1amOpV54DUEVQVLF0 si5w== X-Received: by 10.180.103.131 with SMTP id fw3mr11084866wib.77.1412330585920; Fri, 03 Oct 2014 03:03:05 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id gg18sm1559954wic.21.2014.10.03.03.03.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Oct 2014 03:03:05 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <76A058F8-FFD8-45FE-8155-3162EFF77C6B@gmail.com> Date: Fri, 3 Oct 2014 11:03:02 +0100 Message-Id: <383AC05E-01B3-4146-8FFE-D7E5071CA9A6@gmail.com> References: <542D65BE.8000604@eu.citrix.com> <542D8C5B.7020506@eu.citrix.com> <76A058F8-FFD8-45FE-8155-3162EFF77C6B@gmail.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5587726764224466636==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============5587726764224466636== Content-Type: multipart/alternative; boundary="Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9" --Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii George, seems that in the new Wordpress interface requires you need to publish, = as the article is locked by you Regards Lars On 2 Oct 2014, at 19:12, Lars Kurth wrote: > George, just came across = http://labs.bromium.com/2014/10/01/musings-on-the-recent-xen-security-advi= sories/ - not sure whether relevant > Lars >=20 > On 2 Oct 2014, at 18:33, George Dunlap = wrote: >=20 >> Thanks everyone for your comments (both here and on IRC). >>=20 >> I've posted an updated draft, and included one inline below. In line = with Lars' advice, I'm going to wait until tomorrow morning for more = comments before pulling the trigger. >>=20 >> Peace, >> -George >>=20 >>=20 >> XSA-108: Not the vulnerability you're looking for >>=20 >> There has an unusual amount of media attention to XSA-108 during the = embargo period (which ended Wednesday) -- far more than any of the = previous security issues the Xen Project has reported. It began when a = blogger complained that Amazon was telling customers it would be = rebooting VMs in certain regions before a specific date. Other media = outlets picked it up and noticed that the date happened to coincide with = the release of XSA-108, and conjectured that the reboots had something = to do with that. Soon others were conjecturing that, because of the = major impact to customers of rebooting, that it must be something very = big and important, similar to the recent Heartbleed and Shell Shock = vulnerabilities. Amazon confirmed that the reboots had to do with = XSA-108, but could say nothing else because of the security embargo. >>=20 >> Unfortunately, because of the nature of embargoes, nobody with any = actual knowledge of the vulnerability was allowed to say anything about = it, and so the media was entirely free to speculate without any = additional information to ground the discussion in reality. >>=20 >> Now that the embargo has lifted, we can talk in detail about the = vulnerability; and I'm afraid that people looking for another Shell = Shock or Heartbleed are going to be disappointed. No catchy name for = this one. >>=20 >> >>=20 >>

What is the vulnerability?

>>=20 >> XSA-108 has to do with the emulation of a piece of hardware called an = x2APIC. x2APIC is an = interrupt controller: it allows the operating system to control when and = how and where urgent messages from outside the chip, and from other = cores within the same chip, are delivered. >>=20 >> Interrupt controllers occupy a rather awkward position in the = architecture. They are fairly complicated to implement in hardware; = which is why they are not implemented in earlier generations of Intel = hardware. (They have been implemented in hardware since the Ivy = Bridge architecture came out in mid-2012.) But they are far too = performance critical for Xen to pass emulation off to QEMU, as it does = with virtual disks or virtual networks. This means that they must be = emulated within Xen. >>=20 >> The actual vulnerability, like most vulnerabilities, is pretty = simple. Xen implements 256 x2APIC registers. These registers are = stored in a buffer big enough to hold exactly 256 registers. However, = the limit check for reading these registers was erroneosly set to 1024. >>=20 >> What this means is that, without the fix, if you read x2APIC = registers 0-255, you'll get the correct emulated value from the register = buffer; but if you read x2APIC registers 256-1023, Xen will read memory = from directly after the register buffer. If that memory is not mapped, = Xen will crash; if it is mapped, it will copy it to the guest. >>=20 >> So what this bug gives you is the ability to read (and only read) the = 12k [1] of memory directly adjacent to where Xen is storing the first = 256 registers (and no other area of memory). >>=20 >> The fix simply corrects the limit check to 256. >>=20 >> The emulated x2APIC functionality was introduced in Xen 4.1, so = previous versions of Xen are not affected. Neither are PV guests, since = Xen does not provide them with any emulated hardware. >>=20 >> Unfortunately, the presence of VT support emulating the x2APIC, = available on newer processors, doesn't mitigate the issue: it only = implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers. If you access = registers above 64, it will trap to Xen, and Xen will emulate access to = them, allowing you to trigger the bug. >>=20 >>

The impact

>>=20 >> If this seems like a relatively minor issue, that's because it is. = The most likely scenario is that that 12k of memory contains other Xen = data structures which contain no important information. There is, = however, a chance that this memory might contain memory from = another VM; and a chance that this memory might contain sensitive = information, like passwords, encryption keys, or other private data. >>=20 >> Nonetheless, this is a security issue, and the XenProject = takes all potential security issues very seriously, no matter how minor. = We have a mature process in = place to notify cloud providers, distributions, and software providers = so that they can have a fix in place before publicly disclosing any = vulnerability. >>=20 >> Applying security patches proactively, even though there's very low = risk that anyone might have their secret data leaked because of it, is a = conscientious and diligient thing to do. We're glad to see that so many = cloud providers using Xen are demonstrating how seriously they take = protecting customer data. >>=20 >> But it is by no means a disaster. Those looking for a juicy = vulnerability like Heartbleed and Shell Shock will be disappointed. >>=20 >>=20 >> [1] You may see this reported elsewhere as 3k; saying either 3k or = 12k is simplifiying the truth in different ways. The MSR data is laid = out as a 16-byte structure, of which only the first four bytes (one = 32-bit word) can be read by this vulnerability. So the actual amount of = data which is exposed is 3k, but it's spread out in 4-byte chunks across = 12k of memory. >>=20 >>=20 >> _______________________________________________ >> Publicity mailing list >> Publicity@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity >=20 --Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii George,
seems that in the new Wordpress = interface requires you need to publish, as the article is locked by = you
Regards
Lars

On 2 Oct = 2014, at 19:12, Lars Kurth <lars.kurth.xen@gmail.com> = wrote:

George, just came across http://labs.bromium.com/2014/10/01/musings-on-the-recent-= xen-security-advisories/ - not sure whether = relevant
Lars

On 2 Oct 2014, at 18:33, George = Dunlap <george.dunlap@eu.citrix.com> wrote:

Thanks everyone for your comments (both here and on = IRC).

I've posted an updated draft, and included one inline = below.  In line with Lars' advice, I'm going to wait until tomorrow = morning for more comments before pulling the trigger.

Peace,
= -George


XSA-108: Not the vulnerability you're looking = for

There has an unusual amount of media attention to XSA-108 = during the embargo period (which ended Wednesday) -- far more than any = of the previous security issues the Xen Project has reported.  It = began when a blogger complained that Amazon was telling customers it = would be rebooting VMs in certain regions before a specific date. =  Other media outlets picked it up and noticed that the date = happened to coincide with the release of XSA-108, and conjectured that = the reboots had something to do with that.  Soon others were = conjecturing that, because of the major impact to customers of = rebooting, that it must be something very big and important, similar to = the recent Heartbleed and Shell Shock vulnerabilities.  Amazon = confirmed that the reboots had to do with XSA-108, but could say nothing = else because of the security embargo.

Unfortunately, because of = the nature of embargoes, nobody with any actual knowledge of the = vulnerability was allowed to say anything about it, and so the media was = entirely free to speculate without any additional information to ground = the discussion in reality.

Now that the embargo has lifted, we = can talk in detail about the vulnerability; and I'm afraid that people = looking for another Shell Shock or Heartbleed are going to be = disappointed.  No catchy name for this = one.

<!--more-->

<h1>What is the = vulnerability?</h1>

XSA-108 has to do with the emulation of = a piece of hardware called an <a href=3Dhttp://www.intel.com/content/w= ww/us/en/architecture-and-technology/64-architecture-x2apic-specification.= html>x2APIC</a>. x2APIC is an interrupt controller: it = allows the operating system to control when and how and where urgent = messages from outside the chip, and from other cores within the same = chip, are delivered.

Interrupt controllers occupy a rather = awkward position in the architecture.  They are fairly complicated = to implement in hardware; which is why they are not implemented in = earlier generations of Intel hardware.  (They have been implemented = in hardware since the <a h= ttp://en.wikipedia.org/wiki/Ivy_Bridge_%28microarchitecture%29>Ivy = Bridge</a> architecture came out in mid-2012.)  But they are = far too performance critical for Xen to pass emulation off to QEMU, as = it does with virtual disks or virtual networks.  This means that = they must be emulated within Xen.

The actual vulnerability, like = most vulnerabilities, is pretty simple.  Xen implements 256 x2APIC = registers.  These registers are stored in a buffer big enough to = hold exactly 256 registers. However, the limit check for reading these = registers was erroneosly set to 1024.

What this means is that, = without the fix, if you read x2APIC registers 0-255, you'll get the = correct emulated value from the register buffer; but if you read x2APIC = registers 256-1023, Xen will read memory from directly after the = register buffer.  If that memory is not mapped, Xen will crash; if = it is mapped, it will copy it to the guest.

So what this bug = gives you is the ability to read (and only read) the 12k [1] of memory = directly adjacent to where Xen is storing the first 256 registers (and = no other area of memory).

The fix simply corrects the limit check = to 256.

The emulated x2APIC functionality was introduced in Xen = 4.1, so previous versions of Xen are not affected.  Neither are PV = guests, since Xen does not provide them with any emulated = hardware.

Unfortunately, the presence of VT support emulating the = x2APIC, available on newer processors, doesn't mitigate the issue: it = only implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers.  If you = access registers above 64, it will trap to Xen, and Xen will emulate = access to them, allowing you to trigger the bug.

<h1>The = impact</h1>

If this seems like a relatively minor issue, = that's because it is. The most likely scenario is that that 12k of = memory contains other Xen data structures which contain no important = information.  There is, however, a <i>chance</i> that = this memory might contain memory from another VM; and a = <i>chance</i> that this memory might contain sensitive = information, like passwords, encryption keys, or other private = data.

Nonetheless, this <i>is</i> a security issue, = and the XenProject takes all potential security issues very seriously, = no matter how minor.  We have a mature <a href=3Dhttp://www.xenproj= ect.org/security-policy.html>process</a> in place to notify = cloud providers, distributions, and software providers so that they can = have a fix in place before publicly disclosing any = vulnerability.

Applying security patches proactively, even though = there's very low risk that anyone might have their secret data leaked = because of it, is a conscientious and diligient thing to do.  We're = glad to see that so many cloud providers using Xen are demonstrating how = seriously they take protecting customer data.

But it is by no = means a disaster.  Those looking for a juicy vulnerability like = Heartbleed and Shell Shock will be disappointed.


[1] You may = see this reported elsewhere as 3k; saying either 3k or 12k is = simplifiying the truth in different ways.  The MSR data is laid out = as a 16-byte structure, of which only the first four bytes (one 32-bit = word) can be read by this vulnerability.  So the actual amount of = data which is exposed is 3k, but it's spread out in 4-byte chunks across = 12k of = memory.


_______________________________________________
Publ= icity mailing list
Publicity@lists.xenproject.= org
ht= tp://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity


= --Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9-- --===============5587726764224466636== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============5587726764224466636==-- From publicity-bounces@lists.xenproject.org Fri Oct 03 10:03:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Oct 2014 10:03:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZzhe-0005ju-3j; Fri, 03 Oct 2014 10:03:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XZzhd-0005jp-66 for publicity@lists.xenproject.org; Fri, 03 Oct 2014 10:03:09 +0000 Received: from [85.158.139.211:10001] by server-12.bemta-5.messagelabs.com id 4A/12-22251-C547E245; Fri, 03 Oct 2014 10:03:08 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-206.messagelabs.com!1412330586!11807208!1 X-Originating-IP: [209.85.212.182] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31209 invoked from network); 3 Oct 2014 10:03:06 -0000 Received: from mail-wi0-f182.google.com (HELO mail-wi0-f182.google.com) (209.85.212.182) by server-12.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Oct 2014 10:03:06 -0000 Received: by mail-wi0-f182.google.com with SMTP id n3so1583315wiv.9 for ; Fri, 03 Oct 2014 03:03:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=sgvc4yRKzzxI7EIwpQd+pbj1Dcgy9RiA34G5/VNFWSE=; b=fMfc1ZrujZcc6uSGeJnZ0W2lHjBpym7MYMjPqXqKlisTRd6oxwtANnCC5cv3vO89ak 7WfCjfA9vOYvR71265wIPPOEPmOLx3rgk/+a2HxtjCy4eUsAyrPYrxi4zKfp53tR41PZ qbpcL7ywsX4qkJ8FD6kUc0tYWO+GXcFMjoPmDif9jvYXTplDjkmGNJuUb5byDf7JBq0G jdA41lbBOWsAmDEQSqhzjn9rXDWeVVNEzEHYyFSW9H9Qqmx+igDLTDNENNyLSLRQhR9y y8sahPSBQkYBVU6sgDAeta1MQVSlbwObwMeXCnye7GJ4ynqVg0L1amOpV54DUEVQVLF0 si5w== X-Received: by 10.180.103.131 with SMTP id fw3mr11084866wib.77.1412330585920; Fri, 03 Oct 2014 03:03:05 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id gg18sm1559954wic.21.2014.10.03.03.03.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Oct 2014 03:03:05 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <76A058F8-FFD8-45FE-8155-3162EFF77C6B@gmail.com> Date: Fri, 3 Oct 2014 11:03:02 +0100 Message-Id: <383AC05E-01B3-4146-8FFE-D7E5071CA9A6@gmail.com> References: <542D65BE.8000604@eu.citrix.com> <542D8C5B.7020506@eu.citrix.com> <76A058F8-FFD8-45FE-8155-3162EFF77C6B@gmail.com> To: George Dunlap X-Mailer: Apple Mail (2.1878.6) Cc: Andrew Halley , "publicity@lists.xenproject.org" Subject: Re: [Publicity] Draft technical blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5587726764224466636==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============5587726764224466636== Content-Type: multipart/alternative; boundary="Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9" --Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii George, seems that in the new Wordpress interface requires you need to publish, = as the article is locked by you Regards Lars On 2 Oct 2014, at 19:12, Lars Kurth wrote: > George, just came across = http://labs.bromium.com/2014/10/01/musings-on-the-recent-xen-security-advi= sories/ - not sure whether relevant > Lars >=20 > On 2 Oct 2014, at 18:33, George Dunlap = wrote: >=20 >> Thanks everyone for your comments (both here and on IRC). >>=20 >> I've posted an updated draft, and included one inline below. In line = with Lars' advice, I'm going to wait until tomorrow morning for more = comments before pulling the trigger. >>=20 >> Peace, >> -George >>=20 >>=20 >> XSA-108: Not the vulnerability you're looking for >>=20 >> There has an unusual amount of media attention to XSA-108 during the = embargo period (which ended Wednesday) -- far more than any of the = previous security issues the Xen Project has reported. It began when a = blogger complained that Amazon was telling customers it would be = rebooting VMs in certain regions before a specific date. Other media = outlets picked it up and noticed that the date happened to coincide with = the release of XSA-108, and conjectured that the reboots had something = to do with that. Soon others were conjecturing that, because of the = major impact to customers of rebooting, that it must be something very = big and important, similar to the recent Heartbleed and Shell Shock = vulnerabilities. Amazon confirmed that the reboots had to do with = XSA-108, but could say nothing else because of the security embargo. >>=20 >> Unfortunately, because of the nature of embargoes, nobody with any = actual knowledge of the vulnerability was allowed to say anything about = it, and so the media was entirely free to speculate without any = additional information to ground the discussion in reality. >>=20 >> Now that the embargo has lifted, we can talk in detail about the = vulnerability; and I'm afraid that people looking for another Shell = Shock or Heartbleed are going to be disappointed. No catchy name for = this one. >>=20 >> >>=20 >>

What is the vulnerability?

>>=20 >> XSA-108 has to do with the emulation of a piece of hardware called an = x2APIC. x2APIC is an = interrupt controller: it allows the operating system to control when and = how and where urgent messages from outside the chip, and from other = cores within the same chip, are delivered. >>=20 >> Interrupt controllers occupy a rather awkward position in the = architecture. They are fairly complicated to implement in hardware; = which is why they are not implemented in earlier generations of Intel = hardware. (They have been implemented in hardware since the Ivy = Bridge architecture came out in mid-2012.) But they are far too = performance critical for Xen to pass emulation off to QEMU, as it does = with virtual disks or virtual networks. This means that they must be = emulated within Xen. >>=20 >> The actual vulnerability, like most vulnerabilities, is pretty = simple. Xen implements 256 x2APIC registers. These registers are = stored in a buffer big enough to hold exactly 256 registers. However, = the limit check for reading these registers was erroneosly set to 1024. >>=20 >> What this means is that, without the fix, if you read x2APIC = registers 0-255, you'll get the correct emulated value from the register = buffer; but if you read x2APIC registers 256-1023, Xen will read memory = from directly after the register buffer. If that memory is not mapped, = Xen will crash; if it is mapped, it will copy it to the guest. >>=20 >> So what this bug gives you is the ability to read (and only read) the = 12k [1] of memory directly adjacent to where Xen is storing the first = 256 registers (and no other area of memory). >>=20 >> The fix simply corrects the limit check to 256. >>=20 >> The emulated x2APIC functionality was introduced in Xen 4.1, so = previous versions of Xen are not affected. Neither are PV guests, since = Xen does not provide them with any emulated hardware. >>=20 >> Unfortunately, the presence of VT support emulating the x2APIC, = available on newer processors, doesn't mitigate the issue: it only = implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers. If you access = registers above 64, it will trap to Xen, and Xen will emulate access to = them, allowing you to trigger the bug. >>=20 >>

The impact

>>=20 >> If this seems like a relatively minor issue, that's because it is. = The most likely scenario is that that 12k of memory contains other Xen = data structures which contain no important information. There is, = however, a chance that this memory might contain memory from = another VM; and a chance that this memory might contain sensitive = information, like passwords, encryption keys, or other private data. >>=20 >> Nonetheless, this is a security issue, and the XenProject = takes all potential security issues very seriously, no matter how minor. = We have a mature process in = place to notify cloud providers, distributions, and software providers = so that they can have a fix in place before publicly disclosing any = vulnerability. >>=20 >> Applying security patches proactively, even though there's very low = risk that anyone might have their secret data leaked because of it, is a = conscientious and diligient thing to do. We're glad to see that so many = cloud providers using Xen are demonstrating how seriously they take = protecting customer data. >>=20 >> But it is by no means a disaster. Those looking for a juicy = vulnerability like Heartbleed and Shell Shock will be disappointed. >>=20 >>=20 >> [1] You may see this reported elsewhere as 3k; saying either 3k or = 12k is simplifiying the truth in different ways. The MSR data is laid = out as a 16-byte structure, of which only the first four bytes (one = 32-bit word) can be read by this vulnerability. So the actual amount of = data which is exposed is 3k, but it's spread out in 4-byte chunks across = 12k of memory. >>=20 >>=20 >> _______________________________________________ >> Publicity mailing list >> Publicity@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity >=20 --Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii George,
seems that in the new Wordpress = interface requires you need to publish, as the article is locked by = you
Regards
Lars

On 2 Oct = 2014, at 19:12, Lars Kurth <lars.kurth.xen@gmail.com> = wrote:

George, just came across http://labs.bromium.com/2014/10/01/musings-on-the-recent-= xen-security-advisories/ - not sure whether = relevant
Lars

On 2 Oct 2014, at 18:33, George = Dunlap <george.dunlap@eu.citrix.com> wrote:

Thanks everyone for your comments (both here and on = IRC).

I've posted an updated draft, and included one inline = below.  In line with Lars' advice, I'm going to wait until tomorrow = morning for more comments before pulling the trigger.

Peace,
= -George


XSA-108: Not the vulnerability you're looking = for

There has an unusual amount of media attention to XSA-108 = during the embargo period (which ended Wednesday) -- far more than any = of the previous security issues the Xen Project has reported.  It = began when a blogger complained that Amazon was telling customers it = would be rebooting VMs in certain regions before a specific date. =  Other media outlets picked it up and noticed that the date = happened to coincide with the release of XSA-108, and conjectured that = the reboots had something to do with that.  Soon others were = conjecturing that, because of the major impact to customers of = rebooting, that it must be something very big and important, similar to = the recent Heartbleed and Shell Shock vulnerabilities.  Amazon = confirmed that the reboots had to do with XSA-108, but could say nothing = else because of the security embargo.

Unfortunately, because of = the nature of embargoes, nobody with any actual knowledge of the = vulnerability was allowed to say anything about it, and so the media was = entirely free to speculate without any additional information to ground = the discussion in reality.

Now that the embargo has lifted, we = can talk in detail about the vulnerability; and I'm afraid that people = looking for another Shell Shock or Heartbleed are going to be = disappointed.  No catchy name for this = one.

<!--more-->

<h1>What is the = vulnerability?</h1>

XSA-108 has to do with the emulation of = a piece of hardware called an <a href=3Dhttp://www.intel.com/content/w= ww/us/en/architecture-and-technology/64-architecture-x2apic-specification.= html>x2APIC</a>. x2APIC is an interrupt controller: it = allows the operating system to control when and how and where urgent = messages from outside the chip, and from other cores within the same = chip, are delivered.

Interrupt controllers occupy a rather = awkward position in the architecture.  They are fairly complicated = to implement in hardware; which is why they are not implemented in = earlier generations of Intel hardware.  (They have been implemented = in hardware since the <a h= ttp://en.wikipedia.org/wiki/Ivy_Bridge_%28microarchitecture%29>Ivy = Bridge</a> architecture came out in mid-2012.)  But they are = far too performance critical for Xen to pass emulation off to QEMU, as = it does with virtual disks or virtual networks.  This means that = they must be emulated within Xen.

The actual vulnerability, like = most vulnerabilities, is pretty simple.  Xen implements 256 x2APIC = registers.  These registers are stored in a buffer big enough to = hold exactly 256 registers. However, the limit check for reading these = registers was erroneosly set to 1024.

What this means is that, = without the fix, if you read x2APIC registers 0-255, you'll get the = correct emulated value from the register buffer; but if you read x2APIC = registers 256-1023, Xen will read memory from directly after the = register buffer.  If that memory is not mapped, Xen will crash; if = it is mapped, it will copy it to the guest.

So what this bug = gives you is the ability to read (and only read) the 12k [1] of memory = directly adjacent to where Xen is storing the first 256 registers (and = no other area of memory).

The fix simply corrects the limit check = to 256.

The emulated x2APIC functionality was introduced in Xen = 4.1, so previous versions of Xen are not affected.  Neither are PV = guests, since Xen does not provide them with any emulated = hardware.

Unfortunately, the presence of VT support emulating the = x2APIC, available on newer processors, doesn't mitigate the issue: it = only implements the 64 registers actually used by real hardware at the = moment, leaving Xen to emulate the rest of the registers.  If you = access registers above 64, it will trap to Xen, and Xen will emulate = access to them, allowing you to trigger the bug.

<h1>The = impact</h1>

If this seems like a relatively minor issue, = that's because it is. The most likely scenario is that that 12k of = memory contains other Xen data structures which contain no important = information.  There is, however, a <i>chance</i> that = this memory might contain memory from another VM; and a = <i>chance</i> that this memory might contain sensitive = information, like passwords, encryption keys, or other private = data.

Nonetheless, this <i>is</i> a security issue, = and the XenProject takes all potential security issues very seriously, = no matter how minor.  We have a mature <a href=3Dhttp://www.xenproj= ect.org/security-policy.html>process</a> in place to notify = cloud providers, distributions, and software providers so that they can = have a fix in place before publicly disclosing any = vulnerability.

Applying security patches proactively, even though = there's very low risk that anyone might have their secret data leaked = because of it, is a conscientious and diligient thing to do.  We're = glad to see that so many cloud providers using Xen are demonstrating how = seriously they take protecting customer data.

But it is by no = means a disaster.  Those looking for a juicy vulnerability like = Heartbleed and Shell Shock will be disappointed.


[1] You may = see this reported elsewhere as 3k; saying either 3k or 12k is = simplifiying the truth in different ways.  The MSR data is laid out = as a 16-byte structure, of which only the first four bytes (one 32-bit = word) can be read by this vulnerability.  So the actual amount of = data which is exposed is 3k, but it's spread out in 4-byte chunks across = 12k of = memory.


_______________________________________________
Publ= icity mailing list
Publicity@lists.xenproject.= org
ht= tp://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity


= --Apple-Mail=_AD8715A7-14E4-448F-8D29-3F0BD2E3AAD9-- --===============5587726764224466636== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============5587726764224466636==-- From publicity-bounces@lists.xenproject.org Fri Oct 03 20:14:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Oct 2014 20:14:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xa9Fd-0007hj-4h; Fri, 03 Oct 2014 20:14:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xa9Fc-0007hZ-Cd for publicity@lists.xenproject.org; Fri, 03 Oct 2014 20:14:52 +0000 Received: from [193.109.254.147:18729] by server-10.bemta-14.messagelabs.com id 3F/52-01463-BB30F245; Fri, 03 Oct 2014 20:14:51 +0000 X-Env-Sender: sconway@linuxfoundation.org X-Msg-Ref: server-13.tower-27.messagelabs.com!1412367289!13244829!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17710 invoked from network); 3 Oct 2014 20:14:49 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Oct 2014 20:14:49 -0000 Received: by mail-wi0-f173.google.com with SMTP id fb4so3884872wid.6 for ; Fri, 03 Oct 2014 13:14:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=d4Go85suQLklMXh8CIE/tuZvgsCq5/YHqSq2XNQh3+Y=; b=gZdxOXUKvOocy0HBh26kL0JSb0zVkay0rpOq0xPrfOVpHKSEI0/MoVUgf1Ch46EniZ P5KO7DiEilhJsSm0UO+y2syDmnDbynqInHODSxnli8/omDSry+m2m31rOpBNhT54jaZq tOYnf4xOgpKp3OqWDZwE7ocq2HShwEJ/FLXQI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=d4Go85suQLklMXh8CIE/tuZvgsCq5/YHqSq2XNQh3+Y=; b=NCvespAjtmxiB4MdskHTx0Qp4cLd2L/A4aK39hvt0qpjtndH1hByhAB1RgfkScOBbW t4W/zdHnedVDlBfhYhQVIlXxKMNWRyM4IymLadpTEhMIhyrbXa7b/hVe8+xtyKlU7QbI KVs3yt3y2yaHVgv/+3+ficgm7ZYlyErTnCq6TFt8ujAg0xfIdGDKye1PsT85RmzYmksz +7YiGOWmWoC4sowSJ1m0UQUxKZ0ekttunb2YNWAllZPnLObI0KQzuD/ZIXlLH05MvJs9 9XrFCWsXOFXbE7TpjLXGbCO2Rgxd1yYFvJg9caHSFfpQtbGqkBr1PxCnU49BueqMxIlw vbkg== X-Gm-Message-State: ALoCoQl5C81QPdZhcfxrvU1/8b4iFEYBOkSMXhFaC7izNW9qEwVurQlaeQcHLksDcj9hJ44m5Ni3 MIME-Version: 1.0 X-Received: by 10.180.210.239 with SMTP id mx15mr791334wic.29.1412367289531; Fri, 03 Oct 2014 13:14:49 -0700 (PDT) Received: by 10.194.57.4 with HTTP; Fri, 3 Oct 2014 13:14:49 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 Oct 2014 15:14:49 -0500 Message-ID: From: Sarah Conway To: "publicity@lists.xenproject.org" , Advisory-board discussions Subject: Re: [Publicity] More XSA 108 Coverage X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8434781287625408429==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============8434781287625408429== Content-Type: multipart/alternative; boundary=001a11c32db295d82705048a62f0 --001a11c32db295d82705048a62f0 Content-Type: text/plain; charset=UTF-8 Hi everyone. In addition to eWeek, WSJ and ITNews, here is more coverage appearing since the advisory and blogs were issued this week. Thanks, Rackspace Joins Amazon in Cloud Reboot Over Xen Hypervisor Bug http://vmblog.com/archive/2014/09/29/rackspace-joins-amazon-in-cloud-reboot-over-xen-hypervisor-bug.aspx Understanding The Xen XSA-108 Security Issue http://www.phoronix.com/scan.php?page=news_item&px=MTgwMjQ Xen sheds light on 'serious' security bug affecting servers http://www.v3.co.uk/v3-uk/news/2373641/xen-sheds-light-on-serious-security-bug-affecting-servers Xen reveals XSA-108 memory leak bug details http://www.techrepublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/ Google cuts cloud computing prices http://www.techrepublic.com/article/google-cuts-cloud-computing-prices-gives-away-unlimited-storage-to-students/ Are Google's even lower prices -- and not using Xen -- tantalizing enough to switch to its services? Are the costs low enough to warrant a migration? Do you use Google Apps for Work, or Education? Let us know in the comments. Serious hypervisor bug fix causes unexpected cloud downtime http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660 (reporter we "talked" to on Twitter) CoreOS eliminates downtime from server OS patching http://www.techrepublic.com/article/coreos-eliminates-downtime-from-server-os-patching/ CoreOS commentary on XSA-108 The Shellshock vulnerability and the even more recent Xen hypervisor vulnerability remind us of an important fact of enterprise IT: server OS patching is hard CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve patching headaches. The long-term value proposition of the CoreOS primary product of the same name is to bring Google Chrome-like updates to server updates. -- Sarah Conway PR Manager The Linux Foundation sconway@linuxfoundation.org (978) 578-5300 Cell Skype: sarah.k.conway --001a11c32db295d82705048a62f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi everyone.

In addition to eWeek, WSJ = and ITNews, here is more coverage appearing since the advisory and blogs we= re issued this week.
Xen reve= als XSA-108 memory leak bug details
http://www.techrep= ublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/

<= /div>
Google cuts cloud computing prices
http://www.techrepublic.com/article/google-cuts-clou= d-computing-prices-gives-away-unlimited-storage-to-students/

Are Google's even lower prices -- and not using Xen -- tantaliz= ing enough to switch to its services? Are the costs low enough to warrant a= migration? Do you use Google Apps for Work, or Education? Let us know in t= he comments.

Serious hypervisor bug fix causes unexpected= cloud downtime
http://threatpost.com/serious-= hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660

(reporter we "talked" to on Twitter)

CoreOS eliminates downtime from server OS patching
http://www.techrepublic.com/article/coreos-eliminates-downtime-from-= server-os-patching/

CoreOS commentary on XSA-108
<= br>
The Shellshock vulnerability and the even more recent Xen hyp= ervisor vulnerability remind us of an important fact of enterprise IT: serv= er OS patching is hard

CoreOS is trying to simplify OS patching= . According to CoreOS CEO Alex Polvi, who was a guest on a recent Cloudcast= podcast, CoreOS can solve patching headaches. The long-term value proposit= ion of the CoreOS primary product of the same name is to bring Google Chrom= e-like updates to server updates.



--
Sarah Conway
PR M= anager
The Linux Foundation
sconway@linuxfoundation.org
(978) 578-5300 =C2=A0Cell
Skype= : =C2=A0sarah.k.conway
--001a11c32db295d82705048a62f0-- --===============8434781287625408429== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============8434781287625408429==-- From publicity-bounces@lists.xenproject.org Fri Oct 03 20:14:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Oct 2014 20:14:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xa9Fd-0007hj-4h; Fri, 03 Oct 2014 20:14:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xa9Fc-0007hZ-Cd for publicity@lists.xenproject.org; Fri, 03 Oct 2014 20:14:52 +0000 Received: from [193.109.254.147:18729] by server-10.bemta-14.messagelabs.com id 3F/52-01463-BB30F245; Fri, 03 Oct 2014 20:14:51 +0000 X-Env-Sender: sconway@linuxfoundation.org X-Msg-Ref: server-13.tower-27.messagelabs.com!1412367289!13244829!1 X-Originating-IP: [209.85.212.173] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17710 invoked from network); 3 Oct 2014 20:14:49 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Oct 2014 20:14:49 -0000 Received: by mail-wi0-f173.google.com with SMTP id fb4so3884872wid.6 for ; Fri, 03 Oct 2014 13:14:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=d4Go85suQLklMXh8CIE/tuZvgsCq5/YHqSq2XNQh3+Y=; b=gZdxOXUKvOocy0HBh26kL0JSb0zVkay0rpOq0xPrfOVpHKSEI0/MoVUgf1Ch46EniZ P5KO7DiEilhJsSm0UO+y2syDmnDbynqInHODSxnli8/omDSry+m2m31rOpBNhT54jaZq tOYnf4xOgpKp3OqWDZwE7ocq2HShwEJ/FLXQI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=d4Go85suQLklMXh8CIE/tuZvgsCq5/YHqSq2XNQh3+Y=; b=NCvespAjtmxiB4MdskHTx0Qp4cLd2L/A4aK39hvt0qpjtndH1hByhAB1RgfkScOBbW t4W/zdHnedVDlBfhYhQVIlXxKMNWRyM4IymLadpTEhMIhyrbXa7b/hVe8+xtyKlU7QbI KVs3yt3y2yaHVgv/+3+ficgm7ZYlyErTnCq6TFt8ujAg0xfIdGDKye1PsT85RmzYmksz +7YiGOWmWoC4sowSJ1m0UQUxKZ0ekttunb2YNWAllZPnLObI0KQzuD/ZIXlLH05MvJs9 9XrFCWsXOFXbE7TpjLXGbCO2Rgxd1yYFvJg9caHSFfpQtbGqkBr1PxCnU49BueqMxIlw vbkg== X-Gm-Message-State: ALoCoQl5C81QPdZhcfxrvU1/8b4iFEYBOkSMXhFaC7izNW9qEwVurQlaeQcHLksDcj9hJ44m5Ni3 MIME-Version: 1.0 X-Received: by 10.180.210.239 with SMTP id mx15mr791334wic.29.1412367289531; Fri, 03 Oct 2014 13:14:49 -0700 (PDT) Received: by 10.194.57.4 with HTTP; Fri, 3 Oct 2014 13:14:49 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 Oct 2014 15:14:49 -0500 Message-ID: From: Sarah Conway To: "publicity@lists.xenproject.org" , Advisory-board discussions Subject: Re: [Publicity] More XSA 108 Coverage X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8434781287625408429==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============8434781287625408429== Content-Type: multipart/alternative; boundary=001a11c32db295d82705048a62f0 --001a11c32db295d82705048a62f0 Content-Type: text/plain; charset=UTF-8 Hi everyone. In addition to eWeek, WSJ and ITNews, here is more coverage appearing since the advisory and blogs were issued this week. Thanks, Rackspace Joins Amazon in Cloud Reboot Over Xen Hypervisor Bug http://vmblog.com/archive/2014/09/29/rackspace-joins-amazon-in-cloud-reboot-over-xen-hypervisor-bug.aspx Understanding The Xen XSA-108 Security Issue http://www.phoronix.com/scan.php?page=news_item&px=MTgwMjQ Xen sheds light on 'serious' security bug affecting servers http://www.v3.co.uk/v3-uk/news/2373641/xen-sheds-light-on-serious-security-bug-affecting-servers Xen reveals XSA-108 memory leak bug details http://www.techrepublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/ Google cuts cloud computing prices http://www.techrepublic.com/article/google-cuts-cloud-computing-prices-gives-away-unlimited-storage-to-students/ Are Google's even lower prices -- and not using Xen -- tantalizing enough to switch to its services? Are the costs low enough to warrant a migration? Do you use Google Apps for Work, or Education? Let us know in the comments. Serious hypervisor bug fix causes unexpected cloud downtime http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660 (reporter we "talked" to on Twitter) CoreOS eliminates downtime from server OS patching http://www.techrepublic.com/article/coreos-eliminates-downtime-from-server-os-patching/ CoreOS commentary on XSA-108 The Shellshock vulnerability and the even more recent Xen hypervisor vulnerability remind us of an important fact of enterprise IT: server OS patching is hard CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve patching headaches. The long-term value proposition of the CoreOS primary product of the same name is to bring Google Chrome-like updates to server updates. -- Sarah Conway PR Manager The Linux Foundation sconway@linuxfoundation.org (978) 578-5300 Cell Skype: sarah.k.conway --001a11c32db295d82705048a62f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi everyone.

In addition to eWeek, WSJ = and ITNews, here is more coverage appearing since the advisory and blogs we= re issued this week.
Xen reve= als XSA-108 memory leak bug details
http://www.techrep= ublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/

<= /div>
Google cuts cloud computing prices
http://www.techrepublic.com/article/google-cuts-clou= d-computing-prices-gives-away-unlimited-storage-to-students/

Are Google's even lower prices -- and not using Xen -- tantaliz= ing enough to switch to its services? Are the costs low enough to warrant a= migration? Do you use Google Apps for Work, or Education? Let us know in t= he comments.

Serious hypervisor bug fix causes unexpected= cloud downtime
http://threatpost.com/serious-= hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660

(reporter we "talked" to on Twitter)

CoreOS eliminates downtime from server OS patching
http://www.techrepublic.com/article/coreos-eliminates-downtime-from-= server-os-patching/

CoreOS commentary on XSA-108
<= br>
The Shellshock vulnerability and the even more recent Xen hyp= ervisor vulnerability remind us of an important fact of enterprise IT: serv= er OS patching is hard

CoreOS is trying to simplify OS patching= . According to CoreOS CEO Alex Polvi, who was a guest on a recent Cloudcast= podcast, CoreOS can solve patching headaches. The long-term value proposit= ion of the CoreOS primary product of the same name is to bring Google Chrom= e-like updates to server updates.



--
Sarah Conway
PR M= anager
The Linux Foundation
sconway@linuxfoundation.org
(978) 578-5300 =C2=A0Cell
Skype= : =C2=A0sarah.k.conway
--001a11c32db295d82705048a62f0-- --===============8434781287625408429== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============8434781287625408429==-- From publicity-bounces@lists.xenproject.org Fri Oct 03 22:11:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Oct 2014 22:11:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XaB4C-0004IZ-Ld; Fri, 03 Oct 2014 22:11:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XaB4B-0004IQ-21 for publicity@lists.xenproject.org; Fri, 03 Oct 2014 22:11:11 +0000 Received: from [85.158.143.35:63463] by server-3.bemta-4.messagelabs.com id 84/7D-06192-EFE1F245; Fri, 03 Oct 2014 22:11:10 +0000 X-Env-Sender: dor@cloudius-systems.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1412374267!13786448!1 X-Originating-IP: [209.85.160.170] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20384 invoked from network); 3 Oct 2014 22:11:08 -0000 Received: from mail-yk0-f170.google.com (HELO mail-yk0-f170.google.com) (209.85.160.170) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Oct 2014 22:11:08 -0000 Received: by mail-yk0-f170.google.com with SMTP id 20so683850yks.1 for ; Fri, 03 Oct 2014 15:11:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LxVI8HqEV9YIepM0MHHD+6ccyrf6wWFNzNKnNrssO6Y=; b=LlSSDpwpPsaIGQxESR1aEhp9Wu0shG5hErmaZBN/QRZNXkYQ/SHALZbNLz+9d9w3fr n4yxefI4gTl6ZAp3bhkveFAKw1HbhaNA6TOGP5BUXEdpH/8O+0rSnSdNK6en4Z6kVi2I LGdAvWghaWt4tnhtZx1GdAxotKWWNrM3eg79qgsgBhEVwfZvEzS0+iVlabBoQcZMLSCc UbRtwbPQHOlaXe+fcyZ2ivW0DMMzunz6wgb+S2WwCWkEtFwkyDIU/m6MR/vmHTixXoBE PtEHN8/gUyvTP7jueeNV2UTMtTEE0J6WOSE4YMdskRTVAGEhG6HhHPoxJ8noLEyYgQWB KG8A== X-Gm-Message-State: ALoCoQmpB3TLtWQfPz1nd9ZIICx7kDIooXEFIOWuyRCLuNv3yu+w9B86tr45tjY5OS8F9IPkBh74 MIME-Version: 1.0 X-Received: by 10.236.118.174 with SMTP id l34mr25541yhh.181.1412374266697; Fri, 03 Oct 2014 15:11:06 -0700 (PDT) Received: by 10.170.117.68 with HTTP; Fri, 3 Oct 2014 15:11:06 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 Oct 2014 01:11:06 +0300 Message-ID: From: Dor Laor To: Sarah Conway Cc: Advisory-board discussions , "publicity@lists.xenproject.org" Subject: Re: [Publicity] More XSA 108 Coverage X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2421024753357745645==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============2421024753357745645== Content-Type: multipart/alternative; boundary=20cf301af87f74f09705048c0284 --20cf301af87f74f09705048c0284 Content-Type: text/plain; charset=UTF-8 On Fri, Oct 3, 2014 at 11:14 PM, Sarah Conway wrote: > Hi everyone. > > In addition to eWeek, WSJ and ITNews, here is more coverage appearing > since the advisory and blogs were issued this week. > > Thanks, > > Well done handling it on all levels. I blogged about it as well: http://osv.io/blog/blog/2014/10/03/cloud-reboot/ This is classical KSplice, I hope it will get into Xen > Rackspace Joins Amazon in Cloud Reboot Over Xen Hypervisor Bug > > http://vmblog.com/archive/2014/09/29/rackspace-joins-amazon-in-cloud-reboot-over-xen-hypervisor-bug.aspx > > Understanding The Xen XSA-108 Security Issue > http://www.phoronix.com/scan.php?page=news_item&px=MTgwMjQ > > Xen sheds light on 'serious' security bug affecting servers > > http://www.v3.co.uk/v3-uk/news/2373641/xen-sheds-light-on-serious-security-bug-affecting-servers > > Xen reveals XSA-108 memory leak bug details > > http://www.techrepublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/ > > Google cuts cloud computing prices > > http://www.techrepublic.com/article/google-cuts-cloud-computing-prices-gives-away-unlimited-storage-to-students/ > > Are Google's even lower prices -- and not using Xen -- tantalizing enough > to switch to its services? Are the costs low enough to warrant a migration? > Do you use Google Apps for Work, or Education? Let us know in the comments. > > Serious hypervisor bug fix causes unexpected cloud downtime > > http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660 > > (reporter we "talked" to on Twitter) > > CoreOS eliminates downtime from server OS patching > > http://www.techrepublic.com/article/coreos-eliminates-downtime-from-server-os-patching/ > > CoreOS commentary on XSA-108 > > The Shellshock vulnerability and the even more recent Xen hypervisor > vulnerability remind us of an important fact of enterprise IT: server OS > patching is hard > > CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex > Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve > patching headaches. The long-term value proposition of the CoreOS primary > product of the same name is to bring Google Chrome-like updates to server > updates. > > > > -- > Sarah Conway > PR Manager > The Linux Foundation > sconway@linuxfoundation.org > (978) 578-5300 Cell > Skype: sarah.k.conway > > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity > > --20cf301af87f74f09705048c0284 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Oct 3, 2014 at 11:14 PM, Sarah Conway <sconway@linuxfoundati= on.org> wrote:
Hi everyo= ne.

In addition to eWeek, WSJ and ITNews, here is more c= overage appearing since the advisory and blogs were issued this week.
<= div>
Thanks,


Well done handling it on all levels. I blogged about= it as well:

This is classical KSplice, I hope it will get into Xen
=C2=A0
Xen reveals XSA-108 memory le= ak bug details
http://www.techrepubl= ic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/

Are Google's even lower prices -- and not using = Xen -- tantalizing enough to switch to its services? Are the costs low enou= gh to warrant a migration? Do you use Google Apps for Work, or Education? L= et us know in the comments.

Serious hypervisor bug fix ca= uses unexpected cloud downtime
http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud= -downtime/108660

(reporter we "talked" to o= n Twitter)

CoreOS commentary on XSA-108

The Shells= hock vulnerability and the even more recent Xen hypervisor vulnerability re= mind us of an important fact of enterprise IT: server OS patching is hard
CoreOS is trying to simplify OS patching. According to CoreOS CE= O Alex Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can sol= ve patching headaches. The long-term value proposition of the CoreOS primar= y product of the same name is to bring Google Chrome-like updates to server= updates.



--
Sarah Conway
PR Manager
The Linux Foun= dation
= sconway@linuxfoundation.org
(978) 578-5300 =C2=A0Cell
Skype: =C2= =A0sarah.k.conway

_______________________________________________
Publicity mailing list
Publicity@lists.xenprojec= t.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publ= icity


--20cf301af87f74f09705048c0284-- --===============2421024753357745645== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============2421024753357745645==-- From publicity-bounces@lists.xenproject.org Fri Oct 03 22:11:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 03 Oct 2014 22:11:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XaB4C-0004IZ-Ld; Fri, 03 Oct 2014 22:11:12 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XaB4B-0004IQ-21 for publicity@lists.xenproject.org; Fri, 03 Oct 2014 22:11:11 +0000 Received: from [85.158.143.35:63463] by server-3.bemta-4.messagelabs.com id 84/7D-06192-EFE1F245; Fri, 03 Oct 2014 22:11:10 +0000 X-Env-Sender: dor@cloudius-systems.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1412374267!13786448!1 X-Originating-IP: [209.85.160.170] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20384 invoked from network); 3 Oct 2014 22:11:08 -0000 Received: from mail-yk0-f170.google.com (HELO mail-yk0-f170.google.com) (209.85.160.170) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Oct 2014 22:11:08 -0000 Received: by mail-yk0-f170.google.com with SMTP id 20so683850yks.1 for ; Fri, 03 Oct 2014 15:11:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LxVI8HqEV9YIepM0MHHD+6ccyrf6wWFNzNKnNrssO6Y=; b=LlSSDpwpPsaIGQxESR1aEhp9Wu0shG5hErmaZBN/QRZNXkYQ/SHALZbNLz+9d9w3fr n4yxefI4gTl6ZAp3bhkveFAKw1HbhaNA6TOGP5BUXEdpH/8O+0rSnSdNK6en4Z6kVi2I LGdAvWghaWt4tnhtZx1GdAxotKWWNrM3eg79qgsgBhEVwfZvEzS0+iVlabBoQcZMLSCc UbRtwbPQHOlaXe+fcyZ2ivW0DMMzunz6wgb+S2WwCWkEtFwkyDIU/m6MR/vmHTixXoBE PtEHN8/gUyvTP7jueeNV2UTMtTEE0J6WOSE4YMdskRTVAGEhG6HhHPoxJ8noLEyYgQWB KG8A== X-Gm-Message-State: ALoCoQmpB3TLtWQfPz1nd9ZIICx7kDIooXEFIOWuyRCLuNv3yu+w9B86tr45tjY5OS8F9IPkBh74 MIME-Version: 1.0 X-Received: by 10.236.118.174 with SMTP id l34mr25541yhh.181.1412374266697; Fri, 03 Oct 2014 15:11:06 -0700 (PDT) Received: by 10.170.117.68 with HTTP; Fri, 3 Oct 2014 15:11:06 -0700 (PDT) In-Reply-To: References: Date: Sat, 4 Oct 2014 01:11:06 +0300 Message-ID: From: Dor Laor To: Sarah Conway Cc: Advisory-board discussions , "publicity@lists.xenproject.org" Subject: Re: [Publicity] More XSA 108 Coverage X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2421024753357745645==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============2421024753357745645== Content-Type: multipart/alternative; boundary=20cf301af87f74f09705048c0284 --20cf301af87f74f09705048c0284 Content-Type: text/plain; charset=UTF-8 On Fri, Oct 3, 2014 at 11:14 PM, Sarah Conway wrote: > Hi everyone. > > In addition to eWeek, WSJ and ITNews, here is more coverage appearing > since the advisory and blogs were issued this week. > > Thanks, > > Well done handling it on all levels. I blogged about it as well: http://osv.io/blog/blog/2014/10/03/cloud-reboot/ This is classical KSplice, I hope it will get into Xen > Rackspace Joins Amazon in Cloud Reboot Over Xen Hypervisor Bug > > http://vmblog.com/archive/2014/09/29/rackspace-joins-amazon-in-cloud-reboot-over-xen-hypervisor-bug.aspx > > Understanding The Xen XSA-108 Security Issue > http://www.phoronix.com/scan.php?page=news_item&px=MTgwMjQ > > Xen sheds light on 'serious' security bug affecting servers > > http://www.v3.co.uk/v3-uk/news/2373641/xen-sheds-light-on-serious-security-bug-affecting-servers > > Xen reveals XSA-108 memory leak bug details > > http://www.techrepublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/ > > Google cuts cloud computing prices > > http://www.techrepublic.com/article/google-cuts-cloud-computing-prices-gives-away-unlimited-storage-to-students/ > > Are Google's even lower prices -- and not using Xen -- tantalizing enough > to switch to its services? Are the costs low enough to warrant a migration? > Do you use Google Apps for Work, or Education? Let us know in the comments. > > Serious hypervisor bug fix causes unexpected cloud downtime > > http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660 > > (reporter we "talked" to on Twitter) > > CoreOS eliminates downtime from server OS patching > > http://www.techrepublic.com/article/coreos-eliminates-downtime-from-server-os-patching/ > > CoreOS commentary on XSA-108 > > The Shellshock vulnerability and the even more recent Xen hypervisor > vulnerability remind us of an important fact of enterprise IT: server OS > patching is hard > > CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex > Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve > patching headaches. The long-term value proposition of the CoreOS primary > product of the same name is to bring Google Chrome-like updates to server > updates. > > > > -- > Sarah Conway > PR Manager > The Linux Foundation > sconway@linuxfoundation.org > (978) 578-5300 Cell > Skype: sarah.k.conway > > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity > > --20cf301af87f74f09705048c0284 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On F= ri, Oct 3, 2014 at 11:14 PM, Sarah Conway <sconway@linuxfoundati= on.org> wrote:
Hi everyo= ne.

In addition to eWeek, WSJ and ITNews, here is more c= overage appearing since the advisory and blogs were issued this week.
<= div>
Thanks,


Well done handling it on all levels. I blogged about= it as well:

This is classical KSplice, I hope it will get into Xen
=C2=A0
Xen reveals XSA-108 memory le= ak bug details
http://www.techrepubl= ic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/

Are Google's even lower prices -- and not using = Xen -- tantalizing enough to switch to its services? Are the costs low enou= gh to warrant a migration? Do you use Google Apps for Work, or Education? L= et us know in the comments.

Serious hypervisor bug fix ca= uses unexpected cloud downtime
http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud= -downtime/108660

(reporter we "talked" to o= n Twitter)

CoreOS commentary on XSA-108

The Shells= hock vulnerability and the even more recent Xen hypervisor vulnerability re= mind us of an important fact of enterprise IT: server OS patching is hard
CoreOS is trying to simplify OS patching. According to CoreOS CE= O Alex Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can sol= ve patching headaches. The long-term value proposition of the CoreOS primar= y product of the same name is to bring Google Chrome-like updates to server= updates.



--
Sarah Conway
PR Manager
The Linux Foun= dation
= sconway@linuxfoundation.org
(978) 578-5300 =C2=A0Cell
Skype: =C2= =A0sarah.k.conway

_______________________________________________
Publicity mailing list
Publicity@lists.xenprojec= t.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/publ= icity


--20cf301af87f74f09705048c0284-- --===============2421024753357745645== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============2421024753357745645==-- From publicity-bounces@lists.xenproject.org Mon Oct 06 13:32:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Oct 2014 13:32:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xb8Ou-0000mX-Ut; Mon, 06 Oct 2014 13:32:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xb8Os-0000mK-T4 for publicity@lists.xenproject.org; Mon, 06 Oct 2014 13:32:31 +0000 Received: from [85.158.143.35:9292] by server-2.bemta-4.messagelabs.com id D1/10-04525-EE992345; Mon, 06 Oct 2014 13:32:30 +0000 X-Env-Sender: sconway@linuxfoundation.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1412602347!14066258!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=3.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60, HTML_FONT_LOW_CONTRAST, HTML_MESSAGE, HTML_TINY_FONT, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19722 invoked from network); 6 Oct 2014 13:32:28 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Oct 2014 13:32:28 -0000 Received: by mail-wi0-f180.google.com with SMTP id em10so4621037wid.1 for ; Mon, 06 Oct 2014 06:32:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=p7TFoVlxTcNY/3Y8ZX9NmqlphFGCRX86trYxDSuQ604=; b=Hryh8Mzhf48ZgDtN9fIlsS9Po/XozuWbHrYi5jTgp/cICbBDO3DBS2u+I3wgaXPo8x N1czE0hyf36DBICJq4y/HqcSy+T89CqulCeA5KKgHtVr10i20/JLgMiDeZBJrsw/CpCc N9cfjsRyvDeHGArfxULIELnE4pgSSM7KBKvEI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=p7TFoVlxTcNY/3Y8ZX9NmqlphFGCRX86trYxDSuQ604=; b=FLLd1t5NlLwVDgaD+Pt2e3bAp8S4mhLgBUOJdkab8IyRpwYfNv6b0DyBOIeGov8Suq Yrx8sO5Ep8e5aWQeoQLK9u9Q+DlEmiLnngKuqfIIGntM11lfeUG1KaxmnBOGRjlJUhAF VsWjYktNyoVUUcx0JQFz7Vdm7pYFkQcZdYjhHHsFXg7nK5PFC1xZ2D0SMUOE+TTBkFCE /6gWeli/bxQeKQ1fnL7qROYl8TAGF4Aiou53fRz+Fcc9Mdbu48m4ToC0DITHi1qXyRXn krKMcKbsJpBq9jGNJ0ryzNNG8f5WALZW85Epo114z1LXaQFIrsTgCUt3U2zoV4wGy13z VuAg== X-Gm-Message-State: ALoCoQkz3SiIh9iuyTVSqTqYloccmJRX00AxKJnxDHGcN/2hzEJjTEFlSzeZ8svRS8Nzm/sARo3c MIME-Version: 1.0 X-Received: by 10.180.75.229 with SMTP id f5mr19302218wiw.81.1412602347459; Mon, 06 Oct 2014 06:32:27 -0700 (PDT) Received: by 10.194.239.7 with HTTP; Mon, 6 Oct 2014 06:32:27 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Oct 2014 09:32:27 -0400 Message-ID: From: Sarah Conway To: "publicity@lists.xenproject.org" , Advisory-board discussions Subject: Re: [Publicity] More XSA 108 Coverage X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7835574388137080113==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============7835574388137080113== Content-Type: multipart/alternative; boundary=f46d04389061212f030504c11dd0 --f46d04389061212f030504c11dd0 Content-Type: text/plain; charset=UTF-8 FYI, some more XSA-108 from late Friday and over the weekend. http://www.informationweek.com/cloud/platform-as-a-service/cloud-suppliers-quickly-patched-xen-bug/d/d-id/1316312 The Xen bug is both a good example of collective security and a warning of what can happen as IT shifts toward a greater reliance on cloud computing. The bug was discovered and interested parties notified before the full nature of the exploit was disclosed. Collective security action followed, apparently (at this early date) in time before any malicious code writers could act on the disclosure. At the same time, the bug illustrates the cloud's dependence on one hypervisor or another and how a major hypervisor bug will affect more than one supplier. The growing, more uniform nature of x86 cloud environments represent a fatter target for highly skilled intruders to aim for, and a richer environment for manipulation if they succeed at getting inside. http://www.theinquirer.net/inquirer/news/2373890/xen-reveals-serious-security-bug-that-affected-cloud-servers Responsible vulnerability disclosure is an ongoing matter of debate in the technology community. Google announced a wave of reforms to its Chrome Bug Bounty Programme's submission policy on 1 October designed to make it easier for hunters http://www.usnews.com/news/articles/2014/10/02/will-cloud-security-kill-the-password Article mostly about iCloud server security breach, weak passwords. Xen Project listed as another cloud security example. The latest security gap in a cloud-computing system was announced Thursday by the Xen Project software group, which has released a patch to repair a flaw in its platform that could affect cloud services offered by Amazon and Rackspace. On Fri, Oct 3, 2014 at 4:14 PM, Sarah Conway wrote: > Hi everyone. > > In addition to eWeek, WSJ and ITNews, here is more coverage appearing > since the advisory and blogs were issued this week. > > Thanks, > > Rackspace Joins Amazon in Cloud Reboot Over Xen Hypervisor Bug > > http://vmblog.com/archive/2014/09/29/rackspace-joins-amazon-in-cloud-reboot-over-xen-hypervisor-bug.aspx > > Understanding The Xen XSA-108 Security Issue > http://www.phoronix.com/scan.php?page=news_item&px=MTgwMjQ > > Xen sheds light on 'serious' security bug affecting servers > > http://www.v3.co.uk/v3-uk/news/2373641/xen-sheds-light-on-serious-security-bug-affecting-servers > > Xen reveals XSA-108 memory leak bug details > > http://www.techrepublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/ > > Google cuts cloud computing prices > > http://www.techrepublic.com/article/google-cuts-cloud-computing-prices-gives-away-unlimited-storage-to-students/ > > Are Google's even lower prices -- and not using Xen -- tantalizing enough > to switch to its services? Are the costs low enough to warrant a migration? > Do you use Google Apps for Work, or Education? Let us know in the comments. > > Serious hypervisor bug fix causes unexpected cloud downtime > > http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660 > > (reporter we "talked" to on Twitter) > > CoreOS eliminates downtime from server OS patching > > http://www.techrepublic.com/article/coreos-eliminates-downtime-from-server-os-patching/ > > CoreOS commentary on XSA-108 > > The Shellshock vulnerability and the even more recent Xen hypervisor > vulnerability remind us of an important fact of enterprise IT: server OS > patching is hard > > CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex > Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve > patching headaches. The long-term value proposition of the CoreOS primary > product of the same name is to bring Google Chrome-like updates to server > updates. > > > > -- > Sarah Conway > PR Manager > The Linux Foundation > sconway@linuxfoundation.org > (978) 578-5300 Cell > Skype: sarah.k.conway > -- Sarah Conway PR Manager The Linux Foundation sconway@linuxfoundation.org (978) 578-5300 Cell Skype: sarah.k.conway --f46d04389061212f030504c11dd0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
FYI, some more XSA-108 from late Friday and over the weeke= nd.

The Xen bug is both a= good example of collective security and a warning of what can happen as IT= shifts toward a greater reliance on cloud computing. The bug was discovere= d and interested parties notified before the full nature of the exploit was= disclosed. Collective security action followed, apparently (at this early = date) in time before any malicious code writers could act on the disclosure= .

At the same time, the bug illustrates the cloud's dependence on = one hypervisor or another and how a major hypervisor bug will affect more t= han one supplier. The growing, more uniform nature of x86 cloud environment= s represent a fatter target for highly skilled intruders to aim for, and a = richer environment for manipulation if they succeed at getting inside.

<= p style=3D"padding:0px;margin:1em 0px;color:rgb(65,63,65);border:0px;font-s= ize:1.08333em;line-height:1.38462em;font-family:Helvetica,Arial,sans-serif"= >http://www.theinquirer.net/inquirer/news/237= 3890/xen-reveals-serious-security-bug-that-affected-cloud-servers

Responsible=C2=A0vulnerability=C2=A0disclosure is an ongoin= g matter of debate in the technology community.=C2=A0Google announced a wave of reforms to its Chrome Bug Bounty Progr= amme's submission policy=C2=A0on 1 October designed to= make it easier for hunters

http://www.us= news.com/news/articles/2014/10/02/will-cloud-security-kill-the-password=

Article mostly about iCloud server security b= reach, weak passwords. Xen Project listed as another cloud security example= .

The latest security gap in a cloud-computing = system was=C2=A0announced=C2=A0Thursday by the Xen Project software group, w= hich has released a patch to repair a flaw in its platform that could affec= t cloud services offered by Amazon and Rackspace.


On Fri, Oct 3, 2014 at 4:14= PM, Sarah Conway <sconway@linuxfoundation.org> wr= ote:
Hi everyone.

I= n addition to eWeek, WSJ and ITNews, here is more coverage appearing since = the advisory and blogs were issued this week.

Thank= s,

Xen = sheds light on 'serious' security bug affecting servers
http://www.v3.co.uk/v3-uk/news= /2373641/xen-sheds-light-on-serious-security-bug-affecting-servers
<= br>
Are Googl= e's even lower prices -- and not using Xen -- tantalizing enough to swi= tch to its services? Are the costs low enough to warrant a migration? Do yo= u use Google Apps for Work, or Education? Let us know in the comments.
<= br>
Serious hypervisor bug fix causes unexpected cloud downtimehttp://threatpost.com/serious= -hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660

(reporter we "talked" to on Twitter)

CoreOS eliminates downtime from server OS patch= ing
http://www.techrepublic.c= om/article/coreos-eliminates-downtime-from-server-os-patching/

<= /div>
CoreOS commentary on XSA-108

The Shellshock vul= nerability and the even more recent Xen hypervisor vulnerability remind us = of an important fact of enterprise IT: server OS patching is hard

CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex P= olvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve patch= ing headaches. The long-term value proposition of the CoreOS primary produc= t of the same name is to bring Google Chrome-like updates to server updates= .



--
Sarah Conway
PR Manager
The Linux Foundationsconway@= linuxfoundation.org
(978) 578-5300 =C2=A0Cell
Skype: =C2= =A0sarah.k.conway



--
Sarah Conway
PR Manager
The Linux Foundat= ion
sco= nway@linuxfoundation.org
(978) 578-5300 =C2=A0Cell
= Skype: =C2=A0sarah.k.conway
--f46d04389061212f030504c11dd0-- --===============7835574388137080113== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============7835574388137080113==-- From publicity-bounces@lists.xenproject.org Mon Oct 06 13:32:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 06 Oct 2014 13:32:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xb8Ou-0000mX-Ut; Mon, 06 Oct 2014 13:32:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Xb8Os-0000mK-T4 for publicity@lists.xenproject.org; Mon, 06 Oct 2014 13:32:31 +0000 Received: from [85.158.143.35:9292] by server-2.bemta-4.messagelabs.com id D1/10-04525-EE992345; Mon, 06 Oct 2014 13:32:30 +0000 X-Env-Sender: sconway@linuxfoundation.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1412602347!14066258!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=3.2 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60, HTML_FONT_LOW_CONTRAST, HTML_MESSAGE, HTML_TINY_FONT, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19722 invoked from network); 6 Oct 2014 13:32:28 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Oct 2014 13:32:28 -0000 Received: by mail-wi0-f180.google.com with SMTP id em10so4621037wid.1 for ; Mon, 06 Oct 2014 06:32:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=p7TFoVlxTcNY/3Y8ZX9NmqlphFGCRX86trYxDSuQ604=; b=Hryh8Mzhf48ZgDtN9fIlsS9Po/XozuWbHrYi5jTgp/cICbBDO3DBS2u+I3wgaXPo8x N1czE0hyf36DBICJq4y/HqcSy+T89CqulCeA5KKgHtVr10i20/JLgMiDeZBJrsw/CpCc N9cfjsRyvDeHGArfxULIELnE4pgSSM7KBKvEI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=p7TFoVlxTcNY/3Y8ZX9NmqlphFGCRX86trYxDSuQ604=; b=FLLd1t5NlLwVDgaD+Pt2e3bAp8S4mhLgBUOJdkab8IyRpwYfNv6b0DyBOIeGov8Suq Yrx8sO5Ep8e5aWQeoQLK9u9Q+DlEmiLnngKuqfIIGntM11lfeUG1KaxmnBOGRjlJUhAF VsWjYktNyoVUUcx0JQFz7Vdm7pYFkQcZdYjhHHsFXg7nK5PFC1xZ2D0SMUOE+TTBkFCE /6gWeli/bxQeKQ1fnL7qROYl8TAGF4Aiou53fRz+Fcc9Mdbu48m4ToC0DITHi1qXyRXn krKMcKbsJpBq9jGNJ0ryzNNG8f5WALZW85Epo114z1LXaQFIrsTgCUt3U2zoV4wGy13z VuAg== X-Gm-Message-State: ALoCoQkz3SiIh9iuyTVSqTqYloccmJRX00AxKJnxDHGcN/2hzEJjTEFlSzeZ8svRS8Nzm/sARo3c MIME-Version: 1.0 X-Received: by 10.180.75.229 with SMTP id f5mr19302218wiw.81.1412602347459; Mon, 06 Oct 2014 06:32:27 -0700 (PDT) Received: by 10.194.239.7 with HTTP; Mon, 6 Oct 2014 06:32:27 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 Oct 2014 09:32:27 -0400 Message-ID: From: Sarah Conway To: "publicity@lists.xenproject.org" , Advisory-board discussions Subject: Re: [Publicity] More XSA 108 Coverage X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7835574388137080113==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============7835574388137080113== Content-Type: multipart/alternative; boundary=f46d04389061212f030504c11dd0 --f46d04389061212f030504c11dd0 Content-Type: text/plain; charset=UTF-8 FYI, some more XSA-108 from late Friday and over the weekend. http://www.informationweek.com/cloud/platform-as-a-service/cloud-suppliers-quickly-patched-xen-bug/d/d-id/1316312 The Xen bug is both a good example of collective security and a warning of what can happen as IT shifts toward a greater reliance on cloud computing. The bug was discovered and interested parties notified before the full nature of the exploit was disclosed. Collective security action followed, apparently (at this early date) in time before any malicious code writers could act on the disclosure. At the same time, the bug illustrates the cloud's dependence on one hypervisor or another and how a major hypervisor bug will affect more than one supplier. The growing, more uniform nature of x86 cloud environments represent a fatter target for highly skilled intruders to aim for, and a richer environment for manipulation if they succeed at getting inside. http://www.theinquirer.net/inquirer/news/2373890/xen-reveals-serious-security-bug-that-affected-cloud-servers Responsible vulnerability disclosure is an ongoing matter of debate in the technology community. Google announced a wave of reforms to its Chrome Bug Bounty Programme's submission policy on 1 October designed to make it easier for hunters http://www.usnews.com/news/articles/2014/10/02/will-cloud-security-kill-the-password Article mostly about iCloud server security breach, weak passwords. Xen Project listed as another cloud security example. The latest security gap in a cloud-computing system was announced Thursday by the Xen Project software group, which has released a patch to repair a flaw in its platform that could affect cloud services offered by Amazon and Rackspace. On Fri, Oct 3, 2014 at 4:14 PM, Sarah Conway wrote: > Hi everyone. > > In addition to eWeek, WSJ and ITNews, here is more coverage appearing > since the advisory and blogs were issued this week. > > Thanks, > > Rackspace Joins Amazon in Cloud Reboot Over Xen Hypervisor Bug > > http://vmblog.com/archive/2014/09/29/rackspace-joins-amazon-in-cloud-reboot-over-xen-hypervisor-bug.aspx > > Understanding The Xen XSA-108 Security Issue > http://www.phoronix.com/scan.php?page=news_item&px=MTgwMjQ > > Xen sheds light on 'serious' security bug affecting servers > > http://www.v3.co.uk/v3-uk/news/2373641/xen-sheds-light-on-serious-security-bug-affecting-servers > > Xen reveals XSA-108 memory leak bug details > > http://www.techrepublic.com/article/xen-reveals-xsa-108-memory-leak-bug-details/ > > Google cuts cloud computing prices > > http://www.techrepublic.com/article/google-cuts-cloud-computing-prices-gives-away-unlimited-storage-to-students/ > > Are Google's even lower prices -- and not using Xen -- tantalizing enough > to switch to its services? Are the costs low enough to warrant a migration? > Do you use Google Apps for Work, or Education? Let us know in the comments. > > Serious hypervisor bug fix causes unexpected cloud downtime > > http://threatpost.com/serious-hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660 > > (reporter we "talked" to on Twitter) > > CoreOS eliminates downtime from server OS patching > > http://www.techrepublic.com/article/coreos-eliminates-downtime-from-server-os-patching/ > > CoreOS commentary on XSA-108 > > The Shellshock vulnerability and the even more recent Xen hypervisor > vulnerability remind us of an important fact of enterprise IT: server OS > patching is hard > > CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex > Polvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve > patching headaches. The long-term value proposition of the CoreOS primary > product of the same name is to bring Google Chrome-like updates to server > updates. > > > > -- > Sarah Conway > PR Manager > The Linux Foundation > sconway@linuxfoundation.org > (978) 578-5300 Cell > Skype: sarah.k.conway > -- Sarah Conway PR Manager The Linux Foundation sconway@linuxfoundation.org (978) 578-5300 Cell Skype: sarah.k.conway --f46d04389061212f030504c11dd0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
FYI, some more XSA-108 from late Friday and over the weeke= nd.

The Xen bug is both a= good example of collective security and a warning of what can happen as IT= shifts toward a greater reliance on cloud computing. The bug was discovere= d and interested parties notified before the full nature of the exploit was= disclosed. Collective security action followed, apparently (at this early = date) in time before any malicious code writers could act on the disclosure= .

At the same time, the bug illustrates the cloud's dependence on = one hypervisor or another and how a major hypervisor bug will affect more t= han one supplier. The growing, more uniform nature of x86 cloud environment= s represent a fatter target for highly skilled intruders to aim for, and a = richer environment for manipulation if they succeed at getting inside.

<= p style=3D"padding:0px;margin:1em 0px;color:rgb(65,63,65);border:0px;font-s= ize:1.08333em;line-height:1.38462em;font-family:Helvetica,Arial,sans-serif"= >http://www.theinquirer.net/inquirer/news/237= 3890/xen-reveals-serious-security-bug-that-affected-cloud-servers

Responsible=C2=A0vulnerability=C2=A0disclosure is an ongoin= g matter of debate in the technology community.=C2=A0Google announced a wave of reforms to its Chrome Bug Bounty Progr= amme's submission policy=C2=A0on 1 October designed to= make it easier for hunters

http://www.us= news.com/news/articles/2014/10/02/will-cloud-security-kill-the-password=

Article mostly about iCloud server security b= reach, weak passwords. Xen Project listed as another cloud security example= .

The latest security gap in a cloud-computing = system was=C2=A0announced=C2=A0Thursday by the Xen Project software group, w= hich has released a patch to repair a flaw in its platform that could affec= t cloud services offered by Amazon and Rackspace.


On Fri, Oct 3, 2014 at 4:14= PM, Sarah Conway <sconway@linuxfoundation.org> wr= ote:
Hi everyone.

I= n addition to eWeek, WSJ and ITNews, here is more coverage appearing since = the advisory and blogs were issued this week.

Thank= s,

Xen = sheds light on 'serious' security bug affecting servers
http://www.v3.co.uk/v3-uk/news= /2373641/xen-sheds-light-on-serious-security-bug-affecting-servers
<= br>
Are Googl= e's even lower prices -- and not using Xen -- tantalizing enough to swi= tch to its services? Are the costs low enough to warrant a migration? Do yo= u use Google Apps for Work, or Education? Let us know in the comments.
<= br>
Serious hypervisor bug fix causes unexpected cloud downtimehttp://threatpost.com/serious= -hypervisor-bug-fix-causes-unexpected-cloud-downtime/108660

(reporter we "talked" to on Twitter)

CoreOS eliminates downtime from server OS patch= ing
http://www.techrepublic.c= om/article/coreos-eliminates-downtime-from-server-os-patching/

<= /div>
CoreOS commentary on XSA-108

The Shellshock vul= nerability and the even more recent Xen hypervisor vulnerability remind us = of an important fact of enterprise IT: server OS patching is hard

CoreOS is trying to simplify OS patching. According to CoreOS CEO Alex P= olvi, who was a guest on a recent Cloudcast podcast, CoreOS can solve patch= ing headaches. The long-term value proposition of the CoreOS primary produc= t of the same name is to bring Google Chrome-like updates to server updates= .



--
Sarah Conway
PR Manager
The Linux Foundationsconway@= linuxfoundation.org
(978) 578-5300 =C2=A0Cell
Skype: =C2= =A0sarah.k.conway



--
Sarah Conway
PR Manager
The Linux Foundat= ion
sco= nway@linuxfoundation.org
(978) 578-5300 =C2=A0Cell
= Skype: =C2=A0sarah.k.conway
--f46d04389061212f030504c11dd0-- --===============7835574388137080113== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============7835574388137080113==-- From publicity-bounces@lists.xenproject.org Tue Oct 07 15:18:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:18:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWXQ-0008DP-6H; Tue, 07 Oct 2014 15:18:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWXP-0008DH-CJ for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:18:55 +0000 Received: from [85.158.139.211:42981] by server-14.bemta-5.messagelabs.com id 62/B1-12422-E5404345; Tue, 07 Oct 2014 15:18:54 +0000 X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1412695134!12560420!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5607 invoked from network); 7 Oct 2014 15:18:54 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:18:54 -0000 X-IronPort-AV: E=Sophos;i="5.04,670,1406592000"; d="scan'208";a="25769314" From: Lars Kurth To: Paul Durrant Thread-Topic: blog post Thread-Index: Ac/haZk+buXaoghaT3SWFRH83CqE9gAjPO0A Date: Tue, 7 Oct 2014 15:18:49 +0000 Message-ID: References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.4.140807 Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Paul, the trick is to only save the blog post as draft, select preview and post that link and not to publish the post. You can also schedule it for a future date. We then tend to send a link of the drafted post to publicity@lists.xenproject.org for review But let me have a look and see whether I can fix it, such that others editors can see and review the post before publication Regards Lars On 06/10/2014 14:31, "Paul Durrant" wrote: >Lars, > > I prepared a blog post at >https://blog.xenproject.org/2014/09/18/introducing-the-xen-project-windows >-pv-drivers. I'm not sure anyone but me can see it though; I made it >private as I could not figure out how to make it public without actually >having it appear in 'recent posts' on the front page. Can you access the >link? > > Paul _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:18:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:18:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWXQ-0008DP-6H; Tue, 07 Oct 2014 15:18:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWXP-0008DH-CJ for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:18:55 +0000 Received: from [85.158.139.211:42981] by server-14.bemta-5.messagelabs.com id 62/B1-12422-E5404345; Tue, 07 Oct 2014 15:18:54 +0000 X-Env-Sender: lars.kurth@citrix.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1412695134!12560420!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5607 invoked from network); 7 Oct 2014 15:18:54 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:18:54 -0000 X-IronPort-AV: E=Sophos;i="5.04,670,1406592000"; d="scan'208";a="25769314" From: Lars Kurth To: Paul Durrant Thread-Topic: blog post Thread-Index: Ac/haZk+buXaoghaT3SWFRH83CqE9gAjPO0A Date: Tue, 7 Oct 2014 15:18:49 +0000 Message-ID: References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.4.140807 Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Paul, the trick is to only save the blog post as draft, select preview and post that link and not to publish the post. You can also schedule it for a future date. We then tend to send a link of the drafted post to publicity@lists.xenproject.org for review But let me have a look and see whether I can fix it, such that others editors can see and review the post before publication Regards Lars On 06/10/2014 14:31, "Paul Durrant" wrote: >Lars, > > I prepared a blog post at >https://blog.xenproject.org/2014/09/18/introducing-the-xen-project-windows >-pv-drivers. I'm not sure anyone but me can see it though; I made it >private as I could not figure out how to make it public without actually >having it appear in 'recent posts' on the front page. Can you access the >link? > > Paul _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:25:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:25:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWdL-0008NP-NU; Tue, 07 Oct 2014 15:25:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWdK-0008NK-J1 for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:25:02 +0000 Received: from [85.158.143.35:56871] by server-1.bemta-4.messagelabs.com id A5/7C-05872-DC504345; Tue, 07 Oct 2014 15:25:01 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1412695501!14397483!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18903 invoked from network); 7 Oct 2014 15:25:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:25:01 -0000 X-IronPort-AV: E=Sophos;i="5.04,670,1406592000"; d="scan'208";a="25769523" From: Paul Durrant To: Lars Kurth Thread-Topic: blog post Thread-Index: Ac/haZk+buXaoghaT3SWFRH83CqE9gAjPO0AABMQ24A= Date: Tue, 7 Oct 2014 15:25:00 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA65F@AMSPEX01CL01.citrite.net> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: AMS1 Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org > -----Original Message----- > From: Lars Kurth > Sent: 07 October 2014 16:19 > To: Paul Durrant > Cc: publicity@lists.xenproject.org > Subject: Re: blog post > > Paul, > > the trick is to only save the blog post as draft, select preview and post > that link and not to publish the post. You can also schedule it for a > future date. We then tend to send a link of the drafted post to > publicity@lists.xenproject.org for review > > But let me have a look and see whether I can fix it, such that others > editors can see and review the post before publication > Ok. Thanks. Paul > Regards > Lars > > On 06/10/2014 14:31, "Paul Durrant" wrote: > > >Lars, > > > > I prepared a blog post at > >https://blog.xenproject.org/2014/09/18/introducing-the-xen-project- > windows > >-pv-drivers. I'm not sure anyone but me can see it though; I made it > >private as I could not figure out how to make it public without actually > >having it appear in 'recent posts' on the front page. Can you access the > >link? > > > > Paul _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:25:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:25:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWdL-0008NP-NU; Tue, 07 Oct 2014 15:25:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWdK-0008NK-J1 for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:25:02 +0000 Received: from [85.158.143.35:56871] by server-1.bemta-4.messagelabs.com id A5/7C-05872-DC504345; Tue, 07 Oct 2014 15:25:01 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1412695501!14397483!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18903 invoked from network); 7 Oct 2014 15:25:01 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:25:01 -0000 X-IronPort-AV: E=Sophos;i="5.04,670,1406592000"; d="scan'208";a="25769523" From: Paul Durrant To: Lars Kurth Thread-Topic: blog post Thread-Index: Ac/haZk+buXaoghaT3SWFRH83CqE9gAjPO0AABMQ24A= Date: Tue, 7 Oct 2014 15:25:00 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA65F@AMSPEX01CL01.citrite.net> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: AMS1 Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org > -----Original Message----- > From: Lars Kurth > Sent: 07 October 2014 16:19 > To: Paul Durrant > Cc: publicity@lists.xenproject.org > Subject: Re: blog post > > Paul, > > the trick is to only save the blog post as draft, select preview and post > that link and not to publish the post. You can also schedule it for a > future date. We then tend to send a link of the drafted post to > publicity@lists.xenproject.org for review > > But let me have a look and see whether I can fix it, such that others > editors can see and review the post before publication > Ok. Thanks. Paul > Regards > Lars > > On 06/10/2014 14:31, "Paul Durrant" wrote: > > >Lars, > > > > I prepared a blog post at > >https://blog.xenproject.org/2014/09/18/introducing-the-xen-project- > windows > >-pv-drivers. I'm not sure anyone but me can see it though; I made it > >private as I could not figure out how to make it public without actually > >having it appear in 'recent posts' on the front page. Can you access the > >link? > > > > Paul _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:26:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:26:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWf2-0008OL-T0; Tue, 07 Oct 2014 15:26:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWf2-0008OG-5S for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:26:48 +0000 Received: from [85.158.143.35:19332] by server-3.bemta-4.messagelabs.com id 51/24-06192-73604345; Tue, 07 Oct 2014 15:26:47 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1412695606!11930289!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4395 invoked from network); 7 Oct 2014 15:26:46 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:26:46 -0000 Received: by mail-wg0-f50.google.com with SMTP id a1so9442580wgh.21 for ; Tue, 07 Oct 2014 08:26:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FidT6GKmQb6eW5+O2XbR8l0TMc8u4whL+zv2zHuF1qE=; b=clGyrm6GslC/dvMjbM2TqitiLcI2n/JbSoXboedpPS5wmxTFP4IGifrtKzxcgVRVuU 95pgHEV2flLhMtXUF43OGWf6ci2JK+d2TBYXicl7xN2BUE5cCzMROCpFPVztDYnCl9dZ X7NkBUPYYZCxsE5k8MNQLajrKOqE0qi4nRxH+bl+EI/nueRG9ritMQLb063BA9jNmXxS vJJ/28yNhGMoJyMGyFs7fAK9+hzHPSAT+8knMKGeZTH6AtaAcZxvUlLNk5HEYwtQAALg WfbE3HPwcCfD9IDUUpYlCMhXC/+Mw8ofxWT+jL6sYQpZ261HgfAk8UD6XTHXfeIB1b66 sm7Q== X-Received: by 10.180.90.136 with SMTP id bw8mr27917205wib.42.1412695606622; Tue, 07 Oct 2014 08:26:46 -0700 (PDT) Received: from [107.18.164.209] ([107.18.164.209]) by mx.google.com with ESMTPSA id gg18sm15113008wic.21.2014.10.07.08.26.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 08:26:45 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: Date: Tue, 7 Oct 2014 08:26:40 -0700 Message-Id: <47412E4C-4695-48FB-937C-E4B4B47D4804@gmail.com> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> To: Lars Kurth X-Mailer: Apple Mail (2.1878.6) Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Paul, I made a few formatting changes. Otherwise it looks good and go ahead and p= ublish: because you published it as private, you need to do the following: a) Set the date to a date in the future by going to the edit link besides t= he date (a few minutes past your current time) - of you don=92t it may appe= ar in the past in the blog feed b) Set to public Regards Lars On 7 Oct 2014, at 08:18, Lars Kurth wrote: > Paul, > = > the trick is to only save the blog post as draft, select preview and post > that link and not to publish the post. You can also schedule it for a > future date. We then tend to send a link of the drafted post to > publicity@lists.xenproject.org for review > = > But let me have a look and see whether I can fix it, such that others > editors can see and review the post before publication > = > Regards > Lars > = > On 06/10/2014 14:31, "Paul Durrant" wrote: > = >> Lars, >> = >> I prepared a blog post at >> https://blog.xenproject.org/2014/09/18/introducing-the-xen-project-windo= ws >> -pv-drivers. I'm not sure anyone but me can see it though; I made it >> private as I could not figure out how to make it public without actually >> having it appear in 'recent posts' on the front page. Can you access the >> link? >> = >> Paul > = > = > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:26:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:26:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWf2-0008OL-T0; Tue, 07 Oct 2014 15:26:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWf2-0008OG-5S for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:26:48 +0000 Received: from [85.158.143.35:19332] by server-3.bemta-4.messagelabs.com id 51/24-06192-73604345; Tue, 07 Oct 2014 15:26:47 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1412695606!11930289!1 X-Originating-IP: [74.125.82.50] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4395 invoked from network); 7 Oct 2014 15:26:46 -0000 Received: from mail-wg0-f50.google.com (HELO mail-wg0-f50.google.com) (74.125.82.50) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:26:46 -0000 Received: by mail-wg0-f50.google.com with SMTP id a1so9442580wgh.21 for ; Tue, 07 Oct 2014 08:26:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=FidT6GKmQb6eW5+O2XbR8l0TMc8u4whL+zv2zHuF1qE=; b=clGyrm6GslC/dvMjbM2TqitiLcI2n/JbSoXboedpPS5wmxTFP4IGifrtKzxcgVRVuU 95pgHEV2flLhMtXUF43OGWf6ci2JK+d2TBYXicl7xN2BUE5cCzMROCpFPVztDYnCl9dZ X7NkBUPYYZCxsE5k8MNQLajrKOqE0qi4nRxH+bl+EI/nueRG9ritMQLb063BA9jNmXxS vJJ/28yNhGMoJyMGyFs7fAK9+hzHPSAT+8knMKGeZTH6AtaAcZxvUlLNk5HEYwtQAALg WfbE3HPwcCfD9IDUUpYlCMhXC/+Mw8ofxWT+jL6sYQpZ261HgfAk8UD6XTHXfeIB1b66 sm7Q== X-Received: by 10.180.90.136 with SMTP id bw8mr27917205wib.42.1412695606622; Tue, 07 Oct 2014 08:26:46 -0700 (PDT) Received: from [107.18.164.209] ([107.18.164.209]) by mx.google.com with ESMTPSA id gg18sm15113008wic.21.2014.10.07.08.26.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 08:26:45 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: Date: Tue, 7 Oct 2014 08:26:40 -0700 Message-Id: <47412E4C-4695-48FB-937C-E4B4B47D4804@gmail.com> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> To: Lars Kurth X-Mailer: Apple Mail (2.1878.6) Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org Paul, I made a few formatting changes. Otherwise it looks good and go ahead and p= ublish: because you published it as private, you need to do the following: a) Set the date to a date in the future by going to the edit link besides t= he date (a few minutes past your current time) - of you don=92t it may appe= ar in the past in the blog feed b) Set to public Regards Lars On 7 Oct 2014, at 08:18, Lars Kurth wrote: > Paul, > = > the trick is to only save the blog post as draft, select preview and post > that link and not to publish the post. You can also schedule it for a > future date. We then tend to send a link of the drafted post to > publicity@lists.xenproject.org for review > = > But let me have a look and see whether I can fix it, such that others > editors can see and review the post before publication > = > Regards > Lars > = > On 06/10/2014 14:31, "Paul Durrant" wrote: > = >> Lars, >> = >> I prepared a blog post at >> https://blog.xenproject.org/2014/09/18/introducing-the-xen-project-windo= ws >> -pv-drivers. I'm not sure anyone but me can see it though; I made it >> private as I could not figure out how to make it public without actually >> having it appear in 'recent posts' on the front page. Can you access the >> link? >> = >> Paul > = > = > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:29:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:29:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWhs-000064-MG; Tue, 07 Oct 2014 15:29:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWhr-00005j-Ez for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:29:43 +0000 Received: from [85.158.139.211:10333] by server-11.bemta-5.messagelabs.com id 4C/2C-11011-6E604345; Tue, 07 Oct 2014 15:29:42 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1412695782!7248755!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31651 invoked from network); 7 Oct 2014 15:29:42 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:29:42 -0000 X-IronPort-AV: E=Sophos;i="5.04,670,1406592000"; d="scan'208";a="25769753" From: Paul Durrant To: Lars Kurth , Lars Kurth Thread-Topic: [Publicity] blog post Thread-Index: Ac/haZk+buXaoghaT3SWFRH83CqE9gAjPO0AAA7xuQAABEma4A== Date: Tue, 7 Oct 2014 15:29:40 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA6BB@AMSPEX01CL01.citrite.net> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> <47412E4C-4695-48FB-937C-E4B4B47D4804@gmail.com> In-Reply-To: <47412E4C-4695-48FB-937C-E4B4B47D4804@gmail.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: AMS1 Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org > -----Original Message----- > From: Lars Kurth [mailto:lars.kurth.xen@gmail.com] > Sent: 07 October 2014 16:27 > To: Lars Kurth > Cc: Paul Durrant; publicity@lists.xenproject.org > Subject: Re: [Publicity] blog post > > Paul, > I made a few formatting changes. Otherwise it looks good and go ahead and > publish: because you published it as private, you need to do the following: > a) Set the date to a date in the future by going to the edit link besides the > date (a few minutes past your current time) - of you don't it may appear in > the past in the blog feed > b) Set to public > Regards > Lars > Ok, will do. Paul > On 7 Oct 2014, at 08:18, Lars Kurth wrote: > > > Paul, > > > > the trick is to only save the blog post as draft, select preview and post > > that link and not to publish the post. You can also schedule it for a > > future date. We then tend to send a link of the drafted post to > > publicity@lists.xenproject.org for review > > > > But let me have a look and see whether I can fix it, such that others > > editors can see and review the post before publication > > > > Regards > > Lars > > > > On 06/10/2014 14:31, "Paul Durrant" wrote: > > > >> Lars, > >> > >> I prepared a blog post at > >> https://blog.xenproject.org/2014/09/18/introducing-the-xen-project- > windows > >> -pv-drivers. I'm not sure anyone but me can see it though; I made it > >> private as I could not figure out how to make it public without actually > >> having it appear in 'recent posts' on the front page. Can you access the > >> link? > >> > >> Paul > > > > > > _______________________________________________ > > Publicity mailing list > > Publicity@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:29:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:29:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWhs-000064-MG; Tue, 07 Oct 2014 15:29:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWhr-00005j-Ez for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:29:43 +0000 Received: from [85.158.139.211:10333] by server-11.bemta-5.messagelabs.com id 4C/2C-11011-6E604345; Tue, 07 Oct 2014 15:29:42 +0000 X-Env-Sender: Paul.Durrant@citrix.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1412695782!7248755!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31651 invoked from network); 7 Oct 2014 15:29:42 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:29:42 -0000 X-IronPort-AV: E=Sophos;i="5.04,670,1406592000"; d="scan'208";a="25769753" From: Paul Durrant To: Lars Kurth , Lars Kurth Thread-Topic: [Publicity] blog post Thread-Index: Ac/haZk+buXaoghaT3SWFRH83CqE9gAjPO0AAA7xuQAABEma4A== Date: Tue, 7 Oct 2014 15:29:40 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA6BB@AMSPEX01CL01.citrite.net> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> <47412E4C-4695-48FB-937C-E4B4B47D4804@gmail.com> In-Reply-To: <47412E4C-4695-48FB-937C-E4B4B47D4804@gmail.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 X-DLP: AMS1 Cc: "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org > -----Original Message----- > From: Lars Kurth [mailto:lars.kurth.xen@gmail.com] > Sent: 07 October 2014 16:27 > To: Lars Kurth > Cc: Paul Durrant; publicity@lists.xenproject.org > Subject: Re: [Publicity] blog post > > Paul, > I made a few formatting changes. Otherwise it looks good and go ahead and > publish: because you published it as private, you need to do the following: > a) Set the date to a date in the future by going to the edit link besides the > date (a few minutes past your current time) - of you don't it may appear in > the past in the blog feed > b) Set to public > Regards > Lars > Ok, will do. Paul > On 7 Oct 2014, at 08:18, Lars Kurth wrote: > > > Paul, > > > > the trick is to only save the blog post as draft, select preview and post > > that link and not to publish the post. You can also schedule it for a > > future date. We then tend to send a link of the drafted post to > > publicity@lists.xenproject.org for review > > > > But let me have a look and see whether I can fix it, such that others > > editors can see and review the post before publication > > > > Regards > > Lars > > > > On 06/10/2014 14:31, "Paul Durrant" wrote: > > > >> Lars, > >> > >> I prepared a blog post at > >> https://blog.xenproject.org/2014/09/18/introducing-the-xen-project- > windows > >> -pv-drivers. I'm not sure anyone but me can see it though; I made it > >> private as I could not figure out how to make it public without actually > >> having it appear in 'recent posts' on the front page. Can you access the > >> link? > >> > >> Paul > > > > > > _______________________________________________ > > Publicity mailing list > > Publicity@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Tue Oct 07 15:30:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWiJ-00009P-Od; Tue, 07 Oct 2014 15:30:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWiH-00008u-JC for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:30:09 +0000 Received: from [85.158.137.68:21371] by server-16.bemta-3.messagelabs.com id 81/59-01431-00704345; Tue, 07 Oct 2014 15:30:08 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1412695807!8307892!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5398 invoked from network); 7 Oct 2014 15:30:07 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:30:07 -0000 Received: by mail-wg0-f41.google.com with SMTP id b13so9761066wgh.24 for ; Tue, 07 Oct 2014 08:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=I3lfhGJ2Gdcr6I1P2YfcBAfqMc02NzNbNaZgCxisZys=; b=d00tmbQgAXX1sKerDRLzzKB4UqXxGq8jrLUK/y490XGh8t2TotsglKX0oJLJQAeEn+ xTvgpSLvLOQVT7Uccv/j+Ra3wvICpN5ux6ov1EIfktJWthBPPJq/13nhy1UkRmJzCcRY idMPgVFGFHMzPpwLYfkqQ9cBQ0sI1DyGTeIpcBn+GwAYbflcg7DujyVtllhjfal/cUrn R4sZK/4od81YwmurETVCh9u1TwvmG31GFonUSUY/GgQo8JGQdvzogaf2o/seUdiMsb3g rHlr96YK8ANYca3/dtvbBF60MVssFoLSSL4WGogQLXH+goofLrbtOgKN/VzppA2cxlNz zhYQ== X-Received: by 10.180.187.83 with SMTP id fq19mr27870938wic.59.1412695807490; Tue, 07 Oct 2014 08:30:07 -0700 (PDT) Received: from [107.18.164.209] ([107.18.164.209]) by mx.google.com with ESMTPSA id os4sm20219382wjc.48.2014.10.07.08.30.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 08:30:06 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA65F@AMSPEX01CL01.citrite.net> Date: Tue, 7 Oct 2014 08:30:02 -0700 Message-Id: <5D6B7B79-E7A4-4976-AD09-2AE23D968E24@gmail.com> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA65F@AMSPEX01CL01.citrite.net> To: Paul Durrant X-Mailer: Apple Mail (2.1878.6) Cc: Lars Kurth , "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1052425844064591412==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============1052425844064591412== Content-Type: multipart/alternative; boundary="Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC" --Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 7 Oct 2014, at 08:25, Paul Durrant wrote: >> -----Original Message----- >> From: Lars Kurth >> Sent: 07 October 2014 16:19 >> To: Paul Durrant >> Cc: publicity@lists.xenproject.org >> Subject: Re: blog post >>=20 >> Paul, >>=20 >> the trick is to only save the blog post as draft, select preview and = post >> that link and not to publish the post. You can also schedule it for a >> future date. We then tend to send a link of the drafted post to >> publicity@lists.xenproject.org for review >>=20 >> But let me have a look and see whether I can fix it, such that others >> editors can see and review the post before publication >>=20 >=20 > Ok. Thanks. I just did this: the URL as it = https://blog.xenproject.org/2014/10/31/the-windows-pv-drivers-sub-project/= ?preview=3Dtrue&preview_id=3D10071&preview_nonce=3D24ef9979cc&post_format=3D= standard Lars --Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On 7 Oct 2014, at 08:25, Paul Durrant = <Paul.Durrant@citrix.com> = wrote:

-----Original Message-----
From: Lars Kurth
Sent: 07 = October 2014 16:19
To: Paul Durrant
Cc: publicity@lists.xenproject.= org
Subject: Re: blog post

Paul,

the trick is to = only save the blog post as draft, select preview and post
that link = and not to publish the post. You can also schedule it for a
future = date. We then tend to send a link of the drafted post to
publicity@lists.xenproject.= org for review

But let me have a look and see whether I can = fix it, such that others
editors can see and review the post before = publication


Ok. = Thanks.

I just did this: the URL as = it https://blog.xenproject.org/2014/10/31/the-windows-pv-drivers-sub= -project/?preview=3Dtrue&preview_id=3D10071&preview_nonce=3D24ef99= 79cc&post_format=3Dstandard

Lars

= --Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC-- --===============1052425844064591412== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============1052425844064591412==-- From publicity-bounces@lists.xenproject.org Tue Oct 07 15:30:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 07 Oct 2014 15:30:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWiJ-00009P-Od; Tue, 07 Oct 2014 15:30:11 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XbWiH-00008u-JC for publicity@lists.xenproject.org; Tue, 07 Oct 2014 15:30:09 +0000 Received: from [85.158.137.68:21371] by server-16.bemta-3.messagelabs.com id 81/59-01431-00704345; Tue, 07 Oct 2014 15:30:08 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1412695807!8307892!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5398 invoked from network); 7 Oct 2014 15:30:07 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 7 Oct 2014 15:30:07 -0000 Received: by mail-wg0-f41.google.com with SMTP id b13so9761066wgh.24 for ; Tue, 07 Oct 2014 08:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=I3lfhGJ2Gdcr6I1P2YfcBAfqMc02NzNbNaZgCxisZys=; b=d00tmbQgAXX1sKerDRLzzKB4UqXxGq8jrLUK/y490XGh8t2TotsglKX0oJLJQAeEn+ xTvgpSLvLOQVT7Uccv/j+Ra3wvICpN5ux6ov1EIfktJWthBPPJq/13nhy1UkRmJzCcRY idMPgVFGFHMzPpwLYfkqQ9cBQ0sI1DyGTeIpcBn+GwAYbflcg7DujyVtllhjfal/cUrn R4sZK/4od81YwmurETVCh9u1TwvmG31GFonUSUY/GgQo8JGQdvzogaf2o/seUdiMsb3g rHlr96YK8ANYca3/dtvbBF60MVssFoLSSL4WGogQLXH+goofLrbtOgKN/VzppA2cxlNz zhYQ== X-Received: by 10.180.187.83 with SMTP id fq19mr27870938wic.59.1412695807490; Tue, 07 Oct 2014 08:30:07 -0700 (PDT) Received: from [107.18.164.209] ([107.18.164.209]) by mx.google.com with ESMTPSA id os4sm20219382wjc.48.2014.10.07.08.30.05 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 08:30:06 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA65F@AMSPEX01CL01.citrite.net> Date: Tue, 7 Oct 2014 08:30:02 -0700 Message-Id: <5D6B7B79-E7A4-4976-AD09-2AE23D968E24@gmail.com> References: <9AAE0902D5BC7E449B7C8E4E778ABCD0110F78DF@AMSPEX01CL01.citrite.net> <9AAE0902D5BC7E449B7C8E4E778ABCD0110FA65F@AMSPEX01CL01.citrite.net> To: Paul Durrant X-Mailer: Apple Mail (2.1878.6) Cc: Lars Kurth , "publicity@lists.xenproject.org" Subject: Re: [Publicity] blog post X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1052425844064591412==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============1052425844064591412== Content-Type: multipart/alternative; boundary="Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC" --Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 7 Oct 2014, at 08:25, Paul Durrant wrote: >> -----Original Message----- >> From: Lars Kurth >> Sent: 07 October 2014 16:19 >> To: Paul Durrant >> Cc: publicity@lists.xenproject.org >> Subject: Re: blog post >>=20 >> Paul, >>=20 >> the trick is to only save the blog post as draft, select preview and = post >> that link and not to publish the post. You can also schedule it for a >> future date. We then tend to send a link of the drafted post to >> publicity@lists.xenproject.org for review >>=20 >> But let me have a look and see whether I can fix it, such that others >> editors can see and review the post before publication >>=20 >=20 > Ok. Thanks. I just did this: the URL as it = https://blog.xenproject.org/2014/10/31/the-windows-pv-drivers-sub-project/= ?preview=3Dtrue&preview_id=3D10071&preview_nonce=3D24ef9979cc&post_format=3D= standard Lars --Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
On 7 Oct 2014, at 08:25, Paul Durrant = <Paul.Durrant@citrix.com> = wrote:

-----Original Message-----
From: Lars Kurth
Sent: 07 = October 2014 16:19
To: Paul Durrant
Cc: publicity@lists.xenproject.= org
Subject: Re: blog post

Paul,

the trick is to = only save the blog post as draft, select preview and post
that link = and not to publish the post. You can also schedule it for a
future = date. We then tend to send a link of the drafted post to
publicity@lists.xenproject.= org for review

But let me have a look and see whether I can = fix it, such that others
editors can see and review the post before = publication


Ok. = Thanks.

I just did this: the URL as = it https://blog.xenproject.org/2014/10/31/the-windows-pv-drivers-sub= -project/?preview=3Dtrue&preview_id=3D10071&preview_nonce=3D24ef99= 79cc&post_format=3Dstandard

Lars

= --Apple-Mail=_4852E218-2BA1-415A-8E51-05E1E597B0EC-- --===============1052425844064591412== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============1052425844064591412==-- From publicity-bounces@lists.xenproject.org Tue Oct 21 17:24:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Oct 2014 17:24:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdAi-0000kW-Ne; Tue, 21 Oct 2014 17:24:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdAi-0000j4-5x for publicity@lists.xenproject.org; Tue, 21 Oct 2014 17:24:36 +0000 Received: from [85.158.139.211] by server-12.bemta-5.messagelabs.com id 1C/DC-02709-3D696445; Tue, 21 Oct 2014 17:24:35 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1413912271!10948743!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3354 invoked from network); 21 Oct 2014 17:24:31 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Oct 2014 17:24:31 -0000 Received: by mail-wi0-f177.google.com with SMTP id fb4so2514547wid.16 for ; Tue, 21 Oct 2014 10:24:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=LoqZJrn6Hq+fzjQJRQ98+iy1wS2LxSKfBZTEElkJ6OY=; b=WqtINZrRDCY1GiDBsOJu2w95HjerBo96agSB55uduFf+40lwEAqRcOZdCDRB8E/vY0 mLmz+jFRYZSWavnk14xy0u6pCVhC21KzTKShXhKlchqXZHOjsFFfsyczY5+7CUZtTLm8 cYP8gEZrnQtR/7sTuV4+NtRWWa8q+I896S2g+Qy/V5LPfoij7HeB2+sM8+t1uQYbp7Kr 7Av1fiwUo0vFNHlun63mWAmeoPxi4lr/Ppf4FfMcsD98N/QEn+7z9bltDJx4+zwyE7KS rroYncP8JpIE1uj/+Mu+G3k2KvLYffp478OGcMABQ1VYLwoPRHIiyqQcrIoVIlN7pWsm n0/A== X-Received: by 10.180.24.65 with SMTP id s1mr5759751wif.81.1413912271090; Tue, 21 Oct 2014 10:24:31 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id ha2sm10567537wib.19.2014.10.21.10.24.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 10:24:30 -0700 (PDT) From: Lars Kurth Message-Id: <23E6E8F2-F729-4005-AD3D-27C72D0D632F@gmail.com> Date: Tue, 21 Oct 2014 18:24:27 +0100 To: publicity@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [Publicity] Post "Xen Project Security Policy Improvements: Get Involved" for review X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0367035676632091084==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============0367035676632091084== Content-Type: multipart/alternative; boundary="Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0" --Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii See https://blog.xenproject.org/?p=3D10120&preview=3Dtrue I was planning to publish tomorrow and also send to the users and = announce lists Regards Lars= --Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii See https://blog.xenproject.org/?p=10120&preview=true
I was planning to publish tomorrow and also send to the users and announce lists
Regards
Lars
--Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0-- --===============0367035676632091084== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============0367035676632091084==-- From publicity-bounces@lists.xenproject.org Tue Oct 21 17:24:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Oct 2014 17:24:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdAi-0000kW-Ne; Tue, 21 Oct 2014 17:24:36 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdAi-0000j4-5x for publicity@lists.xenproject.org; Tue, 21 Oct 2014 17:24:36 +0000 Received: from [85.158.139.211] by server-12.bemta-5.messagelabs.com id 1C/DC-02709-3D696445; Tue, 21 Oct 2014 17:24:35 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-206.messagelabs.com!1413912271!10948743!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3354 invoked from network); 21 Oct 2014 17:24:31 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-13.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Oct 2014 17:24:31 -0000 Received: by mail-wi0-f177.google.com with SMTP id fb4so2514547wid.16 for ; Tue, 21 Oct 2014 10:24:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=LoqZJrn6Hq+fzjQJRQ98+iy1wS2LxSKfBZTEElkJ6OY=; b=WqtINZrRDCY1GiDBsOJu2w95HjerBo96agSB55uduFf+40lwEAqRcOZdCDRB8E/vY0 mLmz+jFRYZSWavnk14xy0u6pCVhC21KzTKShXhKlchqXZHOjsFFfsyczY5+7CUZtTLm8 cYP8gEZrnQtR/7sTuV4+NtRWWa8q+I896S2g+Qy/V5LPfoij7HeB2+sM8+t1uQYbp7Kr 7Av1fiwUo0vFNHlun63mWAmeoPxi4lr/Ppf4FfMcsD98N/QEn+7z9bltDJx4+zwyE7KS rroYncP8JpIE1uj/+Mu+G3k2KvLYffp478OGcMABQ1VYLwoPRHIiyqQcrIoVIlN7pWsm n0/A== X-Received: by 10.180.24.65 with SMTP id s1mr5759751wif.81.1413912271090; Tue, 21 Oct 2014 10:24:31 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id ha2sm10567537wib.19.2014.10.21.10.24.29 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 10:24:30 -0700 (PDT) From: Lars Kurth Message-Id: <23E6E8F2-F729-4005-AD3D-27C72D0D632F@gmail.com> Date: Tue, 21 Oct 2014 18:24:27 +0100 To: publicity@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [Publicity] Post "Xen Project Security Policy Improvements: Get Involved" for review X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0367035676632091084==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============0367035676632091084== Content-Type: multipart/alternative; boundary="Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0" --Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii See https://blog.xenproject.org/?p=3D10120&preview=3Dtrue I was planning to publish tomorrow and also send to the users and = announce lists Regards Lars= --Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii See https://blog.xenproject.org/?p=10120&preview=true
I was planning to publish tomorrow and also send to the users and announce lists
Regards
Lars
--Apple-Mail=_29C4A061-E0A7-4E84-8DB0-09C6E1E865E0-- --===============0367035676632091084== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============0367035676632091084==-- From publicity-bounces@lists.xenproject.org Tue Oct 21 17:50:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Oct 2014 17:50:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdZX-0001Qa-3C; Tue, 21 Oct 2014 17:50:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdZW-0001QV-4u for publicity@lists.xenproject.org; Tue, 21 Oct 2014 17:50:14 +0000 Received: from [85.158.137.68:60112] by server-1.bemta-3.messagelabs.com id B3/42-30185-5DC96445; Tue, 21 Oct 2014 17:50:13 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1413913812!6766398!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19001 invoked from network); 21 Oct 2014 17:50:12 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Oct 2014 17:50:12 -0000 Received: by mail-wi0-f170.google.com with SMTP id hi2so11711861wib.1 for ; Tue, 21 Oct 2014 10:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=uJ9sapqIpBcdIuEcYysIpNNiI1lPnfk8NyEkY9rAMBE=; b=KQJ6ahxak4S3EGs9KlsGG0vEY+ErnCrtImWgr8ibCk2skrGCXCdgk5hWgq2xfwNFCG frMR3tPO/ABPFIok41DgwAVcMr6BMzQLSrD7+o7OFPPkCtM5VtagUEz59Qv16hmPzlsB Ndet3rYh7I7j5StPV5Qe/MiAb+PnRR3j+I+TSiHdFFMw9M4MZsu1ADszQyRUiDoT3e3+ GyIaf5vPDP/Qf33Ym7nygGlhPGF3ArEXJsNovNhC3jHscgzGKgrcYAiVnjqiwLtYo2m+ LtDFP+mYfzAOK5p+RFydFSmq3UPkH7Tl1XHj1P1E/kAzmsMxGrw5UUP55hM1/C/Q5Edw oc3w== X-Received: by 10.194.78.113 with SMTP id a17mr14771250wjx.120.1413913812005; Tue, 21 Oct 2014 10:50:12 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id u4sm13821962wiy.9.2014.10.21.10.50.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 10:50:11 -0700 (PDT) From: Lars Kurth Message-Id: Date: Tue, 21 Oct 2014 18:50:08 +0100 To: publicity@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [Publicity] To Editors: Accessing blog previews X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3502751092422857431==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============3502751092422857431== Content-Type: multipart/alternative; boundary="Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1" --Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi all, due to the changes on the blog you will need to reset your password when = reviewing blog posts. To do this, go to * https://blog.xenproject.org/ * Scroll down until you find META (bottom of right hand bottom)=20 * Use the Lost Password link accessible from =93Log In" Regards Lars= --Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Hi = all,
due to the changes on the blog you will need to reset your = password when reviewing blog posts. To do this, go = to
* https://blog.xenproject.org/
* Scroll down until you find META (bottom of right hand = bottom) 
* Use the Lost Password link accessible from = =93Log In"
Regards
Lars
= --Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1-- --===============3502751092422857431== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============3502751092422857431==-- From publicity-bounces@lists.xenproject.org Tue Oct 21 17:50:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 21 Oct 2014 17:50:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdZX-0001Qa-3C; Tue, 21 Oct 2014 17:50:15 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgdZW-0001QV-4u for publicity@lists.xenproject.org; Tue, 21 Oct 2014 17:50:14 +0000 Received: from [85.158.137.68:60112] by server-1.bemta-3.messagelabs.com id B3/42-30185-5DC96445; Tue, 21 Oct 2014 17:50:13 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1413913812!6766398!1 X-Originating-IP: [209.85.212.170] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19001 invoked from network); 21 Oct 2014 17:50:12 -0000 Received: from mail-wi0-f170.google.com (HELO mail-wi0-f170.google.com) (209.85.212.170) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 21 Oct 2014 17:50:12 -0000 Received: by mail-wi0-f170.google.com with SMTP id hi2so11711861wib.1 for ; Tue, 21 Oct 2014 10:50:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=uJ9sapqIpBcdIuEcYysIpNNiI1lPnfk8NyEkY9rAMBE=; b=KQJ6ahxak4S3EGs9KlsGG0vEY+ErnCrtImWgr8ibCk2skrGCXCdgk5hWgq2xfwNFCG frMR3tPO/ABPFIok41DgwAVcMr6BMzQLSrD7+o7OFPPkCtM5VtagUEz59Qv16hmPzlsB Ndet3rYh7I7j5StPV5Qe/MiAb+PnRR3j+I+TSiHdFFMw9M4MZsu1ADszQyRUiDoT3e3+ GyIaf5vPDP/Qf33Ym7nygGlhPGF3ArEXJsNovNhC3jHscgzGKgrcYAiVnjqiwLtYo2m+ LtDFP+mYfzAOK5p+RFydFSmq3UPkH7Tl1XHj1P1E/kAzmsMxGrw5UUP55hM1/C/Q5Edw oc3w== X-Received: by 10.194.78.113 with SMTP id a17mr14771250wjx.120.1413913812005; Tue, 21 Oct 2014 10:50:12 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id u4sm13821962wiy.9.2014.10.21.10.50.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 Oct 2014 10:50:11 -0700 (PDT) From: Lars Kurth Message-Id: Date: Tue, 21 Oct 2014 18:50:08 +0100 To: publicity@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [Publicity] To Editors: Accessing blog previews X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3502751092422857431==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============3502751092422857431== Content-Type: multipart/alternative; boundary="Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1" --Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi all, due to the changes on the blog you will need to reset your password when = reviewing blog posts. To do this, go to * https://blog.xenproject.org/ * Scroll down until you find META (bottom of right hand bottom)=20 * Use the Lost Password link accessible from =93Log In" Regards Lars= --Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Hi = all,
due to the changes on the blog you will need to reset your = password when reviewing blog posts. To do this, go = to
* https://blog.xenproject.org/
* Scroll down until you find META (bottom of right hand = bottom) 
* Use the Lost Password link accessible from = =93Log In"
Regards
Lars
= --Apple-Mail=_A3874B06-81C0-46D7-8AFA-1D5E3AD1DEE1-- --===============3502751092422857431== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============3502751092422857431==-- From publicity-bounces@lists.xenproject.org Wed Oct 22 11:22:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 22 Oct 2014 11:22:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgtzZ-0005Vl-VZ; Wed, 22 Oct 2014 11:22:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgtzY-0005Va-Hc for publicity@lists.xenproject.org; Wed, 22 Oct 2014 11:22:12 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 47/F1-02861-36397445; Wed, 22 Oct 2014 11:22:11 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1413976930!6412353!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21514 invoked from network); 22 Oct 2014 11:22:11 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 22 Oct 2014 11:22:11 -0000 Received: by mail-wg0-f51.google.com with SMTP id b13so3519795wgh.22 for ; Wed, 22 Oct 2014 04:22:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=qiKfgIMzNqynCfG1LKSPgQtqPsD3gm2A6MZPeh2xe0Y=; b=rjJ/7nGV7cWhNl/hoxaHHP2I2hqAdkHGSqejOXuN4UwIzi4vqaGh++DX4oPbn/3Nk+ YLwFXMBDDgWTrHS+vmdL/bAdz8UGp6qh6u8/vW4UgnME5S0XzIP2zlsUlcP2XeyuYfaB Bf75iO8xBw5l5q3WFA0/bAUrbzpaOeM2AKZkupAgaDOeuvKdui255twBGqK5BN6uBS89 FCb/dL+X0Po2PZ9DfF7xufgBauj4HE6xask6WaiMv2sUpnAl9O0Oxi+8+zK+XVG87ybU D9GaBBXN1iTkJq+o4mTzZOz3CBFFBKxhZ6vdA2kxGa/0uOHO99orT1OfaZ+OfK+5woby qXMA== X-Received: by 10.180.206.14 with SMTP id lk14mr20365541wic.47.1413976930428; Wed, 22 Oct 2014 04:22:10 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id u4sm1583994wiy.9.2014.10.22.04.22.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Oct 2014 04:22:09 -0700 (PDT) From: Lars Kurth Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Date: Wed, 22 Oct 2014 12:22:05 +0100 References: <23E6E8F2-F729-4005-AD3D-27C72D0D632F@gmail.com> To: publicity@lists.xenproject.org In-Reply-To: <23E6E8F2-F729-4005-AD3D-27C72D0D632F@gmail.com> X-Mailer: Apple Mail (2.1878.6) Subject: Re: [Publicity] Post "Xen Project Security Policy Improvements: Get Involved" for review X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7660668083705183473==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============7660668083705183473== Content-Type: multipart/alternative; boundary="Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E" --Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii No feedback. So it seems fine to go. Will publish in an hour Lars On 21 Oct 2014, at 18:24, Lars Kurth wrote: > See https://blog.xenproject.org/?p=3D10120&preview=3Dtrue > I was planning to publish tomorrow and also send to the users and = announce lists > Regards > Lars --Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii No feedback. So it seems fine to go. Will publish in an hour
Lars

On 21 Oct 2014, at 18:24, Lars Kurth <lars.kurth.xen@gmail.com> wrote:

See https://blog.xenproject.org/?p=10120&preview=true
I was planning to publish tomorrow and also send to the users and announce lists
Regards
Lars

--Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E-- --===============7660668083705183473== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============7660668083705183473==-- From publicity-bounces@lists.xenproject.org Wed Oct 22 11:22:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 22 Oct 2014 11:22:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgtzZ-0005Vl-VZ; Wed, 22 Oct 2014 11:22:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XgtzY-0005Va-Hc for publicity@lists.xenproject.org; Wed, 22 Oct 2014 11:22:12 +0000 Received: from [85.158.137.68] by server-13.bemta-3.messagelabs.com id 47/F1-02861-36397445; Wed, 22 Oct 2014 11:22:11 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1413976930!6412353!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21514 invoked from network); 22 Oct 2014 11:22:11 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 22 Oct 2014 11:22:11 -0000 Received: by mail-wg0-f51.google.com with SMTP id b13so3519795wgh.22 for ; Wed, 22 Oct 2014 04:22:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to; bh=qiKfgIMzNqynCfG1LKSPgQtqPsD3gm2A6MZPeh2xe0Y=; b=rjJ/7nGV7cWhNl/hoxaHHP2I2hqAdkHGSqejOXuN4UwIzi4vqaGh++DX4oPbn/3Nk+ YLwFXMBDDgWTrHS+vmdL/bAdz8UGp6qh6u8/vW4UgnME5S0XzIP2zlsUlcP2XeyuYfaB Bf75iO8xBw5l5q3WFA0/bAUrbzpaOeM2AKZkupAgaDOeuvKdui255twBGqK5BN6uBS89 FCb/dL+X0Po2PZ9DfF7xufgBauj4HE6xask6WaiMv2sUpnAl9O0Oxi+8+zK+XVG87ybU D9GaBBXN1iTkJq+o4mTzZOz3CBFFBKxhZ6vdA2kxGa/0uOHO99orT1OfaZ+OfK+5woby qXMA== X-Received: by 10.180.206.14 with SMTP id lk14mr20365541wic.47.1413976930428; Wed, 22 Oct 2014 04:22:10 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id u4sm1583994wiy.9.2014.10.22.04.22.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Oct 2014 04:22:09 -0700 (PDT) From: Lars Kurth Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Date: Wed, 22 Oct 2014 12:22:05 +0100 References: <23E6E8F2-F729-4005-AD3D-27C72D0D632F@gmail.com> To: publicity@lists.xenproject.org In-Reply-To: <23E6E8F2-F729-4005-AD3D-27C72D0D632F@gmail.com> X-Mailer: Apple Mail (2.1878.6) Subject: Re: [Publicity] Post "Xen Project Security Policy Improvements: Get Involved" for review X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7660668083705183473==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============7660668083705183473== Content-Type: multipart/alternative; boundary="Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E" --Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii No feedback. So it seems fine to go. Will publish in an hour Lars On 21 Oct 2014, at 18:24, Lars Kurth wrote: > See https://blog.xenproject.org/?p=3D10120&preview=3Dtrue > I was planning to publish tomorrow and also send to the users and = announce lists > Regards > Lars --Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii No feedback. So it seems fine to go. Will publish in an hour
Lars

On 21 Oct 2014, at 18:24, Lars Kurth <lars.kurth.xen@gmail.com> wrote:

See https://blog.xenproject.org/?p=10120&preview=true
I was planning to publish tomorrow and also send to the users and announce lists
Regards
Lars

--Apple-Mail=_CAB84B48-0FF4-4BB7-A189-DC3F0334B76E-- --===============7660668083705183473== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============7660668083705183473==-- From publicity-bounces@lists.xenproject.org Thu Oct 23 23:40:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Oct 2014 23:40:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XhRzC-0003gG-3U; Thu, 23 Oct 2014 23:40:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XhRzA-0003gB-EP for publicity@lists.xenproject.org; Thu, 23 Oct 2014 23:40:04 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id 7B/63-02696-3D199445; Thu, 23 Oct 2014 23:40:03 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1414107602!3866087!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23003 invoked from network); 23 Oct 2014 23:40:03 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 23 Oct 2014 23:40:03 -0000 Received: by mail-la0-f48.google.com with SMTP id gi9so1724397lab.21 for ; Thu, 23 Oct 2014 16:40:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=SE+ZFAlEiV+Dhnxv6lAYPo3HQPh3+kFEB419wtU2fZ0=; b=cyLHnouejUtxRyBcG40o4Hw1BmcLsev8vODbdIc51MR5h51pYPFNXA8YkSx9dAaUZF RybZZPsfUSYge3hBpYXnv7A61BNUFoeTDdz5PQnxnPKjdwSOBDSJizW8GnNe0NnY1LnY gAXHOfmzAfBAlk2cAOcu6Oul+yU0FteqVgGTNzpX3wW53sL7A2iPnFZQDyBYViZ7z9LT vJF7auvZDGR5KKBFuKkx0+E+Rd9QoNS+6lk3n0QarbfiqBH5Z2jutOsoYTR35oE4TO0G AazNcpV2n2TyVS5I1wfuEptszUpaCcqikaiEulVC+xHgjYuxSRTG2gOwgNpRA4ZPjPrz Fs1g== MIME-Version: 1.0 X-Received: by 10.152.120.73 with SMTP id la9mr674622lab.23.1414107602045; Thu, 23 Oct 2014 16:40:02 -0700 (PDT) Received: by 10.112.67.35 with HTTP; Thu, 23 Oct 2014 16:40:02 -0700 (PDT) Date: Thu, 23 Oct 2014 19:40:02 -0400 X-Google-Sender-Auth: EdHgErTQEgAx1mjBhIbajbzUf68 Message-ID: From: Russ Pavlicek To: "publicity@lists.xenproject.org" Subject: [Publicity] Blog Review: Xen Project Test Day on Oct 29 X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org I have a blog post ready for tomorrow to advertise the Test Day on October 29: https://blog.xenproject.org/?p=10148&preview=true You will need to login to the blog system to review. If you have written a blog on the system before, but haven't logged in since the relaunch of the system, you will need to reset your password. If you have issues, please let me know by 15:00 BST/10:00 EDT on Friday. Otherwise, I will publish it shortly thereafter. Thanks, Russ _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Thu Oct 23 23:40:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 23 Oct 2014 23:40:07 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XhRzC-0003gG-3U; Thu, 23 Oct 2014 23:40:06 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XhRzA-0003gB-EP for publicity@lists.xenproject.org; Thu, 23 Oct 2014 23:40:04 +0000 Received: from [85.158.139.211] by server-11.bemta-5.messagelabs.com id 7B/63-02696-3D199445; Thu, 23 Oct 2014 23:40:03 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1414107602!3866087!1 X-Originating-IP: [209.85.215.48] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23003 invoked from network); 23 Oct 2014 23:40:03 -0000 Received: from mail-la0-f48.google.com (HELO mail-la0-f48.google.com) (209.85.215.48) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 23 Oct 2014 23:40:03 -0000 Received: by mail-la0-f48.google.com with SMTP id gi9so1724397lab.21 for ; Thu, 23 Oct 2014 16:40:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=SE+ZFAlEiV+Dhnxv6lAYPo3HQPh3+kFEB419wtU2fZ0=; b=cyLHnouejUtxRyBcG40o4Hw1BmcLsev8vODbdIc51MR5h51pYPFNXA8YkSx9dAaUZF RybZZPsfUSYge3hBpYXnv7A61BNUFoeTDdz5PQnxnPKjdwSOBDSJizW8GnNe0NnY1LnY gAXHOfmzAfBAlk2cAOcu6Oul+yU0FteqVgGTNzpX3wW53sL7A2iPnFZQDyBYViZ7z9LT vJF7auvZDGR5KKBFuKkx0+E+Rd9QoNS+6lk3n0QarbfiqBH5Z2jutOsoYTR35oE4TO0G AazNcpV2n2TyVS5I1wfuEptszUpaCcqikaiEulVC+xHgjYuxSRTG2gOwgNpRA4ZPjPrz Fs1g== MIME-Version: 1.0 X-Received: by 10.152.120.73 with SMTP id la9mr674622lab.23.1414107602045; Thu, 23 Oct 2014 16:40:02 -0700 (PDT) Received: by 10.112.67.35 with HTTP; Thu, 23 Oct 2014 16:40:02 -0700 (PDT) Date: Thu, 23 Oct 2014 19:40:02 -0400 X-Google-Sender-Auth: EdHgErTQEgAx1mjBhIbajbzUf68 Message-ID: From: Russ Pavlicek To: "publicity@lists.xenproject.org" Subject: [Publicity] Blog Review: Xen Project Test Day on Oct 29 X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org I have a blog post ready for tomorrow to advertise the Test Day on October 29: https://blog.xenproject.org/?p=10148&preview=true You will need to login to the blog system to review. If you have written a blog on the system before, but haven't logged in since the relaunch of the system, you will need to reset your password. If you have issues, please let me know by 15:00 BST/10:00 EDT on Friday. Otherwise, I will publish it shortly thereafter. Thanks, Russ _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity From publicity-bounces@lists.xenproject.org Mon Oct 27 13:43:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Oct 2014 13:43:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XikZb-00077V-C8; Mon, 27 Oct 2014 13:43:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XikZY-00077N-Po; Mon, 27 Oct 2014 13:43:01 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 83/9E-02952-4EB4E445; Mon, 27 Oct 2014 13:43:00 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1414417378!12831783!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.1 required=7.0 tests=ADVANCE_FEE_1,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1756 invoked from network); 27 Oct 2014 13:42:58 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Oct 2014 13:42:58 -0000 Received: by mail-wi0-f180.google.com with SMTP id hi2so2871350wib.13 for ; Mon, 27 Oct 2014 06:42:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=osTJgYwe3KdCxSJrzG1082g6eb5k50JIgUN9vvEvwpI=; b=m6OZLlF+z7ALWPY5PXCzBRsNRNE5JfYAZPLZ1KpnRmmSwrnjipuUG6p5pmbsGfZtnl L9a4eASeQHT2KXbe9wDbFP72oTGbwM9o8/sHJBajm7lLXURo2Sc+fccw+p/vkzAYS3RT NcSddcEvoWvaH1GNw4M8jzset/4zD5iHQxoD/ygH+PRhWwL99J7V6dDaSOcjl18FxBtd BGvh7H6ZBmBrEBWIfgg1Pi3rGAeR2sHOR4KDPLPfiblc6lkXx0HtYY4pfv0R6ChBEvYC t+ZyCnkCSLXcwa+ZewV+0DrUZRMY0Q/kkyA4XiqviBqGpnJ69j/FYtw/GWHtL/jT5cQO JRZw== X-Received: by 10.180.211.206 with SMTP id ne14mr21421296wic.79.1414417378423; Mon, 27 Oct 2014 06:42:58 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id y5sm11941545wix.10.2014.10.27.06.42.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Oct 2014 06:42:57 -0700 (PDT) From: Lars Kurth Date: Mon, 27 Oct 2014 13:42:54 +0000 References: <544AAFAF.3030204@redhat.com> To: publicity@lists.xenproject.org, xen-devel Message-Id: <1D97AAB7-04D1-46E2-A645-F7EE9227ACA5@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [Publicity] Infrastructure-as-a-Service (IaaS) Devroom at FOSDEM 15: Call for Participation - Deadline Dec 1st X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4077599378296516913==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============4077599378296516913== Content-Type: multipart/alternative; boundary="Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01" --Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii FYI Begin forwarded message: > From: Joe Brockmeier > Subject: Infrastructure-as-a-Service (IaaS) Devroom at FOSDEM 15: Call = for Participation > Date: 24 October 2014 20:59:43 BST > To: fosdem@lists.fosdem.org > Cc: iaas-virt-devroom@lists.fosdem.org > Reply-To: jzb@redhat.com >=20 > FOSDEM '15 Infrastructure-as-a-Service devroom >=20 > Please forward to any list or individual that might be interested in > participating in this devroom! >=20 > ------------------------- > Important Dates and Info! > ------------------------- >=20 > Submission deadline: 1 December 2014 > Acceptance notifications: 15 December 2014 > Final schedule announcement: 9 January 2015 > Devroom: 31 January 2015 >=20 > ------------------------- > Call for Participation > ------------------------- >=20 > The open source IaaS devroom will host sessions around open source > Infrastructure-as-a-Service projects such as (but not limited to) > Apache CloudStack, OpenStack, oVirt, OpenNebula, and Ganeti. >=20 > This room will focus on collaboration between projects on common > problems and software, such as shared storage, virtualized networking, > interfacing with multiple hypervisors, and scaling across hundreds or > thousands of servers. >=20 > Organizers are seeking topics that are interesting to multiple = projects, > and hope to encourage developers to share experience solving problems > with their own projects. >=20 > ------------------------- > Call for Volunteers > ------------------------- >=20 > We are also looking for volunteers to help run the devroom. We need > assistance watching time for the speakers, and helping with video > for the devroom. Please contact Joe Brockmeier (jzb at redhat.com) for > more information here. >=20 > ------------------------- > Details: READ CAREFULLY > ------------------------- >=20 > This year at FOSDEM there will be a one-day devroom to focus on IaaS > projects. If your project is related to IaaS, we would love to see > your submissions. >=20 > Please note that we expect more proposals than we can possibly accept, > so it is vitally important that you submit your proposal on or before > the deadline. Late submissions are unlikely to be considered. >=20 > All slots are 40 minutes, with 30 minutes planned for presentations, = and > 10 minutes for Q&A. >=20 > All presentations *will* be recorded and made available under Creative > Commons licenses. Please indicate when submitting your talk that your > presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 > license when submitting the talk and that you agree to have your > presentation recorded. For example: >=20 > "If my presentation is accepted for FOSDEM, I hereby agree to license > all recordings, slides, and other associated materials under the > Creative Commons Attribution Share-Alike 4.0 International License. > Sincerely, ." >=20 > Also, in the notes field, please confirm tnat if your talk is accepted > that you *will* be able to attend FOSDEM and deliver your = presentation. > We will not consider proposals from prospective speakers unsure = whether > they will be able to secure funds for travel and lodging to attend > FOSDEM. (Sadly, we are not able to offer travel funding for = prospective > speakers.) >=20 > ------------------------- > How to Submit > ------------------------- >=20 > All submissions are made via the Pentabarf event planning site: >=20 > https://penta.fosdem.org/submission/FOSDEM15 >=20 > If you have not used Pentabarf before, you will need to create an = account. >=20 > After creating the account, select "Create Event" and then be sure to > select "Infrastructure as a service devroom" from the options under > "Track." >=20 > ------------------------- > Questions > ------------------------- >=20 > If you have any questions about this devroom, please send your = questions > to: >=20 > iaas-virt-devroom@lists.fosdem.org >=20 > We will respond as quickly as possible. Thanks! > _______________________________________________ > iaas-virt-devroom mailing list > iaas-virt-devroom@lists.fosdem.org > https://lists.fosdem.org/listinfo/iaas-virt-devroom --Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii FYI

Begin forwarded = message:

From: = Joe Brockmeier = <jzb@redhat.com>
Subject: Infrastructure-as-a-Service (IaaS) = Devroom at FOSDEM 15: Call for Participation
Date: 24 October 2014 20:59:43 = BST
Reply-To: jzb@redhat.com

FOSDEM '15 Infrastructure-as-a-Service devroom

Please forward to = any list or individual that might be interested in
participating in = this devroom!

-------------------------
Important Dates and = Info!
-------------------------

Submission deadline: 1 = December 2014
Acceptance notifications: 15 December 2014
Final = schedule announcement: 9 January 2015
Devroom: 31 January = 2015

-------------------------
Call for = Participation
-------------------------

The open source IaaS = devroom will host sessions around open = source
Infrastructure-as-a-Service projects such as (but not limited = to)
Apache CloudStack, OpenStack, oVirt, OpenNebula, and = Ganeti.

This room will focus on collaboration between projects on = common
problems and software, such as shared storage, virtualized = networking,
interfacing with multiple hypervisors, and scaling across = hundreds or
thousands of servers.

Organizers are seeking = topics that are interesting to multiple projects,
and hope to = encourage developers to share experience solving problems
with their = own projects.

-------------------------
Call for = Volunteers
-------------------------

We are also looking for = volunteers to help run the devroom. We need
assistance watching time = for the speakers, and helping with video
for the devroom. Please = contact Joe Brockmeier (jzb at redhat.com) for
more information = here.

-------------------------
Details: READ = CAREFULLY
-------------------------

This year at FOSDEM there = will be a one-day devroom to focus on IaaS
projects. If your project = is related to IaaS, we would love to see
your = submissions.

Please note that we expect more proposals than we = can possibly accept,
so it is vitally important that you submit your = proposal on or before
the deadline. Late submissions are unlikely to = be considered.

All slots are 40 minutes, with 30 minutes planned = for presentations, and
10 minutes for Q&A.

All = presentations *will* be recorded and made available under = Creative
Commons licenses. Please indicate when submitting your talk = that your
presentation will be licensed under the CC-By-SA-4.0 or = CC-By-4.0
license when submitting the talk and that you agree to have = your
presentation recorded. For example:

 "If my = presentation is accepted for FOSDEM, I hereby agree to license
=   all recordings, slides, and other associated materials under = the
  Creative Commons Attribution Share-Alike 4.0 = International License.
  Sincerely, = <NAME>."

Also, in the notes field, please confirm tnat if = your talk is accepted
that you *will* be able to attend FOSDEM and = deliver your presentation.
We will not consider proposals from = prospective speakers unsure whether
they will be able to secure funds = for travel and lodging to attend
FOSDEM. (Sadly, we are not able to = offer travel funding for = prospective
speakers.)

-------------------------
How to = Submit
-------------------------

All submissions are made via = the Pentabarf event planning site:

https://penta.fosdem= .org/submission/FOSDEM15

If you have not used Pentabarf = before, you will need to create an account.

After creating the = account, select "Create Event" and then be sure to
select = "Infrastructure as a service devroom" from the options = under
"Track."

-------------------------
Questions
-------= ------------------

If you have any questions about this devroom, = please send your = questions
to:

iaas-virt-devroom@lists.fosdem.org

We = will respond as quickly as possible. = Thanks!
_______________________________________________
iaas-virt-de= vroom mailing = list
iaas-virt-devroom@lists.fosdem.org
https://lists.fosdem.org/lis= tinfo/iaas-virt-devroom

= --Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01-- --===============4077599378296516913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============4077599378296516913==-- From publicity-bounces@lists.xenproject.org Mon Oct 27 13:43:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 27 Oct 2014 13:43:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XikZb-00077V-C8; Mon, 27 Oct 2014 13:43:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XikZY-00077N-Po; Mon, 27 Oct 2014 13:43:01 +0000 Received: from [85.158.143.35] by server-1.bemta-4.messagelabs.com id 83/9E-02952-4EB4E445; Mon, 27 Oct 2014 13:43:00 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1414417378!12831783!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.1 required=7.0 tests=ADVANCE_FEE_1,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1756 invoked from network); 27 Oct 2014 13:42:58 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 27 Oct 2014 13:42:58 -0000 Received: by mail-wi0-f180.google.com with SMTP id hi2so2871350wib.13 for ; Mon, 27 Oct 2014 06:42:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=osTJgYwe3KdCxSJrzG1082g6eb5k50JIgUN9vvEvwpI=; b=m6OZLlF+z7ALWPY5PXCzBRsNRNE5JfYAZPLZ1KpnRmmSwrnjipuUG6p5pmbsGfZtnl L9a4eASeQHT2KXbe9wDbFP72oTGbwM9o8/sHJBajm7lLXURo2Sc+fccw+p/vkzAYS3RT NcSddcEvoWvaH1GNw4M8jzset/4zD5iHQxoD/ygH+PRhWwL99J7V6dDaSOcjl18FxBtd BGvh7H6ZBmBrEBWIfgg1Pi3rGAeR2sHOR4KDPLPfiblc6lkXx0HtYY4pfv0R6ChBEvYC t+ZyCnkCSLXcwa+ZewV+0DrUZRMY0Q/kkyA4XiqviBqGpnJ69j/FYtw/GWHtL/jT5cQO JRZw== X-Received: by 10.180.211.206 with SMTP id ne14mr21421296wic.79.1414417378423; Mon, 27 Oct 2014 06:42:58 -0700 (PDT) Received: from [192.168.0.25] (97e553ce.skybroadband.com. [151.229.83.206]) by mx.google.com with ESMTPSA id y5sm11941545wix.10.2014.10.27.06.42.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Oct 2014 06:42:57 -0700 (PDT) From: Lars Kurth Date: Mon, 27 Oct 2014 13:42:54 +0000 References: <544AAFAF.3030204@redhat.com> To: publicity@lists.xenproject.org, xen-devel Message-Id: <1D97AAB7-04D1-46E2-A645-F7EE9227ACA5@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [Publicity] Infrastructure-as-a-Service (IaaS) Devroom at FOSDEM 15: Call for Participation - Deadline Dec 1st X-BeenThere: publicity@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "List for Xen Publicity, PR and events" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4077599378296516913==" Sender: publicity-bounces@lists.xenproject.org Errors-To: publicity-bounces@lists.xenproject.org --===============4077599378296516913== Content-Type: multipart/alternative; boundary="Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01" --Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii FYI Begin forwarded message: > From: Joe Brockmeier > Subject: Infrastructure-as-a-Service (IaaS) Devroom at FOSDEM 15: Call = for Participation > Date: 24 October 2014 20:59:43 BST > To: fosdem@lists.fosdem.org > Cc: iaas-virt-devroom@lists.fosdem.org > Reply-To: jzb@redhat.com >=20 > FOSDEM '15 Infrastructure-as-a-Service devroom >=20 > Please forward to any list or individual that might be interested in > participating in this devroom! >=20 > ------------------------- > Important Dates and Info! > ------------------------- >=20 > Submission deadline: 1 December 2014 > Acceptance notifications: 15 December 2014 > Final schedule announcement: 9 January 2015 > Devroom: 31 January 2015 >=20 > ------------------------- > Call for Participation > ------------------------- >=20 > The open source IaaS devroom will host sessions around open source > Infrastructure-as-a-Service projects such as (but not limited to) > Apache CloudStack, OpenStack, oVirt, OpenNebula, and Ganeti. >=20 > This room will focus on collaboration between projects on common > problems and software, such as shared storage, virtualized networking, > interfacing with multiple hypervisors, and scaling across hundreds or > thousands of servers. >=20 > Organizers are seeking topics that are interesting to multiple = projects, > and hope to encourage developers to share experience solving problems > with their own projects. >=20 > ------------------------- > Call for Volunteers > ------------------------- >=20 > We are also looking for volunteers to help run the devroom. We need > assistance watching time for the speakers, and helping with video > for the devroom. Please contact Joe Brockmeier (jzb at redhat.com) for > more information here. >=20 > ------------------------- > Details: READ CAREFULLY > ------------------------- >=20 > This year at FOSDEM there will be a one-day devroom to focus on IaaS > projects. If your project is related to IaaS, we would love to see > your submissions. >=20 > Please note that we expect more proposals than we can possibly accept, > so it is vitally important that you submit your proposal on or before > the deadline. Late submissions are unlikely to be considered. >=20 > All slots are 40 minutes, with 30 minutes planned for presentations, = and > 10 minutes for Q&A. >=20 > All presentations *will* be recorded and made available under Creative > Commons licenses. Please indicate when submitting your talk that your > presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 > license when submitting the talk and that you agree to have your > presentation recorded. For example: >=20 > "If my presentation is accepted for FOSDEM, I hereby agree to license > all recordings, slides, and other associated materials under the > Creative Commons Attribution Share-Alike 4.0 International License. > Sincerely, ." >=20 > Also, in the notes field, please confirm tnat if your talk is accepted > that you *will* be able to attend FOSDEM and deliver your = presentation. > We will not consider proposals from prospective speakers unsure = whether > they will be able to secure funds for travel and lodging to attend > FOSDEM. (Sadly, we are not able to offer travel funding for = prospective > speakers.) >=20 > ------------------------- > How to Submit > ------------------------- >=20 > All submissions are made via the Pentabarf event planning site: >=20 > https://penta.fosdem.org/submission/FOSDEM15 >=20 > If you have not used Pentabarf before, you will need to create an = account. >=20 > After creating the account, select "Create Event" and then be sure to > select "Infrastructure as a service devroom" from the options under > "Track." >=20 > ------------------------- > Questions > ------------------------- >=20 > If you have any questions about this devroom, please send your = questions > to: >=20 > iaas-virt-devroom@lists.fosdem.org >=20 > We will respond as quickly as possible. Thanks! > _______________________________________________ > iaas-virt-devroom mailing list > iaas-virt-devroom@lists.fosdem.org > https://lists.fosdem.org/listinfo/iaas-virt-devroom --Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii FYI

Begin forwarded = message:

From: = Joe Brockmeier = <jzb@redhat.com>
Subject: Infrastructure-as-a-Service (IaaS) = Devroom at FOSDEM 15: Call for Participation
Date: 24 October 2014 20:59:43 = BST
Reply-To: jzb@redhat.com

FOSDEM '15 Infrastructure-as-a-Service devroom

Please forward to = any list or individual that might be interested in
participating in = this devroom!

-------------------------
Important Dates and = Info!
-------------------------

Submission deadline: 1 = December 2014
Acceptance notifications: 15 December 2014
Final = schedule announcement: 9 January 2015
Devroom: 31 January = 2015

-------------------------
Call for = Participation
-------------------------

The open source IaaS = devroom will host sessions around open = source
Infrastructure-as-a-Service projects such as (but not limited = to)
Apache CloudStack, OpenStack, oVirt, OpenNebula, and = Ganeti.

This room will focus on collaboration between projects on = common
problems and software, such as shared storage, virtualized = networking,
interfacing with multiple hypervisors, and scaling across = hundreds or
thousands of servers.

Organizers are seeking = topics that are interesting to multiple projects,
and hope to = encourage developers to share experience solving problems
with their = own projects.

-------------------------
Call for = Volunteers
-------------------------

We are also looking for = volunteers to help run the devroom. We need
assistance watching time = for the speakers, and helping with video
for the devroom. Please = contact Joe Brockmeier (jzb at redhat.com) for
more information = here.

-------------------------
Details: READ = CAREFULLY
-------------------------

This year at FOSDEM there = will be a one-day devroom to focus on IaaS
projects. If your project = is related to IaaS, we would love to see
your = submissions.

Please note that we expect more proposals than we = can possibly accept,
so it is vitally important that you submit your = proposal on or before
the deadline. Late submissions are unlikely to = be considered.

All slots are 40 minutes, with 30 minutes planned = for presentations, and
10 minutes for Q&A.

All = presentations *will* be recorded and made available under = Creative
Commons licenses. Please indicate when submitting your talk = that your
presentation will be licensed under the CC-By-SA-4.0 or = CC-By-4.0
license when submitting the talk and that you agree to have = your
presentation recorded. For example:

 "If my = presentation is accepted for FOSDEM, I hereby agree to license
=   all recordings, slides, and other associated materials under = the
  Creative Commons Attribution Share-Alike 4.0 = International License.
  Sincerely, = <NAME>."

Also, in the notes field, please confirm tnat if = your talk is accepted
that you *will* be able to attend FOSDEM and = deliver your presentation.
We will not consider proposals from = prospective speakers unsure whether
they will be able to secure funds = for travel and lodging to attend
FOSDEM. (Sadly, we are not able to = offer travel funding for = prospective
speakers.)

-------------------------
How to = Submit
-------------------------

All submissions are made via = the Pentabarf event planning site:

https://penta.fosdem= .org/submission/FOSDEM15

If you have not used Pentabarf = before, you will need to create an account.

After creating the = account, select "Create Event" and then be sure to
select = "Infrastructure as a service devroom" from the options = under
"Track."

-------------------------
Questions
-------= ------------------

If you have any questions about this devroom, = please send your = questions
to:

iaas-virt-devroom@lists.fosdem.org

We = will respond as quickly as possible. = Thanks!
_______________________________________________
iaas-virt-de= vroom mailing = list
iaas-virt-devroom@lists.fosdem.org
https://lists.fosdem.org/lis= tinfo/iaas-virt-devroom

= --Apple-Mail=_76582D68-17D3-4E1B-BCE7-56D088E14B01-- --===============4077599378296516913== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Publicity mailing list Publicity@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity --===============4077599378296516913==--