Booting into Kali (forensics mode) and unlocking the ssd failed.
I typed out the passphrase to a text document, confirmed it was correct,
and pasted it into the prompt.
"incorrect passphrase"
This implies to me that the header was altered in some way. 2 days ago, my
battery has completely
I have tried this process with the other kernel options available as
well, to no avail.
Any help or advice (successful or not) is appreciated.
sounds daunting. So did you use a live-linux that has luks 'onboard'
(like tails) ? That way you could distinguish between luks problems and
qubes
thanks but the drive does not exist as you assume - i want to make the disk
from the existing volumegroup/disk-pool
I think i first need to allocate a lvm, then encrypt it ? and assign it
somehow
to get it to be persistent i think i need to also alter the XLM file used
to define the virtual
Hi
søndag den 28. juni 2020 kl. 23.23.39 UTC+2 skrev Dave C:
>
> A) Is it safe to remove qubes-core-agent-dom0-updates and
> qubes-vm-recommended from a debian template?
> I've noticed that installing qubes-vm-recommended brings yum and yum-utils
> along with it. This leaves me wondering, is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 7/5/20 5:32 AM, Jason Long wrote:
> I just want to use Qubes-OS in general and not use its
> Virtualization feature. Is it secure or just secure in
> Virtualization?
Please always answer to the list so others can follow and contribute
to our
Hello All,
Getting back in the swing after an enforced absence.
I've uploaded new builds of the bionic and Arch templates to
https://qubes.3isec.org/Templates
These packages are signed with my Qubes Signing key - you can find this
on keyservers, in this list, and at GitHub. Verify the key, and
