About
PullSec
about the author
I’m PullSec, a systems & network engineer with a strong interest in cybersecurity, infrastructure, and hands-on experimentation.
By day, I work on systems, networking, and secure development. By night, I explore homelab architectures, reverse engineering, and practical security research.
I enjoy building things, breaking them, and understanding how they work under the hood.
- Systems & Network Engineer · Homelab Builder · CTF Player
- Interests: infrastructure, networking, security, automation, and low-level systems
- Experience with self-hosted environments, reverse proxies, and distributed systems
- Background in Computer Science & Security Engineering
- GitHub: @PullSec
about the blog
Some posts are structured, others are just raw notes all part of the same process: learning, experimenting, and improving over time.
You can subscribe via GitHub.
/**
* "A collection of strengths from all sources"
* Licensed under CC BY-NC-SA 4.0
* @since 2026-05-08 20:01:01
*/
class Blog {
constructor(title, creator, url) {
this.title = title;
this.creator = creator;
this.url = url;
}
}
// The purpose of this site is not to flaunt knowledge, but to record ignorance.
const website = new Blog('A Collection of Strengths', 'PullSec', 'https://pullsec.io');History
- PullSec reached its first major technical milestone. The blog was migrated to FixIt v1, its content structure was reorganized around dedicated research sections, and the publishing workflow was consolidated with automated builds, deployment, and integrated search.
- This blog officially went live. I wanted a place to keep track of what I build, what I test, and what I learn over time.
- I started taking my learning more seriously, focusing on systems, security, and understanding things at a deeper level through hands-on work.
- I began writing things down more consistently notes, experiments, and small lessons from the lab that I didn’t want to forget.
- This is when I really started getting deeper into infrastructure, networking, and security through hands-on projects and a lot of trial and error.
- I spent a lot of time building and breaking things in my homelab setting up services, testing configurations, and learning how systems behave in real conditions.
- I started experimenting more seriously with personal projects small setups, scripts, and ideas that slowly turned into a real learning playground.