Protection & Security

Rings, permissions, and what the kernel actually enforces.

0 of 18 answered

• Not triedA program that runs as its ownerFoundation
• Not triedDeleting a file does not delete the dataFoundation
• Not triedThe web server that runs as rootFoundation
• Not triedWhen nine bits are not enoughFoundation
• Not triedWhy several weak defencesFoundation
• Not triedWhy the processor has two modesFoundation
• Not triedWhy the system stores no passwordsFoundation
• Not triedThe database account an application usesCore
• Not triedThe log an attacker can editCore
• Not triedWhy system calls are checked so carefullyCore
• Not triedWhy writing past the end of an array is not just a crashCore
• Not triedHow a buffer overflow takes controlChallenge
• Not triedRestricting which system calls existChallenge
• Not triedRoot that is not rootChallenge
• Not triedRunning as root inside a containerChallenge
• Not triedThe gap between checking and usingChallenge
• Not triedWhat randomising addresses buysChallenge
• Not triedWhy chroot is not a security boundaryChallenge