Skip to content
KitploitKITPLOIT
उपकरणएक्सप्लॉइटब्लॉग
Log in
जमा करें
उपकरणएक्सप्लॉइटब्लॉग
जमा करें

हैकिंग, पेनटेस्ट और साइबर सुरक्षा उपकरण आपके सुरक्षा शस्त्रागार के लिए!

Kitploit हैकिंग, साइबर सुरक्षा और पेंटेस्टिंग टूल्स की एक निर्देशिका है। कमजोरियों को खोजने, सिस्टम का विश्लेषण करने, परीक्षण को स्वचालित करने और अपनी सुरक्षा को मजबूत करने के लिए नवीनतम प्रोजेक्ट अपडेट खोजें।

फ़ीडसंपर्कगोपनीयता© 2026 Kitploit

टूल निर्देशिका

श्रेणियाँ

सभी श्रेणियाँ देखें
Loading categories
LeitWacht Agent — eBPF + nftables + DNS proxy egress enforcement for GitLab Runner CI/CD job containers — community edition data plane https://leitwacht.eu/ | Kitploit
उपकरण/GitLabGitLab/leitwacht/leitwacht-agent
Cloud Infrastructure SecurityContainer SecurityNetwork SecurityCloud SecurityDevSecOpsMisconfigurationDNS Analysis
GitLableitwacht/leitwacht-agent

LeitWacht Agent

eBPF + nftables + DNS proxy egress enforcement for GitLab Runner CI/CD job containers — community edition data plane https://leitwacht.eu/

रिपॉजिटरी देखें
2552 दिन पहलेअभी तक समीक्षित नहीं
साझा करें
अनुरोधित भाषा में सामग्री उपलब्ध नहीं है। अंग्रेज़ी संस्करण दिखाया जा रहा है।

leitwacht-agent

https://leitwacht.eu — source of truth: https://gitlab.com/leitwacht/leitwacht-agent. Issues, MRs, and discussions live on GitLab.

Pre-1.0. The 0.x series is pre-stable; minor releases may carry breaking changes to APIs, env-var names, helm values.yaml keys, and rule-file schema until 1.0 ships. Pin to image digests (not floating tags) in production. See CHANGELOG.md for upgrade notes.

The data-plane agent for the leitwacht GitLab Runner egress-control system. eBPF + nftables + an in-netns DNS proxy attach to every CI runner container and enforce egress policy. CE (this repo) reads its rules from a local YAML file and is fully standalone — no backend, no phone-home, no enrolment.

A separately-licensed Enterprise Edition (gitlab.com/leitwacht/leitwacht) adds a managed control plane (rule-authoring UI, multi-tenancy, audit, GitLab integration). The EE agent imports agentcore/ from this repo and replaces the YAML loader with a gRPC rule stream.

Layout

agentcore/                   data-plane primitives (MPL-2.0)
  enforcer/                  eBPF + nftables + DNS proxy + LSM cred/proc_mem
  watcher/                   container-lifecycle event source (containerd, docker)
  cgrouppath/ clusterdomain/ procenv/   small helpers (cgroup paths, cluster domain, /proc env reads)
  handler/                   lifecycle handler — edition-neutral
  policy/                    ResolvedPolicy + Source interface + loader
  advisory/                  plain-Go advisory type + Sink interface
  violation/                 plain-Go violation reporting Sink interface
  wildcard/                  domain-pattern matching helpers
  version/                   build-version stamp (set via -ldflags)
  cmd/
    leitwacht-initc/          pod init container that gates entrypoints on agent attach
    buildkit-probe/           dev tool for exercising the BuildKit gRPC subscriber

ce/                          Community Edition daemon (MPL-2.0)
  cmd/agent-ce/              the binary
  config/                    env-driven daemon settings
  ruleyaml/                  YAML rule loader + fsnotify hot-reload
  sinks/                     stdout NDJSON / Prometheus / webhook
  helm/agent-ce/             Helm chart
  SCHEMA.md                  YAML rule schema (v1)

examples/
  rules.yaml                 starter rule set

tools/
  leitwacht-buildx           bash wrapper that injects LEITWACHT_CI_* build-args for BuildKit attribution

tests/                       integration + e2e (Linux, root)

docs/
  EVENT_FLOW.md              watcher → handler → enforcer flow + tunables (with mermaid)
  BUILDKIT.md                BuildKit: secure builder setup, integration, limitations
  BUILDKIT_STEP_ATTRIBUTION.md   original design memo (BUILDKIT.md and the code win on differences)
  BUILDKIT_PERSISTENT_K8S.md     stub pointing to BUILDKIT.md

Container scope

leitwacht-agent is the data plane for GitLab Runner CI egress. What it watches depends on the runtime watcher:

  • Docker / Podman (LEITWACHT_CE_CONTAINER_RUNTIME=docker): only containers carrying the Runner label com.gitlab.gitlab-runner.managed=true. Anything else (hand-started containers, sidecars, application workloads) is ignored.
  • containerd / Kubernetes (default): containers are selected by pod namespace via LEITWACHT_CE_RUNNER_POD_NAMESPACE (helm containerd.runnerPodNamespace, comma-separated). If it is empty, every container in the containerd namespace (k8s.io by default) is considered, so set it on shared nodes. A container without CI_PROJECT_PATH in its environment is handled as a sibling (helper/service container), not a build.

Non-Runner workloads are out of scope.

DNS configuration advisory

At attach the agent reads each container's resolv.conf (ndots and search domains) and logs one dns config observed line with counts only. When the configuration amplifies lookups (ndots >= 3 with 2+ search domains) or carries non-cluster search suffixes, CE emits a dns_config advisory on its NDJSON / webhook / Prometheus sinks, with a lower_ndots or node_search_domains recommendation. Details: docs/EVENT_FLOW.md.

Known limitations

  • IPv4 only. The eBPF programs and DNS proxy enforce on IPv4 traffic; IPv6 egress is dropped at the netns boundary regardless of policy. CI jobs that require IPv6 connectivity cannot use leitwacht enforcement until this is addressed.
  • Linux x86_64 only. arm64 runners are not yet supported (CI ships amd64 images; arm64 follows once we have eBPF artefacts for that architecture).
  • GitLab Runner workloads only. See "Container scope" above.
  • Pre-attach window. On Kubernetes, egress between a build container's start and its own attach runs under an audit-all placeholder policy; see docs/EVENT_FLOW.md.

Quickstart

# Build (CGO_ENABLED=0 lets non-Linux hosts cross-compile cleanly).
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build ./...

# Container image
docker build -f Dockerfile.agent-ce -t leitwacht/agent-ce:dev .

# Helm install (Kubernetes). dnsUpstream is required — point it at your
# cluster DNS resolver, not a public one, so internal services keep
# resolving and queries don't leak.
KUBE_DNS_IP=$(kubectl -n kube-system get svc kube-dns -o jsonpath='{.spec.clusterIP}')
helm install leitwacht-ce ./ce/helm/agent-ce \
  -n leitwacht --create-namespace \
  --set-file rules=examples/rules.yaml \
  --set "dnsUpstream=${KUBE_DNS_IP}:53"

The full schema reference for rules.yaml lives in ce/SCHEMA.md.

License

agentcore/ and ce/ are distributed under the Mozilla Public License 2.0 — see LICENSE. MPL-2.0 is a file-level copyleft license: you may use, modify, and redistribute these files in your own products (commercial or otherwise), but any changes you make to MPL-2.0-licensed files must be made available under the same license.

The Enterprise Edition backend at gitlab.com/leitwacht/leitwacht is distributed under a different license. The two repositories are co-developed by the same team.

Contributing

Issues and merge requests on the canonical GitLab repo (https://gitlab.com/leitwacht/leitwacht-agent). Security issues should follow the process in SECURITY.md. Workflow and style notes are in CONTRIBUTING.md.

Building

Linux only (eBPF + nftables): GOOS=linux GOARCH=amd64 go build ./...

The eBPF objects (*_bpfel.o) are committed because regenerating them requires clang + kernel headers; CI builds rely on the committed artefacts. To regenerate locally on Linux:

make ebpf-generate        # go generate ./agentcore/enforcer/...
make check-ebpf-drift     # what CI runs: fails if committed .o/.go differ from the .c sources

CI regenerates with clang from a pinned Debian bookworm image; a different clang version can produce a diff in the committed objects.

टूल डाउनलोड करें

सबसे लोकप्रिय

सभी देखें →

हमारे समुदाय द्वारा सबसे अधिक उपयोग किए जाने वाले उपकरण खोजें।

अभी तक कोई लोकप्रियता डेटा नहीं है।

सभी उपकरण खोजें

हमारे उपकरणों का संग्रह ब्राउज़ करें

सभी उपकरण देखें →