Add socks 4a proxy support

Open
#70 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
networking

Research direction

Start in lib/rex/socket/comm/local.rb around lines 448-451, where the issue identifies local DNS resolution for SOCKS connections. Trace how the existing SOCKS proxy handling reaches this lookup and determine the behavior needed for SOCKS4a remote resolution. Done means rex-socket supports SOCKS4a without resolving the destination locally.

Written by the indexing model from the issue text.

Description

Requested from https://github.com/rapid7/rex-socket/pull/69

Let's update rex-socket to support socks4a; current the DNS resolution happens locally - and doesn't support the ability to perform DNS resolution remotely via the socks proxy: https://github.com/rapid7/rex-socket/blob/e6c2e61c17eb6ea128575820005bb3a935ea4b54/lib/rex/socket/comm/local.rb#L448-L451

Dominant language
Ruby
Stars
13
Forks
34
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rapid7/rex-socket

All issues in rapid7/rex-socket

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.