News for hackers. Stuff that matters.
Re:SCP – Familiar, Simple, Insecure, and Slow by gpderetta on Friday June 19, 2020 @09:57PM (#23580871)
As long as the evil bits [1] are set correctly, you can filter by that.

[1] https://tools.ietf.org/html/rfc3514

Re:SCP – Familiar, Simple, Insecure, and Slow by matheusmoreira on Friday June 19, 2020 @10:47PM (#23581092)
That RFC is a work of art. Are there more like it?
Re:SCP – Familiar, Simple, Insecure, and Slow by keeganpoppen on Friday June 19, 2020 @11:23PM (#23581306)
> In networks protected by firewalls, it is axiomatic that all attackers are on the outside of the firewall. Therefore, hosts inside the firewall MUST NOT set the evil bit on any packets.

LOL

> Intrusion detection systems (IDSs) have a harder problem. Because of their known propensity for false negatives and false positives, IDSs MUST apply a probabilistic correction factor when evaluating the evil bit. If the evil bit is set, a suitable random number generator [RFC1750] must be consulted to determine if the attempt should be logged. Similarly, if the bit is off, another random number generator must be consulted to determine if it should be logged despite the setting.

i am ashamed (or maybe not) to say that i have engaged in this form of debugging during past moments of desperation...

Re:SCP – Familiar, Simple, Insecure, and Slow by joombaga on Friday June 19, 2020 @11:05PM (#23581204)
Oh yes.

My favorite:

A Standard for the Transmission of IP Datagrams on Avian Carriers

https://tools.ietf.org/html/rfc1149

Check the dates.

Re:SCP – Familiar, Simple, Insecure, and Slow by Groxx on Saturday June 20, 2020 @01:24AM (#23581914)
And what good is a standard without an implementation: https://en.wikipedia.org/wiki/IP_over_Avian_Carriers