Fact-checked by Grok 2 weeks ago

Kerckhoffs's principle

Kerckhoffs's principle is a cornerstone of modern cryptography, asserting that the security of a cryptosystem must depend entirely on the secrecy of the key, while the algorithm and all other components of the system may be publicly known without compromising its strength.^[1] Formulated by Dutch cryptologist Auguste Kerckhoffs in his 1883 publication La Cryptographie Militaire, the principle emerged as part of a broader set of six axioms designed to guide the development of robust military encryption systems.^[2] Kerckhoffs, a professor of German languages at the École des Hautes Études Commerciales in Paris, outlined these principles in two articles published in the Journal des sciences militaires, emphasizing practical requirements for secure communication in wartime.^[1] The second principle specifically states: "The system must not require secrecy, and it must be able to fall into the hands of the enemy without inconvenience," underscoring that true security arises from key management rather than concealing the method itself.^[1] The full set of Kerckhoffs's principles includes: (1) the system must be practically, if not mathematically, undecipherable; (2) no secrecy in the system is required, even if captured; (3) keys must be communicable and memorable without notes, and easily changeable; (4) compatibility with telegraphy; (5) portability and usability by a single person; and (6) simplicity in operation to avoid mental strain or complex rules.^[1] These guidelines addressed the limitations of 19th-century ciphers, which often failed due to over-reliance on obscurity or impracticality, as seen in historical examples like Napoleon's dual codes or indecipherable dispatches from the Turko-Russian War.^[3] In contemporary cryptography, Kerckhoffs's principle underpins the design of open standards such as the Advanced Encryption Standard (AES), where the algorithm is publicly scrutinized to identify weaknesses, ensuring reliability through collective expert review rather than proprietary secrecy.^[4] This approach contrasts with "security through obscurity," which Kerckhoffs implicitly critiqued, and has been validated in scholarly analyses as essential for resilient systems in the face of evolving threats.^[5] By prioritizing key secrecy and algorithmic transparency, the principle facilitates widespread adoption, interoperability, and ongoing improvement in fields from digital communications to financial security.^[6]

History and Development

Original Formulation

Auguste Kerckhoffs (1835–1903), born Jean Guillaume Auguste Victor François Hubert in the Netherlands and trained as a linguist at the University of Liège, served as a professor of German at the École des Hautes Études Commerciales in Paris, where his expertise in languages informed his pioneering work in military cryptography.^[7] Kerckhoffs articulated his ideas in the treatise La Cryptographie Militaire, published in two installments in the Journal des Sciences Militaires: the first part appearing in Volume IX, pages 5–38, in January 1883, and the second in pages 161–191, in February 1883.^[8] In this publication, he proposed six axioms for effective military cryptosystems, drawing on his linguistic background to stress the need for robust, user-friendly methods amid the era's reliance on manual ciphers for wartime communication. The second of these axioms forms the core of what is now known as Kerckhoffs's principle: "The system must not require secrecy, and it must be able to fall into the hands of the enemy without inconvenience."^[8] This condition underscores that a cryptosystem's security must depend entirely on the confidentiality of the key, rather than on keeping the system's design secret, allowing it to withstand analysis even if fully disclosed to adversaries. Kerckhoffs emphasized this by arguing that true strength lies in the key's variability and management, not in obscurity of the mechanism itself.^[8]

Historical Context

In the mid-19th century, cryptography relied heavily on classical methods such as polyalphabetic substitution ciphers, exemplified by the Vigenère cipher invented in the 16th century but widely used into the 1800s for military and diplomatic communications.^[9] These systems aimed to thwart simple frequency analysis by employing multiple substitution alphabets based on a repeating keyword, making letter frequencies less predictable than in monoalphabetic ciphers. However, advancements in cryptanalysis exposed their weaknesses; by the 1860s, techniques like the Kasiski examination, developed by Prussian military officer Friedrich Kasiski, could identify keyword lengths through repeated ciphertext patterns, allowing attackers to reduce the cipher to simpler monoalphabetic components vulnerable to frequency analysis. The Franco-Prussian War of 1870–1871 intensified these challenges, marking the first major European conflict where telegraphy enabled rapid long-distance military coordination but also facilitated widespread interception of messages.^[10] French forces suffered significant cryptographic setbacks, as their codes—often simple nomenclators or homophonic substitutions—proved inadequate against Prussian cryptanalysts, leading to compromised communications and contributing to France's defeat.^[10] This vulnerability, exacerbated by increased training of personnel who could defect or be captured, underscored the urgent need for more robust, user-friendly systems that could withstand enemy analysis even under duress.^[10] Auguste Kerckhoffs, a Dutch-born linguist and professor of German in Paris, addressed these deficiencies through his contributions to military scholarship in the late 1870s and 1880s. Appointed to teach at institutions including the École des Hautes Études Commerciales and École Arago, he critiqued prevailing French military ciphers for their over-reliance on secrecy of the method, excessive complexity that hindered practical use, and failure to prioritize key secrecy amid telegraph-era demands.^[11] In articles published in the Journal des sciences militaires, Kerckhoffs argued that existing systems were too fragile, often broken by basic cryptanalytic methods, and advocated for designs emphasizing simplicity, portability, and resilience to known algorithms. By the late 1800s, cryptographic theory began transitioning from ad hoc, rule-based classical techniques to more systematic frameworks influenced by mathematical rigor and practical military needs.^[12] The proliferation of telegraph networks demanded ciphers that were quick to encode and decode while resisting interception, prompting innovations like improved polyalphabetics and early codebooks that incorporated probabilistic elements to counter frequency-based attacks. This evolution reflected a broader shift toward viewing cryptography as a scientific discipline rather than an arcane art, setting the stage for Kerckhoffs's original formulation as a direct response to the wartime failures of opaque, brittle systems.^[10]

Core Explanation

The Principle Itself

Kerckhoffs's principle asserts that the security of a cryptographic system should depend solely on the secrecy of the key, remaining secure even if all other aspects of the system—including the algorithm, protocols, and implementation details—are fully public knowledge. This foundational idea ensures that the system's strength is not compromised by the potential disclosure of its design, placing the burden of protection entirely on proper key management. As articulated in Auguste Kerckhoffs's 1883 work La Cryptographie Militaire, the principle emphasizes that the system must be practically indecipherable without the key, regardless of an adversary's familiarity with its mechanics.^[13] Central to this principle is the concept of open design, where cryptographic algorithms are subjected to rigorous examination by experts worldwide to detect and mitigate vulnerabilities. By making the design transparent, developers invite diverse perspectives that can reveal subtle flaws, such as unintended side-channel leaks or mathematical weaknesses, which might evade isolated analysis. This collaborative scrutiny fosters robust systems.^[13] The underlying rationale is that proactive public evaluation uncovers issues before malicious actors exploit them, enhancing long-term resilience over temporary obscurity. Concealing the algorithm might delay initial attacks but ultimately weakens security, as isolated teams are prone to oversights that collective expertise can address. This approach aligns with the principle's goal of verifiable strength, where confidence in the system derives from its ability to withstand open challenges.^[14] Analogous to civil engineering, where bridges are built to endure publicly known forces like wind and earthquakes without relying on hidden blueprints for safety, Kerckhoffs's principle promotes designs tested against anticipated threats in full view, ensuring reliability through transparency and proven durability.

Supporting Axioms

In addition to the foundational principle that a cryptosystem's security should depend solely on the secrecy of the key (the second axiom), Kerckhoffs outlined five supporting axioms in his 1883 work La Cryptographie Militaire to ensure the system's overall practicality and robustness in military applications. These axioms emphasize usability, adaptability, and flexibility, reinforcing the core principle by promoting designs that remain secure and effective even when fully disclosed, without compromising on operational efficiency.^[15] The first axiom states that the system must be substantially, if not mathematically, undecipherable. This requires the cryptosystem to resist cryptanalysis in practice, providing a strong baseline security independent of secrecy.^[15] The third axiom requires that the keys must be communicable and memorable without the aid of written notes, and easily changeable or modifiable by correspondence between the parties. This ensures secure key distribution and management, allowing quick adaptation to potential compromises while maintaining operational secrecy focused on the key.^[15] The fourth axiom mandates that the system ought to be compatible with telegraph communication. In the 19th-century context, this ensured adaptability to rapid, long-distance transmission methods like Morse code, integrating the cryptosystem with existing military infrastructures without relying on obscurity.^[15] The fifth axiom specifies that the system must be portable, and its use should not require more than one person or special equipment. This promotes simplicity in deployment, enabling individual field operators to use it without complex setups, supporting key-focused security in diverse environments.^[15] The sixth axiom states that the system must be easy to use, requiring neither mental strain nor knowledge of a long series of rules. This minimizes operator errors under stress or with limited training, upholding security through straightforward procedures rather than concealed mechanisms.^[15] Collectively, these axioms complement the core principle by embedding practical considerations into cryptosystem design, ensuring that openness does not hinder usability or adaptability but instead enhances long-term reliability in real-world scenarios.^[15]

Key Implications

Secrecy of Keys

In Kerckhoffs's principle, the security of a cryptosystem relies solely on the secrecy of the key, while the algorithm and all other components of the system may be fully public knowledge. This distinction ensures that the system's strength derives from the key's high entropy and randomness, making it computationally difficult for adversaries to derive the plaintext without the key, even with complete access to the algorithm's specifications.^[1] A practical illustration is the Advanced Encryption Standard (AES), a symmetric block cipher where the algorithm is openly documented and widely implemented. Despite this transparency, an attacker who knows the AES details cannot feasibly recover the key through brute force if a 256-bit key is used, as the key space encompasses 2^{256} possibilities—far exceeding the computational resources available today or in the foreseeable future. The effectiveness of key-only secrecy underscores the critical role of robust key lifecycle management. Key generation must employ cryptographically secure random number generators to maximize entropy and avoid predictability; distribution protocols, such as those using secure channels, prevent interception during transit; and ongoing management practices, including secure storage and rotation, mitigate risks from side-channel attacks like power analysis or timing leaks that could indirectly expose the key.^[16]^[17] Historically, classical cryptography often depended on the secrecy of the entire algorithm or mechanism, a practice known as security by obscurity that proved vulnerable when systems were compromised or reverse-engineered. Kerckhoffs's formulation in 1883 marked a pivotal shift toward key-only secrecy, establishing a foundational axiom that has influenced modern cryptographic design by prioritizing verifiable strength over hidden implementations.^[1]

Long-Term Security

Under Kerckhoffs's principle, long-term security of a cryptosystem requires mechanisms like forward secrecy and periodic key rotation to mitigate risks from evolving threats, such as key compromise or advances in attack capabilities. Forward secrecy ensures that session keys derived from long-term keys are ephemeral and independent, protecting past communications even if a long-term key is later exposed.^[18] Periodic key rotation, by replacing keys at regular intervals, limits the window of exposure and counters potential weakening over time due to repeated use or partial leaks.^[19] These practices are integral to open cryptosystems, where the algorithm's transparency allows for standardized implementation and ongoing improvements without undermining the system's foundation. Public algorithms enhance resistance to cryptanalysis by enabling broad community vetting, which identifies and patches vulnerabilities that might otherwise remain hidden. When the full system design is openly available, cryptographers worldwide can subject it to rigorous scrutiny, reducing the likelihood of unknown flaws that could be exploited years later.^[20] This collective review process, as seen in the development of standards like AES, has historically strengthened algorithms against diverse attack vectors, ensuring sustained robustness.^[21] Anticipating computational advances is crucial for long-term viability, particularly in designing for future hardware like quantum computers that could break current public-key systems. Post-quantum cryptography algorithms, such as those standardized by NIST, are developed openly to allow expert evaluation and resistance to both classical and quantum threats, aligning with Kerckhoffs's emphasis on verifiable security.^[22] This proactive approach ensures the cryptosystem remains secure as technology evolves, without relying on hidden details. In contrast, outdated proprietary systems often fail catastrophically when design secrets leak, as the entire security model collapses without a vetted fallback. Open designs, however, prove resilient; even if implementation details are known, the core algorithm's proven strength—bolstered by key secrecy—allows for continued use or graceful migration to updated versions.^[19]

Modern Applications

In Symmetric Cryptography

In symmetric cryptography, Kerckhoffs's principle emphasizes that security must derive solely from the secrecy of the shared key, with the algorithm and all other system details publicly known and scrutinized. This approach allows for widespread implementation and verification, reducing vulnerabilities from hidden flaws. Classic examples include the Data Encryption Standard (DES) and the Advanced Encryption Standard (AES), both developed with fully public specifications to enable peer review and adoption. DES, published by the National Bureau of Standards (now NIST) in 1977, uses a 56-bit key for its Feistel network-based block cipher, relying on key confidentiality despite the algorithm's openness.^[23] AES, selected in 2001 after a public competition, employs a substitution-permutation network with key sizes of 128, 192, or 256 bits—such as AES-256 for enhanced resistance to brute-force attacks—ensuring robustness through transparent design.^[24] Historically, deviations from this principle contributed to cryptanalytic successes, as seen with the Enigma machine during World War II. Enigma's security partially depended on the secrecy of its rotor wirings and mechanisms, violating Kerckhoffs's ideal of public algorithms; this reliance on obscurity facilitated breaks by Allied cryptanalysts, including Marian Rejewski and Alan Turing, who exploited known design elements alongside procedural weaknesses. In contrast, modern symmetric standards avoid such pitfalls by mandating open publication, fostering trust and iterative improvements through global expert analysis.^[25] Standardization bodies like NIST play a pivotal role in upholding Kerckhoffs's principle by conducting open competitions and public comment periods to evaluate and refine algorithms. For instance, NIST's process for AES involved soliciting submissions, rigorous testing, and community feedback to select Rijndael, ensuring the final standard withstands diverse attacks. This transparency extends to modes of operation for block and stream ciphers, where public specifications enhance interoperability and security assurance. The Cipher Block Chaining (CBC) mode, defined in NIST SP 800-38A, chains plaintext blocks with the previous ciphertext to prevent pattern repetition, promoting verifiable implementations. Similarly, the Galois/Counter Mode (GCM) in SP 800-38D provides authenticated encryption for both confidentiality and integrity, with its open design allowing detection of implementation errors across applications like TLS.^[26]^[27]^[28]

In Public-Key Systems

Kerckhoffs's principle finds a natural extension in public-key cryptography, where the system's security relies solely on the secrecy of private keys while algorithms, public keys, and protocols are openly published to enable widespread adoption and scrutiny. This approach aligns with the principle by assuming adversaries have full knowledge of the mathematical foundations and implementation details, ensuring robustness against analysis. In asymmetric systems, the public component facilitates key distribution without prior shared secrets, contrasting with symmetric methods but often integrating them in hybrid setups for efficiency. The RSA cryptosystem exemplifies this application, as its algorithm—based on the difficulty of factoring large semiprimes—is fully described in the open literature, with public keys (modulus and exponent) freely shared while private keys remain secret. Similarly, the Diffie-Hellman key exchange protocol publishes its parameters and computational steps, allowing parties to derive a shared secret over insecure channels solely through private exponents. These designs embody Kerckhoffs's principle by deriving security from key secrecy amid complete algorithmic transparency, enabling independent verification and interoperability.^[29]^[30] In digital signatures and public key infrastructure (PKI), the principle supports open standards that bind identities to public keys for verification. PKI frameworks rely on X.509 certificates, an ITU-T standard specifying formats for public-key certificates, which are publicly disseminated to establish trust chains without concealing the underlying mechanisms. This openness allows global validation of signatures while protecting private signing keys, ensuring the system's integrity depends only on key management.^[31] Protocols such as Transport Layer Security (TLS) further illustrate the principle, with their full specifications—including handshake processes, cipher suites, and key exchange methods—published as IETF RFCs for public implementation and review. Security in TLS arises from authenticated key exchanges and certificate validation rather than proprietary details, permitting diverse vendors to deploy compatible systems securely.^[18] The ongoing development of post-quantum cryptography adheres to Kerckhoffs's principle through transparent, competitive standardization. NIST's post-quantum cryptography process, initiated in 2016, solicited public submissions for quantum-resistant algorithms, evaluating them openly through multiple rounds until selecting candidates like ML-KEM for standardization in 2024. This collaborative, peer-reviewed approach ensures selected public-key algorithms withstand quantum threats based on key secrecy alone.^[22]

Contrasts and Critiques

Versus Security by Obscurity

Security by obscurity is a security strategy that depends on keeping the details of a system's design, implementation, or algorithms confidential to deter attacks, rather than relying on the system's mathematical robustness.^[32] This approach assumes that adversaries lack the knowledge to exploit vulnerabilities if the inner workings remain hidden, but it fundamentally contrasts with Kerckhoffs's principle, which insists that security must hold even when the entire system except the key is public.^[1] A prominent historical example of security by obscurity's shortcomings is the Content Scrambling System (CSS), a proprietary encryption scheme introduced in 1996 to protect DVD content from unauthorized copying. CSS employed a simple 40-bit stream cipher based on linear feedback shift registers, with its algorithm and keys deliberately undisclosed to maintain protection; however, in 1999, Norwegian programmer Jon Lech Johansen reverse-engineered the system from a commercial DVD player, releasing the DeCSS tool that decrypted CSS-protected discs in seconds.^[33] Once exposed, CSS's weaknesses—such as poor key management and insufficient key length—rendered it ineffective, leading to widespread circumvention and legal battles over the tool's distribution.^[33] The failure of security by obscurity stems from the inevitability of leaks or discoveries, whether through reverse engineering, insider disclosures, or compelled revelations, which collapse the entire defense into a single point of vulnerability without any fallback strength.^[34] Kerckhoffs critiqued this reliance on secrecy in his 1883 axioms, asserting that a cryptosystem "should not require secrecy, and it should not be a problem if it falls into enemy hands," as obscurity adds no inherent resilience and instead hinders collective improvements by preventing expert scrutiny and iterative refinement.^[1]

Limitations and Debates

While Kerckhoffs's principle emphasizes the security of cryptographic systems relying on the secrecy of keys rather than the algorithm itself, it does not fully address vulnerabilities arising from implementation flaws in open algorithms. For instance, side-channel attacks, such as timing or power analysis, can exploit unintended information leaks during the execution of well-known algorithms like AES, regardless of the key's secrecy. These attacks highlight that openness alone cannot prevent all real-world threats, as adversaries can study the algorithm to craft targeted implementations that reveal sensitive data. A key debate surrounding the principle concerns whether the public disclosure of algorithms invites more targeted attacks from adversaries. Critics argue that openness provides a blueprint for exploiting weaknesses, potentially accelerating the discovery of flaws in widely adopted systems. However, proponents counter that open scrutiny enables the cryptographic community to identify and patch vulnerabilities more rapidly than in closed systems, where issues may remain hidden until exploited. This perspective is supported by historical evidence, such as the swift improvements to DES following its public analysis in the 1970s. In modern critiques, the principle faces challenges in contexts like proprietary software and national security, where partial obscurity persists despite its theoretical flaws. For example, some governments classify certain algorithms for military use, arguing that limited disclosure enhances short-term protection against foreign adversaries, though this contradicts Kerckhoffs's emphasis on long-term robustness. Similarly, commercial entities occasionally embed secret components in encryption tools to deter reverse engineering, illustrating a tension between openness and practical incentives for secrecy. The advent of quantum computing introduces further limitations, necessitating adaptations to the principle while preserving its core validity. Quantum algorithms like Shor's threaten symmetric and asymmetric systems alike, leading to the development and release of open standards such as NIST's post-quantum cryptography standards (e.g., FIPS 203 for ML-KEM, finalized in 2024).^[35] These include algorithms like ML-KEM (based on CRYSTALS-Kyber) for key encapsulation and ML-DSA (based on CRYSTALS-Dilithium) for digital signatures, selected through a public standardization process that embodies Kerckhoffs's principle by inviting global expert review to ensure widespread vetting and interoperability.^[36] Ethically, open cryptography under Kerckhoffs's principle equips both defenders and attackers with equal access to robust tools, raising debates about dual-use implications. While this democratizes security for legitimate users, it also empowers malicious actors, such as in ransomware or state-sponsored espionage, underscoring the need for balanced policies on algorithm dissemination.

References

[1]
Kerckhoffs' principles from « La cryptographie militaire
Here is an approximate English version of the principles that should apply to a crypto-system: The system must be substantially, if not mathematically ...Missing: primary source
[2]
https://www.petitcolas.net/kerckhoffs/la_cryptographie_militaire_i.htm
[3]
Kerckhoffs' history and principles of military cryptography, translated ...
Mar 4, 2015 · Historical Concepts : Cryptography, or the Art of Numbers, is a science as old as the world itself ; confounded in its origin with military ...
[4]
A Modern Interpretation of Kerckhoff - Rambus
Sep 21, 2020 · A modern interpretation of Kerckhoff teaches that you shouldn't rely on the obscurity of your crypto algorithm, but rely instead on standard algorithms with ...
[5]
Technical principles and protocols of encryption and their ...
Sep 17, 2024 · This article examines the foundational principles and protocols that guide the development, implementation and use of encryption2.2. Encryption Architecture · 3.7. Kerckhoff's Other... · 4.3. Encryption Law And...
[6]
adversary: the philosophy of cryptography | Journal of Cybersecurity
Mar 27, 2025 · The essence of cryptography is secure communication in the presence of adversaries. We present an analysis of cryptography in terms of a philosophy founded on ...Philosophical Preliminaries · Access Control And... · The Adversary Revealed
[7]
(PDF) Kerckhoffs Principle - ResearchGate
Kerckhoffs Principle · In book: Encyclopedia of Cryptography and Security · Edition: 2nd · Publisher: Springer · Editors: Henk C. A. van Tilborg, Sushil Jajodia.
[8]
https://www.petitcolas.net/fabien/kerckhoffs/
[9]
Vigenere Cipher - Computer Science
Jun 10, 2014 · Vigenere-like substitution ciphers were regarded by many as practically unbreakable for 300 years. In 1863, a Prussian major named Kasiski ...
[10]
A French cipher from the late 19th century
Apr 9, 2020 · The Franco-Prussian war (1870--1871) was the first major ... Historical cipherFrench cryptographyHippolyte DJosse; Contact author ...
[11]
Cryptography in warfare | Research Starters - EBSCO
Cryptography in warfare refers to the use of coded messages to securely transmit sensitive information among military personnel.
[12]
The Evolution of Cryptography and a Contextual Analysis ... - NHSJS
Apr 3, 2024 · This paper delves into the historical context, examining the limitations of older schemes and their roots. It then navigates through the evolution of ...Missing: 1800s | Show results with:1800s
[13]
Symmetric Cryptography — Study Guide
Kerckhoffs's Principle. A system must remain ... Anyone can design a cipher they cannot break; confidence comes only after broad, sustained public scrutiny.
[14]
Introduction to Symmetric Cryptography - Paul Krzyzanowski
Kerckhoffs's Principle ... This idea is known as Kerckhoffs's Principle. It ... True strength comes from withstanding public scrutiny, not from avoiding it.Goals Of Cryptography · Kerckhoffs's Principle: The... · Why Open Algorithms Work...<|control11|><|separator|>
[15]
[PDF] Kerckhoff's principle - UMD Department of Computer Science
Sep 8, 2019 · More generally we will always use Kerckhoff's principle: ▶ The encryption scheme is not secret ▶ Eve knows the encryption scheme ▶ The only ...
[16]
https://cheatsheetseries.owasp.org/cheatsheets/Key_Management_Cheat_Sheet.html
[17]
Key Management - OWASP Cheat Sheet Series
This Key Management Cheat Sheet provides developers with guidance for implementation of cryptographic key management within an application in a secure manner.
[18]
[PDF] Recommendation for Key Management: Part 1 - General
May 5, 2020 · Improper error handling can allow attacks (e.g., side channel attacks). A security policy (see SP 800-57, Part 2) should define the response ...
[19]
Kerckhoffs's Law for Security Engineers - Devdatta Akhawe
Jun 4, 2021 · Kerckhoffs's law: a cryptosystem should be secure even if everything about the system, except the key, is public knowledge.
[20]
May 15, 2002 - Schneier on Security
May 15, 2002 · The reasoning behind Kerckhoffs' Principle is compelling. If the cryptographic algorithm must remain secret in order for the system to be secure ...May 15, 2002 · Secrecy, Security, And... · Fun With Fingerprint ReadersMissing: vetting | Show results with:vetting
[21]
[PDF] Cryptography - Syed Rafiul Hussain
Kerckhoffs's Principle: – A cryptosystem should be secure even if everything ... ‣ Vetted through crypto community. ‣ Avoid any “proprietary” encryption.
[22]
Post-Quantum Cryptography | CSRC
Post-quantum cryptography aims to develop systems secure against both quantum and classical computers, as current systems are vulnerable to quantum computers.Workshops and Timeline · Post-Quantum · Presentations · Email List (PQC Forum)Missing: Kerckhoffs principle
[23]
Cryptography: How did Microsoft's NTLM failed Kerckhoff's principle ...
Oct 19, 2015 · Alas, there do still exist proprietary systems that are closed-source and which therefore fail to follow the principle. I only recommend open- ...
[24]
FIPS 46, Data Encryption Standard (DES) | CSRC
The standard specifies an encryption algorithm which is to be implemented in an electronic device for use in Federal ADP systems and networks.
[25]
FIPS 197, Advanced Encryption Standard (AES) | CSRC
Three members of the Rijndael family are specified in this Standard: AES-128, AES-192, and AES-256. Each of them transforms data in blocks of 128 bits.
[26]
THE ENIGMA MACHINE AND THE 'ULTRA' SECRET
Military History Journal Vol 11 No 1 - June 1998. THE ENIGMA MACHINE AND THE 'ULTRA' SECRET ... Auguste Kerckhoffs. In 1883, when he was 45 years old, Kerckhoffs wrote what was to become one of the great books on cryptology, La Cryptographic Militaire.
[27]
Cryptographic Standards and Guidelines Development Process
Background: This draft results from a NIST-initiated review of its cryptographic standards development process in response to public concerns about the security ...
[28]
[PDF] NIST SP 800-38A, Recommendation for Block Cipher Modes of ...
The CBC mode is illustrated in Figure 2. 6.3 The Cipher Feedback Mode. The Cipher Feedback (CFB) mode is a confidentiality mode that features the feedback of.
[29]
SP 800-38D, Recommendation for Block Cipher Modes of Operation
This Recommendation specifies the Galois/Counter Mode (GCM), an algorithm for authenticated encryption with associated data, and its specialization, GMAC.
[30]
[PDF] A Method for Obtaining Digital Signatures and Public-Key ...
R.L. Rivest, A. Shamir, and L. Adleman. ∗. Abstract. An encryption method is presented with the novel property that publicly re- vealing an encryption key ...
[31]
[PDF] New Directions in Cryptography - Stanford Electrical Engineering
Diffie and M. E. Hellman, “Cryptanalysis of the NBS data en- cryption standard” submitted to Computer, May 1976. A. V. Aho, J. E. Hopcroft, and J. D. Ullman ...
[32]
RFC 5280 - Internet X.509 Public Key Infrastructure Certificate and ...
RFC 5280 profiles X.509 v3 certificates and X.509 v2 CRLs for the Internet, part of the Internet PKI standards, and describes certification path processing.Missing: Kerckhoffs | Show results with:Kerckhoffs
[33]
RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3
This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet.
[34]
What is Security Through Obscurity? - Recorded Future
Mar 7, 2024 · Security through obscurity (STO) is a security approach that primarily relies on secrecy for securing networks, systems, or applications from unauthorized ...
[35]
[PDF] CRYPTOGRAPHY 2006 THE RISE AND FALL OF DVD ENCRYPTION
Dec 15, 2006 · 5.4 Security through obscurity. There has never been released an official description of the cryptosystem behind CSS. Its creators must have ...
[36]
Security Through Obscurity (STO): History, Criticism & Risks - Okta
Aug 30, 2024 · STO has been a traditional aspect of cryptography with government agencies, such as the NSA (National Security Agency), employing ...