From: "Deepak singhal" <dsinghal@spacewayindia.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SOCKS4/5 daemon (was: Authetication on LAN)
Date: Fri, 11 May 2001 12:30:07 +0000 [thread overview]
Message-ID: <marc-lartc-98958281716658@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98957682132750@msgid-missing>
That would solve my problem also ..!! If anybody can recommend soks4/5
daemon with per user authentication ..
----- Original Message -----
From: "Federico Sevilla III" <jijo@i-manila.com.ph>
To: "LARTC Mailing List" <lartc@mailman.ds9a.nl>
Sent: Friday, May 11, 2001 3:56 PM
Subject: [LARTC] SOCKS4/5 daemon (was: Authetication on LAN)
> On 10 May 2001 at 21:05, Michael T. Babcock wrote:
> > Anything that runs through Socks4/5 (all of the above) can have
> > per-user authentication.
>
> This is slightly (?) off-topic, so I hope you all won't mind. Would anyone
> have a good SOCKS 4/5 daemon to recommend for Linux? Hopefully something
> that aside from being fast and stable, can handle per-user authentication.
>
> Thanks in advance!
>
> --> Jijo
>
> ---
> Linux, MS-DOS, and Windows NT ...
> ... also known as the Good, the Bad, and the Ugly
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO:
http://ds9a.nl/2.4Routing/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-05-11 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 10:26 [LARTC] SOCKS4/5 daemon (was: Authetication on LAN) Federico Sevilla III
2001-05-11 12:30 ` Deepak singhal [this message]
2001-05-11 12:44 ` Federico Sevilla III
2001-05-11 19:49 ` Michael T. Babcock
2001-05-12 8:21 ` RoMaN SoFt / LLFB!!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-98958281716658@msgid-missing \
--to=dsinghal@spacewayindia.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.