Comment

Comment on Deleted GitHub data is forever accessible to anyone, researchers claim | Cybernews

Dave@lemmy.nz ⁨1⁩ ⁨month⁩ ago

The article is really not clear. Is it saying if a project is forked, then the original is made private, the fork can access data from the private fork?

potentially enabling malicious actors to access sensitive information such as API keys and secrets even after users think they’ve deleted it.

Is this saying people misunderstand git and think committing a deletion makes people unable to access the previous version? Or is it saying the sharing between public and private repos can expose keys in private repos?

If you accidentally commit an API key into a public repository… you need to roll that key. Even if it was deleted completely, someone still could have accessed it while it was there.

source

Sort:hotnew top

eager_eagle@lemmy.world ⁨1⁩ ⁨month⁩ ago
from their actual report

As long as one fork exists, any commit to that repository network (ie: commits on the “upstream” repo or “downstream” forks) will exist forever.

This further cements our view that the only way to securely remediate a leaked key on a public GitHub repository is through key rotation. We’ve spent a lot of time documenting how to rotate keys for the most popularly leaked secret types - check our work out here: howtorotate.com.
source
- Dave@lemmy.nz ⁨1⁩ ⁨month⁩ ago
  I’m still not sure that answers it. If I fork a project, and the upstream project commits an API key (after I’ve forked it), then they delete the commit, does this commit stay available to me (unexpected behaviour)? Or is it only if I sync that commit into my repo while it’s in the upstream repo (expected behaviour)?
  
  Or is it talking about this from a comment here:
  
  Word of caution 2: The commit can still be accessible directly via SHA1. Force push does not delete the commit, it creates a new one and moves the file pointer to it. To truly delete a commit you must delete the whole repo.
  
  Someone replies and said by having garbage collection kick in it removes this unconnected commit, but it’s not clear to me whether this works for github or just the local git repo.
  
  Perhaps the issue is that these commits are synced into upstream/downstream repos when synced when they should not be?
  
  Like I said, I’m really confused about the specifics of this.
  
  source
  - Morphit@feddit.uk ⁨1⁩ ⁨month⁩ ago
    I think Github keeps all the commits of forks in a single pool. So if someone commits a secret to one fork, that commit could be looked up in any of them, even if the one that was committed to was private/is deleted/no references exist to the commit.
    
    The big issue is discovery. If no-one has pulled the leaky commit onto a fork, then the only way to access it is to guess the commit hash. Github makes this easier for you:
    
    What’s more, Ayrey explained, you don’t even need the full identifying hash to access the commit. “If you know the first four characters of the identifier, GitHub will almost auto-complete the rest of the identifier for you,” he said, noting that with just sixty-five thousand possible combinations for those characters, that’s a small enough number to test all the possibilities.
    
    I think all GitHub should do is prune orphaned commits from the auto-suggestion list. If someone grabbed the complete commit ID then they probably grabbed the content already anyway.
    
    source
    Dave@lemmy.nz ⁨1⁩ ⁨month⁩ ago
    Thanks, I think that explains it a bit more. It is unexpected to me, as a non-git expert, and I’m sure many others.
    
    source
    -> View More Comments
  - grrgyle@slrpnk.net ⁨1⁩ ⁨month⁩ ago
    In my experience with GitHub, dropped commits remain indefinitely accessible. I use this to my advantage on pull requests with lots of good commit context that I don’t want totally lost in a squash: by copying result of git log --oneline main… into the PR body. The SHAs remain accessible even after I force push my branch down to a single commit.
    
    I think there is a theoretical limit to how long these commits remain accessible, but I haven’t ever hit it in my daily usage.
    
    source
    Dave@lemmy.nz ⁨1⁩ ⁨month⁩ ago
    Ah thanks, this explains it a bit more.
    
    source