1
0
mirror of https://github.com/rofl0r/proxychains-ng synced 2025-03-15 08:27:17 +08:00
Clone
0
quality of haad's fork, or "reasons for the split"
rofl0r edited this page 2019-04-16 13:51:32 +01:00

SOME WORDS ABOUT THE RIVALING FORK ON GITHUB

note that there is another, technically inferior fork of proxychains on github, and its maintainer (haad) unfortunately doesnt seem to have a clue.

his way to deal with problems is to try a lot of different things until it appears to work, and then commits everything he changed, not the one fix that actually made it work. this applies for example to the things he did in order to make proxychains compile on MacOS X. due to this you cannot compile his fork on MacOS X on powerpc, because he added x86-specific CFLAGS: 2250ef66a8

he also adds non-portable headers such as sys/cdefs.h without any actual reason, and then blatantly claims that this is POSIX compliant, however the POSIX spec doesnt say a single word about that header. it is a completely non-standard glibc specific header. 361889a2d2 (L2R18)

thus, his commit history is full of bugs, commits that dont even compile or checked in binaries.

his fork is a couple of months older than mine.

he basically forked proxychains 3.1 and applied 3 or 4 patches floating around on the sf.net forums. that's about anything that he has achieved. when i came, i forked his instead of starting from scratch, and in the beginning i collaborated with him (any changes that add actual value are written by me) and opened pull requests for my work. i quickly became annoyed by his clueless and careless commits, and decided to continue on my own.

meanwhile, his fork has gotten totally irrelevant and unmaintained, apart from the occassional automatic pull request. (i have the impression he doesn't even review them and just clicks on merge whenever a new PR pops up)

here's haad's history of fail:

1c020ced1e 361889a2d2 462e34f447 c1f0c68abd adb13c7e79 f512779539 (L2R481) 865dc76c08 5b7270d75b efa5738a6a 14e15aa2c1