From nobody Thu Mar 31 19:33:06 2022 X-Original-To: freebsd-hackers@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 754FC1A4AA43 for ; Thu, 31 Mar 2022 19:33:26 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KTtks4lTtz3nJt; Thu, 31 Mar 2022 19:33:25 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f47.google.com with SMTP id g21so664290iom.13; Thu, 31 Mar 2022 12:33:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Vhzw79STTkoLDNS50Hw406gAjy7PToj0Fkh4NqUJZDA=; b=J2+CrsNaAOzfKp1lY9mwp2ID2xvppMcnFdPzj8BC5YSsgGaKPRST2QoXfL3L4cznpE qNowqLdJK6CaA1u1Zabyyk/h1DsUEzVjs5p1NO2DI7NXJCyjHdBGFrzyh7OuERdMK2xj 0phFF9MA7tZThbZYZvVRoKiXH9WQGxXtVtNd1UX5QeWtmORiTvIZAyEsc5qaAD6jKyq/ 5wf302LmlgbOL+0v1xnAXTr71KpBHuLVoXv4ANpioDITzrxkM20G6/fyg4rta7A6D5y2 ewgLn9AlhwsZZ2drijL8r5K74uJWXnx/gkjCOzmCrsZV9/pgnRCe2PTFV9q0ccDQEw1b 7AXA== X-Gm-Message-State: AOAM531uJPdFK3WL7NKxWGnmn++3pcHpew0clAiOYAWibnoFcRL4uwt6 cC2QLGlEvhRq1S8Mag7MyMHxEA4MiF7l1+9bO3+luajT X-Google-Smtp-Source: ABdhPJz9rY2fZvaSMAfpUxH227X8KvzzPJuJqrmSQmLuLOY+ohkTmEnCE1a89G54C4le6i3684sh/PISH0iQKlNeRWg= X-Received: by 2002:a6b:8bd7:0:b0:646:2804:5c73 with SMTP id n206-20020a6b8bd7000000b0064628045c73mr14607271iod.112.1648755198919; Thu, 31 Mar 2022 12:33:18 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <25b5c60f-b9cc-78af-86d7-1cc714232364@gmail.com> <01320c49-fa7e-99d2-5840-3c61bb8c0d57@FreeBSD.org> <2d103b77-84d4-fbd7-d957-21b9aa4d5d79@gmail.com> <16ab7cdb-32b4-5ffe-f6a8-a657383b3078@FreeBSD.org> In-Reply-To: <16ab7cdb-32b4-5ffe-f6a8-a657383b3078@FreeBSD.org> From: Ed Maste Date: Thu, 31 Mar 2022 15:33:06 -0400 Message-ID: Subject: Re: curtain: WIP sandboxing mechanism with pledge()/unveil() support To: David Chisnall Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 4KTtks4lTtz3nJt X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.47 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-2.73 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.73)[-0.727]; FREEFALL_USER(0.00)[carpeddiem]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_TLS_ALL(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[209.85.166.47:from]; MLMMJ_DEST(0.00)[freebsd-hackers]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.166.47:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Thu, 31 Mar 2022 at 06:25, David Chisnall wrote: > > Capsicum simply disallows '..' in paths. This is no longer true as of 7359fdcf5ffa. During a lookup the kernel checks that each ".." component specifies a directory that has already been visited in this name lookup call. > The execve hole is the reason that I have little interest in pledge as > an enforcement mechanism. Note that execve is only available if the "exec" keyword is specified. The child does not inherit the parent's limits, though.