To Taiidan and all others complaining about Purism lies and consumer being
misled.
I keep reading stuff about purism lying about deactivating/disabling ME
being impossible, lying about the future of Intel removing ME, etc. I think
THIS is misleading.
First, its me_cleaner job to do the cleaning.
"Their objective is good."
Talking about Purism here, not Intel :)
Le dim. 15 avr. 2018 08:52, Thierry Laurion a
écrit :
> To Taiidan and all others complaining about Purism lies and consumer being
> misled.
>
> I keep reading stuff about purism lying about
One small caveat, whonix-ws updated, everything else says there are no
updates? While this is possible I am thinking its unlikely?
I tried to update dom0 from the terminal
sudo qubes-dom0-update
and got
/usr/lib/qubes/qubes-rpc-multiplexer: 14:
On Sun, April 15, 2018 11:01 pm, vel...@tutamail.com wrote:
> I am exploring the best Qubes laptop based on the following criteria:
>
>
> 1) Secure/Privacy
> 2) Usability and maintenance for the layman in need of security
> 3) Price
> 4) New laptop
I wrote a selection guide here:
I am exploring the best Qubes laptop based on the following criteria:
1) Secure/Privacy
2) Usability and maintenance for the layman in need of security
3) Price
4) New laptop
Based on my research the most secure would be:
Older laptops:
G505
x220
T420
W520/W530
Pro:
-price/value
-Coreboot
On Sun, April 15, 2018 8:41 pm, Chris Laprise wrote:
> On 04/15/2018 04:05 PM, Chris Laprise wrote:
>
>> On 04/15/2018 03:51 PM, Chris Laprise wrote:
>>
>>> Project link: https://github.com/tasket/Qubes-VM-hardening
>>>
>>
>> TL;dr : This closes the obvious loopholes that malware can use in Qubes
On Sun, April 15, 2018 10:24 pm, vel...@tutamail.com wrote:
> I am getting ACPI errors when I boot, everything works, or at least I
> haven't seen a functionaility issue.
I see some as well, with no obvious impact.
> Not sure this is related but my time is off by 5 hours in Qubes. My BIOS
> time
I am getting ACPI errors when I boot, everything works, or at least I haven't
seen a functionaility issue. I am however concerned and trying to understand
implications from a functonal and security perspective. The errors are:
[ 1.] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup
On Sun, April 15, 2018 6:36 pm, Demi M. Obenour wrote:
> How can I build a kernel module for an AppVM? I would like to write
> some simple kernel modules, but I cannot figure out how to build them. I
> get:
>
>
> make[1]: *** No rule to make target 'tools/objtool/objtool', needed by
>
On Sun, April 15, 2018 5:41 pm, lso...@gmail.com wrote:
> On Wednesday, April 11, 2018 at 4:44:11 AM UTC-7, awokd wrote:
>
>> On Wed, April 11, 2018 12:25 am, lsofxp via qubes-users wrote:
>>
>>> On Tue, Apr 10, 2018 at 7:24 AM, 'awokd' via qubes-users
>>>
>>
> Did you increase "system max
On 04/13/18 07:19, Chris Laprise wrote:
I've done some experimenting to get my Debian VMs to boot faster. So far
I've reduced the start time significantly by disabling these services in
the template:
apt-daily.service
apt-daily.timer
apt-daily-upgrade.service
apt-daily-upgrade.timer
pppd-dns
On 04/15/2018 04:05 PM, Chris Laprise wrote:
On 04/15/2018 03:51 PM, Chris Laprise wrote:
Project link: https://github.com/tasket/Qubes-VM-hardening
TL;dr : This closes the obvious loopholes that malware can use in Qubes
AppVMs to escalate privileges, _impersonate_ real apps (to steal
On 2018-04-16 01:05, Chris Laprise wrote:
On 04/15/2018 03:51 PM, Chris Laprise wrote:
Project link: https://github.com/tasket/Qubes-VM-hardening
TL;dr : This closes the obvious loopholes that malware can use in
Qubes AppVMs to escalate privileges, impersonal real apps (to steal
credentials),
On 04/15/2018 03:51 PM, Chris Laprise wrote:
Project link: https://github.com/tasket/Qubes-VM-hardening
TL;dr : This closes the obvious loopholes that malware can use in Qubes
AppVMs to escalate privileges, impersonal real apps (to steal
credentials), and persist after shutdown/restart.
Leverage Qubes template non-persistence to fend off malware. Lock-down,
quarantine and check contents of /rw private storage that affect the VM
execution environment.
vm-boot-protect.service:
* Acts at VM startup before private volume /rw mounts
* User: Protect /home desktop & shell
I have the following setup:
Qubes 3.2, xfce4 interface
sys-usb
I want to be able to connect my Android phone to a vm and rsync its contents.
I can connect the phone and "qvm-usb -a" it to the VM, and it appears available
under the File Manager application as "mtp://[usb:002,004]/" but I
How can I build a kernel module for an AppVM? I would like to write
some simple kernel modules, but I cannot figure out how to build them.
I get:
make[1]: *** No rule to make target 'tools/objtool/objtool', needed by
'/home/user/kernel/wierd.o'. Stop. make: *** [Makefile:1507:
On Wednesday, April 11, 2018 at 4:44:11 AM UTC-7, awokd wrote:
> On Wed, April 11, 2018 12:25 am, lsofxp via qubes-users wrote:
> > On Tue, Apr 10, 2018 at 7:24 AM, 'awokd' via qubes-users
>
> >>> Did you increase "system max storage size" while the VM was off? Do
> >>> that, then look in Disk
On 2018-04-15 10:07, Chris Laprise wrote:
On 04/14/2018 10:03 PM, Stumpy wrote:
I had a really hard time getting a vpnvm to work in 3.2 but finally
got it and it more or less ran great for months. In one of the 4 RCs
(3 I think) I was able to restore that vpnvm to 4.0 rc3. Now I can't
seem to
On Sunday, April 15, 2018 at 3:25:24 PM UTC+2, Taha Ahmed wrote:
> Just in case this might benefit someone else.
>
> The installation of Qubes OS proceeded without any hiccups, and the
> Trackpoint along with its hardware buttons actually worked during the
> installation.
>
> But when Qubes OS
Just in case this might benefit someone else.
The installation of Qubes OS proceeded without any hiccups, and the Trackpoint
along with its hardware buttons actually worked during the installation.
But when Qubes OS itself started, the Trackpoint and its hardware buttons did
not respond. The
On Saturday, April 14, 2018 at 8:33:22 PM UTC-4, awokd wrote:
> On Sat, April 14, 2018 10:12 pm, chipperXXX wrote:
> > Hello,
> > I am fairly new to QUBES, as I have only just installed QUBES 4.0 and have
> > been learning the OS. I initally installed QUBES 3.x (last RC), and
> > immediately
On Sat, April 14, 2018 7:57 am, 799 wrote:
> Hello,
>
>
> I have applied Updates to my Templates and also flashed Coreboot ony
> X230.
> I haven't used my internal WWAN Card for a while as I was using WiFi.
> The WWAN Card was working before (default template/Stock ROM) without a
> problem, now it
23 matches
Mail list logo