Permanently protected template

Template:Committed identity

From Wikipedia, the free encyclopedia
  (Redirected from Template:User committed identity)
Jump to: navigation, search
Committed identity: {{{1}}} is a SHA-512 commitment to this user's real-life identity.
Template documentation[view] [edit] [history] [purge]

This template gives you a way to later prove that you are the person who was in control of your account on the day this template was placed. This is done by putting a code (called a "hash") on your user page so that, in the event that your account is compromised, you can convince someone else that you are really the person behind your username.

Why?

The intended use of this template is to help in the hopefully unlikely event that your account is compromised. If you published your real-life identity, then that identity could be used to reestablish contact with you if your account were compromised; keep in mind, in this scenario contact could not be established with you through your account, since it may be under the control of someone else. However, many Wikipedia users do not disclose their real-life identities, or disclose little enough of them that it may be difficult to establish their identity.

This is not a replacement for having a strong password, nor for registering an email address for your account. You should still do everything you can to prevent your account being compromised, including using a strong password and remembering to log yourself out when using a computer to which others may have access. If you have one, it may also be helpful to post your PGP public key. But even with the best of precautions, your account could become compromised, for instance, via a trojan horse or a brute-force attack on your password. This is intended to be a last resort.

How

The idea is to use cryptographic hashes; you choose a secret string known only to yourself, put it through a one-way hash function, and publish the result somewhere. It is infeasible to determine the secret string corresponding to the hash; hence, an attacker compromising an account presumably would not be able to supply the secret string.

Syntax

{{Committed identity|hash|hash function used|background=CSS color|border=CSS color|article=grammatical article for the hash function}}

Italicized text should be replaced with appropriate input, or its parameter should be removed. Parameters are represented by "parameter=value", and separated by vertical bars |.

  • Replace "hash" with the hash produced from your secret string. This unnamed parameter is equivalent to a parameter named "1" (see parameters).
  • The "hash function used" parameter, if not included, defaults to SHA-512. (This hash function is strongly recommended.)
  • The "background" parameter, if not included, defaults to #E0E8FF (light blue, see Web colors#Hex triplet)
  • The "border" parameter, if not included, also defaults to #E0E8FF.
  • The "article" parameter, if not included, defaults to "a". The other likely value is "an".

For example, if your hash is "1eb00f7cdeaa38f5e9aec8f065b956acf94d416a4a40c1fb5d1dd23b857ba6fe" using SHA-256, and you want a light orange box with a black border, use the following code:

{{Committed identity|1eb00f7cdeaa38f5e9aec8f065b956acf94d416a4a40c1fb5d1dd23b857ba6fe|SHA-256|background=#FC9|border=#000}}

to produce

Committed identity: 1eb00f7cdeaa38f5e9aec8f065b956acf94d416a4a40c1fb5d1dd23b857ba6fe is a SHA-256 commitment to this user's real-life identity.

Obtaining a hash

Use Fastily's browser tool or software on your computer such as sha512sum provided in the GNU Core Utilities.

Choosing a good secret string

  1. Your secret string should end with a long string of random text, such as "fFfwq0DuDmMXj8hYTM3NTKeDhk". This ensures that brute force and dictionary attacks cannot infer your identity from your public hash.
  2. Your secret string should specify enough of your identity that, if the string were revealed, you could unambiguously prove you match that identity. At least two means of contact is a good rule. For instance, your secret string could include a telephone number and email address at which you can be reached. However, it should not contain data that you are not willing to show to Wikipedia's administrative staff.
  3. Try not to choose a secret string that represents your identity that could go completely out of date. For instance, it may be bad to choose a string that specifies only your telephone number as that number might change.
  4. If you want to change your secret string, do so, but keep track of all your old secret strings. It is best to reveal all of them if you ever want to confirm your identity, as this will establish that you are the same person who used your account from the first moment the committed identity was published.
  5. Advanced options:
    • If you have public accounts on other websites with different passwords, list URLs of those accounts. You can later take a specified action to prove that you own those accounts. For example, if you have a YouTube account, an administrator can provide a string which you then insert in a video comment.
    • You may include information such as your driver's license number, national identification number, or passport number. You can then later supply copies of these documents as additional evidence to prove your identity.
    • Another option is to take a photo or video of yourself, take a SHA hash of the resulting file, and include that hash in your secret string. Retain the file. You can then later supply the file to an administrator, and they can video call with you and compare the file with your current appearance. This will remain effective even if the attacker has compromised all your listed means of contact.

Example

full name, multiple forms of contact, contact information for trusted friends, and a random string:

Joe Schmoe. joe@example.com. 555-123-3456. P.O. Box 1234, San Jose, CA. My best friend Bob's email: bob@example.com. fFfwq0DuDmMXj8hYTM3NTKeDhk

which results in a SHA-512 hash of

92938b5423a1793d836333694cf0e55d92b42fb0c14ffcfe8349b51e86bceedcf9631398c31e1afdf114936502ca95577fa9014c26d718e77a235eb889ed56f3

See also

Code Result Transclusions
{{User:Anomie/Userbox committed identity|…}}
Crypto key.svg This user has an SHA-512 committed identity.
See this userbox's invocation.
{{User:Urdna/CIDuserbox}}
Padlock.svg
This user's account is secured with a unique Committed Identity.
Usage
{{Template:User CID}}
Padlock.svg This user account is secured with a unique committed identity.
Usage