Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/21/2017 05:00 AM, loke...@gmail.com wrote: > On Thursday, 20 July 2017 20:29:11 UTC+8, Patrik Hagara wrote: > >> On 07/20/2017 02:08 PM, Patrik Hagara wrote: >>> As for the Linux kernel, you want to use the earlyprintk >>> param, either

Re: [qubes-users] How can I test that my AEM configuration is correct?

On Thursday, 20 July 2017 20:29:11 UTC+8, Patrik Hagara wrote: > On 07/20/2017 02:08 PM, Patrik Hagara wrote: > > As for the Linux kernel, you want to use the earlyprintk param, > > either "earlyprintk=vga,keep" or "earlyprintk=xen,keep" should > > work. Again, the full (and fairly long) list of

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 02:08 PM, Patrik Hagara wrote: > As for the Linux kernel, you want to use the earlyprintk param, > either "earlyprintk=vga,keep" or "earlyprintk=xen,keep" should > work. Again, the full (and fairly long) list of supported > parameters

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 01:13 PM, Elias Mårtenson wrote: > On 20 July 2017 at 17:49, Patrik Hagara > wrote: > > > Oh yes, now I remember! This was definitely a Linux kernel issue > for me, it just didn't

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 17:49, Patrik Hagara wrote: > Oh yes, now I remember! This was definitely a Linux kernel issue for > me, it just didn't setup VGA console logging yet so it seems like a > tboot hang. See the mail I just sent about updating dom0 kernel. I now have

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 11:44 AM, Elias Mårtenson wrote: > On 20 July 2017 at 17:31, Patrik Hagara > wrote: > > Now that I tried removing min_ram from my setup it still works, so > perhaps the fix for

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 17:31, Patrik Hagara wrote: Now that I tried removing min_ram from my setup it still works, so > perhaps the fix for this was something different... Can't recall what > though. :-\ > > Ah well, guess we'll have to go back to taking pictures of the screen.

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 11:21 AM, Elias Mårtenson wrote: > On 20 July 2017 at 16:51, Patrik Hagara > wrote: > > >> Thank you! You were right of course. There was a disabled option >> referring to

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 16:51, Patrik Hagara wrote: > > Thank you! You were right of course. There was a disabled option > > referring to "trusted execution" that was turned off. Enabling that > > gave me much more than 3 pages of debug output. > > > > Unfortunately, the

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 10:46 AM, loke...@gmail.com wrote: > On Thursday, 20 July 2017 16:22:22 UTC+8, Patrik Hagara wrote: > >> That's a non-fatal error, I have that in my log too. >> >> What's more interesting is the last photo, in particular the >>

Re: [qubes-users] How can I test that my AEM configuration is correct?

On Thursday, 20 July 2017 16:22:22 UTC+8, Patrik Hagara wrote: > That's a non-fatal error, I have that in my log too. > > What's more interesting is the last photo, in particular the line: > > ERR: SENTER disabled by feature control MSR (5) > > I _think_ this means that your

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 10:09 AM, Elias Mårtenson wrote: > On 20 July 2017 at 15:58, Patrik Hagara > wrote: > > > This looks to me like tboot either wasn't loaded at all or memory > logging is disabled.

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 20 July 2017 at 15:58, Patrik Hagara wrote: > This looks to me like tboot either wasn't loaded at all or memory > logging is disabled. > > Check the tboot cmdline used -- search for the following in > /boot/grub2/grub.cfg: > > multiboot /tboot.gz placeholder

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 09:42 AM, loke...@gmail.com wrote: > On Thursday, 20 July 2017 15:18:26 UTC+8, Patrik Hagara wrote: > >> Try checking the tboot log (from dom0) for any obvious error >> messages: sudo txt-stat > > Thanks. I did this, but I'm not

Re: [qubes-users] How can I test that my AEM configuration is correct?

On Thursday, 20 July 2017 15:18:26 UTC+8, Patrik Hagara wrote: > Try checking the tboot log (from dom0) for any obvious error messages: > sudo txt-stat Thanks. I did this, but I'm not sure how to interpret the information. It does say "TXT measures launch: FALSE". Does that mean that TXT is

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2017 07:32 AM, loke...@gmail.com wrote: > On Friday, 14 July 2017 16:16:21 UTC+8, Patrik Hagara wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> On 07/14/2017 09:45 AM, loke...@gmail.com wrote: >>> On Friday, 30 June 2017

Re: [qubes-users] How can I test that my AEM configuration is correct?

On Friday, 14 July 2017 16:16:21 UTC+8, Patrik Hagara wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 07/14/2017 09:45 AM, loke...@gmail.com wrote: > > On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki > > wrote: > > > >> Oh, it isn't listed in

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2017 09:45 AM, loke...@gmail.com wrote: > On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki > wrote: > >> Oh, it isn't listed in updates-status[1], so I completely forgot. >> Probably it was uploaded to testing before

Re: [qubes-users] How can I test that my AEM configuration is correct?

On Friday, 30 June 2017 04:17:08 UTC+8, Marek Marczykowski-Górecki wrote: > Oh, it isn't listed in updates-status[1], so I completely forgot. > Probably it was uploaded to testing before introducing that system. Of > course it should be migrated to current, will do. I updated to the latest AEM,

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, Jun 29, 2017 at 03:30:38PM +, Rusty Bird wrote: > loke...@gmail.com: > > Yesterday, I installed a new dom0 update which included an updated > > kernel package. I was expecting to see an AEM error when I rebooted, > > but that never

Re: [qubes-users] How can I test that my AEM configuration is correct?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 loke...@gmail.com: > Yesterday, I installed a new dom0 update which included an updated > kernel package. I was expecting to see an AEM error when I rebooted, > but that never happened. I'm guessing you've installed anti-evil-maid v3.0.4? You could

Re: [qubes-users] How can I test that my AEM configuration is correct?

Thanks for the reply. The funny thing is that I did see my secret message. That's why I thought it was so weird. That's why I asked for a way to force a failure so that I can double check this. -- You received this message because you are subscribed to the Google Groups "qubes-users"

Re: [qubes-users] How can I test that my AEM configuration is correct?

On 06/29/2017 06:47 AM, loke...@gmail.com wrote: I enabled AEM some time ago, and so far it's worked the way I'd expect it to. Based on what I have read here, I came to the understanding that after upgrading the dom0 kernel I'd get an AEM error when I reboot the machine, since the kernel is

[qubes-users] How can I test that my AEM configuration is correct?

I enabled AEM some time ago, and so far it's worked the way I'd expect it to. Based on what I have read here, I came to the understanding that after upgrading the dom0 kernel I'd get an AEM error when I reboot the machine, since the kernel is different from the last boot. Yesterday, I