Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by StavrosK on Wednesday March 27, 2019 @09:01PM
(#19508069)
Ah, but what about packets that aren't evil, just gullible and manipulated by some third party?
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by wincy on Wednesday March 27, 2019 @10:16PM
(#19508541)
Well if you’d read the RFC it’s obvious it’s your routers responsibility to flag those bits as evil. And if you’re using heuristic intrusion detection systems you need to do flag each bit as evil 50% of the time. It’s good we have such amazing protections in place.
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by dvhh on Wednesday March 27, 2019 @10:14PM
(#19508528)
Then add a "tainted by evil" flag to the ipv7 spec, or better, just add a "pure" flag to future ip spec.
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by StavrosK on Thursday March 28, 2019 @06:06AM
(#19510747)
I think I'd almost prefer an "alignment" flag, so we don't mischaracterize all the Chaotic Neutral packets.
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by dvhh on Thursday March 28, 2019 @08:44PM
(#19518126)
But then what to do with the Lawful Evil packets ?
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by webninja on Friday March 29, 2019 @03:39PM
(#19524878)
Add an x-Lawful-Warrant parameter to provide a warrant. It can’t be read by anything but the best AI technology and is included in every HTTP request. No warrant, no response!
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by shmerl on Wednesday March 27, 2019 @11:20PM
(#19508912)
It's not like curl can't easily spoof a user agent either.
Re:Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” i...
by kevin_thibedeau on Thursday March 28, 2019 @12:15AM
(#19509192)
We can claim the LSB of the sequence number.
A better fix would be to just drop all incoming IPv4 packets that have the "evil" bit set. (https://www.ietf.org/rfc/rfc3514.txt) Extending this protection to IPv6 is left as an exercise for the reader.