PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2025-12-25 08:59:01 +00:00
Code Issues Projects Releases Wiki Activity

Design improvements.

Browse Source 
Externally:
  The calling application can build a proxychain object and assign it to one (or
  more) NSP. Once a NSP get assigned a proxychain it's not possible to remove
  it so that consistency is (should be...) ensured.

Internally:
  An IOD comes with a proxychain context structure storing the whole tunnel
  state. Also each proxy type now has a table of associated functions to use
  as hooks for TCP connects(), read() and write() requests. As a result, adding
  support of new proxy type should be easier. Code also gains readability in
  comparison to large switch/cases that redirect the execution flow according to
  the given proxy type.
This commit is contained in:
henri
2013-04-22 19:29:18 +00:00
parent a6bcd9cb7e
commit 28604b63e3
5 changed files with 158 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
nsock/include/nsock.h
View File

@@ -131,6 +131,8 @@ typedef void *nsock_ssl_session;
typedef void *nsock_ssl_ctx;
typedef void *nsock_ssl;
typedef void *nsock_proxychain;
/* Logging-related data structures */
@@ -187,8 +189,6 @@ enum nsock_loopstatus {
NSOCK_LOOP_QUIT
};
int nsock_set_proxychain(nsock_pool nsp, const char *proxystr);
enum nsock_loopstatus nsock_loop(nsock_pool nsp, int msec_timeout);
/* Calling this function will cause nsock_loop to quit on its next iteration
@@ -270,6 +270,21 @@ void nsock_set_log_function(nsock_pool nsp, nsock_logger_t logger);
nsock_loglevel_t nsock_get_loglevel(nsock_pool nsp);
void nsock_set_loglevel(nsock_pool nsp, nsock_loglevel_t loglevel);
/* Parse a proxy chain description string and build a nsock_proxychain object
* accordingly. If the optional nsock_pool parameter is passed in, it gets
* associated to the chain object. The alternative is to pass nsp=NULL and call
* nsp_set_proxychain() manually. Whatever is done, the chain object has to be
* deleted by the caller, using proxychain_delete(). */
int nsock_proxychain_new(const char *proxystr, nsock_proxychain *chain, nsock_pool nspool);
/* If nsock_proxychain_new() returned success, caller has to free the chain
* object using this function. */
void nsock_proxychain_delete(nsock_proxychain chain);
/* Assign a previously created proxychain object to a nsock pool. After this,
* new connections requests will be issued through the chain of proxies (if
* possible). */
int nsp_set_proxychain(nsock_pool nspool, nsock_proxychain chain);
/* nsock_event handles a single event. Its ID is generally returned when the
* event is created, and the event itself is included in callbacks