Code in Response to “The Trouble with Symlinks.”
Code in Response to “The Trouble with Symlinks.”
See: https://news.ycombinator.com/item?id=32190032 This was written in about the past hour or so; it has no documentation or test cases yet. Think twice before relying on it in production. The idea is that we can perform a detailed validation of the trustworthiness of an absolute or relative path, as a simple function that can be reused anywhere: I call this function safepath_check. A trustworthy path is one whose meaning cannot be changed by a third party: another user who isn't root. The path is therefore immune, for instance, to TOCtoTOU security problems, like the insertion of a symbolic link or other tampering. A trustworthy path is allowed to contain symbolic links. Symbolic links can be validated to be safe. To that end, safepath_check performs its own symlink resolution, to ensure that every link resolution step substitutes path material that is trustworthy.
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
The average HTTP response code
My response to "Why isn't your service free?"
Audience Response System
Quick response code manager
Cut RFP & infosec questionnaire response time by 90% with AI
Predicting Population Migration in Response to Crisis in Yemen
Slashing response time for WordPress
Incident Response on Steroids
SetInterval as a Service: Response to Chrome 88
ShiLLM – An LLM that inserts ads into every response