4 ms·

I wonder how the checked in the fix to the source control system?

• Freak_NL 9y ago
  Probably: git rm -r . git add EQNEDT32.EXE git commit -m "Fixed CVE-2017-11882" git push (Provided someone automatically updated the code repository to git or some other modern tool in the past 17 years.)
• misterdata 9y ago
  'FCIB', apparently: https://blogs.msdn.microsoft.com/oldnewthing/20171114-00/?p=97396 https://blogs.msdn.microsoft.com/oldnewthing/20171114-00/?p=...
  • Freak_NL 9y ago
    > F-C-I-B or as a sort-of acronym eff-sib […] stands for "foreign checked-in binary" […] The term FCIB didn't originally mean "foreign checked-in binary". According to legend […] "Not another f—ing checked-in binary!"
• emidln 9y ago
  I've done this in the past by checking in both a binary as well as a diff to the previous version. It's sometimes helpful to have both if your SCM doesn't handle binary diffs well.