All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Earnshaw <tonni@billy.demon.nl>
To: Frank Schaefer <frank.schafer@setuza.cz>
Cc: netfilter@lists.samba.org
Subject: Re: netfilter access control
Date: 06 Jun 2002 09:18:03 +0200	[thread overview]
Message-ID: <1023347885.4299.159.camel@billy.demon.nl> (raw)
In-Reply-To: <1023346651.254.0.camel@ADMIN>

[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]

tor, 2002-06-06 kl. 08:57 skrev Frank Schaefer:

> we solved this task using mod_auth. There wasn't any problem for UNIX
> clients/ users. Doing some Gooooooooooogle we found a Windooooooze
> identd too.

I can't see how continuing to use what's basically a Socks 4 proxy can
help with those other protocols.

I used to use NEC's reference Socks 5 proxy for a subset of what Thierry
wants. There are 2 or 3 kinds of authorization possible.

Using HummingBird's (does HummingBird still exist?) Socks client,
Windows machines get completely transparent access. Otherwise, there's
NEC's SocksCap.

See: http://www.socks.nec.com/socksfaq.html

I haven't used it for years, though.

Best,

Tony

-- 

Tony Earnshaw

e-post:		tonni@billy.demon.nl
www:		http://www.billy.demon.nl
gpg public key:	http://www.billy.demon.nl/tonni.armor

Telefoon:	(+31) (0)172 530428
Mobiel:		(+31) (0)6 51153356

GPG Fingerprint = 3924 6BF8 A755 DE1A 4AD6 FA2B F7D7 6051 3BE7 B981
3BE7B981



[-- Attachment #2: Dette er en digitalt signert meldingsdel --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2002-06-06  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06  8:06 netfilter access control Thierry ITTY
2002-06-06  6:57 ` Frank Schaefer
2002-06-06  7:18   ` Tony Earnshaw [this message]

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=1023347885.4299.159.camel@billy.demon.nl \
    --to=tonni@billy.demon.nl \
    --cc=frank.schafer@setuza.cz \
    --cc=netfilter@lists.samba.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.