Credential storage options in Git - Time & Space Complexity

Time Complexity: Credential storage options

O(n)

Understanding Time Complexity

We want to understand how the time to access stored credentials changes as the number of credentials grows in git.

How does git handle looking up credentials when you have many stored?

Scenario Under Consideration

Analyze the time complexity of this git credential helper usage.

# Store credentials
$ git config --global credential.helper store

# When pushing, git reads credentials from the file
$ git push origin main
# Git reads ~/.git-credentials file line by line to find matching URL
    

This snippet shows git using the 'store' helper which saves credentials in a plain text file and reads it on demand.

Identify Repeating Operations

Look for repeated steps git does when accessing credentials.

• Primary operation: Reading the credentials file line by line to find a matching URL.
• How many times: Once per git command needing credentials, scanning up to all stored entries.

How Execution Grows With Input

As the number of stored credentials grows, git reads more lines to find the right one.

Input Size (n)	Approx. Operations
10	Reads about 10 lines
100	Reads about 100 lines
1000	Reads about 1000 lines

Pattern observation: The time to find credentials grows roughly in direct proportion to the number of stored entries.

Final Time Complexity

Time Complexity: O(n)

This means the time to find credentials grows linearly with how many credentials are stored.

Common Mistake

[X] Wrong: "Git finds credentials instantly no matter how many are stored."

[OK] Correct: Git reads the file line by line, so more entries mean more reading time.

Interview Connect

Understanding how credential lookup scales helps you reason about performance in real tools and shows you can think about efficiency in everyday tasks.

Self-Check

What if git used a database or key-value store instead of a plain file? How would the time complexity change?

Practice

1. Which Git credential helper stores your password temporarily in memory for a limited time?

easy

A. store

B. manager-core

C. osxkeychain

D. cache

Solution

1. Step 1: Understand credential helper types

   Git offers different helpers: cache stores credentials temporarily in memory, store saves them permanently in plain text, and platform helpers like osxkeychain or manager-core store securely.

2. Step 2: Identify temporary storage helper

   The cache helper keeps credentials in memory for a short time (default 15 minutes), so you don't have to retype passwords repeatedly during that period.

3. Final Answer:

   cache -> Option D

4. Quick Check:

   Temporary credential storage = cache [OK]

Hint: Cache means temporary memory storage for credentials [OK]

Common Mistakes:

• Confusing 'store' as temporary storage
• Thinking 'osxkeychain' is temporary
• Assuming 'manager-core' caches credentials

2. Which command correctly sets Git to use the credential helper that saves passwords permanently in plain text?

easy

A. git config --global credential.helper store

B. git config --global credential.helper cache

C. git config --global credential.helper osxkeychain

D. git config --global credential.helper manager-core

Solution

1. Step 1: Recall command syntax for setting credential helper

   The command to set a credential helper globally is git config --global credential.helper <helper-name>.

2. Step 2: Identify helper for permanent plain text storage

   The store helper saves credentials permanently in plain text on disk, so the correct command is git config --global credential.helper store.

3. Final Answer:

   git config --global credential.helper store -> Option A

4. Quick Check:

   Permanent plain text storage uses 'store' helper [OK]

Hint: Use 'store' helper for permanent plain text saving [OK]

Common Mistakes:

• Using 'cache' instead of 'store' for permanent saving
• Confusing platform helpers with plain text storage
• Missing the --global flag

3. What will be the output of the command git config --get credential.helper after running git config --global credential.helper cache?

medium

A. store

B. cache

C. osxkeychain

D. manager-core

Solution

1. Step 1: Understand the effect of setting credential helper globally

   Running git config --global credential.helper cache sets the credential helper to cache in the global Git config.

2. Step 2: Check what git config --get credential.helper returns

   This command reads the current credential helper setting, which will be cache after the previous command.

3. Final Answer:

   cache -> Option B

4. Quick Check:

   Get helper after setting cache = cache [OK]

Hint: Get command shows current helper exactly as set [OK]

Common Mistakes:

• Expecting output to be 'store' or platform helper
• Confusing local and global config scopes
• Assuming no output if helper is set

4. You set your Git credential helper with git config --global credential.helper store, but your password is still asked every time. What is the most likely cause?

medium

A. The credential helper cache is overriding store

B. The platform helper must be used instead of store

C. The stored credentials file is missing or unreadable

D. You need to restart Git after setting the helper

Solution

1. Step 1: Understand how 'store' helper works

   The 'store' helper saves credentials in a plain text file (usually ~/.git-credentials). If this file is missing or unreadable, Git cannot use stored credentials.

2. Step 2: Identify why password prompts continue

   If the credentials file is missing or has wrong permissions, Git will ask for the password every time despite the helper setting.

3. Final Answer:

   The stored credentials file is missing or unreadable -> Option C

4. Quick Check:

   Missing credentials file causes repeated password prompts [OK]

Hint: Check if credentials file exists and is readable [OK]

Common Mistakes:

• Thinking cache overrides store automatically
• Believing Git needs restart after config change
• Assuming platform helpers are mandatory

5. You want to securely store Git credentials on Windows without typing your password every time. Which credential helper should you configure?

hard

A. manager-core

B. store

C. cache

D. osxkeychain

Solution

1. Step 1: Identify platform-specific secure helpers

   On Windows, the recommended secure credential helper is manager-core, which integrates with Windows Credential Manager.

2. Step 2: Compare with other helpers

   cache is temporary, store saves plain text, and osxkeychain is for macOS, so they are not suitable for Windows secure storage.

3. Final Answer:

   manager-core -> Option A

4. Quick Check:

   Windows secure storage uses 'manager-core' helper [OK]

Hint: Use 'manager-core' for secure Windows credential storage [OK]

Common Mistakes:

• Choosing 'store' which is insecure
• Using 'osxkeychain' on Windows
• Expecting 'cache' to be secure and permanent