From: Michael "T." Babcock <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Authetication on LAN
Date: Fri, 11 May 2001 01:15:56 +0000 [thread overview]
Message-ID: <marc-lartc-98954380728519@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98938697519917@msgid-missing>
On 10 May 2001 18:10:43 -0700, Mike Fedyk wrote:
> Ahh, but now we are talking about a non-transparent setup. I want something
> where it will work with any TCP/IP device without any setup besides setting
> IP and routing.
>
> I'd like to see something that can identify which user is using each
> connection, and not need anything more than an identd. This would enable
> access for that ip/port as needed at layer 3/4.
I'm not aware of one, but it shouldn't be too hard to write a program
that would watch for outgoing connections via netlink (Linux) or some
such device and request ident information about that user before
deciding to allow or deny the request.
One might exist.
_______________________________________________
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 1:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 5:43 [LARTC] Authetication on LAN Deepak singhal
2001-05-09 6:28 ` Torge Szczepanek
2001-05-09 7:11 ` Mike Fedyk
2001-05-09 7:26 ` Deepak singhal
2001-05-10 14:19 ` Michael T. Babcock
2001-05-10 17:07 ` Torge Szczepanek
2001-05-10 23:24 ` Mike Fedyk
2001-05-11 1:05 ` Michael T. Babcock
2001-05-11 1:10 ` Mike Fedyk
2001-05-11 1:15 ` Michael T. Babcock [this message]
2001-05-11 1:24 ` Mike Fedyk
2001-05-14 0:41 ` Michael T. Babcock
2001-05-14 1:13 ` Mike Fedyk
2001-05-14 1:25 ` Ramin Alidousti
2001-05-14 2:08 ` Mike Fedyk
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-98954380728519@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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.