netdev - Re: [PATCH v7 0/4] Support administratively closing application sockets

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: <20151216.182413.1561030855644800839.davem@davemloft.net>
Date:	Wed, 16 Dec 2015 18:24:13 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jhs@...atatu.com
Cc:	eric.dumazet@...il.com, stephen@...workplumber.org,
	lorenzo@...gle.com, netdev@...r.kernel.org,
	hannes@...essinduktion.org, ek@...gle.com, tom@...bertland.com,
	zenczykowski@...il.com
Subject: Re: [PATCH v7 0/4] Support administratively closing application
 sockets

From: Jamal Hadi Salim <jhs@...atatu.com>
Date: Wed, 16 Dec 2015 14:55:15 -0500

> The question i had was the opposite when i saw this: why are
> regular users allowed to read admin (and any other users) details?;->
> On this specific feature: why, as a regular user, I cant close
> connections attributed to me (and have to use CAP_NET_ADMIN)?

There is nothing provided via socket diag that can't be seen
also via /proc/net/tcp et al.
--
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