Let’s Go into the rabbit hole (part 1) — the challenges of dynamically hooking Golang programs
blog.quarkslab.com | research | #cloud | #reverse-engineering | #containers | #golang | #runtime | #hooking
Summary
First part of a series on dynamically hooking Golang programs: why runtime detours are needed to instrument cloud-native tools like Kubernetes and gVisor, and why Go hooking is uniquely hard.
- Published
- Collected
--- id: 4395 title: "Let’s Go into the rabbit hole (part 1) — the challenges of dynamically hooking Golang programs" source_domain: blog.quarkslab.com source_url: "https://blog.quarkslab.com/lets-go-into-the-rabbit-hole-part-1-the-challenges-of-dynamically-hooking-golang-program.html" published_at: "2023-10-02T22:00:00Z" tags: ["cloud", "reverse-engineering", "containers", "golang", "runtime", "hooking"] phying_url: "https://phying.com/item/4395" lang: en --- # Let’s Go into the rabbit hole (part 1) — the challenges of dynamically hooking Golang programs ## Summary First part of a series on dynamically hooking Golang programs: why runtime detours are needed to instrument cloud-native tools like Kubernetes and gVisor, and why Go hooking is uniquely hard. ## Intelligence Metadata - **Sources:** blog.quarkslab.com - **Published:** 2023-10-02T22:00:00Z - **Original:** https://blog.quarkslab.com/lets-go-into-the-rabbit-hole-part-1-the-challenges-of-dynamically-hooking-golang-program.html - **Phying News:** https://phying.com/item/4395