| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Check connect address in NETLINK |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 28 Jun 2004 17:30:39 -0700 |
| Cc: | kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20040628231439.GA3021@gondor.apana.org.au> |
| References: | <20040628231439.GA3021@gondor.apana.org.au> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 29 Jun 2004 09:14:39 +1000 Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> wrote: > The solution seems simple. We already have a connect(2) call for > NETLINK sockets. So why don't we check the connected address of > the destination socket against the address of the sender before > putting the packet on the queue? > > Any comments before I go ahead and code it? This really won't break any existing legitimate cases? Are you sure? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Check connect address in NETLINK, Herbert Xu |
|---|---|
| Next by Date: | Re: [PATCH][ATM]: fix sparse checker warnings, Jeff Garzik |
| Previous by Thread: | Check connect address in NETLINK, Herbert Xu |
| Next by Thread: | Re: Check connect address in NETLINK, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |