Radare2 Patch Ritual

vim . # press p over the file name to preview the patch In another terminal in the root of r2: sys/derizin.sh < rizin/0032* > p;git am --abort; git am -3 p If the above command fails do it manually: patch -p1 < p And create the fake commit like this: AUTHOR="`grep p ^From:|cut -d : -f 2-`" git commit --author "$AUTHOR" -a Be careful with new files, you will need to add them with git add missing-file.c PD: Open the 'p' file in a split in vim to copypaste the commit message from the subject of the formatted patch. EOF exit 0 fi sed \ -e 's,_ANALYSIS_,ANAL_,g' \ -e 's,RANal,RAnal,g' \ -e 's,RZ,R_,g' \ -e 's,rz,r_,g' \ -e 's,\([a-z]+\),\1 (,g' \ -e 's,free,(,g' \ -e 's,)),(g' \ -e 's,each,(each (,g' \ -e 's,rz-test,r2r,g' \ -e 's,tools/r/bin/tools/rabin2,g' \ -e 's,analysis,anal,g' \ -e 's,librz,libr,g' \ -e 's,binrz,libr,g' \ -e 's,rizin,radare2,g' \ -e 's,Rz,R,g'

A terminal screenshot shows a long radare2 development shell script for applying a patch, creating a fake commit, and mass-rewriting names with sed. The joke is the absurdly elaborate and fragile workflow hidden behind the uploader’s dry “Interesting” caption, aimed at reverse-engineering and open-source tool developers. It works as a reaction to overcomplicated command-line procedures or cursed developer documentation.

• @infosecmemes / 778 2022-11-16