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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 12 Feb 2022 12:05:38 +0100 From: Harald Welte <laforge@...monks.org> To: "Drewek, Wojciech" <wojciech.drewek@...el.com> Cc: Marcin Szycik <marcin.szycik@...ux.intel.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "michal.swiatkowski@...ux.intel.com" <michal.swiatkowski@...ux.intel.com>, "davem@...emloft.net" <davem@...emloft.net>, "kuba@...nel.org" <kuba@...nel.org>, "pablo@...filter.org" <pablo@...filter.org>, "osmocom-net-gprs@...ts.osmocom.org" <osmocom-net-gprs@...ts.osmocom.org> Subject: Re: [RFC PATCH net-next v4 4/6] gtp: Implement GTP echo response Hi Wojciech, On Fri, Feb 11, 2022 at 12:48:35PM +0000, Drewek, Wojciech wrote: > I have one question. The new cmd should be allowed to send echo request > only to the peers stored in the kernel space (PDP contexts) or the userspace > daemon has its own list of peers and any request should be allowed to be send? I think we can expect userspace to know the peers (after all, it has created those sessions and knows about the peer IP addresses), so we don't have to verify in the kernel if it is a "valid" peer or not. So a pure "send GTP ECHO req to given IP" and a corresponding "received GTP ECHO resp from given IP" (with relevant parameters) without tracking any state in the kernel should be sufficient. -- - Harald Welte <laforge@...monks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Powered by blists - more mailing lists