Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,16 @@
# Changelog

## Unreleased
## 1.13.0 — SRX MNHA IPsec hub builder (draft)

- **srx-ips** (0.1.5, draft): shows the security-policy binding (`application-services idp-policy`), says `match application default` belongs only in IDP rules, and names the `Please install the Signature Database` commit-check error. Verified on vSRX 26.2R1.7; found by the nightly reposbot commit check.
- **srx-nat** (1.1.4): a from/to context holds one source rule-set; a second one fails `commit check` with only `configuration check-out failed`, so add rules to the existing rule-set. Verified on vSRX 26.2R1.7; found by the nightly reposbot commit check.
- **srx-policy** (1.3.3): custom application port ranges are one `low-high` value (`destination-port 8080-8090`); `8080 to 8090` is NAT pool syntax and fails `commit check`. Found by the nightly reposbot commit check.
One new draft skill, dynamic-address feeds that survive Security Director, a warning that a commit check confirms a pending commit, and three syntax gaps found by the nightly reposbot commit check (#113–#117).

- **New skill: `srx-mnha-ipsec-builder`** (0.1.1, draft; contributed by jgrizzuti). Builds one route-based IPsec tunnel from a formed MNHA pair, anchored on a floating loopback in SRG1+ with `managed-services ipsec`, to a spoke SRX over a Junos MCP server, with eBGP/BFD over the tunnel and floating statics. Every push, cutover and failover step needs explicit approval, with a dry run, undo files and commit confirmed. Field basis: vSRX 24.4, flat MNHA model; no 26.x run. eBGP over a synced tunnel is outside Juniper's documented pattern and is marked experimental.
- **srx-dynamic-ip-feed** (1.1.0): keep dynamic-address feeds on Security Director-managed SRXs by defining the feed and the policy's dynamic-address match in configuration groups behind a placeholder address. Field-reported; not lab-validated here.
- **srx-ips** (0.1.4), **srx-mnha-builder** (0.2.7), **srx-mnha-ipsec-builder** (0.1.1): commit confirmed is now in Juniper's own junos-mcp-server — [Juniper/junos-mcp-server#34](https://github.com/Juniper/junos-mcp-server/pull/34), merged 2026-11-02, on `main` but in no tagged release yet — so the "junos-mcp-server with commit confirmed" column points to Juniper instead of a third-party fork. All three skills now say that on Junos a `commit check` or `commit` inside a confirm window **confirms the pending commit**: while one is pending on a device, run only read-only commands there (no dry run, commit check or other push). This matters most for srx-mnha-ipsec-builder's self-restoring uplink test, which a stray check would have left permanently disabled. The merged server refuses such calls with `Error: a commit confirmed is pending on <router>…`, and `confirm_commit` reports `No pending commit confirmed` when nothing is pending, which means the change either rolled back or was already confirmed; both messages are documented, with a baseline comparison to tell which. Lab-verified on vSRX 24.4R2.21 (2026-10-05): a dry run inside a 3-minute window made the change permanent on the unguarded server; with the merged guard the dry run was refused and the rollback timer stayed intact.
- **srx-policy** (1.3.3): custom application port ranges are one `low-high` value (`destination-port 8080-8090`); `8080 to 8090` is NAT pool syntax and fails `commit check`. Found by the nightly reposbot commit check.
- **srx-nat** (1.1.4): a from/to context holds one source rule-set; a second one fails `commit check` with only `configuration check-out failed`, so add rules to the existing rule-set. Verified on vSRX 26.2R1.7; found by the nightly reposbot commit check.
- **srx-ips** (0.1.5, draft): shows the security-policy binding (`application-services idp-policy`), says `match application default` belongs only in IDP rules, and names the `Please install the Signature Database` commit-check error. Verified on vSRX 26.2R1.7; found by the nightly reposbot commit check.
- Catalog: 34 skills.

## 1.12.1 — Documentation accuracy fixes

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Skills are instructions your agent follows, and pasted configs are untrusted inp
1. Clone a tagged release and run the installer:

```bash
git clone --branch v1.12.1 --depth 1 https://github.com/mechubsec/fwskillsshare.git
git clone --branch v1.13.0 --depth 1 https://github.com/mechubsec/fwskillsshare.git
cd fwskillsshare
./install.sh
```
Expand Down
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
1.12.1
1.13.0
6 changes: 3 additions & 3 deletions guides/installation-and-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ release tag (`vX.Y.Z`), never a branch or `HEAD`, and verifies every skill file
against `skills/CHECKSUMS.sha256` before installing anything:

```bash
git clone --branch v1.12.1 --depth 1 https://github.com/mechubsec/fwskillsshare.git
git clone --branch v1.13.0 --depth 1 https://github.com/mechubsec/fwskillsshare.git
cd fwskillsshare

# Interactive: pick skills + target
Expand Down Expand Up @@ -62,7 +62,7 @@ The skills are plain directories — copy the ones you want. Pin a release tag
rather than the default branch so you know exactly what you're copying:

```bash
git clone --branch v1.12.1 --depth 1 git@github.com:mechubsec/fwskillsshare.git
git clone --branch v1.13.0 --depth 1 git@github.com:mechubsec/fwskillsshare.git

# All of them
cp -r fwskillsshare/skills/* ~/.claude/skills/
Expand Down Expand Up @@ -122,7 +122,7 @@ Only then should it run `./install.sh --skill <name> ...` (repeatable) or `./ins
Example prompt to paste:

```text
Install fwskillsshare from the v1.12.1 release clone in this directory.
Install fwskillsshare from the v1.13.0 release clone in this directory.
Before running ./install.sh, use your interactive question tool
(AskUserQuestion in Claude Code, request_user_input in Codex) to ask me:
first the target (claude, codex, or hermes), then which families, then which
Expand Down
4 changes: 2 additions & 2 deletions install.sh
Original file line number Diff line number Diff line change
Expand Up @@ -112,10 +112,10 @@ GITHUB_REPO="mechubsec/fwskillsshare"
# Never point this at a branch or HEAD -- validate_ref() below refuses anything
# that isn't a vX.Y.Z tag, so a moving ref can't slip in via this default either.
#
# NOTE: When cutting a new release, update this to the release tag (e.g. v1.12.1).
# NOTE: When cutting a new release, update this to the release tag (e.g. v1.13.0).
# The checksum manifest (skills/CHECKSUMS.sha256) was added after v1.7.0, so
# this must point to a tag that includes the manifest.
GITHUB_REF_DEFAULT="v1.12.1"
GITHUB_REF_DEFAULT="v1.13.0"
GITHUB_REF="$GITHUB_REF_DEFAULT"
CLAUDE_SKILLS_DIR="${HOME}/.claude/skills"
CODEX_SKILLS_DIR="${HOME}/.agents/skills"
Expand Down
Loading