3 ms·
What I would like to see, and they're effectively doing this already by allowing the Play Store on Chromebooks, is a sandbox INSIDE the encrypted area, but outs
by headmelted 10y ago
What I would like to see, and they're effectively doing this already by allowing the Play Store on Chromebooks, is a sandbox INSIDE the encrypted area, but outside of the signed code.
Basically, an official container support in user space that once you enter developer mode allows you to keep the security features you have currently (signed boot-code checking, encryption), but also a restricted container that allows for native apps like this.
Then we could get rid of the Developer Mode splash screen, or at least allow it to be disabled by choice.
- Pigo 10y agoI like this idea. Official container support would be a game changer, especially for those unnerved by going off the beaten path.
- tmzt 10y agoI really want to see this on Android as well. Having user namespace support on carrier builds would go a long way for this. I've been think about how this would work. Something like the Samsung ultra powersaving mode. A basic lock screen and dialer with 911 support, then the running environment could be swapped between full Android, Ubuntu or anything else.
- digi_owl 10y agoCould have sworn that you already get apps that set up a Debian chroot, complete with a SDL based X11 desktop even.