Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id D2DAC6DE092A for ; Fri, 12 Aug 2016 00:39:05 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.008 X-Spam-Level: X-Spam-Status: No, score=-0.008 tagged_above=-999 required=5 tests=[AWL=0.003, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFdLKRZ0D7hV for ; Fri, 12 Aug 2016 00:38:57 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id BF1A36DE092B for ; Fri, 12 Aug 2016 00:38:57 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1bY73e-0007re-6G; Fri, 12 Aug 2016 03:39:10 -0400 Received: (nullmailer pid 31983 invoked by uid 1000); Fri, 12 Aug 2016 07:38:53 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: [PATCH v4 01/16] add util/search-path.{c, h} to test for executables in $PATH In-Reply-To: <87k2fmse5h.fsf@alice.fifthhorseman.net> References: <1467970047-8013-1-git-send-email-dkg@fifthhorseman.net> <1467970047-8013-2-git-send-email-dkg@fifthhorseman.net> <878tw2r0vf.fsf@maritornes.cs.unb.ca> <87k2fmse5h.fsf@alice.fifthhorseman.net> User-Agent: Notmuch/0.22.1+61~g2ce0f13 (https://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Fri, 12 Aug 2016 16:38:53 +0900 Message-ID: <87y442phbm.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Aug 2016 07:39:06 -0000 Daniel Kahn Gillmor writes: >> >> Should we distinguish between relative and absolute paths here? I can't >> think of any security implications, but I'm wondering if a relative path >> is likely just a user error. > > I don't think a relative path is necessarily a user error. I certainly > use relative paths myself from time to time. As configuration values? That seems quite fragile, since it depends on the current working directory when notmuch is run. d