2022-07-10 21:13:45 +00:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
if [ "$UID" = "0" ]; then
|
|
|
|
|
SUDO=
|
|
|
|
|
else
|
|
|
|
|
SUDO=sudo
|
|
|
|
|
fi
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
|
echo
|
Introduce new `jartsr='` ape prefix
Files beginning with "MZqFpD" are Actually Portable Executables,
which have a printf statement in the first 4096 bytes with octal
codes that specify the ELF header. APE also specifies `jartsr='`
as an alternative prefix, intended for binaries that do not want
to be identified as Windows executables. Like the \177ELF magic,
all these prefixes decode as x86 jump instructions that could be
used for 16-bit bootloaders or 32-bit / 64-bit flat executables.
Most importantly they provide a fallback path for Thompson shell
copmatible command interpreters, which do not require a shebang,
e.g. bash, zsh, fish, bourne, almquist, etc. Please note that in
order to meet the requirements of POSIX.1, the single quote must
be followed by a newline character, before any null bytes occur.
See also: https://www.austingroupbugs.net/view.php?id=1250
2022-11-11 04:58:48 +00:00
|
|
|
echo "APE Uninstaller intends to run (in pseudo-shell)"
|
2022-07-10 21:13:45 +00:00
|
|
|
echo
|
Introduce new `jartsr='` ape prefix
Files beginning with "MZqFpD" are Actually Portable Executables,
which have a printf statement in the first 4096 bytes with octal
codes that specify the ELF header. APE also specifies `jartsr='`
as an alternative prefix, intended for binaries that do not want
to be identified as Windows executables. Like the \177ELF magic,
all these prefixes decode as x86 jump instructions that could be
used for 16-bit bootloaders or 32-bit / 64-bit flat executables.
Most importantly they provide a fallback path for Thompson shell
copmatible command interpreters, which do not require a shebang,
e.g. bash, zsh, fish, bourne, almquist, etc. Please note that in
order to meet the requirements of POSIX.1, the single quote must
be followed by a newline character, before any null bytes occur.
See also: https://www.austingroupbugs.net/view.php?id=1250
2022-11-11 04:58:48 +00:00
|
|
|
echo " sudo echo -1 into /proc/sys/fs/binfmt_misc/APE*"
|
|
|
|
|
echo " sudo rm -f /usr/bin/ape ~/.ape o/tmp/.ape /tmp/.ape"
|
2022-07-10 21:13:45 +00:00
|
|
|
echo
|
|
|
|
|
echo "You may then use ape/apeinstall.sh to reinstall it"
|
|
|
|
|
echo
|
|
|
|
|
} >&2
|
|
|
|
|
|
|
|
|
|
set -ex
|
Introduce new `jartsr='` ape prefix
Files beginning with "MZqFpD" are Actually Portable Executables,
which have a printf statement in the first 4096 bytes with octal
codes that specify the ELF header. APE also specifies `jartsr='`
as an alternative prefix, intended for binaries that do not want
to be identified as Windows executables. Like the \177ELF magic,
all these prefixes decode as x86 jump instructions that could be
used for 16-bit bootloaders or 32-bit / 64-bit flat executables.
Most importantly they provide a fallback path for Thompson shell
copmatible command interpreters, which do not require a shebang,
e.g. bash, zsh, fish, bourne, almquist, etc. Please note that in
order to meet the requirements of POSIX.1, the single quote must
be followed by a newline character, before any null bytes occur.
See also: https://www.austingroupbugs.net/view.php?id=1250
2022-11-11 04:58:48 +00:00
|
|
|
for f in /proc/sys/fs/binfmt_misc/APE*; do
|
|
|
|
|
if [ -f $f ]; then
|
|
|
|
|
$SUDO sh -c "echo -1 >$f" || exit
|
|
|
|
|
fi
|
|
|
|
|
done
|
2022-08-08 05:10:18 +00:00
|
|
|
$SUDO rm -f /usr/bin/ape ~/.ape o/tmp/.ape o/tmp/ape /tmp/.ape /tmp/ape || exit
|
