The commit that fixes this issue: https://github.com/gitster/git/commit/684dd4c2b414bcf648505e... (Surprise, the root cause is a cache )
Another cachelty
He who would pun would pick a pocket.
Git: Malicious repositories can execute remote code while cloning
61–70 of 228 posts
Re: Git: Malicious repositories can execute remote code while cloning
#62Re: Git: Malicious repositories can execute remote code while cloning
#63Earlier quoted context omitted.
I thought the two hardest problems were: 1) naming 2) cache invalidation ... 3) off-by-one errors
I feel like we should have solved the naming problem as an industry by now. Alas.
It’s actually the hardest one of the three, being outside the grasp of formal methods.
Re: Git: Malicious repositories can execute remote code while cloning
#64Earlier quoted context omitted.
The two hardest problems in programming: (1) cache invalidation (3) off-by-one errors (2) appropriately naming things (4) parallel execution [leading to race conditions / ordering bugs]
I think you win a bad in-joke award - the first annual Turing-Dad joke award.
Minor quibble, it should be the three hardest problems.
Re: Git: Malicious repositories can execute remote code while cloning
#65The commit that fixes this issue: https://github.com/gitster/git/commit/684dd4c2b414bcf648505e... (Surprise, the root cause is a cache )
Another cachelty
well played. I think that just got added to my standard vocabulary. Caching has caused more errors and bugs that I've had to deal with than I can recall. My favorite was an off by one error where we returned nicely cached info -- just for the previous user who came through our system! :facepalm: That was a bad one.
Re: Git: Malicious repositories can execute remote code while cloning
#66> This vulnerability affects platforms with case-insensitive filesystems with support for symbolic links, when certain clean/smudge filters are configured globally (e.g. Git LFS). Can we get the title changed to "on macOS and Windows?" I was worried for a second, but this is meaningless.
[deleted]
Re: Git: Malicious repositories can execute remote code while cloning
#67Earlier quoted context omitted.
Another cachelty
well played. I think that just got added to my standard vocabulary. Caching has caused more errors and bugs that I've had to deal with than I can recall. My favorite was an off by one error where we returned nicely cached info -- just for the previous user who came through our system! :facepalm: That was a bad one.
Yeah but the speed.
Re: Git: Malicious repositories can execute remote code while cloning
#68Re: Git: Malicious repositories can execute remote code while cloning
#69Earlier quoted context omitted.
Difficult problems in programming: (1) cache invalidation (2) off-by-one errors
I thought the two hardest problems were: 1) naming 2) cache invalidation ... 3) off-by-one errors
I'm pretty sure it's:
1) naming
4) concurr2) cache invalidationency
...
3) off-by-one errors
Re: Git: Malicious repositories can execute remote code while cloning
#70Earlier quoted context omitted.
Another cachelty
well played. I think that just got added to my standard vocabulary. Caching has caused more errors and bugs that I've had to deal with than I can recall. My favorite was an off by one error where we returned nicely cached info -- just for the previous user who came through our system! :facepalm: That was a bad one.
Here goes the obligatory
> There are only two hard things in Computer Science...