From nobody Fri Jun 07 20:21:02 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Vwsz94y5Bz5MC2n; Fri, 07 Jun 2024 20:21:09 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vwsz94X7Nz45Sf; Fri, 7 Jun 2024 20:21:09 +0000 (UTC) (envelope-from kp@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717791669; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9xrc9k8xRWVVfjaqhkoH61skS2Q/LLZpwd9KtOHjFZg=; b=J4NhljJKtq4mdVA9ITB3vm6VBpojYWhoTbRSewd5/o+JmdQ96lms81rCIhNyP/rdemvvLL iYsUGRpRShRs9ZFlgXz8t/VD65pQhbxufhHQhcwJ9RWoICApgivYZBs8UbJ++xmQRMr76E 0+OLlgrtIJSMRxNM/wslqkPTbSsmE5D5V4DgsWtG4Vm8h7yumAXKBYQZzm2TS1Qd3sAmIp DjFhJVleYj5qDv6DDaWem35mhw0hpL7vXI8iteiPsrEPEE2FJYsnoevS/PhiuRXk2ThFeE 5SyXuZDsUlDA6N9dnmW+ynagW9s0i0lE1fa7NakOyxQxqJLijNHDFvcNPxM0ug== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1717791669; a=rsa-sha256; cv=none; b=iV/JRXJ2h3vkANS48kcc8Oid58NoohFWhwT+gW8rT4rAo+ViPYo98bgFVDBRepMo/Vt0X1 U7H6si7c4LyLBtnVO9PSvYC8t9cACD1fK+moMWhBNRSIYi5Y2qqDd8t0wUbyPrhrfbgmMb 8TrK+Fg9jOgcLaY+VHo2Ub3klxovdl9jPRPRrNubrf4DPmITXo3yiOq2/O94g4uKlQl2ji JLXO8wTB9T90KhkZUxdVituriLbd1W1VLG0IPHzGBx/cKDrLSLtcj6m2R2fxXeNVcFtSqA hzMQrNRO4jPMQMdicKrWZIXq92zzkhDC3KnL4dae+fYcNFMP8iiPvKD+Gcz27w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1717791669; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9xrc9k8xRWVVfjaqhkoH61skS2Q/LLZpwd9KtOHjFZg=; b=CaifaNAxplBqfcu4xSyhlYBTj25xDGYQmHEekDX0YcX+vXrjTTMrpu9IMdELlq705iFw7H Rn33cIe8/naz4Gzsf4hp8J2v8C9tMgTC8lGG62E8C1BuRuAZKB8Kl4CgQx78pbs8r4Eabo GsgVkyYo5p9JWvpEVoEcIJ1SCAkpOZAUHeBrHx2r44D6lYJzd6CMXCUP29SmXtlOZcbsOt B6nEWtHxAXGN2lgYXdaqCZdHQ3GukWj7yhDJgNGhQzj65DGjbk2M2vQ+C/ah4hJw0SuDpJ 6ef+O8uTw7821kfUU+f64nj5URV9pWoP4raCH+gUiV4OsoKMAxcKbaO2eJx7dA== Received: from venus.codepro.be (venus.codepro.be [5.9.86.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.codepro.be", Issuer "R3" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Vwsz93Xh9zYqZ; Fri, 7 Jun 2024 20:21:09 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id AACC334BCA; Fri, 07 Jun 2024 22:21:07 +0200 (CEST) From: Kristof Provost To: FreeBSD PF List , FreeBSD Ports ML Subject: Re: pf userspace API changes Date: Fri, 07 Jun 2024 16:21:02 -0400 X-Mailer: MailMate (1.14r5937) Message-ID: In-Reply-To: <0E45DD6F-81E3-45DB-9FB2-E47B8F26FD00@FreeBSD.org> References: <0E45DD6F-81E3-45DB-9FB2-E47B8F26FD00@FreeBSD.org> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; markup=markdown Content-Transfer-Encoding: quoted-printable On 6 Apr 2023, at 10:21, Kristof Provost wrote: > Quick heads up that there are going to be breaking changes to the pf AP= I towards userspace for 14.0. (That is, the ioctl interface presented by = /dev/pf). > Building on this, I=E2=80=99m in the process of providing netlink impleme= ntation and associated libpfctl abstraction for all existing (and still r= elevant) ioctl calls. My hope is to get that all done before we branch stable/15 (currently exp= ected in late 2025). If that succeeds I intend to remove the entire ioctl= handling code from pf for 16. There is no need for immediate action, but be aware that ports will need = to migrate to libpfctl before that removal lands. Tl;dr: this is your 18 month warning on ports breakage for any port that = uses /dev/pf. Best regards, Kristof