On 23.01.2020 15:52, Julien Grall wrote:
> Therefore, they will have to accept whatever string is reported by
> HVMLoader (or Xen). As you already allow Xen to configure it, why would
> that be a problem to change the one in Kconfig? Why do you need to fix
> it up in hvmloader as well?
On 1/23/20 2:52 PM, Julien Grall wrote:
> Hi,
>
> On 23/01/2020 14:45, George Dunlap wrote:
>> On 1/23/20 2:42 PM, Julien Grall wrote:
>>> Hi,
>>>
>>> On 23/01/2020 11:32, Sergey Dyasli wrote:
On 22/01/2020 11:25, Julien Grall wrote:
>
>
> On 22/01/2020 11:19, Sergey Dyasli
Hi,
On 23/01/2020 14:45, George Dunlap wrote:
On 1/23/20 2:42 PM, Julien Grall wrote:
Hi,
On 23/01/2020 11:32, Sergey Dyasli wrote:
On 22/01/2020 11:25, Julien Grall wrote:
On 22/01/2020 11:19, Sergey Dyasli wrote:
On 22/01/2020 10:14, Julien Grall wrote:
On 22/01/2020 10:01, Sergey
On 1/23/20 2:42 PM, Julien Grall wrote:
> Hi,
>
> On 23/01/2020 11:32, Sergey Dyasli wrote:
>> On 22/01/2020 11:25, Julien Grall wrote:
>>>
>>>
>>> On 22/01/2020 11:19, Sergey Dyasli wrote:
On 22/01/2020 10:14, Julien Grall wrote:
>
>
> On 22/01/2020 10:01, Sergey Dyasli wrote:
Hi,
On 23/01/2020 11:32, Sergey Dyasli wrote:
On 22/01/2020 11:25, Julien Grall wrote:
On 22/01/2020 11:19, Sergey Dyasli wrote:
On 22/01/2020 10:14, Julien Grall wrote:
On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
On 17.01.2020 17:44, Sergey Dyasli
On 1/22/20 11:44 AM, Sergey Dyasli wrote:
> On 22/01/2020 10:57, George Dunlap wrote:
>> On 1/22/20 10:14 AM, Julien Grall wrote:
>>>
>>>
>>> On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
> On 17.01.2020 17:44, Sergey Dyasli wrote:
>> v2 --> v3:
On 22/01/2020 11:25, Julien Grall wrote:
>
>
> On 22/01/2020 11:19, Sergey Dyasli wrote:
>> On 22/01/2020 10:14, Julien Grall wrote:
>>>
>>>
>>> On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
> On 17.01.2020 17:44, Sergey Dyasli wrote:
>> v2 --> v3:
On 22/01/2020 12:32, Jan Beulich wrote:
On 22.01.2020 13:05, Julien Grall wrote:
Hi George,
On 22/01/2020 10:57, George Dunlap wrote:
On 1/22/20 10:14 AM, Julien Grall wrote:
On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
On 17.01.2020 17:44, Sergey
On 22.01.2020 13:05, Julien Grall wrote:
> Hi George,
>
> On 22/01/2020 10:57, George Dunlap wrote:
>> On 1/22/20 10:14 AM, Julien Grall wrote:
>>>
>>>
>>> On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
> On 17.01.2020 17:44, Sergey Dyasli wrote:
>>
Hi George,
On 22/01/2020 10:57, George Dunlap wrote:
On 1/22/20 10:14 AM, Julien Grall wrote:
On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
On 17.01.2020 17:44, Sergey Dyasli wrote:
v2 --> v3:
- Remove hvmloader filtering
Why? Seeing the prior
On 22/01/2020 10:57, George Dunlap wrote:
> On 1/22/20 10:14 AM, Julien Grall wrote:
>>
>>
>> On 22/01/2020 10:01, Sergey Dyasli wrote:
>>> On 20/01/2020 10:01, Jan Beulich wrote:
On 17.01.2020 17:44, Sergey Dyasli wrote:
> v2 --> v3:
> - Remove hvmloader filtering
Why?
On 22/01/2020 11:19, Sergey Dyasli wrote:
On 22/01/2020 10:14, Julien Grall wrote:
On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
On 17.01.2020 17:44, Sergey Dyasli wrote:
v2 --> v3:
- Remove hvmloader filtering
Why? Seeing the prior discussion, how
On 22/01/2020 10:14, Julien Grall wrote:
>
>
> On 22/01/2020 10:01, Sergey Dyasli wrote:
>> On 20/01/2020 10:01, Jan Beulich wrote:
>>> On 17.01.2020 17:44, Sergey Dyasli wrote:
v2 --> v3:
- Remove hvmloader filtering
>>>
>>> Why? Seeing the prior discussion, how about adding
On 1/22/20 10:14 AM, Julien Grall wrote:
>
>
> On 22/01/2020 10:01, Sergey Dyasli wrote:
>> On 20/01/2020 10:01, Jan Beulich wrote:
>>> On 17.01.2020 17:44, Sergey Dyasli wrote:
v2 --> v3:
- Remove hvmloader filtering
>>>
>>> Why? Seeing the prior discussion, how about adding
On 22/01/2020 10:01, Sergey Dyasli wrote:
On 20/01/2020 10:01, Jan Beulich wrote:
On 17.01.2020 17:44, Sergey Dyasli wrote:
v2 --> v3:
- Remove hvmloader filtering
Why? Seeing the prior discussion, how about adding XENVER_denied to
return the "denied" string, allowing components which want
On 22.01.2020 11:01, Sergey Dyasli wrote:
> On 20/01/2020 10:01, Jan Beulich wrote:
>> On 17.01.2020 17:44, Sergey Dyasli wrote:
>>> v2 --> v3:
>>> - Remove hvmloader filtering
>>
>> Why? Seeing the prior discussion, how about adding XENVER_denied to
>> return the "denied" string, allowing
On 20/01/2020 10:01, Jan Beulich wrote:
> On 17.01.2020 17:44, Sergey Dyasli wrote:
>> v2 --> v3:
>> - Remove hvmloader filtering
>
> Why? Seeing the prior discussion, how about adding XENVER_denied to
> return the "denied" string, allowing components which want to filter
> to know exactly what to
On 17.01.2020 17:44, Sergey Dyasli wrote:
> v2 --> v3:
> - Remove hvmloader filtering
Why? Seeing the prior discussion, how about adding XENVER_denied to
return the "denied" string, allowing components which want to filter
to know exactly what to look for? And then re-add the filtering you
had?
Hide the following information that can help identify the running Xen
binary version: XENVER_extraversion, XENVER_compile_info, XENVER_changeset.
This makes harder for malicious guests to fingerprint Xen to identify
exploitable systems.
Add explicit cases for XENVER_commandline and
19 matches
Mail list logo
