first commit

This commit is contained in:
libroot 2026-11-19 04:39:11 +02:00
commit 0d90363116
Signed by: libroot
GPG key ID: 2AC68C029EBE9ACE
6510 changed files with 679146 additions and 0 deletions

View file

@ -0,0 +1,56 @@
{
"title": "Template:POISONNUT Product",
"type": "REPORTED",
"description": "An NSA WikiInfo page describing the POISONNUT ESP attack scheduling component — the internal software element responsible for determining whether a VPN key recovery attack can proceed, submitting it to the cryptanalytic processing infrastructure, correlating responses, and marking each attack attempt as successful or failed.",
"long_description": "This is a TOP SECRET//SI//REL TO USA, FVEY NSA WikiInfo template page for a POISONNUT product component, published by Der Spiegel under the German title \"Erklärung des POISONNUT Produktes, um Angriffe auf VPN durchzuführen\" (\"Explanation of the POISONNUT product for conducting attacks on VPN\"). The page describes the internal software design of the ESP attack scheduling element within POISONNUT — the VPN Attack Orchestrator that forms the core of NSA's IPSec VPN key recovery capability under the LONGHAUL programme.\n\nThe component is responsible for scheduling ESP attacks, receiving incoming attack requests on the incomingESPAttack channel and outputting successful results on the successfulESPAttack channel. The design flowchart reveals a six-stage processing pipeline. First, a \"Can Attack\" determination checks whether sufficient Phase 1 IKE data is available to proceed with the current attack plan — if not, the request is routed to a cannotAttack path without marking the strategy as failed, leaving that decision to the calling component. If attack data is sufficient, a \"Submit Attack\" stage creates the attack command and submits it to the VRI with the appropriate resource from the attack strategy. A \"Submission to Output Correlator\" stage then correlates the Phase 1 IKE data with its VRI output using a correlation ID, with a timeout mechanism for cases where no VRI output is received. If the attack times out or is cancelled, a \"Cancel Attack\" message is sent to the VRI. An \"Attack Output Processor\" handles whatever the VRI returns — including no output in timeout cases — and marks the attack strategy as successful or failed. Finally, a \"Was Attack Successful\" check evaluates the result, potentially reusing the Phase 1 key material content-based router with different channel configuration.\nThe channel guide reveals the messaging architecture: all channels use Spring Integration Direct channels, with IKE Phase 1 data as the primary payload type flowing through the attack determination stages, and VRISubmission and VRIResponse objects flowing through the correlation stages. The document notes the component is implemented in the poisonnut-phaseprocessing-phaseattack Maven project, confirming POISONNUT was developed using standard enterprise Java tooling.\n\nThe metrics and issues sections are unpopulated template placeholders, suggesting this page was a living development document rather than a completed reference.\n\nTaken together, this document provides a rare view inside the actual software engineering of NSA's VPN decryption capability — showing that the attack orchestration pipeline was built as a modular, message-driven Java application with explicit handling for attack failures, timeouts and resource constraints, designed to manage large volumes of concurrent VPN key recovery attempts against the cryptanalytic processing infrastructure.",
"tags": [
"VPN exploitation",
"VPN decryption",
"VPN Attack Orchestrator",
"ESP attack",
"IKE",
"surveillance architecture",
"attack orchestration",
"key recovery",
"IPSec"
],
"document": {
"creator": "NSA",
"date_created": "",
"classification": [
"TOP SECRET",
"SI"
],
"dissemination": [
"REL TO USA, FVEY"
],
"banner": "TOP SECRET//SI-GAMMA/TALENT KEYHOLE//ORCON/PROPIN/RELIDO/REL TO USA, FVEY",
"genre": "wiki",
"programs": [
"POISONNUT"
],
"countries": [],
"people": []
},
"publication": [
{
"publisher": "Der Spiegel",
"date_published": "2014-12-28",
"title": "Prying Eyes: Inside the NSA's War on Internet Security",
"link": "https://www.spiegel.de/international/germany/inside-the-nsa-s-war-on-internet-security-a-1010361.html",
"reporters": [
"Appelbaum, Jacob",
"Gibson, Aaron",
"Grothoff, Christian",
"Müller-Maguhn, Andy",
"Poitras, Laura",
"Sontheimer, Michael",
"Stöcker, Christian"
],
"contributors": [],
"doc_url": "https://cdn.prod.www.spiegel.de/media/0932ba67-0001-0014-0000-000000035524/media-35524.pdf"
}
],
"pdf_sha256": "95b7476893926e464b3b8f48fee2af01066bef0179669eb838ab9101dccf1f86",
"pages": 2
}

View file

@ -0,0 +1,116 @@
Template:POISONNUT Product - WikiInfo
The accredited security level of this system is: TOP SECRET//SI-GAMMA/TALENT KEYHOLE//ORCON/PROPIN/RELIDO/REL TO USA, FVEY * TOP SECRET//SI//REL TO USA, FVEY
(U) Template:POISONNUT Product
From WikiInfo
Contents
* 1 (TS//REL) Overview
* 2 (TS//REL) Design
* 3 (TS//REL) Capabilities
* 3.1 (TS//REL) Can Attack
* 3.2 (TS//REL) Submit Attack
* 3.3 (TS//REL) Submission to Output Correlator
* 3.4 (TS//REL) Cancel Attack
* 3.5 (TS//REL) Attack Output Processor
* 3.6 (TS//REL) Was Attack Successful
* 4 (U//FOUO) Infrastructure
* 4.1 (U//FOUO) Channel Guide
* 5 (U//FOUO) Metrics
* 6 (U//FOUO) Issues
(TS//REL) Overview
* (TS//REL) Description: This complex element is responsible for scheduling ESP attacks.
* (U//FOUO) Input Channel(s): incomingESPAttack
* (S//REL) Output Channel(s): successfulESPAttack (successful attack)
* See the poisonnut-phaseprocessing-phaseattack Maven Project.
(TS//REL) Design
Channel 1
Can Attack?
Can Attack
Channel 2
Submit Attack
Channel 3
Submission to Attack Correlator
VRI Output
Channel 4
VRI Output
Cannot Attack
Channel 7
Attack Output Processor
Channel 6
Correlated
Time out/Cancelled
Channel 5
Cancel Attack
(TS//REL) ESP Attack Desgin
(TS//REL) Capabilities
(TS//REL) Can Attack
* (TS//REL) Description: Determines if the data that is available for the Phase1 Attack is enough to do the current attack in the attack plan. If it is not, it sets the result text and returns the cannotAttack route. The strategy is not marked as failed, this is left for the object on the other side of the channel to decide how to handle the failure. If no plan is set or the plan has no attacks, it returns the cannotAttack route. If there are strategies but all of them have been exhausted, the plan will throw an IllegalStateException.
(TS//REL) Submit Attack
* (TS//REL) Description: Creates the Attack command and submits it to the VRI with the Resource of the Attack Strategy. The VRI correlation id must be set with the Phase1 data.
(TS//REL) Submission to Output Correlator
* (TS//REL) Description: Correlates the Phase1 with it's VRI Output. The VRI Correlation id will be used for the correlation. There will be a time out on the phase1 that will indicate that we never got the VRI Output.
1 of 2
Template:POISONNUT Product - WikiInfo
(TS//REL) Cancel Attack
* (TS//REL) Description: Sends a message to the VRI that the job has been canceled.
(TS//REL) Attack Output Processor
* (TS//REL) Description: Processes the output of the Attack. This output may not even be there if the Attack timed out. The Attack Strategy needs to be marked as successful or failed based on the data the Attack gives back.
(TS//REL) Was Attack Successful
* (TS//REL) Description: Checks to see if the current Attack Strategy was successful. This component could use the Has Phase1 Key Material Content Based Router implementation with a different input channel/output channel configuration.
(U//FOUO) Infrastructure
(U//FOUO) Channel Guide
(TS//REL) Spring Integration Channel Guide
| Channel | Name | Type | Payload |
| :---------------------------------- | :---------------------- | :----- | :------------ |
| CanAttack Input 1 (Channel L) | incomingPhaseAttack | Direct | IKE Phase1 |
| CanAttack Output 1 | canAttackPhase1 | Direct | IKE Phase1 |
| CanAttack Output 2 | cannotAttackPhase1 | Direct | IKE Phase1 |
| RequestResponseCorrelator Input 1 | attackRequestSubmitted | Direct | VRISubmission |
| RequestResponseCorrelator Input 2 | attackResponseReceived | Direct | VRIResponse |
| RequestResponseCorrelator Output 1 | attackCompleted | Direct | VRISubmission |
| RequestResponseCorrelator Output 2 | attackTimedOut | Direct | VRISubmission |
(U//FOUO) Metrics
{{{metrics}}}
(U//FOUO) Issues
{{{issues}}}
Retrieved from [REDACTED]
Category: POISONNUT products
Derived From: SI Classification Guide, 02-01, Dated: 20060711
and NSA/CSSM 1-52, Dated: 20070108
Declassify On: 20320108
TOP SECRET//SI//REL TO USA, FVEY
2 of 2