From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: John Richard Moser <nigelenki@comcast.net>
Cc: netdev@oss.sgi.com
Subject: Re: Sockets from kernel space?
Date: Thu, 16 Dec 2004 00:29:46 -0200 [thread overview]
Message-ID: <41C0F31A.4050305@conectiva.com.br> (raw)
In-Reply-To: <41C0FDBA.5060406@comcast.net>
John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Thanks. I'll look at those.
>
> I'm aiming at potentially writing an LSM that allows a process to attach
> to the kernel, which will then be sent messages through an AF_UNIX
> (these are the app<->app sockets right?) socket with the details of any
> listen(2) or connect(2) calls made. I was going to do it in userspace,
> but realized it was easily avoidable that way.
>
> If this works, I can pretty much securely create a host firewall that
> regulates based on network operations, user, and program. This would
> allow the creation of discressionary firewalls, like Zone Alarm, Norton
> PF, McAffee PF, etc. The daemon sits in userspace, the kernel asks it
> for policy decisions, it asks connected/authenticated clients about
> unknown policy, and makes them re-authenticate to get an answer. The
> authentication is in userspace (PAM), hence the daemon.
Look at the iproute2 code to know how to use netlink 8)
- Arnaldo
prev parent reply other threads:[~2004-12-16 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41C0E720.8050201@comcast.net>
2004-12-16 1:06 ` Sockets from kernel space? Arnaldo Carvalho de Melo
2004-12-16 3:15 ` John Richard Moser
2004-12-16 2:29 ` Arnaldo Carvalho de Melo [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=41C0F31A.4050305@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=netdev@oss.sgi.com \
--cc=nigelenki@comcast.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).