Apps ship with source. To let you run without reading the source, apps run without any privileges by default. No files, no network.
You can grant broad privileges to a single function after reading just its source.
The issue: functions can be over-ridden, so you end up accidentally granting privileges to malicious nooks and crannies.
I need to go back to app-level permissions. Grant narrow privileges to the whole app, without regard to what function uses them.
A concrete use case for permissions by caller (now removed from Teliva)
By its nature, a file browser can list directory contents and open files all over the computer. How could we convince ourselves that it's only using these privileges to meet our requests?
My old solution: app is written in such a way that someone can grant these privileges to a single function after convincing themselves it opens a single file/directory every time the Enter key is pressed.
"Part 2 is tricky. The first output value 'cdfgba' could be either a 0, 6, or 9. To figure out which one it is I could do some fancy constraint satisfaction. That sounds hard. Or I could exhaustively try all permutations of the 7 letters. That sounds easy! Here's my plan.."
It just occurred to me that I can smush the dependencies of two packages together to visualize them at the same time. Here's libcairo2-dev and libsdl2-dev at once.
Apologies for the low volume of the recording :/ This copy seems slightly louder to me than the version on the official page. However the official page includes (high-quality and audible) Q&A at the end.
"Third, FOSS has become a religion for many. All things must be FOSS because itβs a holy conquest, and if just everything were FOSS all would be perfection because reasons."
If FOSS were actually a religion, the holy conquest you describe would be the most adorable and least bloody holy conquest in the history civilization.
If FOSS were actually a religion, then what is stopping you from joining the least bloody and most adorable religion in the history of civilization?