News for hackers. Stuff that matters.

archrabbit

archrabbit on Hacker News

Re:A modern tool for the Windows kernel exploration and observability on Sunday December 06, 2020 @05:42AM (#25322630)
I've hopefully fixed the UI issues for now :)
Re:A modern tool for the Windows kernel exploration and observability on Sunday December 06, 2020 @03:57AM (#25322164)
You can check the kcap layout diagram in the source code docs:

https://github.com/rabbitstack/fibratus/blob/ee26bbc73999895...

Re:A modern tool for the Windows kernel exploration and observability on Sunday December 06, 2020 @02:52AM (#25321913)
Could you share your impressions?
Re:A modern tool for the Windows kernel exploration and observability on Saturday December 05, 2020 @04:15PM (#25318446)
Besides it is: - fully programmable and extensible with Python scripts - has out of the box alerting - support for capture files - highly customizable regarding transporting events to output sinks
Re:A modern tool for the Windows kernel exploration and observability on Saturday December 05, 2020 @04:12PM (#25318409)
Author here. I'll make sure to address the UI issue soon.

Oxdpus – attaching prebuilt XDP bytecode to network devices in Go

Posted by archrabbit on Monday June 03, 2019 @10:19AM
from the self-post dept.

Hi, I built a small tool (https://github.com/sematext/oxdpus) to complement the write up (https://sematext.com/blog/ebpf-and-xdp-for-processing-packets-at-bare-metal-speed/) about XDP (Express Data Path) internals. The tool basically consists in CLI that offers various options for attaching XDP programs to the network interfaces, managing IP blacklisting, and so on. Unlike in my previous blog...

( Read More... | 1 comment | 8 points | on HN )
Re:Rabbitc – Micro-container runtime built in Rust on Monday July 16, 2018 @03:46AM (#17539469)
One thing to note about railcar is that it completely lacks the network stack, but it will probably be my "starting point" if someday I decide to evolve `rabbitc` into something "more serious".
Re:Linux Container Internals on Tuesday June 06, 2017 @03:24AM (#14495402)
Sure, there is definitely a lot of possible improvements for the code examples, like avoiding `clone` on a heap allocated strings, etc. I had some really odd issues when passing a statically allocated strings to the `libc` functions (the function's arguments from the previous calls ended up concatenated in the later function's invocations, just use `strace` to observe that behavior).
Re:Linux Container Internals on Monday June 05, 2017 @03:32PM (#14490676)
I probably could wrap in the `unsafe` block just the invocations to the system calls. I'm learning Rust and I wanted to give the post some freshness. There are already a plethora of examples in C.
Re:Linux Container Internals on Monday June 05, 2017 @02:12PM (#14489854)
it's Rust. Btw, did you see erlang or clojure? ;p