3 ms·
> But [a bunch of random files] is EXACTLY WHAT GIT IS! Well, yeah, but only in the same limp way that "a bunch of random bytes" describes both (A) some text f
by Terr_ 3y ago
> But [a bunch of random files] is EXACTLY WHAT GIT IS!
Well, yeah, but only in the same limp way that "a bunch of random bytes" describes both (A) some text file versus (B) an e-mail with valid DKIM headers with a PGP signature.
It's possible that both could arrive containing your CEO's name and an urgent demand to wire all company funds to some random city in Myanmar... but one approach is fundamentally more secure.
> the only difference is that you also get the previous versions too.
No, that's not the only difference nor the most-important.
The important difference is that the files represented by a particular git-revision all exist with cryptographically-hashed relationships on their content, and that structure prevents/deters multiple kinds of secret meddling or impersonation.
- badsectoracula 3y ago> The important difference is that the files represented by a particular git-revision all exist with cryptographically-hashed relationships on their content, and that structure prevents/deters multiple kinds of secret meddling or impersonation. ...which a developer with proper write access to the repository (i.e. the same developer that'd make the tarballs) wont need to do since they can decide what goes in there in the first place, thus making this "important difference" not at all important when it comes to the case i argue in this entire thread.