I guess many people on this mailinglist are using a smartphone, regardless of the downsides. More and more services are only fully accessible via smartphone, at least where Im from. Employers force you to. In 2020 we are probably going to see two new smartphones capable of running software based on the mainline linux kernel: pinephone an librem5. Im interested technically and security wise.

I'm curious about peoples view on this from a qubes/security perspective.

Two articles that will get you up to speed, first on hardware, second on software.

https://tuxphones.com/yet-another-librem-5-and-pinephone-linux-smartphone-comparison/
https://fam-ribbers.com/2019/12/28/State-of-Linux-on-mobile-and-common-misconceptions.html

Currently I'd say
- dont mix security domains on your smartphone that you dont mix on qubes (ie if you have separate qubes for work mail and private mail on your laptop, dont put work and private mail together on the same smartphone). This is hard though. Do people walk around with 3 or more smartphones? - smartphones are less secure than qubes or well maintained regular linux pc's

Things I wonder about:
- Is there a possibility that we are in the foreseeable future going to see Qubes-level security (domain separation by baremetal virtualisation) on a smartphone/ARM? Is there an effort being made? - Does the arrival of mainline linux on smartphones and other developments around pinephone/librem5 change anything for Qubes users in particular and security conscious people in general?
- Can we put more trust in these new phones than in current phones?
- Particular strategies for using the smartphone next to qubes in a safe way that arent commonly known.


--
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 an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/quclsp%24d30%241%40blaine.gmane.org.

Reply via email to