NetBSD Problem Report #53854

From www@NetBSD.org  Thu Jan 10 13:44:15 2019
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id C3A507A1B4
	for <gnats-bugs@gnats.NetBSD.org>; Thu, 10 Jan 2019 13:44:14 +0000 (UTC)
Message-Id: <20190110134413.C34D37A27C@mollari.NetBSD.org>
Date: Thu, 10 Jan 2019 13:44:13 +0000 (UTC)
From: rlntlss83@gmail.com
Reply-To: rlntlss83@gmail.com
To: gnats-bugs@NetBSD.org
Subject: A SOCKS4/4a/5 daemon would be (very) nice
X-Send-Pr-Version: www-1.0

>Number:         53854
>Category:       bin
>Synopsis:       A SOCKS4/4a/5 daemon would be (very) nice
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    bin-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 10 13:45:00 +0000 2019
>Last-Modified:  Thu Jan 10 14:20:11 +0000 2019
>Originator:     rlntlss
>Release:        8.0
>Organization:
independent
>Environment:
8.0 amd64
>Description:
I was surprised not to find anything but SSH serving something SOCKSish in base -- I wouldn't be surprised if I just missed something.

SOCKS4 - https://www.openssh.com/txt/socks4.protocol
SOCKS4 FQDN extension
SOCKS5 - RFC1928/1929/1961

It seems like a simple enough protocol to serve.

A small addition, but would be exceedingly nice to find in NetBSD
>How-To-Repeat:
I did check pkgsrc, but saw nothing of use
>Fix:
I started a socksd.c; it's in my plan for the year; still I'm sure an experienced developer could come up with something without too much strain (GSS-API is the only thing foreign to me, I don't know what kind of effort that aspect would take)

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: standards-manager->bin-manager
Responsible-Changed-By: kleink@NetBSD.org
Responsible-Changed-When: Thu, 10 Jan 2019 14:20:11 +0000
Responsible-Changed-Why:
Not a standards conformance issue; base system feature request.


>Unformatted:

Home	PR Database Search