| commit | 060801d8c8613692469c8d1ccfc2598fb8a2992a | |
| author | rofl0r <rofl0r@users.noreply.github.com> | |
| Thu, 21 Jul 2022 23:00:15 +0000 (21 23:00 +0000) | ||
| committer | rofl0r <rofl0r@users.noreply.github.com> | |
| Thu, 21 Jul 2022 23:04:03 +0000 (21 23:04 +0000) | ||
| tree | 8836ff3aeccf786308530d740eda63d8fa8e7500 | treesnapshot (tar.gz zip) |
| parent | 09142579c5711c57e7f80986f22b388185cb0585 | commitdiff |
fat-binary-m1: use arm64e for dylib, but not for executable
according to research done by @malash, the proxychains4 binary
itself isn't allowed to use system-internal arm64e mode; but
it's possible to add it as a 3rd architecture to the shared
library (.dylib), and then even inject it into system binaries
like /usr/bin/curl, which didn't work since the introduction
of SIP.
therefore, we now create the dylib with all 3 archs, but the
launcher only with arm64 and x86_64.
closes #453
according to research done by @malash, the proxychains4 binary
itself isn't allowed to use system-internal arm64e mode; but
it's possible to add it as a 3rd architecture to the shared
library (.dylib), and then even inject it into system binaries
like /usr/bin/curl, which didn't work since the introduction
of SIP.
therefore, we now create the dylib with all 3 archs, but the
launcher only with arm64 and x86_64.
closes #453
| Makefile | diffblobblamehistory | |
| configure | diffblobblamehistory |