Source files: 4 | Classes: 5 | Methods: 2 | Enums: 0

---

GTOS.Security.Navajo

DecodingResult

readonly struct

Result of steganography decoding operation.
SECURITY:
- DecodedMessage: Extracted plaintext (handle securely!)
- MessageLength: For validation
- ValidationStatus: Detect tampering/corruption
PERFORMANCE: 16 bytes, stack-allocated

Source: NavajoCore.cs

Constants and Fields

DecodedMessage

readonly string

Decoded message text

MessageLength

readonly int

Message length in characters

ValidationStatus

readonly ValidationResult

Validation result

EncodingResult

readonly struct

Result of steganography encoding operation.
PLAUSIBLE DENIABILITY:
- EncodedData: Looks like normal image/audio file
- OriginalSize: For capacity planning
- EncodedSize: For transmission planning
- ValidationStatus: Success/failure indication
PERFORMANCE: 24 bytes, stack-allocated

Source: NavajoCore.cs

Constants and Fields

EncodedData

readonly byte[]

Encoded data (image/audio with hidden message)

EncodedSize

readonly int

Encoded data size in bytes

OriginalSize

readonly int

Original data size in bytes

ValidationStatus

readonly ValidationResult

Validation result

NavajoAPI

static class

Navajo post-quantum cryptographic API for covert communications.
AVAILABILITY:
✓ API surface: Always visible (IntelliSense available)
⚡ Functionality: MISSION_LOGIC builds only
SECURITY MODEL:
This API provides INFORMATION-THEORETIC SECURITY - immune to quantum computing
attacks because there's no mathematical encryption to break. Messages are hidden
in plain sight using steganography and cultural context dependency.
PLAUSIBLE DENIABILITY: "Just sharing memes bro"
- Output images look like normal photos (cat memes, vacation pics)
- Output audio looks like normal music/speech files
- Text looks like poetry or gibberish
- No cryptographic headers, signatures, or metadata
POST-QUANTUM RESISTANT:
Even quantum computers can't break this because there's nothing to compute.
The message is hidden using physical information encoding, not mathematical keys.
HISTORICAL PRECEDENT:
Navajo Code Talkers were the ONLY WWII code never broken - not due to complex
math, but due to CULTURAL CONTEXT DEPENDENCY. This API replicates that strategy.
USE CASES:
- Covert military communications
- Operational security (OPSEC)
- Data exfiltration (hide documents in photos)
- Cultural encryption (Beatles songs, historical speeches)
- Plausible deniability ("Just my vacation photos")
COMMERCIAL BUILDS:
In commercial builds, all methods return empty results with RequiresMissionLogic
validation status. The API exists for documentation and compatibility, but does
not provide actual cryptographic functionality.
EXAMPLE (MISSION_LOGIC build):
csharp<br>// Hide message in cat meme<br>byte[] catMeme = File.ReadAllBytes("cat.jpg");<br>EncodingResult result = NavajoAPI.EncodeInImage(<br>message: "Attack at dawn",<br>imageData: catMeme,<br>method: ImageSteganographyMethod.RGBA<br>);<br>if (result.ValidationStatus == ValidationResult.Success) {<br>File.WriteAllBytes("innocent_cat_meme.jpg", result.EncodedData);<br>// Result: Innocent-looking cat meme with hidden message<br>// "I was just sharing cat memes, officer."<br>}<br>

Source: NavajoAPI.cs

Methods

EncodeInImage

EncodingResult EncodeInImage ( string message, byte[] imageData, ImageSteganographyMethod method )

Encode message in image using steganography.
AVAILABILITY: MISSION_LOGIC builds only
METHODS:
- RGBA: Hide in all color channels (4 bits/pixel, high capacity)
- LSB: Least significant bit (1 bit/pixel, fast, classic)
- Frequency: DCT/FFT domain (compression-resistant)
- Arithmetic: Pixel-based offset (unique pattern)
PLAUSIBLE DENIABILITY:
Output is a valid image file indistinguishable from the original.
No headers, no metadata, no signatures. Perfect cover.
SECURITY:
- Post-quantum resistant (no math to break)
- Information-theoretic security
- Adversary can't prove message exists
INPUTS:
- message: Text to hide (UTF-8 encoded)
- imageData: Carrier image (PNG, JPG, BMP)
- method: Steganography algorithm
OUTPUT:
- EncodingResult with encoded image or error status
PERFORMANCE: ~50-500μs per image (depends on size and method)
EXAMPLE:
csharp<br>EncodingResult result = NavajoAPI.EncodeInImage(<br>"Secret message",<br>imageBytes,<br>ImageSteganographyMethod.RGBA<br>);<br>

NavajoCapacity

static class

Utility methods for calculating steganography capacity.
CAPACITY PLANNING:
Before encoding, check if message fits in carrier (image/audio).
Avoid truncation and data loss.
PERFORMANCE: <1ns per call (simple arithmetic)
EXAMPLE:
csharp<br>int capacity = NavajoCapacity.CalculateImageCapacity(1920, 1080, ImageSteganographyMethod.RGBA);<br>// Result: 2,073,600 bytes capacity (RGBA = 4 bits per pixel)<br>if (message.Length < capacity) {<br>// Safe to encode<br>}<br>

Source: NavajoCore.cs

Methods

CalculateImageCapacity

int CalculateImageCapacity ( int width, int height, ImageSteganographyMethod method )

Calculate maximum message capacity for image steganography.
CAPACITY BY METHOD:
- RGBA: 4 bits per pixel (width × height / 2 bytes)
- LSB: 1 bit per pixel (width × height / 8 bytes)
- Frequency: ~50% of RGBA capacity (DCT overhead)
- Arithmetic: 1 character per pixel (width × height bytes)
INPUTS:
- width: Image width in pixels
- height: Image height in pixels
- method: Steganography method
OUTPUT: Maximum message size in bytes

ScrambleResult

readonly struct

Result of text scrambling operation.
COVER TEXT:
- ScrambledText: Appears innocuous (nature poetry, gibberish)
- OriginalLength: For capacity planning
- ScrambledLength: May be longer than original
- ValidationStatus: Success/failure
PERFORMANCE: 16 bytes, stack-allocated

Source: NavajoCore.cs

Constants and Fields

OriginalLength

readonly int

Original text length

ScrambledLength

readonly int

Scrambled text length

ScrambledText

readonly string

Scrambled text (looks innocuous)

ValidationStatus

readonly ValidationResult

Validation result

---

Generated from GTOS Savants source -- 2026-03-22