8839075805
Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB
v2.0.1 (Mar 29, 2021)
IMPORTANT: Security Fix
This version contains an important security fix. If you are using netmask
<=2.0.0, please upgrade to2.0.1or above.
- Rewrite byte parsing without using JS
parseInt()(commit)- This is CVE-2021-29418.
Bugfixes
- Add checks on spaces before and after bytes
- This will now throw an exception when spaces are present like ' 1.2.3.4' or '1. 2.3.4' or '1.2.3.4 '.
Internal Changes
- Avoid some useless memory allocations
- New Mocha testing suite, thanks @kaoudis #36
v2.0.0 (Mar 19, 2021)
Breaking Change
Previous API was treating IPs with less than for bytes as IP with a netmask of the size of the provided bytes (1=8, 2=16, 3=24) and was interpreting the IP as if it was completed with 0s on the right side.
Proper IP parsing for these is to consider missing bytes as being 0s on the left side.
Mask size is no longer infered by the number of bytes provided.
This means that the input 216.240 will no longer be interpreted as 216.240.0.0/16, but as 0.0.216.240/32,
as per convention.
See the change.
Bugfixes
- Fix improper parsing of hex bytes
v1.1.0 (Mar 18, 2021)
IMPORTANT: Security Fix
This version contains an important security fix. If you are using netmask
<=1.0.6, please upgrade to1.1.0or above.
- Fix improper parsing of octal bytes (commit)
- This is CVE-2021-28918.
- See also the npm advisory
Other Changes
- Performance: Avoid large allocations when provided large netmasks (like
/8)- Thanks @dschenkelman #34
v1.0.6 (May 30, 2016)
- Changes before this release are not documented here. Please see the commit list or the compare view.