11–20 of 38 posts
The future ought to be capabilities. All this policy scripting stuff is just drudgery make-work that gets us nowhere.
Disclaimer: I wrote the post. Happy to answer any questions.
As for the question: How are you looking to make money?
Disclaimer: I wrote the post. Happy to answer any questions.
First of all, congrats. The tech is great and I hope you'll be able to make a company around it. As for the question: How are you looking to make money?
The future ought to be capabilities. All this policy scripting stuff is just drudgery make-work that gets us nowhere.
BPF wasn't originally conceived of as a reference monitor or ACL system; in fact, originally, it was believed that operating systems would use BPF-style packet filters to do pretty much all their demuxing.
Earlier quoted context omitted.
The shift from BPF to eBPF was less of an evolutionary step as the name might indicate. The overlap with the name BPF is primarily due to the requirement for eBPF to be a superset of BPF in order to avoid having to maintain two virtual machines long-term. This was one of the conditions for eBPF to be merged and in that context, the name eBPF made sense.
Disagree (see sibling post). Classic BPF could have been translated into any virtual machine design they came up with (because classic BPF is incredibly simple). When McCanne came up with the same design in 1998, his team called it "BPF+", for the same reason eBPF is called eBPF --- because it is pretty much an evolution of the earlier idea.
The future ought to be capabilities. All this policy scripting stuff is just drudgery make-work that gets us nowhere.
BPF wasn't originally conceived of as a reference monitor or ACL system; in fact, originally, it was believed that operating systems would use BPF-style packet filters to do pretty much all their demuxing.
https://github.com/solana-labs/rbpf
Unlike more common Rust + LLVM + WASM toolchain, Solana smart contracts use Rust + LLVM + eBPF.
Earlier quoted context omitted.
BPF wasn't originally conceived of as a reference monitor or ACL system; in fact, originally, it was believed that operating systems would use BPF-style packet filters to do pretty much all their demuxing.
AFAIK BPF wasn’t conceived as anything security-related, it was just an optimization.
The future ought to be capabilities. All this policy scripting stuff is just drudgery make-work that gets us nowhere.
BPF wasn't originally conceived of as a reference monitor or ACL system; in fact, originally, it was believed that operating systems would use BPF-style packet filters to do pretty much all their demuxing.
Earlier quoted context omitted.
BPF wasn't originally conceived of as a reference monitor or ACL system; in fact, originally, it was believed that operating systems would use BPF-style packet filters to do pretty much all their demuxing.
Are you referring to STREAMS? https://en.m.wikipedia.org/wiki/STREAMS