FM-R1: FM-R1: Secure Communication Networks for Decentralized Resistance
UNCLASSIFIED
Section 4-1 to 4-8

Chapter 4: Secure Messaging and Voice Communications

Chapter Overview

This chapter provides detailed configuration and operational guidance for implementing secure messaging systems within the multi-layer communication architecture. Each messaging system covered here serves specific security requirements and operational scenarios, from maximum-security real-time coordination to secure group collaboration.

Sections in this chapter:


Section 4-1: Session Messenger Configuration

Overview

Session Messenger provides maximum security messaging through onion routing and the Signal Protocol, making it ideal for Layer 1 high-risk communications. Session eliminates phone number requirements and metadata collection while providing strong encryption and anonymity protection.

Installation and Initial Setup

Download and Verification

# Download Session from official sources only
# Desktop: https://getsession.org/download
# Mobile: Official app stores or F-Droid

# Verify download integrity (desktop)
gpg --verify session-desktop-linux-x86_64-*.AppImage.sig

Initial Configuration

Security Settings Checklist:
□ Disable read receipts
□ Disable typing indicators  
□ Enable disappearing messages (shortest duration)
□ Disable message notifications
□ Disable message previews
□ Enable screen security (mobile)
□ Disable automatic media downloads

Session ID Creation

Session ID Best Practices:
1. Generate new Session ID for each operational role
2. Use random Session ID, not recovery phrase
3. Record Session ID securely for sharing with contacts
4. Never link Session ID to real identity or other accounts
5. Rotate Session IDs regularly (monthly or per operation)

Advanced Security Configuration

Network Security

Network Configuration:
- Always use Tor Browser or Tor proxy for desktop access
- Enable VPN on mobile devices before using Session
- Disable automatic updates to prevent traffic analysis
- Use public WiFi from locations unconnected to identity
- Avoid using Session on home or work networks

Device Security

Device Hardening for Session:
1. Use dedicated device not linked to real identity
2. Enable full disk encryption
3. Use strong device lock screen password
4. Disable biometric authentication
5. Install minimal additional software
6. Regular security updates through secure channels

Operational Security

Session OpSec Procedures:
1. Create new Session ID for each operation or role
2. Share Session ID only through secure out-of-band channels
3. Verify contact identity before sensitive communications
4. Use coded language even in encrypted messages
5. Delete conversations regularly
6. Monitor for unusual behavior or timing

Contact Management

Adding Contacts Securely

Secure Contact Addition Process:
1. Generate Session ID and share through secure channel
2. Verify recipient received correct Session ID
3. Send test message with predetermined verification phrase
4. Confirm identity through separate communication channel
5. Establish communication protocols and schedules

Contact Verification

Identity Verification Methods:
- Out-of-band verification through trusted intermediary
- Predetermined code words or phrases
- Reference to shared experiences or knowledge
- Voice verification through separate secure channel
- Physical meeting for high-value contacts

Contact Hygiene

Message Security

Disappearing Messages

Message Retention Settings:
- Use shortest available timer (5 seconds to 1 week)
- Adjust based on message sensitivity and operational needs
- Ensure all participants understand and enable feature
- Verify messages actually disappear on all devices
- Use manual deletion for immediate removal

Message Content Security

Secure Messaging Practices:
1. Use coded language for sensitive topics
2. Avoid specific names, locations, or times
3. Break complex information into multiple messages
4. Use predetermined code words for common concepts
5. Verify critical information through separate channels

Emergency Procedures

Emergency Response Protocols:
1. Duress Codes: Predetermined phrases indicating compromise
2. Burn Procedures: Rapid deletion of all Session data
3. Emergency Contacts: Backup communication methods
4. Fallback Protocols: Alternative communication channels
5. Recovery Procedures: Re-establishing secure communications
Session Limitations

Session provides excellent security but has limitations: slower message delivery due to onion routing, limited group messaging features, and dependency on network connectivity. Plan accordingly for operational requirements.


Section 4-2: Element/Matrix Self-Hosted Setup

Overview

Element/Matrix provides secure group communications and collaboration features through self-hosted infrastructure, making it ideal for Layer 2 secure collaboration systems. Self-hosting ensures complete control over security and data while providing rich communication features.

Server Infrastructure Setup

Hardware Requirements

Minimum Server Specifications:
- CPU: 2 cores, 2.4 GHz
- RAM: 4 GB (8 GB recommended)
- Storage: 50 GB SSD (100 GB+ for larger deployments)
- Network: Reliable internet connection with static IP
- OS: Ubuntu 20.04 LTS or Debian 11 (recommended)

Initial Server Hardening

# Update system and install security updates
sudo apt update && sudo apt upgrade -y

# Install fail2ban for intrusion prevention
sudo apt install fail2ban ufw -y

# Configure firewall
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow ssh
sudo ufw allow 80
sudo ufw allow 443
sudo ufw enable

# Disable root login and password authentication
sudo sed -i 's/PermitRootLogin yes/PermitRootLogin no/' /etc/ssh/sshd_config
sudo sed -i 's/#PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config
sudo systemctl restart ssh

Synapse Installation

# Install Synapse Matrix server
sudo apt install matrix-synapse -y

# Generate configuration
sudo -u matrix-synapse /usr/bin/python3 -m synapse.app.homeserver \
    --server-name your-domain.com \
    --config-path /etc/matrix-synapse/homeserver.yaml \
    --generate-config \
    --report-stats=no

Database Configuration

# Install PostgreSQL for better performance
sudo apt install postgresql postgresql-contrib -y

# Create Matrix database and user
sudo -u postgres createuser --pwprompt synapse_user
sudo -u postgres createdb --encoding=UTF8 --locale=C --template=template0 --owner=synapse_user synapse

# Configure Synapse to use PostgreSQL
sudo nano /etc/matrix-synapse/homeserver.yaml
# Database configuration in homeserver.yaml
database:
  name: psycopg2
  args:
    user: synapse_user
    password: your_secure_password
    database: synapse
    host: localhost
    cp_min: 5
    cp_max: 10

Security Configuration

Encryption Settings

# Enable end-to-end encryption in homeserver.yaml
encryption_enabled_by_default_for_room_type: all
trusted_key_servers:
  - server_name: "matrix.org"
    verify_keys:
      "ed25519:auto": "Noi6WqcDj0QmPxCNQqgezwTlBKrfqehY1u2FyWP9uYw"

# Disable federation for security
federation_domain_whitelist: []

Access Control

# Registration and access control
enable_registration: false
registration_shared_secret: "your_very_long_random_string"
allow_guest_access: false
enable_registration_captcha: false

# Rate limiting
rc_message:
  per_second: 0.2
  burst_count: 10

rc_registration:
  per_second: 0.17
  burst_count: 3

Privacy Settings

# Privacy and security settings
enable_metrics: false
report_stats: false
enable_media_repo: true
max_upload_size: 50M

# Disable unnecessary features
enable_group_creation: false
autocreate_auto_join_rooms: false

Element Web Client Setup

Installation

# Download and install Element Web
cd /var/www
sudo wget https://github.com/vector-im/element-web/releases/download/v1.11.8/element-v1.11.8.tar.gz
sudo tar -xzf element-v1.11.8.tar.gz
sudo mv element-v1.11.8 element
sudo chown -R www-data:www-data element

Configuration

{
    "default_server_config": {
        "m.homeserver": {
            "base_url": "https://your-domain.com",
            "server_name": "your-domain.com"
        }
    },
    "disable_custom_urls": true,
    "disable_guests": true,
    "disable_login_language_selector": true,
    "disable_3pid_login": true,
    "brand": "Resistance Communications",
    "integrations_ui_url": "",
    "integrations_rest_url": "",
    "bug_report_endpoint_url": "",
    "features": {
        "feature_pinning": "disable",
        "feature_custom_status": "disable",
        "feature_custom_tags": "disable"
    }
}

Operational Procedures

User Management

# Create admin user
register_new_matrix_user -c /etc/matrix-synapse/homeserver.yaml http://localhost:8008

# Create regular users (admin only)
# Use Element admin interface or command line tools

Room Creation and Management

Secure Room Setup:
1. Create private, invite-only rooms
2. Enable end-to-end encryption for all rooms
3. Set appropriate power levels for participants
4. Configure message retention policies
5. Establish room-specific communication protocols

Backup and Recovery

# Database backup script
#!/bin/bash
BACKUP_DIR="/backup/matrix"
DATE=$(date +%Y%m%d_%H%M%S)

# Create backup directory
mkdir -p $BACKUP_DIR

# Backup database
sudo -u postgres pg_dump synapse > $BACKUP_DIR/synapse_$DATE.sql

# Backup media files
tar -czf $BACKUP_DIR/media_$DATE.tar.gz /var/lib/matrix-synapse/media

# Encrypt backups
gpg --cipher-algo AES256 --compress-algo 1 --s2k-mode 3 \
    --s2k-digest-algo SHA512 --s2k-count 65536 --symmetric \
    --output $BACKUP_DIR/synapse_$DATE.sql.gpg $BACKUP_DIR/synapse_$DATE.sql

# Remove unencrypted backup
rm $BACKUP_DIR/synapse_$DATE.sql
Server Maintenance

Self-hosted Matrix servers require ongoing maintenance including security updates, monitoring, backup verification, and performance optimization. Plan for dedicated technical resources or consider managed hosting with trusted providers.


Section 4-3: Briar Peer-to-Peer Messaging

Overview

Briar provides true peer-to-peer messaging without central servers, making it ideal for high-security scenarios and situations where internet infrastructure is unreliable or compromised. Briar supports Bluetooth, WiFi, and Tor connections for maximum flexibility.

Installation and Setup

Download and Installation

Official Sources:
- F-Droid: https://f-droid.org/packages/org.briarproject.briar.android/
- Google Play: https://play.google.com/store/apps/details?id=org.briarproject.briar.android
- Direct APK: https://briarproject.org/download-briar/

Desktop Beta:
- Available for testing but not recommended for operational use
- Mobile version provides full functionality

Initial Configuration

Setup Checklist:
□ Create strong password for Briar account
□ Enable screen lock on device
□ Configure network settings (Tor, WiFi, Bluetooth)
□ Disable automatic backups to cloud services
□ Review and adjust privacy settings
□ Test connectivity through different network types

Network Configuration

Network Settings:
1. Tor: Enable for internet connections
   - Provides anonymity and censorship resistance
   - Required for remote contact connections
   - May be slower but more secure

2. WiFi: Enable for local area networking
   - Direct device-to-device connections
   - Faster than Tor for local communications
   - Use only in secure environments

3. Bluetooth: Enable for close-proximity messaging
   - Works without internet or WiFi
   - Very short range (10-30 meters)
   - Useful for covert meetings and mesh networking

Contact Management

Adding Contacts

Contact Addition Methods:
1. QR Code Exchange:
   - Generate QR code in Briar
   - Scan contact's QR code in person
   - Most secure method for initial contact

2. Briar Link Sharing:
   - Generate Briar link for contact
   - Share through secure out-of-band channel
   - Verify identity after connection

3. Introduction by Mutual Contact:
   - Existing contact introduces new contact
   - Provides verification through trusted intermediary
   - Useful for expanding secure networks

Contact Verification

Identity Verification Process:
1. Exchange contact information through secure channel
2. Verify identity through predetermined questions or codes
3. Confirm connection through separate communication method
4. Establish communication protocols and schedules
5. Regular re-verification for high-value contacts

Contact Security

Contact Management Security:
- Use aliases instead of real names
- Regularly review and clean contact lists
- Remove contacts who are no longer active
- Monitor for unusual behavior or timing
- Implement contact rotation for high-risk operations

Messaging Security

Message Types and Features

Briar Message Features:
1. Private Messages:
   - One-to-one encrypted messaging
   - Automatic forward secrecy
   - Message deletion and retention controls

2. Private Groups:
   - Small group messaging (recommended <10 people)
   - Invitation-only membership
   - Shared group keys and forward secrecy

3. Forums:
   - Larger group discussions
   - Topic-based organization
   - Moderation and access controls

4. Blogs:
   - One-to-many publishing
   - RSS-like feed functionality
   - Comment and discussion features

Security Best Practices

Briar Security Procedures:
1. Use coded language for sensitive topics
2. Enable message deletion timers when available
3. Regularly clear message history
4. Monitor contact online status patterns
5. Use different devices for different operational roles
6. Implement emergency deletion procedures

Mesh Networking

Local Mesh Setup

Mesh Network Configuration:
1. Enable WiFi and Bluetooth on all devices
2. Ensure devices are within range (WiFi: 100m, Bluetooth: 30m)
3. Configure Briar to use local networks
4. Test message routing through intermediate devices
5. Establish mesh network protocols and procedures

Mesh Security Considerations

Mesh Network Security:
- Only enable mesh in secure, controlled environments
- Monitor for unauthorized devices joining network
- Use temporary mesh networks for specific operations
- Disable mesh when not needed to reduce attack surface
- Implement physical security for mesh network areas

Offline Message Storage

Store-and-Forward Messaging:
- Messages stored locally when contacts offline
- Automatic delivery when contacts come online
- Configurable storage limits and retention
- Encrypted storage on device
- Manual message deletion for sensitive content

Operational Procedures

Communication Protocols

Briar Communication Protocols:
1. Regular Check-ins:
   - Scheduled online times for message exchange
   - Staggered schedules to avoid pattern analysis
   - Emergency contact procedures

2. Message Handling:
   - Immediate reading and response to urgent messages
   - Delayed response for routine communications
   - Message verification for critical information

3. Group Management:
   - Clear roles and responsibilities
   - Invitation and removal procedures
   - Conflict resolution and moderation

Emergency Procedures

Emergency Response with Briar:
1. Emergency Contacts:
   - Predetermined emergency contact procedures
   - Multiple backup contacts for redundancy
   - Emergency message formats and codes

2. Compromise Response:
   - Immediate contact removal if compromise suspected
   - Message deletion and device sanitization
   - Alternative contact methods activation

3. Network Disruption:
   - Mesh networking activation for local communications
   - Store-and-forward for delayed message delivery
   - Physical meeting coordination through Briar
Briar Advantages

Briar's peer-to-peer architecture provides unique advantages: no central servers to compromise, offline messaging capability, and mesh networking for local communications. These features make it invaluable for high-security scenarios and network disruption situations.


Section 4-4: Signal Security Best Practices

Overview

While Signal is not recommended for the highest-security resistance communications due to phone number requirements and centralized infrastructure, it remains widely used and can be secured for medium-risk communications when properly configured and used with appropriate operational security.

Secure Installation and Setup

Installation Security

Secure Signal Installation:
1. Download only from official sources:
   - iOS: Apple App Store
   - Android: Google Play Store or Signal.org
   - Desktop: signal.org/download

2. Verify installation integrity:
   - Check app signatures and certificates
   - Verify download checksums when available
   - Use clean device for installation

Registration Security

Phone Number Considerations:
1. Use dedicated phone number not linked to real identity:
   - Prepaid phone with cash purchase
   - VoIP number from privacy-focused provider
   - Temporary number for specific operations

2. Registration Process:
   - Use VPN or Tor during registration
   - Register from location unconnected to identity
   - Disable SMS backup and cloud sync

Initial Configuration

Signal Security Settings:
□ Enable registration lock with strong PIN
□ Disable read receipts
□ Disable typing indicators
□ Enable disappearing messages (shortest duration)
□ Disable message notifications and previews
□ Enable screen lock and screen security
□ Disable automatic media downloads
□ Turn off contact discovery
□ Disable link previews

Advanced Security Configuration

Privacy Settings

Privacy Configuration:
1. Profile Settings:
   - Use pseudonym instead of real name
   - Avoid identifying profile photos
   - Disable profile sharing with contacts

2. Contact Management:
   - Manually add contacts instead of syncing
   - Use contact names that don't reveal identity
   - Regularly review and clean contact list

3. Group Settings:
   - Disable group link sharing
   - Require admin approval for new members
   - Use descriptive but non-identifying group names

Network Security

Network Protection:
1. VPN Usage:
   - Always use VPN when using Signal
   - Choose VPN provider with no-logging policy
   - Use different VPN servers for different operations

2. Tor Integration:
   - Use Signal through Tor proxy when possible
   - Configure Orbot on Android for Tor routing
   - Accept slower performance for better anonymity

3. Network Monitoring:
   - Monitor for unusual network activity
   - Use network analysis tools to verify Tor routing
   - Avoid using Signal on monitored networks

Operational Security

Communication Protocols

Signal OpSec Procedures:
1. Contact Verification:
   - Verify safety numbers for all contacts
   - Re-verify after app updates or device changes
   - Use out-of-band verification for critical contacts

2. Message Security:
   - Use coded language for sensitive topics
   - Enable disappearing messages for all conversations
   - Manually delete sensitive messages immediately
   - Avoid sending identifying information

3. Group Management:
   - Limit group size to operational necessity
   - Use separate groups for different purposes
   - Regularly review group membership
   - Remove inactive or compromised members

Device Security

Device Hardening for Signal:
1. Physical Security:
   - Use strong device lock screen
   - Enable remote wipe capability
   - Avoid leaving device unattended
   - Use device encryption

2. App Security:
   - Keep Signal updated to latest version
   - Enable app-specific lock if available
   - Disable Signal in app switcher/recent apps
   - Clear app cache regularly

3. Backup Security:
   - Disable automatic cloud backups
   - Use local encrypted backups only if necessary
   - Regularly delete old backup files
   - Secure backup storage and access

Limitations and Risks

Signal Limitations

Known Signal Limitations:
1. Metadata Collection:
   - Phone numbers linked to accounts
   - Message timing and frequency data
   - Contact discovery information
   - Server connection logs

2. Centralized Infrastructure:
   - Single point of failure and control
   - Subject to legal demands and pressure
   - Potential for service disruption
   - Limited user control over security

3. Phone Number Requirement:
   - Links account to identity verification system
   - Enables contact discovery and correlation
   - Difficult to maintain anonymity
   - Vulnerable to SIM swapping attacks

Risk Mitigation

Signal Risk Mitigation:
1. Use for medium-risk communications only
2. Combine with other communication layers
3. Implement strong operational security
4. Regular account rotation and cleanup
5. Monitor for service changes and updates
6. Prepare alternative communication methods
Signal Limitations

Signal's phone number requirement and centralized infrastructure make it unsuitable for high-risk resistance communications. Use Signal only for medium-risk scenarios and always in combination with more secure alternatives.


Section 4-5: Voice Communication Security

Overview

Voice communications present unique security challenges due to real-time requirements, voice recognition possibilities, and the difficulty of implementing strong encryption. This section covers secure voice communication methods and operational security procedures.

Secure Voice Technologies

VoIP Security

Secure VoIP Configuration:
1. Signal Voice Calls:
   - End-to-end encrypted voice calls
   - Verify safety numbers before sensitive calls
   - Use coded language and predetermined phrases
   - Keep calls brief and focused

2. Element/Matrix Voice:
   - Encrypted voice calls through Matrix protocol
   - Self-hosted infrastructure for maximum control
   - Group voice calls with access controls
   - Integration with text messaging

3. Briar Voice (Future):
   - Peer-to-peer voice calls without servers
   - Currently in development
   - Will provide maximum security when available

Traditional Phone Security

Landline and Mobile Security:
1. Operational Phones:
   - Use dedicated phones not linked to identity
   - Prepaid phones purchased with cash
   - Regular phone rotation and disposal
   - Physical security and access controls

2. Call Security:
   - Assume all traditional calls are monitored
   - Use only for non-sensitive communications
   - Implement coded language and phrases
   - Keep calls brief and infrequent

3. Location Security:
   - Disable GPS and location services
   - Use phones only in secure locations
   - Avoid patterns in call timing and location
   - Physical separation from personal devices

Voice Operational Security

Call Planning

Secure Call Procedures:
1. Pre-Call Planning:
   - Determine necessity of voice communication
   - Prepare coded language and key points
   - Verify recipient identity and availability
   - Choose secure location and timing

2. Call Execution:
   - Verify recipient identity at call start
   - Use predetermined identification phrases
   - Speak clearly but avoid identifying characteristics
   - Keep calls brief and focused on essential information

3. Post-Call Security:
   - Verify information received through separate channel
   - Document essential information securely
   - Clear call logs and temporary data
   - Monitor for signs of interception or compromise

Voice Disguise and Security

Voice Security Techniques:
1. Voice Modification:
   - Speak in different pitch or tone
   - Use accent or speech pattern changes
   - Employ voice changing software when possible
   - Practice consistent voice modifications

2. Language Security:
   - Use coded language for sensitive topics
   - Avoid names, locations, and specific details
   - Employ predetermined phrases and responses
   - Implement duress codes for emergency situations

3. Content Security:
   - Limit sensitive information in voice calls
   - Use voice for coordination, text for details
   - Verify critical information through separate channels
   - Avoid discussing operational specifics

Emergency Voice Communications

Emergency Protocols

Emergency Voice Procedures:
1. Emergency Identification:
   - Predetermined emergency phrases
   - Duress codes indicating compromise
   - Authentication challenges and responses
   - Emergency contact escalation procedures

2. Emergency Information:
   - Essential information only
   - Predetermined emergency message formats
   - Location and timing information
   - Resource and assistance requirements

3. Emergency Response:
   - Immediate response protocols
   - Backup communication activation
   - Security assessment and adjustment
   - Follow-up verification procedures

Backup Voice Systems

Backup Voice Communication:
1. Amateur Radio:
   - Licensed amateur radio operations
   - Digital modes for text over radio
   - Mesh networking and repeater systems
   - Emergency communication networks

2. Satellite Communications:
   - Satellite phones for remote areas
   - Satellite internet for VoIP calls
   - Emergency satellite communication services
   - Cost and availability considerations

3. Mesh Voice Networks:
   - Local mesh networking with voice capability
   - Peer-to-peer voice over WiFi
   - Offline voice communication systems
   - Integration with existing mesh networks
Voice Communication Limits

Voice communications should be used sparingly in resistance operations due to security limitations. Prioritize text-based communications for most coordination, using voice only when real-time interaction is essential and cannot be achieved through other means.


Section 4-6: Group Communication Management

Overview

Group communications present amplified security challenges due to multiple participants, varied security practices, and increased metadata exposure. This section provides frameworks for managing group communications securely while maintaining operational effectiveness.

Group Security Architecture

Group Types and Security Levels

Group Classification:
1. High-Security Cells (3-7 members):
   - Operational planning and coordination
   - Maximum security protocols required
   - Layer 1 communications (Session, Briar)
   - Strict access controls and verification

2. Coordination Groups (8-15 members):
   - Cross-cell coordination and resource sharing
   - High security with collaboration features
   - Layer 2 communications (Matrix/Element)
   - Role-based access and permissions

3. Support Networks (16+ members):
   - Broader support and resource networks
   - Medium security with usability focus
   - Layer 2/3 communications
   - Moderated access and content controls

4. Public Communications (unlimited):
   - Public outreach and information sharing
   - Layer 4 broadcasting systems
   - Anonymous participation options
   - Open access with moderation

Group Formation Protocols

Secure Group Creation:
1. Purpose Definition:
   - Clear operational purpose and scope
   - Security requirements assessment
   - Participant role definitions
   - Communication protocols establishment

2. Member Selection:
   - Operational necessity verification
   - Security clearance and vetting
   - Role-appropriate access levels
   - Ongoing membership review

3. Technical Setup:
   - Appropriate platform selection
   - Security configuration implementation
   - Access controls and permissions
   - Backup and recovery procedures

4. Operational Procedures:
   - Communication protocols and schedules
   - Information sharing guidelines
   - Conflict resolution procedures
   - Emergency response protocols

Group Access Controls

Role-Based Permissions

Group Role Structure:
1. Administrators:
   - Full group management permissions
   - Member addition and removal authority
   - Security configuration control
   - Emergency response coordination

2. Moderators:
   - Content moderation and enforcement
   - Limited member management
   - Protocol enforcement authority
   - Conflict resolution responsibility

3. Active Members:
   - Full participation in group discussions
   - File sharing and collaboration access
   - Voice in group decisions
   - Operational task assignments

4. Observers:
   - Read-only access to group content
   - Limited participation in discussions
   - No access to sensitive materials
   - Probationary or support role status

Access Control Implementation

Technical Access Controls:
1. Matrix/Element Groups:
   - Power level configuration for different roles
   - Room encryption and access controls
   - Invitation-only membership
   - Message retention and deletion policies

2. Signal Groups:
   - Admin approval for new members
   - Disappearing messages for all participants
   - Group link sharing disabled
   - Regular membership review and cleanup

3. Briar Groups:
   - Invitation-only private groups
   - Peer-to-peer verification required
   - Local group management
   - Offline capability maintenance

Group Communication Protocols

Information Sharing Guidelines

Group Information Security:
1. Classification Levels:
   - Public: Shareable without restriction
   - Internal: Group members only
   - Restricted: Specific roles only
   - Classified: Administrators only

2. Sharing Protocols:
   - Clear marking of information sensitivity
   - Verification of recipient authorization
   - Secure transmission methods
   - Access logging and monitoring

3. Content Guidelines:
   - No personal identifying information
   - Coded language for sensitive topics
   - Operational security considerations
   - Legal and safety implications

Discussion Management

Group Discussion Protocols:
1. Topic Management:
   - Separate channels for different topics
   - Clear topic guidelines and scope
   - Moderation of off-topic discussions
   - Archive and retention policies

2. Participation Guidelines:
   - Respectful and professional communication
   - Constructive contribution requirements
   - Conflict resolution procedures
   - Enforcement and consequences

3. Security Reminders:
   - Regular security awareness messages
   - Operational security reminders
   - Protocol updates and changes
   - Emergency procedure reviews

Group Compromise Response

Compromise Detection

Compromise Indicators:
1. Technical Indicators:
   - Unusual login patterns or locations
   - Unexpected message deletions or modifications
   - New members without proper authorization
   - System configuration changes

2. Behavioral Indicators:
   - Unusual communication patterns
   - Inappropriate information requests
   - Violation of established protocols
   - Suspicious timing or coordination

3. External Indicators:
   - Law enforcement activity
   - Media attention or exposure
   - Adversary knowledge of group activities
   - Correlation with other security incidents

Response Procedures

Group Compromise Response:
1. Immediate Actions:
   - Suspend group communications
   - Notify all members through backup channels
   - Assess scope and impact of compromise
   - Implement emergency security measures

2. Investigation:
   - Determine source and method of compromise
   - Assess information exposed or stolen
   - Identify affected members and operations
   - Document lessons learned

3. Recovery:
   - Create new secure group with updated security
   - Re-verify all member identities
   - Implement additional security measures
   - Resume operations with enhanced protocols

4. Prevention:
   - Update security procedures based on lessons learned
   - Provide additional training to group members
   - Implement monitoring and detection improvements
   - Regular security assessments and reviews
Group Security Challenges

Group communications are inherently less secure than one-to-one communications due to multiple participants, varied security practices, and increased attack surface. Implement strict security protocols and regular security reviews for all group communications.


Section 4-7: Message Verification and Authentication

Overview

Message verification and authentication ensure that communications are genuine, unmodified, and from verified senders. This is critical in resistance operations where disinformation, impersonation, and message manipulation are common adversary tactics.

Cryptographic Verification

Digital Signatures

Message Signing Process:
1. PGP/GPG Signatures:
   - Generate PGP key pair for signing
   - Sign all sensitive messages with private key
   - Recipients verify with public key
   - Maintain secure key management practices

2. Signal Protocol Verification:
   - Automatic cryptographic signatures
   - Safety number verification between contacts
   - Forward secrecy and message authentication
   - Regular verification of contact keys

3. Matrix/Element Verification:
   - Cross-signing device verification
   - Message authentication codes
   - Key verification through multiple channels
   - Regular key rotation and verification

Key Management

Cryptographic Key Security:
1. Key Generation:
   - Use secure random number generation
   - Generate keys on secure, offline systems
   - Use strong key lengths (RSA 4096, ECC 384)
   - Implement proper key backup and recovery

2. Key Distribution:
   - Verify key fingerprints through out-of-band channels
   - Use key signing parties for verification
   - Implement web of trust for key validation
   - Regular key rotation and update procedures

3. Key Storage:
   - Encrypt private keys with strong passphrases
   - Store keys on secure, encrypted devices
   - Implement key escrow for critical operations
   - Regular backup and recovery testing

Authentication Protocols

Identity Verification

Contact Authentication Methods:
1. Out-of-Band Verification:
   - Phone calls to verify identity
   - In-person meetings for key exchange
   - Trusted intermediary introductions
   - Physical document verification

2. Challenge-Response Authentication:
   - Predetermined questions and answers
   - Shared secret verification
   - Historical knowledge verification
   - Behavioral pattern recognition

3. Multi-Factor Authentication:
   - Something you know (password/passphrase)
   - Something you have (device/token)
   - Something you are (biometric/behavioral)
   - Somewhere you are (location verification)

Message Authentication

Message Verification Procedures:
1. Content Verification:
   - Cryptographic signature verification
   - Message integrity checking
   - Timestamp validation
   - Source authentication

2. Context Verification:
   - Message content consistency
   - Timing and sequence verification
   - Cross-reference with other sources
   - Operational context validation

3. Behavioral Verification:
   - Writing style and pattern analysis
   - Communication timing patterns
   - Operational knowledge verification
   - Relationship context validation

Anti-Spoofing Measures

Impersonation Detection

Impersonation Prevention:
1. Technical Measures:
   - Strong cryptographic authentication
   - Device fingerprinting and verification
   - Network analysis and monitoring
   - Automated anomaly detection

2. Procedural Measures:
   - Regular identity verification
   - Predetermined authentication protocols
   - Suspicious activity reporting
   - Cross-verification through multiple channels

3. Human Factors:
   - Training in impersonation detection
   - Awareness of social engineering tactics
   - Verification of unusual requests
   - Reporting of suspicious communications

Message Integrity Protection

Integrity Verification:
1. Cryptographic Protection:
   - Message authentication codes (MAC)
   - Digital signatures for non-repudiation
   - Hash verification for content integrity
   - Timestamp verification for freshness

2. Operational Protection:
   - Message sequence numbering
   - Duplicate message detection
   - Replay attack prevention
   - Message correlation and validation

3. Recovery Procedures:
   - Integrity failure response protocols
   - Message re-transmission procedures
   - Alternative verification methods
   - Incident reporting and investigation

Verification Protocols

Routine Verification

Regular Verification Procedures:
1. Daily Operations:
   - Verify sender identity for all sensitive messages
   - Check message signatures and authentication
   - Cross-reference with expected communications
   - Report anomalies and suspicious activity

2. Weekly Reviews:
   - Review all contact verifications
   - Update authentication credentials
   - Assess verification procedure effectiveness
   - Train participants in verification techniques

3. Monthly Audits:
   - Comprehensive verification system review
   - Update verification procedures and protocols
   - Assess and address verification failures
   - Implement improvements and enhancements

Emergency Verification

Emergency Authentication:
1. Duress Codes:
   - Predetermined phrases indicating compromise
   - Subtle indicators of coercion
   - Emergency authentication procedures
   - Backup verification methods

2. Emergency Contacts:
   - Alternative contact methods for verification
   - Trusted intermediaries for authentication
   - Emergency communication protocols
   - Rapid response verification procedures

3. Crisis Response:
   - Immediate verification of emergency communications
   - Rapid authentication of crisis information
   - Emergency decision-making protocols
   - Post-crisis verification and assessment
Verification Culture

Effective message verification requires developing a culture where verification is routine and expected. All participants must understand the importance of verification and consistently apply verification procedures without exception.


Section 4-8: Communication Scheduling and Protocols

Overview

Communication scheduling and protocols provide the operational framework for secure communications, defining when, how, and under what circumstances different communication methods should be used. Proper scheduling minimizes metadata exposure while ensuring operational effectiveness.

Communication Scheduling

Timing Security

Temporal Security Principles:
1. Pattern Avoidance:
   - Avoid regular communication schedules
   - Randomize communication timing
   - Use predetermined time windows
   - Implement communication blackout periods

2. Time Delays:
   - Introduce random delays between messages
   - Use store-and-forward for non-urgent communications
   - Implement minimum delay periods
   - Coordinate timing across multiple participants

3. Operational Timing:
   - Align communications with operational requirements
   - Avoid communications during high-risk periods
   - Coordinate timing with other operational activities
   - Plan for emergency communication needs

Schedule Development

Communication Schedule Planning:
1. Operational Requirements:
   - Identify communication needs and timing
   - Assess urgency and priority levels
   - Determine participant availability
   - Plan for contingencies and emergencies

2. Security Considerations:
   - Assess surveillance and monitoring risks
   - Implement timing randomization
   - Plan for communication security measures
   - Coordinate with other security protocols

3. Resource Allocation:
   - Assign communication responsibilities
   - Allocate technical resources and infrastructure
   - Plan for backup and redundancy
   - Implement monitoring and maintenance

Protocol Development

Communication Protocols

Protocol Framework:
1. Purpose and Scope:
   - Define communication objectives
   - Identify participants and roles
   - Establish security requirements
   - Determine success criteria

2. Technical Specifications:
   - Select appropriate communication tools
   - Configure security settings
   - Implement access controls
   - Establish backup procedures

3. Operational Procedures:
   - Define communication workflows
   - Establish authentication procedures
   - Implement verification protocols
   - Plan for emergency situations

4. Monitoring and Review:
   - Implement effectiveness monitoring
   - Regular protocol review and updates
   - Incident response and improvement
   - Training and compliance enforcement

Protocol Implementation

Implementation Process:
1. Planning Phase:
   - Develop detailed implementation plan
   - Identify required resources and training
   - Assess risks and mitigation strategies
   - Establish timeline and milestones

2. Testing Phase:
   - Test protocols in safe environments
   - Verify technical functionality
   - Train participants in procedures
   - Identify and address issues

3. Deployment Phase:
   - Gradual rollout of new protocols
   - Monitor implementation effectiveness
   - Provide ongoing support and training
   - Adjust protocols based on experience

4. Maintenance Phase:
   - Regular protocol review and updates
   - Ongoing training and compliance monitoring
   - Incident response and improvement
   - Long-term effectiveness assessment

Emergency Communication Protocols

Emergency Procedures

Emergency Communication Framework:
1. Emergency Classification:
   - Immediate threat to personnel safety
   - Operational compromise or exposure
   - Communication system failure
   - External crisis or disruption

2. Emergency Response:
   - Immediate notification procedures
   - Emergency contact activation
   - Backup communication system deployment
   - Crisis coordination and management

3. Emergency Recovery:
   - Damage assessment and analysis
   - System restoration and recovery
   - Lessons learned and improvement
   - Return to normal operations

Contingency Planning

Contingency Communication Plans:
1. System Failure:
   - Primary system backup procedures
   - Alternative communication methods
   - Emergency contact protocols
   - Service restoration procedures

2. Compromise Response:
   - Immediate isolation and containment
   - Alternative system activation
   - Participant notification and protection
   - Investigation and recovery

3. External Disruption:
   - Network outage response
   - Censorship and blocking countermeasures
   - Physical security threats
   - Legal and regulatory challenges

Protocol Compliance and Enforcement

Compliance Monitoring

Protocol Compliance Framework:
1. Monitoring Systems:
   - Automated compliance checking
   - Regular audit and review procedures
   - Participant self-assessment
   - Peer review and feedback

2. Compliance Metrics:
   - Protocol adherence rates
   - Security incident frequency
   - Communication effectiveness measures
   - Participant satisfaction and feedback

3. Improvement Process:
   - Regular protocol review and updates
   - Training and education programs
   - Incentive and recognition systems
   - Corrective action procedures

Enforcement Procedures

Protocol Enforcement:
1. Education and Training:
   - Initial protocol training for all participants
   - Regular refresher training and updates
   - Specialized training for specific roles
   - Ongoing education and awareness

2. Monitoring and Feedback:
   - Regular compliance monitoring
   - Constructive feedback and guidance
   - Recognition of good practices
   - Early intervention for issues

3. Corrective Action:
   - Progressive discipline for violations
   - Additional training and support
   - Temporary restriction of access
   - Removal from communication systems

4. Continuous Improvement:
   - Regular protocol effectiveness review
   - Participant feedback integration
   - Best practice identification and sharing
   - Protocol updates and enhancements
Protocol Evolution

Communication protocols must evolve continuously as threats change, technology advances, and operational requirements shift. Regular review and updating of protocols ensures continued effectiveness and security.


Chapter Summary

Chapter 4 has provided comprehensive guidance for implementing secure messaging and voice communications within the multi-layer communication architecture:

Section 4-1 covered Session Messenger configuration for maximum-security real-time communications with onion routing and metadata protection.

Section 4-2 detailed Element/Matrix self-hosted setup for secure collaboration systems with end-to-end encryption and rich features.

Section 4-3 explained Briar peer-to-peer messaging for decentralized communications without central servers.

Section 4-4 provided Signal security best practices for medium-risk communications with proper operational security.

Section 4-5 addressed voice communication security challenges and secure voice communication methods.

Section 4-6 covered group communication management with appropriate security controls and access management.

Section 4-7 detailed message verification and authentication procedures to ensure communication integrity and authenticity.

Section 4-8 established communication scheduling and protocols for operational effectiveness while maintaining security.

Implementation Priorities

For new resistance networks, implement secure messaging capabilities in this order:

  1. Basic Secure Messaging: Start with Signal or Session for immediate secure communication needs
  2. Group Collaboration: Deploy Matrix/Element for group coordination and collaboration
  3. High-Security Communications: Implement Briar for maximum-security scenarios
  4. Voice Communications: Add secure voice capabilities as operationally required
  5. Advanced Protocols: Develop sophisticated communication protocols and procedures

Integration with File Sharing

The messaging systems covered in this chapter provide the foundation for secure communications, but many resistance operations also require secure file sharing and collaboration capabilities. Chapter 5 builds on these messaging foundations to provide comprehensive file sharing and collaboration security.


Next: Chapter 5: File Sharing and Collaboration →