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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 22 Aug 2020 13:53:03 -0700
From:   Pascal Bouchareine <>
To:     David Miller <>
Cc:,,, Jakub Kicinski <>,
        Andrew Morton <>,
        Alexey Dobriyan <>,
        Al Viro <>
Subject: Re: [PATCH v2 2/2] net: socket: implement SO_DESCRIPTION

On Sat, Aug 22, 2020 at 1:19 PM Pascal Bouchareine <> wrote:
> On Sat, Aug 22, 2020 at 12:59 PM Pascal Bouchareine <> wrote:
> > Would it make sense to also make UDIAG_SHOW_NAME use sk_description?
> > (And keep the existing change - setsockopt + show_fd_info via
> > /proc/.../fdinfo/..)
> Ah,very wrong example - to be more precise, I suppose that'd be adding
> a couple idiag_ext for sk_description and pid if possible instead

About the pid part -
On top of multiple pids to scan for a given socket, there's also the
security provided by /proc - I'm not sure what inet_diag does for that
So maybe users calling it will need to scan /proc for a long time anyway...

Or is that doable?

Powered by blists - more mailing lists