On Friday, June 12, 2020 at 7:38:42 PM UTC-4, unman wrote:
> On Fri, Jun 12, 2020 at 03:57:35PM -0700, xyzo wrote:
> > qubes version 4.0.
> > I need to copy files from win7-template to a Linux appvm. I was suggested
> > to use (qvm-run --pass-io win7-template "type C:\n.pdf" > ./n.pdf)
> > To
On Fri, Jun 12, 2020 at 03:57:35PM -0700, xyzo wrote:
> qubes version 4.0.
> I need to copy files from win7-template to a Linux appvm. I was suggested to
> use (qvm-run --pass-io win7-template "type C:\n.pdf" > ./n.pdf)
> To copy files from win7-template to dom0 then move it from dom0 to any
>
qubes version 4.0.
I need to copy files from win7-template to a Linux appvm. I was suggested to
use (qvm-run --pass-io win7-template "type C:\n.pdf" > ./n.pdf)
To copy files from win7-template to dom0 then move it from dom0 to any
destination appvm. Invoking this command in dom0 terminal, the
Thank you Emily and dhorf-hfr...@hashmail.org for your useful information.
I learned quite a bit more about Qubes OS and ZFS.
--
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
On Friday, June 12, 2020 at 10:10:25 PM UTC+2, Steve Coleman wrote:
>
>
> That being said, it is extremely difficult to reflash your BIOS when
> running a general OS in the normal user context, and even more difficult
> when running a virtualized system such as Qubes. So, if you can prevent
On Fri, Jun 12, 2020 at 2:35 PM wrote:
> Well that's the problem indeed, knowing if you are clean from firmware
> viruses in the first place. But i don't suspect i have firmware viruses and
> i have new pc. It takes a lot of time and money and no one would bother to
> infect specific user. I am
Well that's the problem indeed, knowing if you are clean from firmware
viruses in the first place. But i don't suspect i have firmware viruses and
i have new pc. It takes a lot of time and money and no one would bother to
infect specific user. I am no one. It could be used in attacks on multi
Well that's the problem indeed, knowing if you are clean from firmware
viruses in the first place. But i don't suspect i have firmware viruses and
i have new pc. It takes a lot of time and money and no one would bother to
infect specific user. I am no one. It could be used in attacks on multi
I've worked out what that screen is for, apparently it's analyzing the
hardware, I just let it run for over twenty minutes...I'm guessing that
what I have is too new for that release, then again I'm seeing similar set
ups in the Hardware Compatibility List that are using Qubes OS 4.0. I
Greetings,
I've been having a lot of difficulty over the past year with Qubes and I
wanted to know if I could get some help with the parameters, and
dependencies.
*1 set up the network connections*
i.e. Wifi
*2 set up sys-firewall*
*3 set up the sys-net*
to use Wifi and Firewall
I've had Qubes installed previously on my old motherboard, an ASRock
Fatal1ty Z97X, now I'm seeing if it'll run on my new ASRock Taichi x570.
I'm able to boot from USB via legacy, I get the first GUI install screen
menu, but when I select the option to install, I get an eternal black
screen
dhorf-hfref.4a288...@hashmail.org:
> On Fri, Jun 12, 2020 at 12:49:04PM +, taran1s wrote:
>> - - set a higher encryption from qubes default to aes 512-bit full disk
>> encryption.
>
> a) there is no "aes 512".
> b) the qubes default is aes-xts-512. (which is really aes-256 with
>two
On Fri, Jun 12, 2020 at 12:49:04PM +, taran1s wrote:
> - - set a higher encryption from qubes default to aes 512-bit full disk
> encryption.
a) there is no "aes 512".
b) the qubes default is aes-xts-512. (which is really aes-256 with
two different keys since whoever implemented it for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I would like to change the encryption password of my qubes
installation. And once I start to play with this, I would like to also:
- - set a higher encryption from qubes default to aes 512-bit full disk
encryption.
- - move the /boot partition to
On Friday, 12 June 2020 13:06:01 UTC+1, Rafael Reis wrote:
>
> I’ve also started with no sys-usb and a flash drive. Then imaged the usb
> drive to the internal ssd, and installed sys-usb afterwards. Everything
> went smoothly.
> You indeed cannot have sys-usb if you are booting from the usb
I’ve also started with no sys-usb and a flash drive. Then imaged the usb drive
to the internal ssd, and installed sys-usb afterwards. Everything went smoothly.
You indeed cannot have sys-usb if you are booting from the usb stick.
Never tried the webcam to be honest. I find it counterintuitive to
Hi,
I managed to reboot the PC after the first stage and I'll just add a new
key to luks afterwards.
I still have to find a way to either automate the second stage or skip it
altogether since i can launch it later once logged in for the first time.
Is there a way to at least skip initial
17 matches
Mail list logo
