KO
|
EN
gitlite — search
Search
#typescript
#ai-agents
#deepseek-harness
#dsh-plugin
#open-source
#ai
#cli
#dsh
#claude-code
#codex
#developer-tools
#react
shc
★ 2,245
Open GitHub ↗
Shell script compiler
Download README (.md)
Explore Similar Repositories
splitpanes
:
A Vue 3 (and 2) reliable, simple and touch-ready panes splitter / resizer.
Giraffe
:
A native functional ASP.NET Core web framework for F# developers.
ImGui.NET
:
An ImGui wrapper for .NET.
Lumina-T2X
:
Lumina-T2X is a unified framework for Text to Any Modality Generation
AndroidControl
:
超强群控，可以实时查看和控制安卓手机的安卓远程控制软件，致力于完成一个高端的安卓群控软件 可以群控，录制运行脚本等等功能......
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
shc
?
Download (.md)
[](https://travis-ci.org/neurobin/shc) [](https://github.com/neurobin/shc/stargazers) [](https://github.com/neurobin/shc/network) [](https://github.com/neurobin/shc/issues) # Shell Script Compiler A generic shell script compiler. Shc takes a script, which is specified on the command line and produces C source code. The generated source code is then compiled and linked to produce a stripped binary executable. The compiled binary will still be dependent on the shell specified in the first line of the shell code (i.e shebang) (i.e. #!/bin/sh), thus shc does not create completely independent binaries. shc itself is not a compiler such as cc, it rather encodes and encrypts a shell script and generates C source code with the added expiration capability. It then uses the system compiler to compile a stripped binary which behaves exactly like the original script. Upon execution, the compiled binary will decrypt and execute the code with the shell -c option. ## Install ```bash ./configure make sudo make install ``` **Note** If `make` fails due to *automake* version, run `./autogen.sh` before running the above commands. ### Ubuntu-specific ``` sudo add-apt-repository ppa:neurobin/ppa sudo apt-get update sudo apt-get install shc ``` If the above installation method seems like too much work, then just download a compiled binary package from [release page](https://github.com/neurobin/shc/releases/latest) and copy the `shc` binary to `/usr/bin` and `shc.1` file to `/usr/share/man/man1`. ## Usage ``` shc [options] shc -f script.sh -o binary shc -U -f script.sh -o binary # Untraceable binary (prevent strace, ptrace etc..) shc -H -f script.sh -o binary # Untraceable binary, does not require root (only bourne shell (sh) scripts with no parameter) ``` ## The hardening flag -H This flag is currently in an experimental state and may not work in all systems. This flag only works for **default** shell. For example, if you compile a **bash** script with `-H` flag then the resultant executable will only work in systems where the default shell is **bash**. You may change the default shell which generally is `/bin/sh` which further is just a link to another shell like bash or dash etc. **Also `-H` does not work with positional parameters (yet)** ## Testing ```bash ./configure make make check ``` ## Known limitations The one (and I hope the only) limitation using shc is the _SC_ARG_MAX system configuration parameter. It limits the maximum length of the arguments to the exec function, limiting the maximum length of the runnable script of shc. !! - CHECK YOUR RESULTS CAREFULLY BEFORE USING - !! ## Links 1. [Man Page](http://neurobin.github.io/shc/man.html) 2. [Web Page](http://neurobin.github.io/shc) # Contributing If you want to make pull requests, please do so against the **master** branch. The default branch is **release** which should contain clean package files ready to be used. If you want to edit the manual, please edit the **man.md** file (available in the master branch) instead and then generate the manual file from it with the command (requires `pandoc` to be installed): ```bash pandoc -s man.md -t man -o shc.1 #also run this command to generate the html manual pandoc -s man.md -t html -o man.html ``` If you change anything related to autotools, please run `./autogen.sh` afterwards.
