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
Would there be any opposition to me filing a pull request for an extra option to filter some of the data included in the --info field that is included in the final output (ie: my_installer.run)? One thing I'd like to remove is the fields showing the full command used to generate the installer, which includes the full path to the source locations (ie: my home folder). I'd like to strip those out of "production" installers. In my case, I'd like to prevent the following from appearing in a production installer:
echo Built with Makeself version 2.3.0 on
echo Build command was: "./makeself.sh \\
\"/home/ford_prefect/installer\" \\
\"/home/ford_prefect/installer.run\" \\
\"42\" \\
\"./42.sh\""
The text was updated successfully, but these errors were encountered:
Was something like this ever merged? Recent updates include sensitive data in the --info command such as GPG and SSL passphrases. It seems as if it would be appropriate to omit the "Build command was:" line in makeself-header.sh until a sanitized version can be displayed.
I don't remember seeing a pull request for this and it's quite possible it was closed without it being proposed. However I'd be OK with having a command-line option to makeself to prevent the build command from being stored in the archive.
Would there be any opposition to me filing a pull request for an extra option to filter some of the data included in the
--info
field that is included in the final output (ie:my_installer.run
)? One thing I'd like to remove is the fields showing the full command used to generate the installer, which includes the full path to the source locations (ie: my home folder). I'd like to strip those out of "production" installers. In my case, I'd like to prevent the following from appearing in a production installer:The text was updated successfully, but these errors were encountered: