Template:Infobox encryption method
| {{{name}}} | |
| {{{image}}}
{{{caption}}} | |
| Designer(s): | {{{designers}}} |
|---|---|
| First published: | {{{publish date}}} |
| Derived from: | {{{derived from}}} |
| Successor(s): | {{{derived to}}} |
| Related to: | {{{related to}}} |
| Certification: | {{{certification}}} |
| Key size(s): | {{{key size}}} |
| Security claim(s): | {{{security claim}}} |
| Block size(s): | {{{block size}}} |
| Structure: | {{{structure}}} |
| Rounds: | {{{rounds}}} |
| Best public cryptanalysis: | |
| {{{cryptanalysis}}} | |
Syntax
{{Infobox block cipher
| name =
| image =
| caption =
| designers =
| publish date =
| derived from =
| derived to =
| related to =
| certification =
| key size =
| security claim =
| block size =
| structure =
| rounds =
| cryptanalysis =
}}
Description of fields
(See talk page for an example)
All fields except for name are optional.
- name: Name of the block cipher, or preferably the abbreviation if the expansion contains multiple words and would not fit well.
- image: An illustrative image for the block cipher; typically this would contain the cipher's Feistel function for Feistel-structured ciphers.
- caption: (Only if the image field is specified) caption for the image.
- designers: Names of the designers/authors of the block cipher, separated by commas. Should not contain organization names unless names of the real authors are unknown. The names should be linked if articles about them exist.
- publish date: Date that the block cipher was first presented. If the exact date is unknown, this should at least contain the year number.
- derived from: A comma-separated list of block ciphers that inspired the design of the subject block cipher.
- derived to: A comma-separated list of block ciphers whose design was inspired by the subject block cipher.
- related to: A list of block ciphers that are otherwise related to the subject. This field should be used minimally, and only when the relation is clearly remarkable.
- certification: Entities that have selected/recommended this algorithm. For example, "AES finalist", "NESSIE", "CRYPTREC"
- key size: Key size(s) that the block cipher was originally designed to operate with, in bits. Should contain the suffix "bits". May contain multiple sizes. For example, AES submissions would have "128, 192 or 256 bits"
- security claim: Security claims(s) that the block cipher was originally designed to achieve with, in bits. Should contain the suffix "bits". May contain multiple sizes. For example, submissions would have "128, 192 or 256 bits"
- block size: Size(s) of the input and output blocks of the block cipher. Should contain the suffix "bits". May contain multiple sizes.
- structure: If the cipher follows a common structure. Typical ciphers should have "Feistel network" or "Substitution-permutation network" here.
- rounds: The number(s) of rounds the cipher was originally designed to work with. May contain several values.
- cryptanalysis: The best-known cryptanalysis for the subject cipher. Should contain a brief overview of the vulnerabilities found, and a footnote link to the reference.
Extra features
- Articles that use this template are automatically included in the Category:Block ciphers.