6 ms·

I'm not talking about syscalls, but that in modern times everything of value is in your account, and computers are rarely shared. So when you download a game y

I'm not talking about syscalls, but that in modern times everything of value is in your account, and computers are rarely shared. So when you download a game your threat model isn't that it might want to mess with the kernel, but that it's going to steal all your data from your browser cache. Dealing with that requires some sort of sandboxing.

lmm 3y ago
> I'm not talking about syscalls, but that in modern times everything of value is in your account, and computers are rarely shared. Huh? No-one is advocating using user accounts for security. > So when you download a game your threat model isn't that it might want to mess with the kernel, but that it's going to steal all your data from your browser cache. Why do you think this contradicts anything I said? And what mechanism do you think it's going to use to do that? Maybe not syscalls in the narrow sense, but certainly via one of the "zillion different ways apps could potentially interact with each other". > Dealing with that requires some sort of sandboxing. Is this the "something must be done" fallacy? "We need some kind of sandbox, snap/flatpak are some kind of sandbox, therefore we need snap/flatpak".