netdev - RE: reading SA state via XFRM / AF

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] [day] [month] [year] [list]

Message-ID: <BB7E16A14DE689469A181EC770AFBF4D02EF3D74@exch-one.centrify.com>
Date:	Fri, 10 Apr 2009 09:25:50 -0700
From:	"Paul Moore" <paul.moore@...trify.com>
To:	"Paul Moore" <paul.moore@...trify.com>, <netdev@...r.kernel.org>
Subject: RE: reading SA state via XFRM / AF_NETLINK

I will take the thunderous silence as a confirmation that this data is
not available via xfrm
any suggestions on how to synthesize it would be welcome

-----Original Message-----
From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
On Behalf Of Paul Moore
Sent: Tuesday, April 07, 2009 6:21 PM
To: netdev@...r.kernel.org
Subject: reading SA state via XFRM / AF_NETLINK

as far as I can see there is no way to read the state (larval, mature,
dying, etc) of an SA via AF_NETLINK

af_key.c provides this information to AF_KEY callers by peeking at
xfrm_state.km.state but xfrm_user.c does not seem to make this data
available (and there dont appear to be places in the user mode xfrm
structures for it either)

is this correct? did I miss a back channel somewhere?
--
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
--
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