Le samedi 13 janvier 2018 19:15:19 UTC+1, Reg Tiangha a écrit :
> Hey everyone,
>
> I managed to get the Retpoline and IBRS kernel patches off the LKML
> working on Qubes (I also included the Linux-Hardened Project patches in
> there too), so I figured I'd share my work. I have a branch here for
On Saturday, 13 January 2018 20:39:18 CET Mohit Goyal wrote:
> Question 1: What is your development environment ?
The beauty of Qubes is that its rather fluid in a lot of things. For
instance your distribution of choice.
I have a desktop computer and I have a VM called 'Work'. In it it contains
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I'm testing upgrade process for QSB37 patches for R3.2[1]. And it
isn't straightforward, mostly because of major Xen upgrade (4.6->4.8).
What I have currently:
1. Execute `sudo qubes-dom0-update`, but when prompted for confirmation,
abort
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-14 15:51, Marek Marczykowski-Górecki wrote:
> Hi,
>
> I'm testing upgrade process for QSB37 patches for R3.2[1]. And it
> isn't straightforward, mostly because of major Xen upgrade
> (4.6->4.8). What I have currently:
>
> 1. Execute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Jan 14, 2018 at 11:54:38PM +0100, 'Tom Zander' via qubes-devel wrote:
> On Sunday, 14 January 2018 22:09:10 CET Marek Marczykowski-Górecki wrote:
> > Ok, lets start with ~/.config/xdg/autostart/*.desktop. "files with
> > key/value pairs",
On Monday, 15 January 2018 00:31:14 CET Marek Marczykowski-Górecki wrote:
> I'm trying to show you how things one can consider a configuration, may
> enable you to compromise a VM.
This may show the underlying reason for the mis-communication.
What is considered a configuration is not really
Perhaps a method to change the presented screen resolution in a VM to
make browser fingerprinting more difficult?
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, Jan 13, 2018 at 05:22:11PM +, Tom Zander wrote:
> On Friday, 12 January 2018 15:18:39 GMT Marek Marczykowski-Górecki wrote:
> > Well, such sanitization would need to be application specific, and would
> > be *very* fragile element. For
On Sunday, 14 January 2018 22:09:10 CET Marek Marczykowski-Górecki wrote:
> Ok, lets start with ~/.config/xdg/autostart/*.desktop. "files with
> key/value pairs", right? Those don't have executable bit either.
I'm not sure why you are trying really hard to misunderstand me :(
I wrote that this
On 01/14/2018 06:17 AM, Reg Tiangha wrote:
> On 01/14/2018 03:18 AM, Frédéric Pierret (fepitre) wrote:
>> Le samedi 13 janvier 2018 19:15:19 UTC+1, Reg Tiangha a écrit :
>>
>> Hi Reg,
>>
>> Thank you for your work. I'm also interested for my own work. Have you
>> tested yourself the patches
On 01/14/2018 03:18 AM, Frédéric Pierret (fepitre) wrote:
> Le samedi 13 janvier 2018 19:15:19 UTC+1, Reg Tiangha a écrit :
>
> Hi Reg,
>
> Thank you for your work. I'm also interested for my own work. Have you tested
> yourself the patches against a Spectre POC code?
>
> Thank you again.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/14/2018 10:51 PM, Marek Marczykowski-Górecki wrote:
> There was a suggestion to name an updated version as r3.3 (which
> means separate repository). But this technically would also break
> our promise to keep "R3.2" supported at least 1 year
12 matches
Mail list logo