base on A socksv5 proxy tool Written by CLang. 一款纯C实现的轻量内网穿透工具，支持正向，反向socks5代理隧道的搭建，支持跨平台使用。 # README.md <h1>yuze🤗 (2025.3.3日重大更新)</h1> ## 简介 yuze 是一款纯C实现的轻量内网穿透工具，支持正向，反向socks5代理隧道的搭建，支持跨平台使用。 特点 - 支持正向、反向代理（均支持用户名密码验证） - 支持任意以`Tcp`协议为基础的服务，（`RDP`等） - 体积小, 极轻量的内网穿透工具 - 跨平台，支持Windows、Linux # 最新版本 当前最新 `v0.4.0` （2025/3/3更新，功能基本重写） # 使用简介 ## 正向代理功能 (Proxy Mode) 在 `0.0.0.0:1080`启动Socks5服务 ``` yuze proxy -l 1080 //有公网IP的受控主机 ``` 正向代理的用户验证功能 ``` yuze proxy -l 1080 -u test -p test //有公网IP的受控主机 ``` ## 反向代理 (reverse Mode) 在公网VPS的`1080` 端口启动Socks5服务 ``` yuze reverse -s 1080 -l 5050 //公网VPS上执行 yuze reverse -c 127.0.0.1:5050 //内网可控主机执行 ``` 反向代理的用户验证功能 ``` yuze reverse -s 1080 -l 5050 yuze reverse -c 127.0.0.1:5050 -u test -p test ``` ## 端口转发 （fwd Mode） 1080端口是起的socks5服务 `fwd` 模式端口转发实现在5050端口访问1080端口的 ``` yuze proxy -l 1080 yuze fwd -l 5050 -f 127.0.0.1:1080 ``` ## TODO 1. 通信流量加密（试验中） ## 闲谈 yuze是我学习socket网络编程后产出的工具，它帮助我深入了解了内网渗透中常见基于socks协议的隧道代理，流量转发的原理。最初用go语言实现了正向、反向代理。由于编译后体积问题，改用纯C实现，支持ew的全部数据转发方式。 它的很多的灵感来自于对EarthWorm（ew）的逆向，向前辈致敬。 2025.3.3 更新 鸽了挺久，最近闲了基本重写了，有gpt的加成快了许多 ## 致谢 https://rootkiter.com/EarthWorm/", Assign "at most 3 tags" to the expected json: {"id":"7240","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"