Since I don't have two identical drives, I tried to do this:
- clone MBR and partition info
$ sudo dd if=/dev/sdc of=aem-mbr.img bs=512 count=1
- clone AEM partition
$ sudo dd if=/dev/sdc1 of=aem-partition.img bs=128K conv=noerror,sync
- copy cloned images to a new USB drive
$ sudo dd if=aem-mb
On Thursday, June 29, 2017 at 9:49:24 PM UTC-4, alexey@gmail.com wrote:
> ... bump ...
To anybody with AEM & USBVM.
$ sudo qubes-dom0-update
Works perfectly after you seize USB controller from USBVM (or sys-net in my
case) back to dom0, reboot and mount your AEM USB drive to /boot. It even
... bump ...
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegrou
Hi All,
I recently figured out how to make my Thinkpad work with Qubes3.2+AEM. Now the
question I have is regarding the dom0 updates (e.g. kernel).
I should just manually mount AEM to /boot and perform the update? Then, AEM
will automatically run another measurement on reboot, update TPM and re
Just want to confirm that the solution suggested in [issue #2155][1] solved my
problem with TBOOT. Basically, when you substitute default TBOOT 1.8.2 from
QubesOS repo with TBOOT 1.9.4 from [Ubuntu][2] my laptop boots and able to
seal/unseal secrets.
It would be great if TBOOT 1.9.4 is included
Hi All,
I am experiencing the same problem with AEM v3.0.4 and TBOOT v1.8.2 on Thinkpad
X1 Carbon 4th Gen (20FCS5CY00) where it reboots precisely after executing
GETSEC[SENTER]. "min_ram" option does not help.
My setup:
* UEFI BIOS in LegacyBoot mode with SecureBoot disabled
* Discrete TPM 1.2
