How the Lorenz SZ 42 Teleprinter Cipher Machine Worked: Nazi High Command Encryption and Its 1941 Breakthrough
In 1940, British interceptors detected unfamiliar teleprinter signals in the ether, mechanical trills instead of Morse code. These German encrypted teleprinter systems were collectively called Fish. Analysis of Lorenz messages between Vienna and Athens began in summer 1941, with the codename Tunny adopted in 1942. The German designation was Schlüsselzusatz, first SZ 40 then SZ 42 and variants.
Why Lorenz When Enigma Already Existed
Enigma M3 was portable but required separate encryption and transmission steps. The Wehrmacht high command needed direct teleprinter links between headquarters. The Lorenz SZ 40/42 sat between the teleprinter and the line, automatically encrypting the five-bit stream. Operators prepared messages on punched tape for transmission; the receiving unit restored plaintext for printing.
Four largely complete machines survive. Serial 1137 is at The National Museum of Computing, serial 1077 at Bletchley Park, serial 1116 at the National Cryptologic Museum, and one at the Deutsches Museum.
ITA2 Code and Vernam Cipher
Lorenz used the five-bit ITA2 code. It implements the Vernam cipher: plaintext bits XORed with a keystream produced by the wheels. When the keystream matches exactly and is used once, perfect secrecy results, but mechanical repetition created exploitable patterns.
Twelve Wheels: χ, ψ and μ Groups
Twelve wheels generated the keystream. Five χ wheels stepped every character; five ψ wheels stepped together but could be halted by two μ motor wheels. Each χ and ψ wheel contributed one bit, yielding Kᵢ = χᵢ ⊕ ψᵢ. Wheel lengths were pairwise coprime, producing a long period before repetition.
The Stuttering Psi Mechanism and Cryptanalysis
The μ61 wheel controlled μ37, which in turn decided whether the ψ wheels advanced. When ψ wheels stayed still, Δψ became zero, simplifying statistical attacks on ΔC = ΔP ⊕ Δχ ⊕ Δψ. Long messages revealed language biases once χ was correctly guessed, enabling recovery without exhaustive search of all 1.6 × 10¹⁹ starting positions.
Operator Error of 30 August 1941
Two long transmissions between Vienna and Athens used the same starting positions after an operator repeated a message with minor corrections. This depth allowed British analysts to reconstruct wheel patterns and movement rules, paving the way for Colossus in 1944.
Related articles
OpenAI Releases GPT-6.1 Terra: Cost-Effective Model Focused on Computer Control, Image Analysis and Practical Automation
OpenAI has launched GPT-6.1 Terra, a new model positioned between its high-end GPT-6 Astra and more affordable options in the GPT-6 family. The model emphasizes real-world computer interaction, visual understanding of documents and interfaces, and reduced error rates rather than raw reasoning benchmarks. It supports a 1.05 million token context window, image inputs, and tool use through the Responses API while cutting input token prices by half compared with its predecessor. Published benchmarks show substantial gains on Terminal-Bench 4.0, OSWorld 2.1 and Agents' Last Exam, with error rates dropping sharply at both low and maximum reasoning levels. OpenAI stresses that the model still requires human oversight for high-stakes actions and does not directly process audio or video. The release targets developers and enterprises seeking reliable automation of repetitive multi-step tasks at lower cost than flagship models.
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.