InnerScientist

joined 2 years ago
[–] InnerScientist@lemmy.world 5 points 1 day ago (1 children)

Works for me with Voyager on mobile.

[–] InnerScientist@lemmy.world 8 points 1 week ago

Shriveled up in fear

[–] InnerScientist@lemmy.world 2 points 1 week ago (1 children)

It has exclusives iirc, steam deck "just" has the rest.

The switch also has coop multiplayer and a few other things going for it as well.

[–] InnerScientist@lemmy.world 30 points 1 week ago (1 children)

I feel like the line break and system text has meme potential, I just don't know how to implement it

[–] InnerScientist@lemmy.world 4 points 1 week ago (1 children)

Just waiting for someone to "leak" a phone and it turns out to be last years phone, just to see how long it takes people to notice.

[–] InnerScientist@lemmy.world 3 points 1 week ago

blinks left
blinks right
accelerates backwards

[–] InnerScientist@lemmy.world 2 points 2 weeks ago (3 children)

That just moves the problem, what happens if I put a piece of paper between them? Unless they don't interact with anything they still face the same problem.

[–] InnerScientist@lemmy.world 5 points 2 weeks ago

You can nixos-rebuild her, you have the technology.

[–] InnerScientist@lemmy.world 2 points 2 weeks ago

Tldr:

Rootful podman with podman run --userns=auto is more secure than one rootless host user running many pods, because those pods could (theoretically) attack each other.
though you still have the possibility of an exploit in the image pull

Rootless podman running one pod (as in service including database and so on) per host user with different subuid Ranges is the most secure, but you have to actually set that up which can be a lot of work depending on distribution.

[–] InnerScientist@lemmy.world 2 points 2 weeks ago

All devices launching with Android 10 and higher are required to use file-based encryption.

To use the AOSP implementation of FBE securely, a device needs to meet the following dependencies:

  • Kernel Support for Ext4 encryption or F2FS encryption.
  • Keymaster Support with HAL version 1.0 or higher. There is no support for Keymaster 0.3 as that does not provide the necessary capabilities or assure sufficient protection for encryption keys.   
    
  • Keymaster/Keystore and Gatekeeper must be implemented in a Trusted Execution Environment (TEE) to provide protection for the DE keys so that an unauthorized OS (custom OS flashed onto the device) cannot simply request the DE keys.   
    
  • Hardware Root of Trust and Verified Boot bound to the Keymaster initialization is required to ensure that DE keys are not accessible by an unauthorized operating system.

https://source.android.com/docs/security/features/encryption/file-based?hl=en

view more: next ›