On 06/28/2016 02:23 PM, Marek Marczykowski-Górecki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Jun 28, 2016 at 10:36:42AM -0700, raahe...@gmail.com wrote:
Will we be able to upgrade to 3.2 from dom0 update eventually? Or if we choose
not to reinstall is there security
Maybe some hotlink for this operation at Qubes Manager menu ?
If you execute `qvm-shutdown --all --wait` just before shutting down the
>
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
On Tue, 28 Jun 2016, 12384013418489'14'810'4 wrote:
> would be the Intel Skylake Technology SGX a solution, so that the keys
> cannot be read from the crypto processes?
In these covert attacks, the keys are not "read" but leaked. Those leaks
are unlikely to be solved by SGX as it's not the
On 2016-06-28 12:01, Franz wrote:
Hello,
is there some form of tutorial for using Bitcoins with Qubes,
considering that I have no experience of bitcoins?
It seem I should have a VM for a hot wallet for making transactions
and another for a cold wallet to keep the bitcoins. But have no idea
if
Hello,
would be the Intel Skylake Technology SGX a solution, so that the keys cannot
be read from the crypto processes?
https://github.com/01org/linux-sgx
Kind Regards
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this
does the nvidia display work with qubes 3.2?
from what i gather it should due to the newer linux hernel.
so far its the only reasonably priced qubes compatable 4k, 16gb, backlit kb,
15" laptop i found yet even without tpm
cant find a 17" the w450, p50, p70 are over $2k easy
the big risk with
Hello,
is there some form of tutorial for using Bitcoins with Qubes, considering
that I have no experience of bitcoins?
It seem I should have a VM for a hot wallet for making transactions and
another for a cold wallet to keep the bitcoins. But have no idea if it is
possible to move bitcoins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Jun 28, 2016 at 10:36:42AM -0700, raahe...@gmail.com wrote:
> Will we be able to upgrade to 3.2 from dom0 update eventually? Or if we
> choose not to reinstall is there security implications?
Yes. Experimental instruction already online:
On Tuesday, June 21, 2016 at 1:45:48 AM UTC-4, mmih...@gmail.com wrote:
> > > one other thing i noticed a while ago - the dracut text-mode
> > > installer does not show the pop-up asking the user for the LUKS
> > > passphrase, the installation doesn't work because of that.. bug?
> > > feature?
On Monday, June 27, 2016 at 9:12:43 PM UTC-4, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, Jun 27, 2016 at 05:57:00PM -0700, Eva Star wrote:
> > https://github.com/QubesOS/qubes-issues/issues/1581
> >
> > What do you think about adding
Holger,
Great to hear you managed to upgrade the kernel !! This means I might not
need to buy an other laptop after all.
I looked back at what you posted but it's a bit confusing. I'm probably not
the only one.
Would it be possible for you to make a clear overview of all the steps to
take
On 06/27/2016 09:18 PM, Eva Star wrote:
1) VPN doc say at the first part that need to add "network-manager"
and enable it. At the second part it's without "network-manager".
When/On what situations I need I enable?
When using a proxy vm to run the vpn client, you can either enable
network
I installed the debian and whonix templates
But then, whenever I open VM Manager, I get the following error:
"Whoops. A critical error has occured. This is most likely a bug in Qubes
Manager.
libvirtError: internal error: client socket is closed at line 1268 of the file
libvirt.py"
Not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-28 05:05, Chris Grimmett wrote:
> I did the command you suggested, then tried again. I saw the same
> 404 errors. It wasn't until I was working on another project,
> getting screenshots to save to AppVMs
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-28 01:31, qubescr...@gmail.com wrote:
> Hi
>
> Amidst a sea of complaints and bug reports, I just wanted to drop
> a note to say thank you to everyone who's working on Qubes, so
> THANK YOU! You are doing an amazing job, guys! :-)
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-28 00:17, Albin Otterhäll wrote:
> Andrew David Wong:
>> I noticed you started a thread on this last month, too:
>>
>> https://groups.google.com/d/topic/qubes-users/rgjQoi40XKY/discussion
>
>>
> My question was regarding the eventual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-27 18:18, Eva Star wrote:
> 3) I'm worry about hdd encryption by cryptosetup. Is it strong by
> default? We can not choose ALGs at installer...
It uses cryptsetup (LUKS/dm-crypt) under the hood. You can configure
the settings manually
Andrew David Wong:
> I noticed you started a thread on this last month, too:
>
> https://groups.google.com/d/topic/qubes-users/rgjQoi40XKY/discussion
My question was regarding the eventual requirement for customization
that is documented on that page. I didn't think that the installation
18 matches
Mail list logo
