It was initially intended to be a video stream handler, but they had concerns with audio syncing. They figured they might as well also handle audio in one cohesive AV server instead
Unreal Engine is a major example, you get access to a private repo containing the engine's source code but you're bound by an agreement regarding what you can do with it IIRC. Of course anyone is allowed to apply for access though
For 2, the issue is most phones have a lock screen overview sorta effect, where the phone can wake up from sleep with movement or gestures. Actions on the lock screen can hence trigger things, like media playback and emergency dialling
Huh, I was about to correct you on the use of embarrassment in that the intent was to mean a large amount, but it seems a Wiki edit reverted it to your meaning a year ago, thanks for making me check!
Containers, the concept that Docker implements, lets app developers give a self-contained environment for distribution. For devs that means consistency in deployments across environments, which in turn means sysadmins can deploy each of these apps as fully isolated units.
With that, you get really clean installs/updates/uninstalls, and your deployments get done with a well-defined, declarative definition file which can also handle multi service dependencies (a la Docker Compose/K8s)
The firmware has to allow it, so if you've got physical access to the machine that's possible. Remote access root, on the other hand, can't tell the firmware to register new keys as long as it's configured correctly
Generally yes. For many distros, the kernel signing key is with the distro maintainers and so the package comes with pre-signed kernel images. For distros like Arch and Gentoo, it's the user's responsibility to maintain the signing key and sign each updated kernel
Doesn't that already exist as the Factory Reset Protection (FRP) partition?