Shellroute update: it now works with your own proxy, no account needed

[u/vitascivilis]

I built Shellroute, an open-source CLI that lets you save your own HTTP, HTTPS, or SOCKS5 proxy and use it from an interactive shell without creating a Shellroute account. Save the proxy once, open Shellroute, connect to it by name, and then use normal terminal commands.

shellroute upstream add my-proxy 'https://USER:PASSWORD@HOST:PORT'
shellroute
/connect my-proxy
curl -I https://example.com/

`USER`, `PASSWORD`, `HOST`, and `PORT` are the details from your proxy provider. `my-proxy` is just a name you choose for the saved proxy.

The proxy applies inside that Shellroute shell, while the rest of your machine keeps its normal connection. Shellroute also has optional hosted country and city routes, which are paid.

Source: https://github.com/shellroute/shellroute-cli

Does this kind of saved-proxy shell fit how you use proxies from the command line?

Earlier thread: https://www.reddit.com/r/commandline/comments/1w6ze7u/shellroute_a_cli_that_gives_each_shell_its_own/

[u/donp1ano]

uhm...its basically proxychains in go?

[u/vitascivilis → u/donp1ano]

Yeah, there’s real overlap: both can put command-line traffic through a proxy. ProxyChains works by loading a small helper into a program and hooking C-library network functions. It can redirect only the connection calls that helper intercepts. Static binaries, programs that bypass those hooked calls, and OS-protected programs fall outside that mechanism. macOS’s built-in curl is one example of an OS-protected program, and ProxyChains also warns that some scripts, daemons, and dynamically loaded modules may not work.

Shellroute works differently: it starts a local HTTP proxy and gives the shell normal proxy settings, so the client uses proxy support itself. That means a program ProxyChains cannot hook can still work if it supports those proxy settings. The reverse is also true: tools that ignore proxy settings can go direct unless explicitly configured, and some cannot use a proxy at all.

The practical Shellroute workflow is saving proxies by name, switching them with `/connect`, and seeing the active route in the prompt. So I’d describe it as a shell proxy manager with a different compatibility trade-off, not a Go port of ProxyChains.

[u/AutoModerator]

Every new subreddit post is automatically copied into a comment for preservation.

User: vitascivilis, Flair: Command Line Interface, Title: Shellroute update: it now works with your own proxy, no account needed

I built Shellroute, an open-source CLI that lets you save your own HTTP, HTTPS, or SOCKS5 proxy and use it from an interactive shell without creating a Shellroute account. Save the proxy once, open Shellroute, connect to it by name, and then use normal terminal commands.

shellroute upstream add my-proxy 'https://USER:PASSWORD@HOST:PORT'
shellroute
/connect my-proxy
curl -I https://example.com/

`USER`, `PASSWORD`, `HOST`, and `PORT` are the details from your proxy provider. `my-proxy` is just a name you choose for the saved proxy.

The proxy applies inside that Shellroute shell, while the rest of your machine keeps its normal connection. Shellroute also has optional hosted country and city routes, which are paid.

Source: https://github.com/shellroute/shellroute-cli

Does this kind of saved-proxy shell fit how you use proxies from the command line?

Earlier thread: https://www.reddit.com/r/commandline/comments/1w6ze7u/shellroute_a_cli_that_gives_each_shell_its_own/

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.