Habr•October 17, 2026•🇷🇺Translated from Russian

25-Year Mystery Solved: NIST Elliptic Curve Seeds Came from lrand48 and Unix Timestamps

For 25 years the cryptographic community wondered about the provenance of the SEED values published alongside the NIST elliptic curves in the FIPS 186-2 standard. These seeds determine the curve coefficient b through a hash function, yet the NSA provided them without any explanation of their origin.

Early speculation suggested that long-time NSA employee Jerry Solinas had produced the seeds by hashing humorous internal phrases such as “Give Bob and Jerry a raise.” That theory remained unverified after Solinas’s death in 2023.

Claude identifies the true source

Engineers at Anthropic asked the internal research model Claude to investigate without supplying the old rumor. Within minutes the model recognized that the published seeds matched output from the lrand48 generator in the C standard library, initialized with Unix timestamps.

The generation process worked as follows: the generator was seeded with a Unix time t, then 20-byte candidates were extracted every 20 calls. The published seed for NIST P-256 corresponds to the 1842nd candidate produced on 16 August 1997 at 01:52:34 UTC. Similar timestamps between May 1997 and April 1998 account for all five prime-field curves.

Base points also traced

Base points for six curves created in May 1997, including P-192 and several ANSI X9.62 examples, were generated by the random routine inside FreeLIP, Arjen Lenstra’s long-integer package. The starting seeds for that generator (20000, 20420, etc.) have now been recovered and reproduce the published points exactly.

Implications for trust

The discovery shows that the curves were chosen by a weak, publicly reproducible process rather than by any sophisticated backdoor insertion. While a few valid candidate curves were skipped and one binary-field seed remains unexplained, the overall methodology leaves far less room for hidden weaknesses than previously feared.

The full reproduction code, written in Python, has been released under CC0 and confirms every recovered seed and base point.

Related articles

Security NEXT•Policy & Regulation

Japan's IPA Opens Special Consultation Desk for Suspected Cyberattack Data Leaks

The Information-technology Promotion Agency (IPA) has launched a dedicated Unauthorized Access Special Consultation Desk to assist companies and organizations affected by cyber attacks resulting in information leaks. The service accepts inquiries from entities that only suspect they may have been victimized, providing initial response guidance even before confirmed incidents. Consultations cover advice on whether unauthorized access or data exfiltration is likely, recommended immediate containment steps, lists of incident response vendors, and reporting obligations to relevant authorities. The hotline operates on weekdays from 9:30 to 17:30 excluding the lunch hour, while email replies may take until the next business day. Separate channels exist for non-access incidents, general security advice, and individual personal data breach concerns. The move responds to a rising number of breaches targeting online services handling personal information.

AntiMalware•Policy & Regulation

Russian State Duma Approves Outsourcing of Banking Secrecy and Client Data Without Consent

The State Duma has passed legislation in its second and third readings permitting Russian banks to transfer client data processing, including banking secrecy and personal information, to external IT contractors and cloud providers. No separate client consent will be required for such transfers. Only accredited Russian IT companies and banks holding a universal license that meet strict domestic control criteria may act as processors, with all servers required to remain inside Russia. Banks must notify the Central Bank of Russia in advance, and contractors must undergo audits by organizations licensed by FSTEC or FSB Russia. Special approval procedures involving the Central Bank, FSB, and Rosfinmonitoring apply to banks under foreign control. The law preserves banking secrecy while expanding the circle of authorized handlers under defined security obligations.

AntiMalware•Policy & Regulation

Russia's MinTsifry Drafts Security Requirements for Trusted Domestic Software

The Russian Ministry of Digital Development has published a draft set of requirements for trusted Russian software that go beyond simple domestic origin. The proposals focus on resilience against external interference, absence of known unpatched vulnerabilities, and full development and build processes conducted inside Russia under controlled conditions. Additional rules cover up-to-date component inventories, in-country technical support, and timely disclosure of software updates. Special compatibility mandates are included for Russian browsers and electronic signature tools across multiple product classes such as operating systems, databases, office suites, and communication applications. Compliance verification would be voluntary through expert review, with results recorded in the official Russian software registry and internal-use software lists.

AntiMalware•Policy & Regulation

Rostelecom Calls for 'Doomsday' Data Centers to Counter Drone Attacks and Infrastructure Risks

Rostelecom executive Valery Ermakov has urged Russian companies to build geographically distributed backup data centers, dubbed 'doomsday' facilities, to ensure service recovery after site losses. The recommendation follows drone strikes that disabled three Yandex data centers in Sasovo, Kaluga, and Vladimir, disrupting both internal services and Yandex Cloud clients. Ermakov explained that previous centralized infrastructure, built for economic efficiency, is no longer viable under changed threat models that now include physical attacks previously considered unthinkable. He advocated a micro-cellular architecture with services spread across many sites connected by high-speed links, while warning that Russian backbone networks are overloaded and much fiber optic infrastructure dates back 20-30 years. Rostelecom positioned its TEA NEXT line running from Kaliningrad to Mongolia as a source of additional capacity to address potential backbone shortages. Yandex responded to the incidents by accelerating client data migration to partner cloud providers.