Hello,
I just made a new installation of Qubes 3.2 and tried to update dom0 in
it, without success.
It always says there is no update, over CLI aswell as over the Qubes VM
Manager.
1.
[fabian@dom0 ~]$ sudo qubes-dom0-update
2.
Using sys-firewall as UpdateVM to download updates for Dom
Hello,
I just wanted to give some positive feedback on the kernel.
I'm using a i7-6700K CPU and a AMD RX 480 GPU, and kernel-4.9.35-19 is the
first kernel version which runs with my dedicated graphics card. This *should*
have been the case starting with kernel 4.8, but until now it never did. Alw
I'm not sure if it is, or if it is open source.
But he didn't mentioned it at all in his blog post (
https://eugene.kaspersky.com/2016/11/15/finally-our-own-os-oh-yes/)
If I would make such an operating system, I would at least mention that it
will be open source, if it would be. He didn't, an
I don't like this project at all to be honest.
First thing is that it's closed source, which means he can prove exactly
*nothing* to me in terms of security. As long as I can't check, I don't
believe. Sorry.
Second: He writes it's hacking proof, which is impossible to proof. Yes,
maybe it's har
2:24:02PM +0200, Fabian Wloch wrote:
I can confirm that error under certain circumstances.
If I write the ISO (checked via Sha256+GPG) with Rufus from Windows 10, I
get the exact same error under multiple computers with totally different
hardware.
If I write it on my USB drive with dd under Fedo
I can confirm that error under certain circumstances.
If I write the ISO (checked via Sha256+GPG) with Rufus from Windows 10, I
get the exact same error under multiple computers with totally different
hardware.
If I write it on my USB drive with dd under Fedora 24, it works without any
errors.
I just installed Qubes 3.1 on the same hardware, and the performance was
"how it should be". Then I made the in-place-upgrade to Qubes 3.2, which
resulted in the same problems as I mentioned in the first mail.
So I guess its not the Kernel, but some kind of software that causes the
problem.
An
Does anyone use a CPU from the current Skylake-Generation, or maybe even a
i7 6700k?
I bought the hardware a couple weeks ago, and just tested it with Qubes
3.2, and it quit works.
Just the performance is a mess.
There are constantly small laggs, which I don't have with an older Core i5
in m
What is the purpose of sys-firewall..?
I noticed that every App VM has its own "Firewall Rules" > inside of VM
Settings.
So therefore, what is the purpose of sys-firewall..?
Thanks
The reason I am aware of: VMs should not see each other. firewallVM allows
them to see/connect to netVM, but
Am 20.09.2016 09:25 schrieb amadaus:
I'd like to create my own personal email server but don not feel
technically competent to set it up securely. However I've read about a
"out of the box" solution called Mail-In-A-Box. Do any Qubes users have
experience or thoughts on this potential solution?
I had my raspberry pi configured as tor-wifi-hotspot, which worked fine.
But its about a year ago, and my raspi died a few months ago after I tried
some... stupid thing with it.
But it worked without any problems, so if you think it makes sense to you,
I don't see any problems with this.
I p
Hello,
I have the following problem: I want to make some screenshots during the
installation / record the installation process on video, but I can't boot into
the installer at all.
My reason for this is to make some screenshots/video for an installation guide.
I tried with Qubes 3.2-RC2 and 3.2
I built my "Workstation" myself a couple weeks ago, here are the first results:
Tested this with Qubes 3.1, 3.2-RC2 and just now with 3.2-RC3.
== Hardware ==
Mainboard: ASRock Z170 Extreme4
BIOS Version: P3.40
CPU: Intel Core i7 6700K
Graphics: Intel HD Graphics 530
TPM Chip: ASRock TPM-S Module (
I built my own workstation about 3 weeks ago and tested it within that time,
and I finally finished my HCL report :)
== Hardware ==
Mainboard: ASRock Z170 Extreme4
BIOS Version: P3.40
CPU: Intel Core i7 6700K
Graphics: Intel HD Graphics 530
TPM Chip: ASRock TPM-S Module (More details below)
Othe
Bought my "Workstation" a couple weeks ago and tested it pretty good so far.
== Hardware ==
Mainboard: ASRock Z170 Extreme4
BIOS Version: P3.40
CPU: Intel Core i7 6700K
Graphics: Intel HD Graphics 530
TPM Chip: ASRock TPM-S Module (More details below)
Others: 16 GB RAM (2x8GB); SATA-3 SSD (Crucia
Am Dienstag, 30. August 2016 19:49:02 UTC+2 schrieb neilh...@gmail.com:
> What would a BIOS exploit mean for QUBES users..?
>
> 1. Can the BIOS directly access the network? For something like sending
> keystrokes directly to the network card, bypassing QUBES OS..?
>
> 2. Or does it just inject s
Am Sonntag, 31. Juli 2016 01:22:48 UTC+2 schrieb Andrew David Wong:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-07-30 16:06, Fabian Wloch wrote:
> > Am Samstag, 30. Juli 2016 23:25:05 UTC+2 schrieb Markus Kilås:
> >> On 07/30/2016 06:25 PM, Fabian W
Am Samstag, 30. Juli 2016 23:25:05 UTC+2 schrieb Markus Kilås:
> On 07/30/2016 06:25 PM, Fabian Wloch wrote:
> The issues with unprotected /boot and BIOS is briefly mentioned on the
> below link and it sounds like AEM should be able to at least be able to
> detect a compromise for
Hello,
there are plenty threads of people asking for advice for dual boot, but this is
not my intention here.
What I would like to know is, what are the risks of a Qubes-Dualboot System?
Let's assume I have installed the latest version of Qubes, Encrypted the whole
drive using LUKS (and a 32 ch
19 matches
Mail list logo