netdev - Re: [PATCH 1/1] Allow LSM to use IP address/port number.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200707211057.ACE39835.WUNtGEPSOFF@I-love.SAKURA.ne.jp>
Date:	Sat, 21 Jul 2007 10:57:35 +0900
From:	Tetsuo Handa <from-netdev@...ove.SAKURA.ne.jp>
To:	kaber@...sh.net, jmorris@...ei.org
Cc:	netdev@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [PATCH 1/1] Allow LSM to use IP address/port number.

Hello.

Patrick McHardy wrote:
> Quoting Tetsuo:
> > > So, my approach is not using security context associated with a socket
> > > but security context associated with a process.
> Isn't the socket context derived from the process context?
Not so regarding my case.

static int smack_sk_alloc_security(struct sock *sk, int family, gfp_t priority)
{
	sk->sk_security = current->security;
	return 0;
}

will not help what I want to do.
So, I'm not planning to use "sk->sk_security".
I'm planning to use "current->security" at accept()/recvmsg() time.

What I want to do is to enforce subset of TCP Wrapper inside the kernel space
so that "IP/port based filtering for TCP and UDP is applied to ALL processes"
and "IP/port based filtering for TCP and UDP is not bypassed by processes that are
linked with TCP Wrapper library (even if accept()/recvmsg() syscalls are directly called)".

To receive source IP/port of a incoming packet, non-NULL msg->msg_name is needed for receiving them,
and I'm proposing modifications in net/socket.c .

Regards.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html