>>> On 19.06.18 at 15:33, wrote:
> Michael Young writes ("Re: [Xen-devel] Status of comet-4.10 branch"):
>> +1 to an update on the status of extra branches for XSA-254.
>
> I'm drafting this update now. I think that the status is:
>
> 4.10.0-s
Michael Young writes ("Re: [Xen-devel] Status of comet-4.10 branch"):
> +1 to an update on the status of extra branches for XSA-254.
I'm drafting this update now. I think that the status is:
4.10.0-shim-comet:
Merged into and superseded by staging-4.10.
"Testing st
>>> Ian Jackson 06/15/18 6:26 PM >>>
>The right approach to this depends on whether the functionality in the
>comet and shim branches is now in released Xen branches. Should comet
>4.10 be retired in favour of stable-4.10 or RELEASE-4.10.1 ?
It is my understanding that with the merging of the sh
On Fri, 15 Jun 2018, Ian Jackson wrote:
In XSA-254, we advertised siome special new branches, comet and vixen,
which were intended to be used as the shim in the PV-in-HVM shim
approaches to XSA-254 mitigation.
With my Debian maintainer hat on, I chose to do that. (I don't know,
of course, what
In XSA-254, we advertised siome special new branches, comet and vixen,
which were intended to be used as the shim in the PV-in-HVM shim
approaches to XSA-254 mitigation.
With my Debian maintainer hat on, I chose to do that. (I don't know,
of course, what proportion of Debian users are using shim
