SHA-1
E437745
SHA-1 is a now-legacy 160-bit cryptographic hash function once widely used for data integrity and digital signatures but today considered insecure due to practical collision attacks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| SHA-1 canonical | 4 |
How this entity was disambiguated
This entity first appeared as the object of triple T4381641 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SHA-1 Context triple: [Merkle–Damgård construction, usedIn, SHA-1]
-
A.
SHA-0
SHA-0 is an early, now-obsolete cryptographic hash function in the Secure Hash Algorithm family, known for its structural weaknesses and subsequent replacement by SHA-1.
-
B.
SHA-256
SHA-256 is a widely used cryptographic hash function from the SHA-2 family that produces a 256-bit hash value for securing data integrity and authentication.
-
C.
SHA-2
SHA-2 is a family of cryptographic hash functions widely used for data integrity, digital signatures, and security protocols on the internet.
-
D.
MD5
MD5 is a widely known but now cryptographically broken 128-bit hash function formerly used for checksums, data integrity, and security applications.
-
E.
RIPEMD-160
RIPEMD-160 is a 160-bit cryptographic hash function designed as an alternative to SHA-1, commonly used for data integrity and security applications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SHA-1 Target entity description: SHA-1 is a now-legacy 160-bit cryptographic hash function once widely used for data integrity and digital signatures but today considered insecure due to practical collision attacks.
-
A.
SHA-0
SHA-0 is an early, now-obsolete cryptographic hash function in the Secure Hash Algorithm family, known for its structural weaknesses and subsequent replacement by SHA-1.
-
B.
SHA-256
SHA-256 is a widely used cryptographic hash function from the SHA-2 family that produces a 256-bit hash value for securing data integrity and authentication.
-
C.
SHA-2
SHA-2 is a family of cryptographic hash functions widely used for data integrity, digital signatures, and security protocols on the internet.
-
D.
MD5
MD5 is a widely known but now cryptographically broken 128-bit hash function formerly used for checksums, data integrity, and security applications.
-
E.
RIPEMD-160
RIPEMD-160 is a 160-bit cryptographic hash function designed as an alternative to SHA-1, commonly used for data integrity and security applications.
- F. None of above. chosen
Statements (59)
| Predicate | Object |
|---|---|
| instanceOf |
cryptographic hash function
ⓘ
hash function ⓘ message digest algorithm ⓘ |
| abbreviationOf | Secure Hash Algorithm 1 NERFINISHED ⓘ |
| bitLength | 160 bits ⓘ |
| blockSize | 512 bits ⓘ |
| browserSupportForTLSCertificates | removed by major browsers by 2017 ⓘ |
| category | legacy cryptographic algorithm ⓘ |
| chosenPrefixCollisionProjectName | SHA-1 is a Shambles ⓘ |
| chosenPrefixCollisionYear | 2020 ⓘ |
| collisionComplexityBestKnown | significantly less than 2^80 operations ⓘ |
| collisionComplexityTheoretical | 2^80 operations ⓘ |
| collisionResistance | broken in practice ⓘ |
| deprecatedBy |
CA/Browser Forum
NERFINISHED
ⓘ
NIST NERFINISHED ⓘ |
| designedBy | National Security Agency NERFINISHED ⓘ |
| digestSize | 20 bytes ⓘ |
| firstPublicCollisionDemonstratedBy |
CWI Amsterdam
NERFINISHED
ⓘ
Google NERFINISHED ⓘ |
| firstPublicCollisionProjectName | SHAttered NERFINISHED ⓘ |
| firstPublicCollisionYear | 2017 ⓘ |
| introducedInYear | 1995 ⓘ |
| notation | Secure Hash Algorithm 1 NERFINISHED ⓘ |
| outputSize | 160 bits ⓘ |
| partOfStandard |
FIPS 180-1
NERFINISHED
ⓘ
FIPS 180-2 NERFINISHED ⓘ FIPS 180-3 NERFINISHED ⓘ FIPS 180-4 NERFINISHED ⓘ |
| predecessor | SHA-0 NERFINISHED ⓘ |
| preimageResistance | not practically broken as of late 2010s ⓘ |
| recommendedReplacement |
SHA-2 family
NERFINISHED
ⓘ
SHA-256 ⓘ SHA-3 family ⓘ |
| rounds | 80 ⓘ |
| secondPreimageResistance | not practically broken as of late 2010s ⓘ |
| securityStatus | insecure against collision attacks ⓘ |
| standardizedBy | NIST NERFINISHED ⓘ |
| status | deprecated ⓘ |
| successor |
SHA-224
NERFINISHED
ⓘ
SHA-256 NERFINISHED ⓘ SHA-3 NERFINISHED ⓘ SHA-384 NERFINISHED ⓘ SHA-512 NERFINISHED ⓘ |
| usedFor |
TLS certificates
ⓘ
data integrity ⓘ digital signatures ⓘ file checksums ⓘ version control systems ⓘ |
| usedIn |
Git
NERFINISHED
ⓘ
Mercurial NERFINISHED ⓘ PGP implementations ⓘ Subversion (optional components) ⓘ X.509 certificates NERFINISHED ⓘ |
| usesConstruction | Merkle–Damgård construction NERFINISHED ⓘ |
| usesOperation |
bitwise operations
ⓘ
logical functions ⓘ modular addition ⓘ |
| vulnerabilityType |
chosen-prefix collision attacks
ⓘ
collision attacks ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: SHA-1 Description of subject: SHA-1 is a now-legacy 160-bit cryptographic hash function once widely used for data integrity and digital signatures but today considered insecure due to practical collision attacks.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.