env/dotfiles

0 Fork 0

mirror of https://github.com/prdlk/dotfiles.git synced 2026-11-02 11:32:42 +00:00

Files

T

Prad Nukala 6406208b35 shell: fish functions -> ~/.local/bin executables + bash/zsh ports; manage ~/.agents

- 16 cross-shell utilities converted to sh/bash chezmoi executables:
  ai c2p cp-appid extract_agents fab gdc gh-sonr-org-migrate ghg-clone
  ghn gho git-summary launch_omp_livediff_overlay lc-elir mdcp mdp pj
  (ghg-clone not named ghg: unrelated cargo binary owns that name)
- cwd/history helpers stay per-shell: yy c cd clip-last + ghg/ghn/gho
  cd-wrappers in bash/functions/ and zsh/functions/, loaded by rc files
- fish keeps only shell-state functions; converted ones now hit PATH
- cp-appid ignore gating moved to .local/bin path
- dot_agents/skills: 82 skills materialized from dotstate storage so
  dot_claude skill symlinks resolve on fresh bootstrap; dotstate
  profile/symlinks.json released .agents/skills .bashrc .zshrc

2026-08-10 15:15:06 -04:00

2.9 KiB

Raw Blame History

DDoS Configuration

Dashboard Setup

Navigate to Security > DDoS
Select HTTP DDoS or Network-layer DDoS
Configure sensitivity & action per ruleset/category/rule
Apply overrides with optional expressions (Enterprise Advanced)
Enable Adaptive DDoS toggle (Enterprise/Enterprise Advanced, requires 7 days traffic history)

Rule Structure

interface DDoSOverride {
  description: string;
  rules: Array<{
    action: "execute";
    expression: string; // Custom expression (Enterprise Advanced) or "true" for all
    action_parameters: {
      id: string; // Managed ruleset ID (discover via api.md)
      overrides: {
        sensitivity_level?: "default" | "medium" | "low" | "eoff";
        action?: "block" | "managed_challenge" | "challenge" | "log"; // log = Enterprise Advanced only
        categories?: Array<{
          category: string; // e.g., "http-flood", "udp-flood"
          sensitivity_level?: string;
        }>;
        rules?: Array<{
          id: string;
          action?: string;
          sensitivity_level?: string;
        }>;
      };
    };
  }>;
}

Expression Availability

Plan	Custom Expressions	Example
Free/Pro/Business	✗	Use `"true"` only
Enterprise	✗	Use `"true"` only
Enterprise Advanced	✓	`ip.src in {...}`, `http.request.uri.path matches "..."`

Sensitivity Mapping

UI	API	Threshold
High	`default`	Most aggressive
Medium	`medium`	Balanced
Low	`low`	Less aggressive
Essentially Off	`eoff`	Minimal mitigation

Common Categories

http-flood, http-anomaly (L7)
udp-flood, syn-flood, dns-flood (L3/4)

Override Precedence

Multiple override layers apply in this order (higher precedence wins):

Zone-level > Account-level
Individual Rule > Category > Global sensitivity/action

Example: Zone rule for /api/* overrides account-level global settings.

Adaptive DDoS Profiles

Availability: Enterprise, Enterprise Advanced
Learning period: 7 days of traffic history required

Profile Type	Description	Detects
Origins	Traffic patterns per origin server	Anomalous requests to specific origins
User-Agents	Traffic patterns per User-Agent	Malicious/anomalous user agent strings
Locations	Traffic patterns per geo-location	Attacks from specific countries/regions
Protocols	Traffic patterns per protocol (L3/4)	Protocol-specific flood attacks

Configure by targeting specific adaptive rule IDs via API (see api.md#typed-override-examples).

Alerting

Configure via Notifications:

Alert types: http_ddos_attack_alert, layer_3_4_ddos_attack_alert, advanced_* variants
Filters: zones, hostnames, RPS/PPS/Mbps thresholds, IPs, protocols
Mechanisms: email, webhooks, PagerDuty

See api.md for API examples.

2.9 KiB Raw Blame History