Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by ezoe on Thursday March 28, 2019 @04:02AM
(#19510233)
Why stop there? The user can easily modify the kernel to disable such prevention measures for malicious usage.
We must have a regulation to require a hardware level detection and prevention features of curl which all hardware vendors must follow.
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by asynch8 on Thursday March 28, 2019 @05:56AM
(#19510698)
oh god stop some politician might see this and take you for being srs
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by craftinator on Thursday March 28, 2019 @02:19PM
(#19515001)
But users have fingers, which can be used to disable or subvert said "features". Thus, those fingers are just gonna have to go. They're a security risk, and security risks are against the regulations.
Unfortunately it is also possible to do this using file redirection or to write a new program that will make a TCP connection and send arbitrary data through it, making it necessary to do the same for all editors, compilers and interpreters.
That sounds like a lot of work though (there are many such programs), so maybe we ought to just patch the kernel to prohibit any of those strings from being written to a file descriptor. There can't be that many false positives.