From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: nft authentication Date: Wed, 1 Mar 2017 00:24:51 +0100 Message-ID: <20170228232451.GA24798@breakpoint.cc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netfilter-devel@vger.kernel.org To: Fabian Franz Return-path: Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:36346 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751623AbdB1X5T (ORCPT ); Tue, 28 Feb 2017 18:57:19 -0500 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Fabian Franz wrote: > I am working on my module but I cannot get the match visible to the nft > tool. Could you please give me a hint, what is wrong in the code? I have > uploaded it to my web server: http://files.fabian-franz.eu/nft_auth.c I do not know what 'visible to the nft tool' means. No 'obvious' mistake in the register department. My only comment is that it looks like you are re-inventing the wheels we already have, such as nf_log and nf_queue. If this is a learning exercise, fine, but we have real missing functionality that could be added instead. If this targets upstream, you should really discuss what problem wants to be solved. The building blocks we already have should be enough to do uid based authentication. (something like nf_log/queue -> userspace daemon -> query -> update nft set w. uid)