Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.networking > #1222 > unrolled thread

test protocol at client?

Back to article view | Back to comp.os.linux.networking

Contents

  test protocol at client? "ghand" <ghand45@hotmail.com> - 2012-03-31 09:05 +0100
    Re: test protocol at client? Chris Davies <chris-usenet@roaima.co.uk> - 2012-03-31 12:03 +0100
      Re: test protocol at client? "ghand" <ghand45@hotmail.com> - 2012-04-02 10:31 +0100
        Re: test protocol at client? Chris Davies <chris-usenet@roaima.co.uk> - 2012-04-02 13:03 +0100

#1222 — test protocol at client?

I know nmap can test (sometimes) the protocol running at a server(http etc),
but is there anything that can test the protocol being used by a client?  
     

[toc] | [next] | [standalone]

#1223

ghand <ghand45@hotmail.com> wrote:
> but is there anything that can test the protocol being used by a client?  

Not meaningfully, no, short of sniffing the wire between client and server.
Chris

[toc] | [prev] | [next] | [standalone]

#1225

Chris Davies <chris-usenet@roaima.co.uk> wrote:
>ghand <ghand45@hotmail.com> wrote:
>> but is there anything that can test the protocol being used by a
>client?  
>
>Not meaningfully, no, short of sniffing the wire between client and
>server.
>Chris

OK so I suppose it can't set itself up as a server let the client connect,
and then detect what protocol is used at the client?

How about..

Suppose I have a client and SOCKS server, and sniff the packets between them
and capture them. (with tcpdump)

I have done that with a SOCKS server I have. And i'd like something to detect
whether the packets, are SOCKS4 or SOCKS5.

Wireshark doesn't seem to tell me.

Is there anything that would? 

What are my options for what would tell me?

[toc] | [prev] | [next] | [standalone]

#1226

ghand <ghand45@hotmail.com> wrote:
> OK so I suppose it can't set itself up as a server let the client connect,
> and then detect what protocol is used at the client?

In many caess the server is expected to say "hello" before the client
is permitted to talk. (SMTP and FTP are examples of this.)


> Suppose I have a client and SOCKS server, and sniff the packets between
> them and capture them. (with tcpdump)

> I have done that with a SOCKS server I have. And i'd like something
> to detect whether the packets, are SOCKS4 or SOCKS5.

Personally I don't know the difference. But I see no reason why there
couldn't be something that looked at the packet contents and determined
whether to route them to a SOCKS4 or SOCKS5 server.

A quick google suggests that you might want to take a look at "redsocks";
looks like it already does this.

Chris

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.networking

csiph-web