From: mop2 on
On 2010-01-01, Murray R. Van Luyn. <valid(a)email.address> wrote:
> I'll see what my ISP has to say about the apparent, predominately
> un-locatable zip executable. They're not known for their fabulous customer
> service, so I fear this may be where the current avenue of exploration ends.
>

Perhaps be more dynamic, as first try, speak with the servers.
If you can upload your zip script, possibly you can upload others.
For example:

#!/bin/sh
{
echo ----------- find zip
which zip ||
whereis zip ||
find /usr -name zip
echo -----------
} >>./Secure/touchzipfilepayloads.log 2>&1


The server will answer in the log file and, if zip is found,
you can try supply the absolute path to it in your zip script.
This can additionally reduce the reply time when running the script.

Of course, even if it was not found, the zip command can be available in an
absolutely non predictable place.

From: mop2 on
On Sun, 03 Jan 2010 12:48:17 -0200, houghi <houghi(a)houghi.org.invalid> wrote:
> mop2 wrote:
>> Of course, even if it was not found, the zip command can be available in an
>> absolutely non predictable place.
>
> And if it is not, perhaps you can upload the binary from an other
> machine and use that. Just see that you place it in a directory where
> you are able to execurte it. If that is not available, perhaps `/bin/sh
> /fir/to/zip <whatever>` works.


Exactly, and its dependency is very simple:

$ which zip
/usr/bin/zip

$ ldd /usr/bin/zip
linux-gate.so.1 => (0xb7713000)
libbz2.so.1 => /lib/libbz2.so.1 (0xb76f2000)
libc.so.6 => /lib/libc.so.6 (0xb7592000)
/lib/ld-linux.so.2 (0xb7714000)

Well, in principle, the same dir of the script seems good, since
libraries are in the correct place,then zip in the script will be just
../zip
or
${0%/*}/zip

I don't know if the ISP's server isn't a linux machine (a *bsd, for example)
this simple approach is applicable.