@dreadcode

Tortures computers for fun and profit. Interested in network security monitoring, machine learning, Golang and Rust. Shellscript ninja. Will debug for food.

 Amsterdam, The Netherlands
github.com/dreadl0ck
Joined June 2017
  • Tweets236
  • Following1.2K
  • Followers338
22Media
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Curios about the impact of this on the Go compiler and the security implications? Read my blogpost :) dreadl0ck.net/posts/faster-b…

Faster builds on macOS: a good idea? - Philipp Mieden

Explore how to speed up Go and Rust compilation on macOS by bypassing XProtect checks. Includes benchmarks, security implications, and performance analysis of Developer Tools exemption.

dreadl0ck.net
Daniel Lockyer
@DanielLockyer24 Dec 2025
TIL that macOS has a security feature called XProtect, which scans any new binaries you execute But it also means it slows down edit-compile-run workflows with excessive checking And the daemon is single threaded, so concurrent binary executions are blocked good lord
114
Replying to @kylancodes @fofrAI @replicate
Have a similar effect at dreadl0ck.net but yours definitely wins 😆

Philipp Mieden

Philipp Mieden - Security and Network Engineer specializing in cybersecurity, network analysis, Go programming, and open source tools. Based in Amsterdam.

dreadl0ck.net
67
Attacking UNIX Systems via CUPS, Part I evilsocket.net/2024/09/26/At…

Attacking UNIX Systems via CUPS, Part I | evilsocket

Hello friends, this is the first of two, possibly three (if and when I have time to finish the Windows research) writeups. We will start with targeting GNU/Lin…

evilsocket.net
168
1,108
291
3,581
1,061,280
I'm glad everyone has discovered memory safe languages after several decades. Now can we start looking at secure package management or are we just going to import memory safe rando libs from ninja876 on Github forever?
1
7
33
3,955
My dystopian vision of an AI-powered future is that LLMs drives down the cost of generating long text even further, and the only way for readers to keep up is to use LLMs to summarize.
Christian Keil
@pronounced_kyle22 Sep 2023
Okay here's a ridiculous (but true) take: word processing is bad. Before it, document length was bounded by the human capacity to copy long-form text. After word processing, the tax & legal codes grew without check. And became incomprehensible to anyone but career experts.
20
59
9
256
63,843
Guest: “Is that a RAM stick glued to your door?” Me: “Yes. Old memories.”
1
4
191
Load more