PingCrypt is a terminal-first secure messaging protocol. This guide covers authentication, session management, and the encrypted packet lifecycle.
The easiest way to use PingCrypt is by sourcing our shell helper into your environment. This enables high-level functions that abstract away complex curl commands.
pc.ps1 script provides identical functionality via Invoke-RestMethod.Initializes a secure session. Prompts for PingCrypt ID and Password. Tokens are cached in ~/.pc_session with 600 permissions for persistent CLI use.
Transmits an encrypted string to a receiver. AES-256-GCM encryption is applied server-side before storage.
Sends a single message to multiple comma-separated IDs (limit: 10). Each recipient receives a unique cryptographic envelope.
Replies to a specific message ID. The system automatically resolves the recipient from the original message metadata.
Fetches your cryptographic logs. Sent messages are decrypted on the fly for your review.
Marks a received packet as acknowledged.
Sender-only: Flags a message as retracted globally.
Removes a message from your local view permanently.
AES-256-GCM EncryptionMessages are encrypted using AES-GCM for both confidentiality and integrity protection. High-entropy initialization vectors prevent pattern recognition.
Rate Limiting & Anti-BruteEndpoints are protected by leaky-bucket rate limiting. Attempts are throttled by IP and UID to prevent automated crawling or brute-force attacks.
Hardened CLI ProtocolThe CLI scripts utilize stty for silent password input and manage session files with restricted OS permissions.
HSTS & CSP HeadersProduction builds enforce Strict-Transport-Security and restrictive Content-Security-Policies to neutralize XSS and session hijacking.
Protocol_Version_1.0.4