This is the real solution for the Intel problem :)
https://github.com/QubesOS/qubes-issues/issues/4318
I believe IBM stated they also have protections against the Rowhammer
attacks
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
'qvm-prefs fedora-32-dvm-template' shows that 'template_for_dispvms' is
marked as 'True' and the template is Fedora-32.
I will try fully updating, deleting, restarting, and trying again.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
> Yes, it is, and from what you have said, that is what you have. (EXCEPT
> that the flag is `template_for_dispvms` not `template_for_dvms` - is this
> a
> typo or the root of the problem?)
>
>
I believe that was a typo, sorry. I was just stating what the flag was
from your first post,
I appreciate your help.
'qvm-run dispvm=fedora-32-dvm-template --service qubes.StartApp+xterm'
results in the error:
unrecognized arguments: qubes.StartApp+xterm.
I don't know if I am communicating this correctly, but I am trying to
create a fedora-32-dvm, that is also itself a DVMTemplate
According to the documentation, I try:
'qvm-prefs fedora-32-dvm template_for_dispvms True'
error: no such domain: 'fedora-32-dvm'
Tried 'qvm-prefs fedora-32 template_for_dispvms True'
error: no such property: 'template_for_dispvms'
Following 'Creating a New DisposableVM Template' further
Thank you both.
For security reasons, in case the DVMTemplate has been compromised, I
deleted it.
How would I go about properly creating a fedora-32-dvm with the
'template_for_dvms' flag set?
Thank you
--
You received this message because you are subscribed to the Google Groups
I have a debian-10-dvm and a whonix-ws-15-dvm. I also had a fedora-30-dvm,
but when upgrading to fedora-32, I followed "Creating a New DisposableVM
Template" here: (https://www.qubes-os.org/doc/disposablevm-customization/),
so no longer have the fedora-30-dvm. Instead, I have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
That was, I admit, an embarrassing mistake.
Split GPG encryption is now working! Thank you for helpin gme.
Please post a bitcoin address (signed and encrypted); would like to thank
you for your time.
My new, secure Split GPG public key
> Once the simple variant works, try a more complicated one...
>
> Great idea. Just to see if I was being crazy, I created a new AppVM and
GPG key to test with. No 'qubes-gpg-client', '--trusted-key', etc.
Like @unman had been suggested, I continued to try:
gpg -r New_Key -e '/home/user/Test
> >
>
> Read my last message - you dont actually type the angle brackets
> This is simply a bash script, you can inspect for yourself: it's at
> /usr/bin/qubes-gpg-client-wrapper
>
> I'm not sure I understand your clarification - in any case, use the
> command line I cited without the angle
qubes-gpg-client-wrapper -r robertspig...@protonmail.ch --trusted-key
-e
'/home/user/Documents/Test_Encryption.txt' -o /home/user/Documents/Final.gpg
Still results in:
bash: C2C60E279E86F10D5697782535CE0FE6C2141823: No such file or directory
What is the wrapper? This also does not open the
I tried the command with '--output OutPutFilePath.asc':
qubes-gpg-client --output /home/user/Documents/Final.asc --encrypt
--recipient --trusted-key
'/home/user/Documents/Test_Encryption.txt'
Resulted in the error:
bash: C2C60E279E86F10D5697782535CE0FE6C2141823: No such file or directory
I apologize for the long absence. I appreciate your help.
While this helped with the 'There is no assurance this key belongs to the
named user' error, it still could not complete the encryption.
qubes-gpg-client --output --OUTPUT_PATH.asc --encrypt --recipient
--trusted-key InFile
Continues
I'm considering posting in qubes-issues, but I want to make sure this isn't
something I'm doing wrong myself/a stupid mistake before I do so. Looked
around online, asked here and on twitter/reddit, and I'll continue to wait
a few more days.
--
You received this message because you are
I have a master private key (Certify Only) stored in Vault, separate
Encryption and Sign secrete_subkeys generated in Vault and stored in
networkless work-gpg. All public keys stored in a separate AppVM for
'qubes-gpg-client' command to access the work-gpg VM via the Split GPG
protocol.
I
15 matches
Mail list logo
