SHA-1 hashing concept in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does SHA-1 hashing in Git uniquely identify?

In Git, SHA-1 hashes are used to identify objects. What exactly does a SHA-1 hash uniquely identify?

A The content of a file or commit, ensuring integrity and uniqueness

B The file name and its location in the repository

C The date and time when the commit was made

D The user who made the commit

💡 Hint

Think about what Git uses to detect changes and avoid duplicates.

Git uses SHA-1 hashes to uniquely identify the content of files, commits, trees, and other objects. This ensures that if the content changes, the hash changes, helping Git track changes and maintain integrity.

💻 Command Output

intermediate

Output of SHA-1 hash command on a file

What is the output of the following command if the file example.txt contains the text Hello?

git hash-object example.txt

A da39a3ee5e6b4b0d3255bfef95601890afd80709

B 2aae6c35c94fcfb415dbe95f408b9ce91ee846ed

C aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d

D e69de29bb2d1d6434b8b29ae775ad8c2e48c5391

💡 Hint

Check the SHA-1 hash of the string 'Hello' without newline.

The SHA-1 hash of the string 'Hello' (without newline) is aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d. The command git hash-object outputs this hash for the file content.

❓ Troubleshoot

advanced

Why does Git show different SHA-1 hashes for identical file content?

You have two files with exactly the same content, but git hash-object shows different SHA-1 hashes for each. What could cause this?

A The files are in different folders

B The files have different file names

C Git caches the hash and shows old values

D One file has different line endings (CRLF vs LF)

💡 Hint

Think about invisible characters that affect file content.

Different line endings (Windows CRLF vs Unix LF) change the actual bytes in the file, causing different SHA-1 hashes even if the visible text looks the same.

🔀 Workflow

advanced

Order of Git object creation and SHA-1 hashing

Arrange the steps Git follows when creating a commit object and calculating its SHA-1 hash.

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about how Git builds from directory snapshot to commit storage.

Git first creates a tree object for the directory, then a commit object referencing that tree and parents. It then calculates the SHA-1 hash of the commit content and stores the commit object named by that hash.

✅ Best Practice

expert

Why is SHA-1 considered weak for Git security and what is Git's response?

SHA-1 hashing is known to have vulnerabilities. Why is this a concern for Git, and what approach has Git taken to address it?

A SHA-1 hashes are too long; Git shortened them to 8 characters to save space.

B SHA-1 collisions can allow fake commits; Git is transitioning to SHA-256 hashing for stronger security.

C SHA-1 is slow; Git replaced it with MD5 for faster hashing.

D SHA-1 is proprietary; Git switched to a custom hashing algorithm.

💡 Hint

Consider cryptographic weaknesses and Git's recent updates.

SHA-1 has known collision vulnerabilities that could allow attackers to create fake commits with the same hash. Git is gradually moving to SHA-256, a stronger hash algorithm, to improve security.