socksify-ruby icon indicating copy to clipboard operation
socksify-ruby copied to clipboard

Redirect any TCP connection initiated by a Ruby script through a SOCKS5 proxy

Results 12 socksify-ruby issues
Sort by recently updated
recently updated
newest added

I'm trying to connect to a socks5 proxy that requires credentials. I'm using socksify-ruby but can't stop receiving this error ``` SOCKSError::NotAllowed: connection not allowed by ruleset ``` From what...

This MR is inspired by #24, but does not use thread-local variables to store username/password. This is IMO safest and cleanest way to do it.

We are currently using Socksify to proxy FTP connections through our SOCKS proxy. This has been working for years in Ruby 2.3 (and older versions.) I've upgraded to Ruby 2.5...

Got this by mail, leaving it here for the new maintainer, @musybite

Back in April, a PR was introduced that made the license for this gem `GPL-3.0`. The PR in question: https://github.com/astro/socksify-ruby/pull/30 Was this a mistake? GPL-3.0 has implications that seem out...

Would love if this could be threadsafe, often want a few tcp sockets open at same time, some via socks and some not

I am having difficulties trying to make FTPS connection to SOCKS5 tunnel I've open via Putty. I am able to get it work using FileZilla settings: ![image](https://user-images.githubusercontent.com/5944110/194100542-69a52d58-472f-4e9a-9887-0cc883dd2c23.png) so I know...

``` irb(main):001:0> require 'socksify/http' => true irb(main):003:0> Net::HTTP.socks_proxy('127.0.0.1', 9050) (irb):3:in `': undefined method `socks_proxy' for Net::HTTP:Class (NoMethodError) Did you mean? SOCKSProxy from /usr/share/gems/gems/irb-1.4.1/exe/irb:11:in `' from /usr/bin/irb:25:in `load' from /usr/bin/irb:25:in `'...

```ruby require 'socksify/http' Socksify::debug = true uri = URI.parse('https://google.com') Net::HTTP.socks_proxy('127.0.0.1', 3999).start(uri.host, uri.port) do |http| req = Net::HTTP::Get.new uri resp = http.request(req) puts resp.inspect puts resp.body end ``` gives this error:...