ajor

Privacy Badger says that "Yellow" sites where it blocks cookies do appear to be trying to track you, but are necessary for the site to work[1]. That makes 5 trackers PB has identified on Lambeth's website.

[1] https://www.eff.org/privacybadger/faq#What-do-the-red,-yello...

Still some workarounds to the slash-stripping:

  #include "\
  /etc/passwd"

  program221/code.cpp:1:11: warning: backslash-newline at end of file
      1 | #include "\
        |            
  In file included from program221/code.cpp:2:
  /etc/passwd:1:5: error: found ':' in nested-name-specifier, expected '::'
      1 | root:x:0:0:root:/root:/bin/bash
        |     ^
        |     ::
  /etc/passwd:1:1: error: 'root' does not name a type
      1 | root:x:0:0:root:/root:/bin/bash
        | ^~~~

Is it possible to restrict the compiler's access to only files in "/usr/include" instead? Seems like it'd be hard to cover every case with just pattern matching.

I'd also recommend looking at bpftrace[1], which provides a simple DSL specifically for writing BPF programs and attaching them to events. (Disclaimer: I started the project)

[1] https://github.com/iovisor/bpftrace/blob/master/docs/tutoria...

There are still people working on packet filtering! The BPF enhancements are benefiting lots of different areas of the Linux world at the same time.

Cilium [1] is a great example of how the new capabilities of BPF can be used for more complex packet filtering, such as understanding higher level protocols.

[1] https://cilium.io/