SHA-256
A one-way cryptographic hash function that generates a fixed-length 256-bit digest from arbitrary input. Often combined with salting techniques in cryptographic commitment schemes, it is widely used in blockchain, zero-knowledge proofs, and secure multi-party computation.
Core Facts
SHA-256 is a one-way hash function that generates a fixed-length 256-bit digest for any input and is computationally irreversible; salting refers to appending a random string to the original content before hashing to prevent rainbow table reverse lookups.
SHA-256 is a cryptographic hash function in the SHA-2 family with an output length of 256 bits, possessing collision resistance and preimage resistance.
In Git, each object has a SHA-1 hash computed for it, and starting from Git 2.29, the more secure SHA-256 is supported.
Timeline (last 90 days)
If P=NP, RSA public-key encryption, SHA-256, HMAC, pseudorandom number generators, and even blockchain security would all be broken by polynomial-time algorithms.
File fingerprints (such as SHA-256 checksums) are used to uniquely identify file contents; as long as the file contents change in any way, the fingerprint will differ.
When downloading files from GitHub Releases, users should make sure to get the installer package for the corresponding operating system and architecture, and can verify file integrity using the SHA-256 checksum.
Trust policies typically use a hash of the SPKI (such as SHA-256) as a fixed identifier for the public key, a technique known as "public key pinning".
A robust idempotency architecture should compute a SHA-256 hash of the normalized request body and store it together with the idempotency key, and return 422 Unprocessable Entity when a new request's hash does not match.
Hash comparison cannot detect files deleted during execution unless the key set is explicitly checked.
SHA-256 has an avalanche effect, where any tiny change in the input causes a significantly different output hash value.
The final cache key that passed contains three things—modelId, templateHash, and diffHash—joined with \u0000 and then SHA-256 hashed.
Hashing the raw request dictionary directly with SHA-256 causes a miss on every replay, for reasons including differing dictionary insertion order, trailing-whitespace drift in message content, and differences in implicit defaults such as temperature.
A content checksum is a fixed-length digest computed over data content (such as MD5 or SHA-256), and any tiny change in the content makes the checksum significantly different.
40 more timeline events
All Facts (20)
SHA-256 is a one-way hash function that generates a fixed-length 256-bit digest for any input and is computationally irreversible; salting refers to appending a random string to the original content before hashing to prevent rainbow table reverse lookups.
65%VerifiedSHA-256 is a cryptographic hash function in the SHA-2 family with an output length of 256 bits, possessing collision resistance and preimage resistance.
65%VerifiedIn Git, each object has a SHA-1 hash computed for it, and starting from Git 2.29, the more secure SHA-256 is supported.
65%VerifiedSince version 2.29 (October 2020), Git supports the SHA-256 object format, created via git init --object-format=sha256, extending the hash length from 160 bits to 256 bits.
65%UnverifiedSHA-256算法生成256位的哈希值，碰撞概率极低，可视为文件的唯一身份证
95%UnverifiedThe core idea of content-addressable storage (CAS) is that a data item's address is determined by its content itself (typically a SHA-256 hash), and Git's object storage model is a classic implementation of CAS
60%UnverifiedThe Git community is gradually migrating to the SHA-256 algorithm, with experimental support for SHA-256 beginning in Git 2.29+.
60%UnverifiedIf P=NP, RSA public-key encryption, SHA-256, HMAC, pseudorandom number generators, and even blockchain security would all be broken by polynomial-time algorithms.
50%UnverifiedFile fingerprints (such as SHA-256 checksums) are used to uniquely identify file contents; as long as the file contents change in any way, the fingerprint will differ.
50%UnverifiedWhen downloading files from GitHub Releases, users should make sure to get the installer package for the corresponding operating system and architecture, and can verify file integrity using the SHA-256 checksum.
50%UnverifiedTrust policies typically use a hash of the SPKI (such as SHA-256) as a fixed identifier for the public key, a technique known as "public key pinning".
50%UnverifiedA robust idempotency architecture should compute a SHA-256 hash of the normalized request body and store it together with the idempotency key, and return 422 Unprocessable Entity when a new request's hash does not match.
50%UnverifiedSHA-256 has an avalanche effect, where any tiny change in the input causes a significantly different output hash value.
50%UnverifiedHash comparison cannot detect files deleted during execution unless the key set is explicitly checked.
50%UnverifiedThe final cache key that passed contains three things—modelId, templateHash, and diffHash—joined with \u0000 and then SHA-256 hashed.
50%UnverifiedHashing the raw request dictionary directly with SHA-256 causes a miss on every replay, for reasons including differing dictionary insertion order, trailing-whitespace drift in message content, and differences in implicit defaults such as temperature.
50%UnverifiedA content checksum is a fixed-length digest computed over data content (such as MD5 or SHA-256), and any tiny change in the content makes the checksum significantly different.
50%UnverifiedHRR uses SHA-256 hashing to deterministically generate text atoms and supports algebraic operations such as bind, unbind, and bundle, but hash-generated vectors cannot reflect semantic similarity.
50%UnverifiedOnce an article is approved, the site stores the SHA-256 hash of the approved text and the hash of the evidence, and the article can be indexed only when both hashes still match.
50%UnverifiedSHA-256 produces a fixed 256-bit (64 hexadecimal character) digest for input of any length, with collision resistance and the avalanche effect.
50%