netdev - Re: [PATCH v5 0/3] VSOCK: vsockmon virtual device to monitor 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: <20170424.123633.1996395785851142975.davem@davemloft.net>
Date:   Mon, 24 Apr 2017 12:36:33 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     stefanha@...hat.com
Cc:     netdev@...r.kernel.org, zyjzyj2000@...il.com, mst@...hat.com,
        ggarcia@...a.uab.cat, jhansen@...are.com
Subject: Re: [PATCH v5 0/3] VSOCK: vsockmon virtual device to monitor
 AF_VSOCK sockets.

From: Stefan Hajnoczi <stefanha@...hat.com>
Date: Fri, 21 Apr 2017 10:10:43 +0100

> This is a continuation of Gerard Garcia's work on the vsockmon packet capture
> interface for AF_VSOCK.  Packet capture is an essential feature for network
> communication.  Gerard began addressing this feature gap in his Google Summer
> of Code 2016 project.  I have cleaned up, rebased, and retested the v2 series
> he posted previously.
> 
> The design follows the nlmon packet capture interface closely.  This is because
> vsock has the same problem as netlink: there is no netdev on which packets can
> be captured.  The nlmon driver is a synthetic netdev purely for the purpose of
> enabling packet capture.  We follow the same approach here with vsockmon.
> 
> See include/uapi/linux/vsockmon.h in this series for details on the packet
> layout.

Series applied, thanks.