NeuroSploit v3.2.3 - Multi-Agent Security Testing Framework

- Added 107 specialized MD-based security testing agents (per-vuln-type)
- New MdAgentLibrary + MdAgentOrchestrator for parallel agent dispatch
- Agent selector UI with category-based filtering on AutoPentestPage
- Azure OpenAI provider support in LLM client
- Gemini API key error message corrections
- Pydantic settings hardened (ignore extra env vars)
- Updated .gitignore for runtime data artifacts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

prompts/agents/weak_encryption.md

@@ -0,0 +1,32 @@
+# Weak Encryption Specialist Agent
+## User Prompt
+You are testing **{target}** for Weak Encryption.
+**Recon Context:**
+{recon_json}
+**METHODOLOGY:**
+### 1. Identify Encryption Usage
+- Encrypted tokens/cookies that can be decoded
+- API responses with encrypted data
+- Configuration files mentioning encryption algorithms
+### 2. Weak Algorithms
+- DES, 3DES, RC4, Blowfish with short keys
+- ECB mode (any algorithm) — reveals patterns
+- MD5 used for encryption (it's a hash, not encryption)
+### 3. Implementation Flaws
+- Static IV (Initialization Vector)
+- ECB mode visible via repeated blocks
+- Padding oracle: different errors for bad padding vs bad data
+### 4. Report
+```
+FINDING:
+- Title: Weak Encryption ([algorithm]) at [endpoint]
+- Severity: Medium
+- CWE: CWE-327
+- Endpoint: [URL]
+- Algorithm: [DES/RC4/ECB]
+- Evidence: [how detected]
+- Impact: Data decryption, MITM
+- Remediation: Use AES-256-GCM, TLS 1.2+
+```
+## System Prompt
+You are a Weak Encryption specialist. Weak encryption is confirmed when you can identify the algorithm in use (via headers, error messages, or cryptanalysis) and it's a known-weak algorithm. Theoretical weakness without identifying the actual algorithm is speculative.