From owner-freebsd-arch@freebsd.org Sun Jun 24 10:32:46 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD7DE10231B9 for ; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6563B83844 for ; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2771210231B7; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1512B10231B6 for ; Sun, 24 Jun 2018 10:32:46 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD63783842 for ; Sun, 24 Jun 2018 10:32:45 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x235.google.com with SMTP id s14-v6so4110549ybp.13 for ; Sun, 24 Jun 2018 03:32:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=gFxC4TTdkWXENkiFjpeZmug2cweTMUojdYoxiwL00pM=; b=lbI5Y2pIB42rcaa4OXidkHZryfu0h9VmGkgbF6pQFm2G/jBNuucqFLr4ILP1YhsPc3 PjjXp/iq3jS/Lo+B21A6+r2VYs+qne/EruP9FuFMCNTTrYY6JQwOEb8+mLgPOqSJj6/j TFfxhlJM9WM/b6Wy1B1B1sMn5P+8L3OGwDgQE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=gFxC4TTdkWXENkiFjpeZmug2cweTMUojdYoxiwL00pM=; b=rvtYthR5kHx2shbCtVsOXKNys0PqWCTrzNntB9teRx6faOoh2CjPTyEVd4mWsCN+F0 IcD32GW02ED6BFGRU0tpTi+mOENFhO5/4H/6rTce2qkXjO70qAHxBCHiY7LMDvM0XYdQ 6S+Z9d98mgDtotDOityygUCYBrYHYeXc1kE5q0hwjmwv7RX9uA7YyVGL7CIHBR2R9eQc EP80P7GOmhjHF3NtQDVtMv+ryecFsw4TFUlRftBbupu1gn617ABtTjeoXw9dr1wBQfjP Kcvy9KSrddp0gVShoB0fHml8/GsGaFcaFyAWtNSVqGLbGTU9CGDyQ6ogSsdjaPS3fZMO bcgg== X-Gm-Message-State: APt69E3uJ5Sks1PP9riH3bErf7teft9D6sDCguVpPXC+VdgGaPNA/Q89 28YlxcmhoBEH/S4LRcKT+JN3C1LSs/CPJ/qo53O9Wgkj X-Google-Smtp-Source: ADUXVKKogjN/W4KM0FAyOD5VWQJZg6m/hBFkErnSB0farnCqNaOPdTMWcMYWLfapKc2nbXkjM+tYs0NASK+dEJIzAMU= X-Received: by 2002:a25:734f:: with SMTP id o76-v6mr3984480ybc.69.1529836364814; Sun, 24 Jun 2018 03:32:44 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sun, 24 Jun 2018 03:32:13 -0700 (PDT) From: Eitan Adler Date: Sun, 24 Jun 2018 03:32:13 -0700 Message-ID: Subject: What to do about rcmdsh(3) ? To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2018 10:32:47 -0000 Now that the rcmds are removed from base, it opens a question about what to do with rcmdsh(3). This is documented as rcmdsh =E2=80=93 return a stream to a remote command without superuser And is implemented as a rather simple wrapper of getaddrinfo and exec. This isn't something I'd imagine we'd add to libc now-a-days and is currently broken by default (due to defaulting to _PATH_RSH) I'm not sure there is much value in keeping this function around. I did a rather naive search for uses of this function in ports and couldn't find any. I'm preparing a more comprehensive patch for an exp-run. Does anyone have a reason to keep in libc? Any objection to removing it? If no, is there anything special I need to do beyond just removing the implementation and references? --=20 Eitan Adler