You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using staticx, you can rename the resulting executable whatever you want, but looking at a process listing or the /tmp directory, you can easily see that it's a staticx program and you can see the original name of the program too.
Say you're making Impacket's Python smbserver example portable, you would do something like the following.
Then once it's on another system, you might want to rename it something other than smbserver. But when the program is run, it extracts to and shows up in a process list as /tmp/staticx-XXXXXX/smbserver. It would be nice if there were an option when running staticx to specify the bundle directory and the program path instead of having them decided for you. A workaround for the program name is to rename it before running staticx, but that is not ideal. There is no workaround for the bundle directory.
I'm proposing new CLI options --bundle-dir and --prog-name to keep the naming similar to the environment variables STATICX_BUNDLE_DIR, and STATICX_PROG_PATH.
The text was updated successfully, but these errors were encountered:
andria-dev
changed the title
Feature: CLI options for bundle directory and program path
Feature: CLI options for bundle directory and program name
Jul 22, 2024
When using
staticx
, you can rename the resulting executable whatever you want, but looking at a process listing or the/tmp
directory, you can easily see that it's astaticx
program and you can see the original name of the program too.Say you're making Impacket's Python smbserver example portable, you would do something like the following.
Then once it's on another system, you might want to rename it something other than
smbserver
. But when the program is run, it extracts to and shows up in a process list as/tmp/staticx-XXXXXX/smbserver
. It would be nice if there were an option when runningstaticx
to specify the bundle directory and the program path instead of having them decided for you. A workaround for the program name is to rename it before runningstaticx
, but that is not ideal. There is no workaround for the bundle directory.I'm proposing new CLI options
--bundle-dir
and--prog-name
to keep the naming similar to the environment variablesSTATICX_BUNDLE_DIR
, andSTATICX_PROG_PATH
.The text was updated successfully, but these errors were encountered: