NetBSD Problem Report #50782

From campbell@mumble.net  Mon Feb  8 01:35:42 2016
Return-Path: <campbell@mumble.net>
Received: from mail.netbsd.org (mail.NetBSD.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 426F27A215
	for <gnats-bugs@gnats.NetBSD.org>; Mon,  8 Feb 2016 01:35:42 +0000 (UTC)
Message-Id: <20160208001507.9FE966035E@jupiter.mumble.net>
Date: Mon,  8 Feb 2016 00:15:07 +0000 (UTC)
From: riastradh@NetBSD.org
Reply-To: riastradh@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: `npfctl validate' should not need to talk to kernel
X-Send-Pr-Version: 3.95

>Number:         50782
>Category:       bin
>Synopsis:       `npfctl validate' should not need to talk to kernel
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 08 01:40:00 +0000 2016
>Closed-Date:    Sat Jan 19 21:45:46 +0000 2019
>Last-Modified:  Sat Jan 19 21:45:46 +0000 2019
>Originator:     riastradh@NetBSD.org
>Release:        NetBSD-current
>Organization:
>Environment:
>Description:

	There's plenty of validation that `npfctl validate' can do
	without talking to the kernel.  It should do that, and have a
	separate way to make sure it makes sense with respect to the
	current kernel.

>How-To-Repeat:

	Attempt to run `npfctl validate foo.conf' unprivileged, or for
	a system that is not the current one.

>Fix:

	Yes, please!

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->closed
State-Changed-By: rmind@NetBSD.org
State-Changed-When: Sat, 19 Jan 2019 21:45:46 +0000
State-Changed-Why:
This has been fixed some years ago.


>Unformatted:

Home	PR Database Search