Website · Report Bug · Contribute

About

This repository contains the public editorial content of the PullSec technical blog.

It contains Markdown documents and associated resources covering topics such as:

• cybersecurity research;
• CVE and vulnerability analysis;
• security incidents;
• system and network administration;
• infrastructure and homelab projects;
• technical guides;
• security news;
• CTF and Hack The Box write-ups.

This repository intentionally contains content only.

The Hugo engine, FixIt theme, layouts, assets, archetypes, configuration and deployment workflows are maintained separately in the main hugo-fixit repository.

This separation keeps the project architecture modular and allows the published content to remain publicly accessible independently from the site infrastructure.

Architecture

flowchart LR
    A[Content Authoring
Markdown + Media]
    B[Public Repository
hugo-content]
    C[Main Blog Repository
hugo-fixit]
    D[Hugo + FixIt]
    E[GitHub Actions]
    F[GitHub Pages]
    G[Public Website
pullsec.io]

    A -->|git commit + push| B
    B -->|Git submodule| C
    C --> D
    D -->|production build| E
    E --> F
    F --> G

flowchart LR
    A[Content Authoring
Markdown + Media]
    B[Public Repository
hugo-content]
    C[Main Blog Repository
hugo-fixit]
    D[Hugo + FixIt]
    E[GitHub Actions]
    F[GitHub Pages]
    G[Public Website
pullsec.io]

    A -->|git commit + push| B
    B -->|Git submodule| C
    C --> D
    D -->|production build| E
    E --> F
    F --> G

flowchart LR
    A[Content Authoring
Markdown + Media]
    B[Public Repository
hugo-content]
    C[Main Blog Repository
hugo-fixit]
    D[Hugo + FixIt]
    E[GitHub Actions]
    F[GitHub Pages]
    G[Public Website
pullsec.io]

    A -->|git commit + push| B
    B -->|Git submodule| C
    C --> D
    D -->|production build| E
    E --> F
    F --> G

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

flowchart LR
    A[Content Authoring<br/>Markdown + Media]
    B[Public Repository<br/>hugo-content]
    C[Main Blog Repository<br/>hugo-fixit]
    D[Hugo + FixIt]
    E[GitHub Actions]
    F[GitHub Pages]
    G[Public Website<br/>pullsec.io]

    A -->|git commit + push| B
    B -->|Git submodule| C
    C --> D
    D -->|production build| E
    E --> F
    F --> G

Workflow Summary

Publishing Model

This repository is public by design.

The content itself is intended to be published and shared openly, while the site infrastructure is maintained separately.

The separation can be represented as:

1
2
3
4
5
6
7
8
9

hugo-fixit
│
├── archetypes/
├── assets/
├── config/
├── layouts/
├── themes/
│
└── content/ ───────────────► hugo-content

The main repository controls how content is rendered.

This repository controls what content is published.

Repository Structure

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

.
├── .github/
│   └── workflows/       Repository automation
│
├── about/               About and profile content
├── categories/          Category taxonomy pages
├── collections/         Collection taxonomy pages
├── community/           Community-related content
├── cve/                 CVE and vulnerability research
├── guides/              Technical guides and tutorials
├── incident/            Security incident analysis
├── posts/               General articles and news
├── projects/            Project-related content
├── reward/              Reward/support-related content
├── tags/                Tag taxonomy pages
├── writeups/            CTF and Hack The Box write-ups
│
└── README.md            Repository documentation

Content organization follows Hugo’s content model.

Some sections contain regular Markdown files while others use page bundles when local resources such as screenshots or diagrams are required.

Content Types

PullSec separates content according to its technical purpose.

CVE Research

Location:

1

cve/

Used for vulnerability analysis and CVE research.

Example:

1
2
3

cve/
└── kernel/
    └── CVE-2026-31431.md

Typical subjects include:

• vulnerability analysis;
• exploitation primitives;
• root cause analysis;
• affected components;
• mitigation;
• detection opportunities;
• technical references.

Security Incidents

Location:

1

incident/

Used for security incident analysis and threat activity.

Page bundles are preferred when the article requires local resources.

Example:

1
2
3
4

incident/
└── ai-powershell/
    ├── index.md
    └── images/

Typical subjects include:

• intrusion analysis;
• attack chains;
• threat actor activity;
• PowerShell abuse;
• credential compromise;
• persistence;
• lateral movement;
• detection engineering;
• lessons learned.

Guides

Location:

1

guides/

Used for technical tutorials and operational documentation.

Example:

1
2

guides/
└── wireless/

Typical subjects include:

• system administration;
• networking;
• wireless security;
• homelab infrastructure;
• Linux;
• security tooling;
• configuration walkthroughs.

News

Location:

1

posts/news/

Used for cybersecurity news, ecosystem developments and technical commentary.

Example:

1
2
3

posts/
└── news/
    └── example.md

Write-ups

Location:

1

writeups/

Used primarily for CTF and Hack The Box technical walkthroughs.

Example:

1
2
3
4
5

writeups/
└── hackthebox/
    └── artificial/
        ├── index.md
        └── images/

Write-ups generally document:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13

Reconnaissance
      ↓
Enumeration
      ↓
Initial Access
      ↓
Exploitation
      ↓
Privilege Escalation
      ↓
Post-Exploitation
      ↓
Lessons Learned

Projects

Location:

1

projects/

Used for project-related pages and technical project documentation.

Content Workflow

The content publishing workflow is intentionally separated from the site infrastructure.

flowchart TD
    A[Create or update content]
    B[Write and research]
    C[Preview locally]
    D[Review front matter]
    E[Commit to hugo-content]
    F[Push hugo-content]
    G[Update content submodule in hugo-fixit]
    H[Commit updated submodule pointer]
    I[GitHub Actions]
    J[Hugo production build]
    K[GitHub Pages]
    L[pullsec.io]

    A --> B
    B --> C
    C --> D
    D --> E
    E --> F
    F --> G
    G --> H
    H --> I
    I --> J
    J --> K
    K --> L

flowchart TD
    A[Create or update content]
    B[Write and research]
    C[Preview locally]
    D[Review front matter]
    E[Commit to hugo-content]
    F[Push hugo-content]
    G[Update content submodule in hugo-fixit]
    H[Commit updated submodule pointer]
    I[GitHub Actions]
    J[Hugo production build]
    K[GitHub Pages]
    L[pullsec.io]

    A --> B
    B --> C
    C --> D
    D --> E
    E --> F
    F --> G
    G --> H
    H --> I
    I --> J
    J --> K
    K --> L

flowchart TD
    A[Create or update content]
    B[Write and research]
    C[Preview locally]
    D[Review front matter]
    E[Commit to hugo-content]
    F[Push hugo-content]
    G[Update content submodule in hugo-fixit]
    H[Commit updated submodule pointer]
    I[GitHub Actions]
    J[Hugo production build]
    K[GitHub Pages]
    L[pullsec.io]

    A --> B
    B --> C
    C --> D
    D --> E
    E --> F
    F --> G
    G --> H
    H --> I
    I --> J
    J --> K
    K --> L

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

flowchart TD
    A[Create or update content]
    B[Write and research]
    C[Preview locally]
    D[Review front matter]
    E[Commit to hugo-content]
    F[Push hugo-content]
    G[Update content submodule in hugo-fixit]
    H[Commit updated submodule pointer]
    I[GitHub Actions]
    J[Hugo production build]
    K[GitHub Pages]
    L[pullsec.io]

    A --> B
    B --> C
    C --> D
    D --> E
    E --> F
    F --> G
    G --> H
    H --> I
    I --> J
    J --> K
    K --> L

Clone the Content Repository

For direct content work:

1
2

git clone https://github.com/pullsec/hugo-content.git
cd hugo-content

Before editing:

1
2

git checkout main
git pull --rebase

Creating Content

Content templates are maintained as Hugo archetypes in the parent hugo-fixit repository.

Available specialized archetypes include:

Create a CVE Article

1

hugo new content cve/kernel/CVE-YYYY-NNNNN.md --kind cve

Example:

1

hugo new content cve/kernel/CVE-2026-12345.md --kind cve

Create an Incident Analysis

1

hugo new content incident/example/index.md --kind incident

Create a Guide

1

hugo new content guides/example.md --kind guide

Create a News Article

1

hugo new content posts/news/example.md --kind news

Create a Write-up

1

hugo new content writeups/hackthebox/machine/index.md --kind writeup

Create Content with Podman

When Hugo is not installed directly on the host:

1
2
3
4
5
6
7

podman run --rm -it \
  --userns=keep-id \
  -v "$PWD":/src:Z \
  -w /src \
  ghcr.io/gohugoio/hugo:v0.164.0 \
  new content incident/example/index.md \
  --kind incident

This command must be executed from the main hugo-fixit repository.

Page Bundles and Assets

Page bundles should be preferred when an article contains local resources.

For example:

1
2
3
4
5
6
7
8

writeups/
└── hackthebox/
    └── machine/
        ├── index.md
        └── images/
            ├── enumeration.png
            ├── foothold.png
            └── privilege-escalation.png

Likewise for incident research:

1
2
3
4
5
6

incident/
└── example/
    ├── index.md
    └── images/
        ├── attack-chain.png
        └── timeline.png

This keeps article-specific resources close to the content that consumes them.

It also prevents the global static asset directories from becoming a collection of unrelated article resources.

Front Matter

Content metadata is defined using YAML front matter.

A typical PullSec article contains metadata similar to:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

---
title: "Example Article"
date: 2026-01-01T12:00:00+02:00
lastmod: 2026-01-01T12:00:00+02:00

description: "Technical description of the article."

comment: false

type: posts

toc:
  enable: true

categories:
  - security

collections:
  - research

tags:
  - linux
  - security
  - research

keywords:
  - cybersecurity
  - vulnerability research
---

The exact front matter depends on the content archetype.

Metadata Guidelines

title should clearly identify the subject.

description should provide a concise technical summary suitable for search results and metadata.

categories should represent the broad content family.

collections should group related research or technical subjects.

tags should describe technologies, techniques, platforms or concepts.

keywords may provide additional search and SEO context.

lastmod should reflect meaningful article modifications rather than cosmetic changes.

Integration with the Main Blog

This repository is mounted by the main Hugo project as:

1

content/

From the main hugo-fixit repository:

1

git submodule status content

To initialize the content submodule after cloning:

1

git submodule update --init --recursive

Updating the Content Pointer

After committing and pushing changes from hugo-content:

1

cd ../hugo-fixit

Update the submodule:

1

git submodule update --remote --merge content

Review the change:

1

git diff --submodule

Then commit the new content revision:

1
2
3

git add content
git commit -m "chore(content): update content submodule"
git push origin main

The main repository now references the new hugo-content commit.

Local Preview

This repository does not contain everything required to render PullSec by itself.

The proper preview environment is the main hugo-fixit repository.

From its root directory:

1
2
3
4
5
6
7
8
9

podman run --rm -it \
  --userns=keep-id \
  -p 1313:1313 \
  -v "$PWD":/src:Z \
  -w /src \
  ghcr.io/gohugoio/hugo:v0.164.0 \
  server \
  --bind 0.0.0.0 \
  --baseURL http://localhost:1313

Open:

1

http://localhost:1313/

This ensures the content is rendered using the actual:

• Hugo configuration;
• FixIt theme;
• layouts;
• shortcodes;
• components;
• assets;
• production content structure.

Git Workflow

Before Editing

1
2
3

git checkout main
git pull --rebase
git status

After Editing

Inspect the changes:

1
2

git status
git diff

Stage the required content:

1

git add path/to/content

Commit:

1

git commit -m "docs: update article"

Push:

1

git push origin main

Example Commit Messages

New CVE research:

1

feat(cve): add CVE-2026-12345 analysis

New incident:

1

feat(incident): add PowerShell intrusion analysis

New guide:

1

feat(guides): add wireless security guide

New write-up:

1

feat(writeups): add Hack The Box machine writeup

Article correction:

1

fix(content): correct technical details

Article update:

1

docs: update vulnerability analysis

Common Pitfalls

Can this repository build PullSec by itself?

No.

FAQ

1
2

git checkout main
git pull --rebase origin main

1

git status

1
2
3
4
5
6
7
8

cd content
git checkout main
git pull --rebase origin main
cd ..

git add content
git commit -m "chore(content): update content submodule"
git push origin main

1
2
3
4
5

cve.md
guide.md
incident.md
news.md
writeup.md

1

hugo-fixit/archetypes/

1
2
3
4
5

writeups/hackthebox/example/
├── index.md
└── images/
    ├── enumeration.png
    └── exploitation.png

1

! [rejected] main -> main (fetch first)

1

git pull --rebase origin main

1

git push origin main

Project Relationship

PullSec separates the website infrastructure from the public editorial content.

flowchart TB
    P[PullSec]

    HF[hugo-fixit]
    HC[hugo-content]

    HUGO[Hugo v0.164.0]
    FIXIT[FixIt v1]
    CONFIG[Configuration]
    LAYOUTS[Layouts]
    ARCH[Archetypes]
    CICD[GitHub Actions]

    CVE[CVE Research]
    INCIDENT[Incident Analysis]
    GUIDES[Guides]
    NEWS[News]
    WRITEUPS[Write-ups]
    PROJECTS[Projects]

    BUILD[Production Build]
    PAGES[GitHub Pages]
    SITE[pullsec.io]

    P --> HF
    P --> HC

    HF --> HUGO
    HF --> FIXIT
    HF --> CONFIG
    HF --> LAYOUTS
    HF --> ARCH
    HF --> CICD

    HC --> CVE
    HC --> INCIDENT
    HC --> GUIDES
    HC --> NEWS
    HC --> WRITEUPS
    HC --> PROJECTS

    HF --> BUILD
    HC -->|content submodule| BUILD

    BUILD --> CICD
    CICD --> PAGES
    PAGES --> SITE

flowchart TB
    P[PullSec]

    HF[hugo-fixit]
    HC[hugo-content]

    HUGO[Hugo v0.164.0]
    FIXIT[FixIt v1]
    CONFIG[Configuration]
    LAYOUTS[Layouts]
    ARCH[Archetypes]
    CICD[GitHub Actions]

    CVE[CVE Research]
    INCIDENT[Incident Analysis]
    GUIDES[Guides]
    NEWS[News]
    WRITEUPS[Write-ups]
    PROJECTS[Projects]

    BUILD[Production Build]
    PAGES[GitHub Pages]
    SITE[pullsec.io]

    P --> HF
    P --> HC

    HF --> HUGO
    HF --> FIXIT
    HF --> CONFIG
    HF --> LAYOUTS
    HF --> ARCH
    HF --> CICD

    HC --> CVE
    HC --> INCIDENT
    HC --> GUIDES
    HC --> NEWS
    HC --> WRITEUPS
    HC --> PROJECTS

    HF --> BUILD
    HC -->|content submodule| BUILD

    BUILD --> CICD
    CICD --> PAGES
    PAGES --> SITE

flowchart TB
    P[PullSec]

    HF[hugo-fixit]
    HC[hugo-content]

    HUGO[Hugo v0.164.0]
    FIXIT[FixIt v1]
    CONFIG[Configuration]
    LAYOUTS[Layouts]
    ARCH[Archetypes]
    CICD[GitHub Actions]

    CVE[CVE Research]
    INCIDENT[Incident Analysis]
    GUIDES[Guides]
    NEWS[News]
    WRITEUPS[Write-ups]
    PROJECTS[Projects]

    BUILD[Production Build]
    PAGES[GitHub Pages]
    SITE[pullsec.io]

    P --> HF
    P --> HC

    HF --> HUGO
    HF --> FIXIT
    HF --> CONFIG
    HF --> LAYOUTS
    HF --> ARCH
    HF --> CICD

    HC --> CVE
    HC --> INCIDENT
    HC --> GUIDES
    HC --> NEWS
    HC --> WRITEUPS
    HC --> PROJECTS

    HF --> BUILD
    HC -->|content submodule| BUILD

    BUILD --> CICD
    CICD --> PAGES
    PAGES --> SITE

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

flowchart TB
    P[PullSec]

    HF[hugo-fixit]
    HC[hugo-content]

    HUGO[Hugo v0.164.0]
    FIXIT[FixIt v1]
    CONFIG[Configuration]
    LAYOUTS[Layouts]
    ARCH[Archetypes]
    CICD[GitHub Actions]

    CVE[CVE Research]
    INCIDENT[Incident Analysis]
    GUIDES[Guides]
    NEWS[News]
    WRITEUPS[Write-ups]
    PROJECTS[Projects]

    BUILD[Production Build]
    PAGES[GitHub Pages]
    SITE[pullsec.io]

    P --> HF
    P --> HC

    HF --> HUGO
    HF --> FIXIT
    HF --> CONFIG
    HF --> LAYOUTS
    HF --> ARCH
    HF --> CICD

    HC --> CVE
    HC --> INCIDENT
    HC --> GUIDES
    HC --> NEWS
    HC --> WRITEUPS
    HC --> PROJECTS

    HF --> BUILD
    HC -->|content submodule| BUILD

    BUILD --> CICD
    CICD --> PAGES
    PAGES --> SITE