| Message ID | 20210529013516.767555-1-sergio@outerface.net |
|---|---|
| State | Accepted |
| Headers |
Return-Path: <openvpn-devel-bounces@lists.sourceforge.net> Delivered-To: patchwork@openvpn.net Delivered-To: patchwork@openvpn.net Received: from director14.mail.ord1d.rsapps.net ([172.30.191.6]) by backend30.mail.ord1d.rsapps.net with LMTP id wTBPGKmasWBFIgAAIUCqbw (envelope-from <openvpn-devel-bounces@lists.sourceforge.net>) for <patchwork@openvpn.net>; Fri, 28 May 2021 21:36:41 -0400 Received: from proxy8.mail.ord1d.rsapps.net ([172.30.191.6]) by director14.mail.ord1d.rsapps.net with LMTP id 0J+qF6masWBZRQAAeJ7fFg (envelope-from <openvpn-devel-bounces@lists.sourceforge.net>) for <patchwork@openvpn.net>; Fri, 28 May 2021 21:36:41 -0400 Received: from smtp38.gate.ord1d ([172.30.191.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) by proxy8.mail.ord1d.rsapps.net with LMTPS id YN9dF6masWAEJwAAGdz6CA (envelope-from <openvpn-devel-bounces@lists.sourceforge.net>) for <patchwork@openvpn.net>; Fri, 28 May 2021 21:36:41 -0400 X-Spam-Threshold: 95 X-Spam-Score: 0 X-Spam-Flag: NO X-Virus-Scanned: OK X-Orig-To: openvpnslackdevel@openvpn.net X-Originating-Ip: [216.105.38.7] Authentication-Results: smtp38.gate.ord1d.rsapps.net; iprev=pass policy.iprev="216.105.38.7"; spf=pass smtp.mailfrom="openvpn-devel-bounces@lists.sourceforge.net" smtp.helo="lists.sourceforge.net"; dkim=fail (signature verification failed) header.d=sourceforge.net; dkim=fail (signature verification failed) header.d=sf.net; dkim=fail (signature verification failed) header.d=outerface.net; dkim=fail (signature algorithm invalid) header.d=outerface.net; dmarc=fail (p=none; dis=none) header.from=outerface.net X-Suspicious-Flag: YES X-Classification-ID: 50c87032-c01e-11eb-a2f1-525400f6a58b-1-1 Received: from [216.105.38.7] ([216.105.38.7:35578] helo=lists.sourceforge.net) by smtp38.gate.ord1d.rsapps.net (envelope-from <openvpn-devel-bounces@lists.sourceforge.net>) (ecelerity 4.2.38.62370 r(:)) with ESMTPS (cipher=DHE-RSA-AES256-GCM-SHA384) id 2A/97-03748-8AA91B06; Fri, 28 May 2021 21:36:40 -0400 Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from <openvpn-devel-bounces@lists.sourceforge.net>) id 1lmnsz-0003Ib-HM; Sat, 29 May 2021 01:35:33 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from <sergio@outerface.net>) id 1lmnsx-0003IQ-Lo for openvpn-devel@lists.sourceforge.net; Sat, 29 May 2021 01:35:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:MIME-Version:Message-Id: Date:Subject:To:From:Sender:Reply-To:Cc:Content-Type:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=AmoY8s1jQ3WbekvEQaAVfCt5F/RLv/UG/L747rT+cP0=; b=TUCNWIF0B1aKz6Vp32Y2unYcbV JNcQBVoUFC4MhdledkQvmM5cASHN76ybpu1LAcfU9qcHQy46A1NwcGPFam3SE+sBYeEd2tGn/xxVc ZYmkx3iqPPnSs2hCusKQwZzFyZPIgHYtV6jSg4oM9npPoPsr5sWdMHwLn+BJEzyLf2Uc=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:MIME-Version:Message-Id:Date:Subject:To:From: Sender:Reply-To:Cc:Content-Type:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=AmoY8s1jQ3WbekvEQaAVfCt5F/RLv/UG/L747rT+cP0=; b=m T2+M5GdhPBBVJ41j/YyCX7aVgr2HqINDsqBnaDYoLEr97GuX1MMhgT0whKnmiGdI/cR/0v8WXjt96 Dn+8Vjwa3SgIFkK0XRBufgsa3PHLuVMpnP8yU97Pg9vRCc1dX7EkuxUf5q6o1ceDYZR9c7VkgQMoQ aWemu8vEXhR88qQU=; Received: from outerface.net ([195.70.199.109] helo=mail.outerface.net) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) id 1lmnss-001XI8-RR for openvpn-devel@lists.sourceforge.net; Sat, 29 May 2021 01:35:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=outerface.net; s=rsa2048; h=Content-Transfer-Encoding:MIME-Version: Message-Id:Date:Subject:To:From:Sender:Reply-To:Cc:Content-Type:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=AmoY8s1jQ3WbekvEQaAVfCt5F/RLv/UG/L747rT+cP0=; b=l7MX2rnfAXTSgKo2eZaezO28Zm EpFMlSGJSJiBsyFclNru1XB0Jt82aRZIb7JzeQ6RwvmIh8Kxmr3P4Vg3vq9RUi9TvjQgWfLTEorAY aCXEDFiBbFb7FRcIXYDrUbGh6TciztVq8LM7rJNvkvg6QfF8C/mNr+QNiftkbhtWqli63kQ9VHaPH FsBzCpr7+jofLWHSbwg89wA6/GrqxHKoB6m/NX6tEPmeeouENxGauumZhVTHhRFXkz0VqG3p4Z1cl R/USQcSt1O3bB/E1MRV96Nj/zapIv14VEVvkznu8mUd4FNJ7qQlqKc0KbgdwI9Vg5fYGjpLtTT7E1 PdlFveAQ==; DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=outerface.net; s=ed25519; h=Content-Transfer-Encoding:MIME-Version: Message-Id:Date:Subject:To:From:Sender:Reply-To:Cc:Content-Type:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=AmoY8s1jQ3WbekvEQaAVfCt5F/RLv/UG/L747rT+cP0=; b=OJXNm4OKKfY0oVG0GlI4/Fu/SP O1xObzuurtxe06bOoWyVEDxrbyvf7vJpsEiHhISG3Ht/wWrJN+g/Sva1xzDw==; Received: from [10.8.4.44] (port=53806 helo=disaster.outerface.net) by mail.outerface.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <sergio@outerface.net>) id 1lmnsl-0007XZ-Va; Sat, 29 May 2021 04:35:20 +0300 From: sergio <sergio@outerface.net> To: openvpn-devel@lists.sourceforge.net Date: Sat, 29 May 2021 04:35:16 +0300 Message-Id: <20210529013516.767555-1-sergio@outerface.net> X-Mailer: git-send-email 2.32.0.rc0 MIME-Version: 1.0 X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: outerface.net] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid X-Headers-End: 1lmnss-001XI8-RR Subject: [Openvpn-devel] [PATCH] resolvconf fails with -p X-BeenThere: openvpn-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: <openvpn-devel.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/options/openvpn-devel>, <mailto:openvpn-devel-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=openvpn-devel> List-Post: <mailto:openvpn-devel@lists.sourceforge.net> List-Help: <mailto:openvpn-devel-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/openvpn-devel>, <mailto:openvpn-devel-request@lists.sourceforge.net?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: openvpn-devel-bounces@lists.sourceforge.net X-getmail-retrieved-from-mailbox: Inbox |
| Series |
[Openvpn-devel] resolvconf fails with -p
|
|
Commit Message
sergio
May 28, 2021, 3:35 p.m. UTC
From: "Sergio E. Nemirowski" <sergio@outerface.net> resolvconf -p resolvconf: Error: Command not recognized Signed-off-by: Sergio E. Nemirowski <sergio@outerface.net> --- contrib/pull-resolv-conf/client.up | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Comments
Hi, On Sat, May 29, 2021 at 04:35:16AM +0300, sergio wrote: > From: "Sergio E. Nemirowski" <sergio@outerface.net> > > resolvconf -p > resolvconf: Error: Command not recognized Which platform does this fail on? The fact that the -p is currently there hints at "on some other platforms this works and is useful"... gert
> Which platform does this fail on? The fact that the -p is currently there > hints at "on some other platforms this works and is useful"... Debian bullseye & sid, v1.87
On 29/05/2021 03:35, sergio wrote: > From: "Sergio E. Nemirowski" <sergio@outerface.net> > > resolvconf -p > resolvconf: Error: Command not recognized > > Signed-off-by: Sergio E. Nemirowski <sergio@outerface.net> > --- > contrib/pull-resolv-conf/client.up | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/contrib/pull-resolv-conf/client.up b/contrib/pull-resolv-conf/client.up > index f0769740..220aeb74 100644 > --- a/contrib/pull-resolv-conf/client.up > +++ b/contrib/pull-resolv-conf/client.up > @@ -91,7 +91,7 @@ out="# resolv.conf autogenerated by ${0} (${dev})${nl}${dns}${ds}${domains}" > > # use resolvconf if it's available > if type resolvconf >/dev/null 2>&1; then > - printf "%s\n" "${out}" | resolvconf -p -a "${dev}" > + printf "%s\n" "${out}" | resolvconf -a "${dev}" > else > # Preserve the existing resolv.conf > if [ -e /etc/resolv.conf ] ; then > I quickly checked resolveconf on Ubuntu {18,20,21}.04 and Debian 9-11. Neither of them supports the '-p' argument. I've checked Fedora 34, RHEL-{7,8} too, where I could not find any obvious alternative to the old version of resolvconf tool. On RHEL-8 and Fedora, systemd-resolved is available and provides a different resolveconf which targets to replace this old utility. This replacement neither support '-p'. This option got added in commit 3adf2f558e157ef508 back in 2010, but there's too little information why it was needed back then. But given that neither relevant Linux distributions supports this option today, it's reasonable to remove it now. Acked-By: David Sommerseth <davids@openvpn.net> -- kind regards, David Sommerseth OpenVPN Inc
Sorry that it took so long. But here we go.
Your patch has been applied to the master and release/2.5 branch.
commit e739f41d05084c1bc9bfb6c5d49c74de37e53dc7 (master)
commit 8fcce5042865b6bed7dcde5d7d0372ae83d54708 (release/2.5)
Author: Sergio E. Nemirowski
Date: Sat May 29 04:35:16 2021 +0300
resolvconf fails with -p
Signed-off-by: Sergio E. Nemirowski <sergio@outerface.net>
Acked-by: David Sommerseth <davids@openvpn.net>
Message-Id: <20210529013516.767555-1-sergio@outerface.net>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg22467.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>
--
kind regards,
Gert Doering
On Sat, Nov 6, 2021 at 7:37 PM David Sommerseth < openvpn@sf.lists.topphemmelig.net> wrote: > I quickly checked resolveconf on Ubuntu {18,20,21}.04 and Debian 9-11. > Neither of them supports the '-p' argument. > > I've checked Fedora 34, RHEL-{7,8} too, where I could not find any > obvious alternative to the old version of resolvconf tool. On RHEL-8 > and Fedora, systemd-resolved is available and provides a different > resolveconf which targets to replace this old utility. This replacement > neither support '-p'. > > This option got added in commit 3adf2f558e157ef508 back in 2010, but > there's too little information why it was needed back then. But given > that neither relevant Linux distributions supports this option today, > it's reasonable to remove it now. > Openresolv uses it, and Arch offers that package. https://github.com/NetworkConfiguration/openresolv/blob/master/resolvconf.in#L108 has a -p That's my best guess where this came from. And then, since this is off buried in 'contrib', "nobody" noticed it for years. (I don't disagree with removing it, I just like forensics). <div dir="ltr"><div dir="ltr" class="gmail_attr">On Sat, Nov 6, 2021 at 7:37 PM David Sommerseth <<a href="mailto:openvpn@sf.lists.topphemmelig.net" target="_blank">openvpn@sf.lists.topphemmelig.net</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I quickly checked resolveconf on Ubuntu {18,20,21}.04 and Debian 9-11. <br> Neither of them supports the '-p' argument.<br> <br> I've checked Fedora 34, RHEL-{7,8} too, where I could not find any <br> obvious alternative to the old version of resolvconf tool. On RHEL-8 <br> and Fedora, systemd-resolved is available and provides a different <br> resolveconf which targets to replace this old utility. This replacement <br> neither support '-p'.<br> <br> This option got added in commit 3adf2f558e157ef508 back in 2010, but <br> there's too little information why it was needed back then. But given <br> that neither relevant Linux distributions supports this option today, <br> it's reasonable to remove it now.<br></blockquote><div><br></div><div style="font-family:courier new,monospace" class="gmail_default">Openresolv uses it, and Arch offers that package.</div><div style="font-family:courier new,monospace" class="gmail_default"> <a href="https://github.com/NetworkConfiguration/openresolv/blob/master/resolvconf.in#L108">https://github.com/NetworkConfiguration/openresolv/blob/master/resolvconf.in#L108</a> has a -p</div><div style="font-family:courier new,monospace" class="gmail_default"><br></div><div style="font-family:courier new,monospace" class="gmail_default">That's my best guess where this came from. And then, since this is off buried in 'contrib', "nobody" noticed it for years.<br></div><div style="font-family:courier new,monospace" class="gmail_default"><br></div><div style="font-family:courier new,monospace" class="gmail_default">(I don't disagree with removing it, I just like forensics).<br></div></div> </div>
diff --git a/contrib/pull-resolv-conf/client.up b/contrib/pull-resolv-conf/client.up index f0769740..220aeb74 100644 --- a/contrib/pull-resolv-conf/client.up +++ b/contrib/pull-resolv-conf/client.up @@ -91,7 +91,7 @@ out="# resolv.conf autogenerated by ${0} (${dev})${nl}${dns}${ds}${domains}" # use resolvconf if it's available if type resolvconf >/dev/null 2>&1; then - printf "%s\n" "${out}" | resolvconf -p -a "${dev}" + printf "%s\n" "${out}" | resolvconf -a "${dev}" else # Preserve the existing resolv.conf if [ -e /etc/resolv.conf ] ; then