Trojan Setup
v1.0.0自动安装和配置 Trojan 代理客户端，支持 proxychains4 全局代理，修复 Chrome 官方源。适用于 Linux 系统的翻墙环境搭建。
⭐ 0· 80·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (install/configure Trojan client, proxychains, fix Chrome source) match the included README, SKILL.md, and install.sh. The script downloads Trojan from GitHub releases and installs proxychains4 and Chrome repo updates — all consistent with the stated purpose.
Instruction Scope
SKILL.md instructs running the included install.sh and editing /usr/src/trojan/config.json; the script and docs only reference expected paths and tools (apt, wget, gpg, /etc/proxychains4.conf, /etc/apt). It requires sudo and modifies system files, which is within scope for an installer but worth noting.
Install Mechanism
No platform install spec; this is an instruction-only skill with a bundled install.sh. The script downloads the Trojan release from GitHub (official releases URL) and the Google signing key from dl.google.com — both well-known hosts. The script extracts and writes binaries to /usr/src and updates system config; this is expected for an installer.
Credentials
The skill does not request environment variables or secrets. It asks the user to manually populate Trojan server credentials in the config file (local input), which is proportionate to its function.
Persistence & Privilege
The installer runs as root and modifies system-wide files (apt sources, proxychains config, keyrings, /usr/src). It also instructs enabling a systemd service 'trojan' (the script does not create a service file itself). These are expected for system-level installation but grant persistent system changes — review before running as root.
Assessment
This skill is coherent with its stated purpose, but it is a system-level installer: it requires sudo and will modify /etc/* and /usr/src/*. Before running: (1) review the install.sh contents (included) yourself; (2) verify the trojan GitHub release/version and consider checking checksums if available; (3) back up any affected config files (proxychains, apt sources); (4) be aware the script does not create a systemd service file for 'trojan' — you may need to provide one; (5) only use trojan and proxy tools in ways that comply with local law and your network policies; (6) avoid running untrusted install scripts as root on production systems.Like a lobster shell, security has layers — review code before you run it.
latestvk975ahj990mcm7k3n4h1a92wwn83wpnc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis