From owner-freebsd-jail@freebsd.org Tue May 15 11:17:22 2018 Return-Path: Delivered-To: freebsd-jail@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 7C865EAE9B2 for ; Tue, 15 May 2018 11:17:22 +0000 (UTC) (envelope-from andreas.sommer87@googlemail.com) Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (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 E7E9E6D4D4 for ; Tue, 15 May 2018 11:17:21 +0000 (UTC) (envelope-from andreas.sommer87@googlemail.com) Received: by mail-wr0-x22b.google.com with SMTP id y15-v6so15562779wrg.11 for ; Tue, 15 May 2018 04:17:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=geKzpGS5cBmNgRJuwG7qVwpA758aukaaMLR+3STfH5g=; b=l3svocSn+ELqw1CUfD6VvJkYBYaO3Op7LpP1bzF8pH8kxJbbJ1ZeOz49ZrrSI1VCed bs7x/RM74AxXcPputqeZIRmE7imFAyinYcXGTFkovNUxpXg7Lg+LtAZGv7agpifOo0YC XPEWwffrPVihjK1UKSExa518iHv+gz1CSQskncfxdfgIVpBAs0qbBf0CJMG5HcTAMcxh YSFStI1JuyN8lDbMuvJBZxg4sKyXyqh12TeEWFrQrFbzXSxBREVSkp2jwhZROuTyd+uP ogLqFMWJ+EM+oqb79g5mcSk8CnaA5/VUFxY5QDclYz/27VJRZboxSlV8diH2FS/fCpkn 1VmA== X-Gm-Message-State: ALKqPwdALlDS0l7pMyq+CEAd8+F1Mt61EEjt5xNuh4xPppNBxKqW/xk/ r8ZuwIuqUt/36glRWUKpuP8Xgg== X-Google-Smtp-Source: AB8JxZoS9cujMrIPxMhBlUjfmMATnAaACyrqAhCz3tai5KQDHw7oxrKCoqOt5S3pYkh8Ob/Yh7MwHw== X-Received: by 2002:adf:87d4:: with SMTP id c20-v6mr10126828wrc.197.1526383040436; Tue, 15 May 2018 04:17:20 -0700 (PDT) Received: from asommer-mac.local ([195.30.121.97]) by smtp.googlemail.com with ESMTPSA id w6-v6sm13901050wra.16.2018.05.15.04.17.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 May 2018 04:17:19 -0700 (PDT) To: freebsd-jail@freebsd.org From: Andreas Sommer Subject: Configure jail in /etc/jail.my-jail-name.conf while allowing auto-start with "service jail start" Message-ID: Date: Tue, 15 May 2018 13:17:18 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 11:17:22 -0000 Hi all, as I can see, this combination simply isn't part of /etc/rc.d/jail and jail(8). In fact, jail(8) always only reads one config file (`-f` parameter, default /etc/jail.conf). This also relates to why ezjail was still not ported to use jail.conf [0][1]. It would be a great fit to automated configuration management (e.g. via Ansible or pkg POST-INSTALL scripts) because it allows overwriting complete files instead of having to edit the global jail.conf to make changes. Jail configured only in /etc/jail.my-jail-name.conf: > # service jail onestart > Starting jails:. (nothing started because jail not recognized as configured) Jail configured in /etc/jail.my-jail-name.conf and "mentioned" as `jail my-jail-name {}` in /etc/jail.conf: > # service jail onestart > Starting jails:jail: my-jail-name: new jail must persist or attach (this means only /etc/jail.conf was parsed) Any way to achieve this? I assume the answer is no, so here's a suggestion: what about having jail(8) read/merge configuration from another file? Example: > # cat /etc/jail.conf > my-jail-name { config = "/etc/jail.my-jail-name.conf"; } > # cat /etc/jail.my-jail-name.conf > my-jail-name { ...config goes here... } Thanks, Andreas [0] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849 [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218849#c13 (ezjail maintainer comment) From owner-freebsd-jail@freebsd.org Tue May 15 11:30:34 2018 Return-Path: Delivered-To: freebsd-jail@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 DB638EAF663 for ; Tue, 15 May 2018 11:30:33 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 467F070014 for ; Tue, 15 May 2018 11:30:33 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id j193-v6so22857780lfg.6 for ; Tue, 15 May 2018 04:30:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3HIpGwrYB10PzmBcbjFXxhFhkeCIzpnI1MEngPjPqOo=; b=Y4H8Um8nFARkSG9ZyN2QCE3eznHHvFVl8awPP7DvNWIxcJazAbXxm8N73AdbelnUrW WGOq8SKFWsMy/9OrPpkCl5HuZ84WI/vmP4VqtmE/B5kXHZcYosqLWzJCKL8dsG7uuJeM vhNq/wToXM7SdFzShO3GC7vpNUGGYtXrUeDHqKtTsaaeqhGsE8GhfdnMdLK/ujH7VJqT CUdXpal06Rcf/yN2d48IXWchMWiOO2WubQ6O3E/RMDHBUkNxWrz40l+KJvzN88M287wq 7VxW+tH0CMYvxl5z6R07JwZBmqQhrfFRUTQAod+QSRka/dB9fsKnuBV+4zI9AT26fCeW y1nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3HIpGwrYB10PzmBcbjFXxhFhkeCIzpnI1MEngPjPqOo=; b=jDLHUPHQOO71u1wQbgVSl5eBr8fNd3KFPdzmtk/siQmMRKr7RcgOPmbbSy0fBX9gfk tm7q0RMd3B+2YYVexpw4TzrV2pjrVKXKE3Dvy9lx/m0/L1y7cX7bP/KgMyoAK/klT8qm BMgWXni0cToYW41KtolJf0cEx6anZsKW1wiTdrymqCEGHisY+OGHawrrZhJgI4JA0cP+ kq2xBiMZzGvm6ogC82IPoPg124UdFkMIS9R/PLGo5Bkp91kwD8V0gv4xQ/rAYp0r3Zup n+UhSEN6PM4Kmbgpem6564XVGl+4WjWOQD7s4faBsbwP6te386pyFAKRt83dg1mp7quG 0niQ== X-Gm-Message-State: ALKqPwek4ae0pQDosG9DUbwfIoqY23XwRHa0gbHgni1sxPR2ygbDlB/0 z8qdevP8MaYaxRICi0arSPHA1DkN4Gf6HP3WOSY= X-Google-Smtp-Source: AB8JxZqkUbN7cFmRTgqyYlAEIxkr7MkcU/WyE6qg6nigYCfwbUyXIUpFKI0c373nCPTSLjkP4cz+jTaTsFqE4nERv9Y= X-Received: by 2002:a2e:96d2:: with SMTP id d18-v6mr6889233ljj.21.1526383831577; Tue, 15 May 2018 04:30:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.131.76 with HTTP; Tue, 15 May 2018 04:30:31 -0700 (PDT) In-Reply-To: References: From: Andreas Nilsson Date: Tue, 15 May 2018 13:30:31 +0200 Message-ID: Subject: Re: Configure jail in /etc/jail.my-jail-name.conf while allowing auto-start with "service jail start" To: Andreas Sommer Cc: Mailinglists FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 11:30:34 -0000 On Tue, May 15, 2018 at 1:17 PM, Andreas Sommer via freebsd-jail < freebsd-jail@freebsd.org> wrote: > Hi all, > > as I can see, this combination simply isn't part of /etc/rc.d/jail and > jail(8). > In fact, jail(8) always only reads one config file (`-f` parameter, default > /etc/jail.conf). > > This also relates to why ezjail was still not ported to use jail.conf > [0][1]. > > It would be a great fit to automated configuration management (e.g. via > Ansible > or pkg POST-INSTALL scripts) because it allows overwriting complete files > instead of having to edit the global jail.conf to make changes. > > Jail configured only in /etc/jail.my-jail-name.conf: > > > # service jail onestart > > Starting jails:. > (nothing started because jail not recognized as configured) > > Jail configured in /etc/jail.my-jail-name.conf and "mentioned" as > `jail my-jail-name {}` in /etc/jail.conf: > > > # service jail onestart > > Starting jails:jail: my-jail-name: new jail must persist or attach > (this means only /etc/jail.conf was parsed) > > Any way to achieve this? I assume the answer is no, so here's a suggestion: > what about having jail(8) read/merge configuration from another file? > > Example: > > # cat /etc/jail.conf > > my-jail-name { config = "/etc/jail.my-jail-name.conf"; } > > # cat /etc/jail.my-jail-name.conf > > my-jail-name { ...config goes here... } > > Thanks, > Andreas > > Hello Andreas, at least on -CURRENT the files are read as long as the jail names are in jail_list in rc.conf. It is though somewhat frustrating that you do not get defaults set in jail.conf, so you need to specify stuff like persist in jail.$name.conf Best regards Andreas From owner-freebsd-jail@freebsd.org Thu May 17 17:52:38 2018 Return-Path: Delivered-To: freebsd-jail@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 36913EDB5D4; Thu, 17 May 2018 17:52:38 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from mail.physik.tu-berlin.de (mail.physik-pool.tu-berlin.de [130.149.50.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C8EA46CE0D; Thu, 17 May 2018 17:52:36 +0000 (UTC) (envelope-from fabian.freyer@physik.tu-berlin.de) Received: from [192.168.119.1] (wlan-141-23-160-161.tubit.tu-berlin.de [141.23.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.physik.tu-berlin.de (Postfix) with ESMTPSA id 51E5561FD0; Thu, 17 May 2018 17:43:59 +0000 (UTC) From: "Fabian Freyer" To: freebsd-jail@freebsd.org, freebsd-hackers@freebsd.org Subject: sizeof jail parameter value strings Date: Thu, 17 May 2018 19:43:57 +0200 X-Mailer: MailMate (1.11.2r5479) Message-ID: <6BDE831C-48AC-4FA3-B0EC-C4B7D275AFFE@physik.tu-berlin.de> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_A00A7A58-F35D-4F7C-AEB5-82B656D8CD52_="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 May 2018 17:52:38 -0000 This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_A00A7A58-F35D-4F7C-AEB5-82B656D8CD52_= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello lists, =46rom jail(3): > The jail_getv() function takes a null-terminated list of name and v= alue > strings, and passes it to jail_get(2). It is the caller's responsi= bility > to ensure that the value strings point to buffers large enough to h= old > the string representation of the returned parameters. What exactly does =E2=80=9Clarge enough=E2=80=9D mean here? Is there a wa= y to query the size of the corresponding kernel buffers at runtime? Is there a maximum length =C3= =A0 la MAX_JAIL_PARAM_LEN that the string representations of the returned parame= ters are guaranteed to be shorter than? I=E2=80=99m currently implementing a rust wrapper[1] around the jail(2) i= nterface, and am not sure how large buffers for the string parameters I=E2=80=99m querying= with jail_get jail_set have to be. Fabian (I=E2=80=99m not on the freebsd-jail mailing list, so I=E2=80=99d appreci= ate being kept in the CC) [1] https://github.com/fubarnetes/libjail-rs --=_MailMate_A00A7A58-F35D-4F7C-AEB5-82B656D8CD52_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQJWBAEBCgBAFiEEX6JoxdmEemcFacQZmealkcs85+YFAlr9v10iHGZhYmlhbi5m cmV5ZXJAcGh5c2lrLnR1LWJlcmxpbi5kZQAKCRCZ5qWRyzzn5vs9D/40QAEzqkm2 BCyUzh4lJ1uihMPU8x1u1L+pef7ocBJ8zVX/atLAroX5+08zlT8crZqMmz7fvzaa Ba4M3xwIrg0n5OHVWoskPlLs7T0N1WazfIzd733/S5FKfAp8c6GMn1QnMEmTHzzw 45vA0XlIb+0AeiDn+ydcb2AMrpFE6KMq33MmI5qBWzrzsfbRl3rj9jjATcnCZbGq IR11+LAk/jbJgOHEiWWuM2ErFrzsZ1Gv/OI+hiNYiqb7hRM9waTRzLBoQmOdMbUq CgfCuF780mFJxUfLSRv466ISssmmyyA4npv4QKBzVB19raltoJeP0hTn/vIUYcKn bVte/QouOlVJgGFI63zOFBLYY+W6P/7Cq+MlYQADRg3VSWZwekUgr/Ptjc7UpJiV k1PZGSXmh1Vv+soK0b2CbXj/WxuA3hOaFt4cT60R7QmNlVoYDrRNOQ60OEOB/nO8 pm/grbM2ECFn1CpaRWJfp3BDJ9/3tfbvDh/hFa1IDMaWhf6QkJlEpYpzYVDVxrL6 m9SGtPA4RQ1d/FYUJWU3xMf0k6gSe9tLSBz/D2SQ38THDO9+035I85To7aChtav5 AVdWob4OCBLwOKsp594uQkyVHuHKS3d3rf2Piu+hOtioBRcPfJJlUvCgERx6dRoY VOtU+YhlDyso81qzvq4s+oLptmOjf1inRQ== =J/MM -----END PGP SIGNATURE----- --=_MailMate_A00A7A58-F35D-4F7C-AEB5-82B656D8CD52_=-- From owner-freebsd-jail@freebsd.org Fri May 18 11:04:18 2018 Return-Path: Delivered-To: freebsd-jail@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 9BA51EF1A74 for ; Fri, 18 May 2018 11:04:18 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 E54077139B for ; Fri, 18 May 2018 11:04:17 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id r2-v6so13355646lff.4 for ; Fri, 18 May 2018 04:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=k/7vZ0I7U8pxMreasLUTyEKoBWVJcfgYfP3IaDJ2ud4=; b=kshOm2H1v3mc6H6OWl+E++iId4NKGdbptjRUCc0pOA8BagZLIQdW1jggz4DiWlehQX SGzudmm0q5VQYiqEBFtvzoCg1Ex7JXtZAyZbALb3Lk9xa5XkktMtxWAs46+HYVsUFFxR XGeY6012abh9U7Hht9RG37qzHjplYHHYhCYGYWIGHK7P+yufK5GFFIp6OjJWp9pH1K1O Rp3b3wSIsg7ebPiTvlKa26ZJswS7u9yNlrTR8FC8V5tnPfOQrjaFsl1B/CpMPqsKih42 Bbhyk4rQiQFVnWEfKAkLjtRwPmtvKe5AcdklEzGD+cCc/qqwKscDc0graZfWXetvSwmy BHOw== 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; bh=k/7vZ0I7U8pxMreasLUTyEKoBWVJcfgYfP3IaDJ2ud4=; b=g8xtiQcTBKkDCWf7rQUiEMmOpEJZGVN8hEEkarD6R8wxOtHkYLA6YszTWaCSS+UBfL BUKRKVsYBShZ9rEYPRuaA46hT37a4zYtSwiHW1Q0AEeMV/EbC69zrsYjpQWJTKWZW83A z0vqvniM9PzNOszEr/AGBT1b/JMQHJ41ltjMxIJwKT8u5cfRtRibxiNLcq2TOfGraLPR GjFajqMnMyDOVRJrsUdodb6xT+TFkttXnG95I4iRRfPzH/QCvajLShFdX5lCcNK2+qRc 71QUFEgsJ+LPjwUHcFrRA4PDO7dm9ZnTNpv0l5e87Lq+S2hovKhlAxtai/kVfresaNJB vVYQ== X-Gm-Message-State: ALKqPwf+M0C3XqRdZkkwxA+qWhsuC3RnaliGQUE8Kds+3+4lFwBR5Xmx iRoTirEX8DZ95UVB1+kwRdBK9dJenSFT3GUD1FY= X-Google-Smtp-Source: AB8JxZqQirdsEnIoH/faWz0wGCV3Vk728WhKmeWVB5bJWnFVZkaPV5LisjNPZV3fuK4Btl+1rjoYEIm4hNOvF+LZfIc= X-Received: by 2002:a2e:4949:: with SMTP id b9-v6mr5715752ljd.116.1526641456316; Fri, 18 May 2018 04:04:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.131.76 with HTTP; Fri, 18 May 2018 04:04:15 -0700 (PDT) From: Andreas Nilsson Date: Fri, 18 May 2018 13:04:15 +0200 Message-ID: Subject: rc.conf kld_list vs kern.securelevel To: Mailinglists FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 11:04:18 -0000 Hello, I recently configured a system where kern.securelevel=1 would be good, but noticed that modules listed in kld_list in rc.conf is then not loaded. Would it not be a good to either explicitly state that kld_list cannot be used with kern.securelevel, or have kld run before sysctl? Best regards Andreas From owner-freebsd-jail@freebsd.org Fri May 18 13:48:17 2018 Return-Path: Delivered-To: freebsd-jail@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 3AA2DEA8BD2 for ; Fri, 18 May 2018 13:48:17 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC55276924 for ; Fri, 18 May 2018 13:48:16 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id D884E1AA20 for ; Fri, 18 May 2018 13:48:10 +0000 (UTC) Subject: Re: rc.conf kld_list vs kern.securelevel To: freebsd-jail@freebsd.org References: From: Allan Jude Openpgp: preference=signencrypt Autocrypt: addr=allanjude@freebsd.org; prefer-encrypt=mutual; keydata= xsFNBFVwZcYBEADwrZDH0xe0ZVjc9ORCc6PcBLwS/RTXA6NkvpD6ea02pZ8lPOVgteuuugFc D34LdDbiWr+479vfrKBh+Y38GL0oZ0/13j10tIlDMHSa5BU0y6ACtnhupFvVlQ57+XaJAb/q 7qkfSiuxVwQ3FY3PL3cl1RrIP5eGHLA9hu4eVbu+FOX/q/XVKz49HaeIaxzo2Q54572VzIo6 C28McX9m65UL5fXMUGJDDLCItLmehZlHsQQ+uBxvODLFpVV2lUgDR/0rDa0B9zHZX8jY8qQ7 ZdCSy7CwClXI054CkXZCaBzgxYh/CotdI8ezmaw7NLs5vWNTxaDEFXaFMQtMVhvqQBpHkfOD 7rjjOmFw00nJL4FuPE5Yut0CPyx8vLjVmNJSt/Y8WxxmhutsqJYFgYfWl/vaWkrFLur/Zcmz IklwLw35HLsCZytCN5A3rGKdRbQjD6QPXOTJu0JPrJF6t2xFkWAT7oxnSV0ELhl2g+JfMMz2 Z1PDmS3NRnyEdqEm7NoRGXJJ7bgxDbN+9SXTyOletqGNXj/bSrBvhvZ0RQrzdHAPwQUfVSU2 qBhQEi2apSZstgVNMan0GUPqCdbE2zpysg+zT7Yhvf9EUQbzPL4LpdK1llT9fZbrdMzEXvEF oSvwJFdV3sqKmZc7b+E3PuxK6GTsKqaukd/3Cj8aLHG1T1im1QARAQABzSJBbGxhbiBKdWRl IDxhbGxhbmp1ZGVAZnJlZWJzZC5vcmc+wsF/BBMBAgApBQJVcGXGAhsjBQkSzAMABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AACgkQGZU1PhKYC34Muw/+JOKpSfhhysWFYiRXynGRDe07 Z6pVsn7DzrPUMRNZfHu8Uujmmy3p2nx9FelIY9yjd2UKHhug+whM54MiIFs90eCRVa4XEsPR 4FFAm0DAWrrb7qhZFcE/GhHdRWpZ341WAElWf6Puj2devtRjfYbikvj5+1V1QmDbju7cEw5D mEET44pTuD2VMRJpu2yZZzkM0i+wKFuPxlhqreufA1VNkZXI/rIfkYWK+nkXd9Efw3YdCyCQ zUgTUCb88ttSqcyhik/li1CDbXBpkzDCKI6I/8fAb7jjOC9LAtrZJrdgONywcVFoyK9ZN7EN AVA+xvYCmuYhR/3zHWH1g4hAm1v1+gIsufhajhfo8/wY1SetlzPaYkSkVQLqD8T6zZyhf+AN bC7ci44UsiKGAplB3phAXrtSPUEqM86kbnHg3fSx37kWKUiYNOnx4AC2VXvEiKsOBlpyt3dw WQbOtOYM+vkfbBwDtoGOOPYAKxc4LOIt9r+J8aD+gTooi9Eo5tvphATf9WkCpl9+aaGbSixB tUpvQMRnSMqTqq4Z7DeiG6VMRQIjsXDSLJEUqcfhnLFo0Ko/RiaHd5xyAQ4DhQ9QpkyQjjNf /3f/dYG7JAtoD30txaQ5V8uHrz210/77DRRX+HJjEj6xCxWUGvQgvEZf5XXyxeePvqZ+zQyT DX61bYw6w6bOwU0EVXBlxgEQAMy7YVnCCLN4oAOBVLZ5nUbVPvpUhsdA94/0/P+uqCIh28Cz ar56OCX0X19N/nAWecxL4H32zFbIRyDB2V/MEh4p9Qvyu/j4i1r3Ex5GhOT2hnit43Ng46z5 29Es4TijrHJP4/l/rB2VOqMKBS7Cq8zk1cWqaI9XZ59imxDNjtLLPPM+zQ1yE3OAMb475QwN UgWxTMw8rkA7CEaqeIn4sqpTSD5C7kT1Bh26+rbgJDZ77D6Uv1LaCZZOaW52okW3bFbdozV8 yM2u+xz2Qs8bHz67p+s+BlygryiOyYytpkiK6Iy4N7FTolyj5EIwCuqzfk0SaRHeOKX2ZRjC qatkgoD/t13PNT38V9tw3qZVOJDS0W6WM8VSg+F+bkM9LgJ8CmKV+Hj0k3pfGfYPOZJ/v18i +SmZmL/Uw2RghnwDWGAsPCKu4uZR777iw7n9Io6Vfxndw2dcS0e9klvFYoaGS6H2F13Asygr WBzFNGFQscN4mUW+ZYBzpTOcHkdT7w8WS55BmXYLna+dYer9/HaAuUrONjujukN4SPS1fMJ2 /CS/idAUKyyVVX5vozoNK2JVC1h1zUAVsdnmhEzNPsvBoqcVNfyqBFROEVLIPwq+lQMGNVjH ekLTKRWf59MEhUC2ztjSKkGmwdg73d6xSXMuq45EgIJV2wPvOgWQonoHH/kxABEBAAHCwWUE GAECAA8FAlVwZcYCGwwFCRLMAwAACgkQGZU1PhKYC34w5A//YViBtZyDV5O+SJT9FFO3lb9x Zdxf0trA3ooCt7gdBkdnBM6T5EmjgVZ3KYYyFfwXZVkteuCCycMF/zVw5eE9FL1+zz9gg663 nY9q2F77TZTKXVWOLlOV2bY+xaK94U4ytogOGhh9b4UnQ/Ct3+6aviCF78Go608BXbmF/GVT 7uhddemk7ItxM1gE5Hscx3saxGKlayaOsdPKeGTVJCDEtHDuOc7/+jGh5Zxpk/Hpi+DUt1ot 8e6hPYLIQa4uVx4f1xxxV858PQ7QysSLr9pTV7FAQ18JclCaMc7JWIa3homZQL/MNKOfST0S 2e+msuRwQo7AnnfFKBUtb02KwpA4GhWryhkjUh/kbVc1wmGxaU3DgXYQ5GV5+Zf4kk/wqr/7 KG0dkTz6NLCVLyDlmAzuFhf66DJ3zzz4yIo3pbDYi3HB/BwJXVSKB3Ko0oUo+6/qMrOIS02L s++QE/z7K12CCcs7WwOjfCYHK7VtE0Sr/PfybBdTbuDncOuAyAIeIKxdI2nmQHzl035hhvQX s4CSghsP319jAOQiIolCeSbTMD4QWMK8RL/Pe1FI1jC3Nw9s+jq8Dudtbcj2UwAP/STUEbJ9 5rznzuuhPjE0e++EU/RpWmcaIMK/z1zZDMN+ce2v1qzgV936ZhJ3iaVzyqbEE81gDxg3P+IM kiYh4ZtPB4Q= Message-ID: Date: Fri, 18 May 2018 09:48:02 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FhzckGNiZVS9FNjG4MBOHAUMp00nYKxZj" X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 13:48:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --FhzckGNiZVS9FNjG4MBOHAUMp00nYKxZj Content-Type: multipart/mixed; boundary="ZzRhyTPxTBY9Mkn80w2KObk5ISZAkvBdn"; protected-headers="v1" From: Allan Jude To: freebsd-jail@freebsd.org Message-ID: Subject: Re: rc.conf kld_list vs kern.securelevel References: In-Reply-To: --ZzRhyTPxTBY9Mkn80w2KObk5ISZAkvBdn Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2018-05-18 07:04, Andreas Nilsson wrote: > Hello, >=20 > I recently configured a system where kern.securelevel=3D1 would be good= , but > noticed that modules listed in kld_list in rc.conf is then not loaded. > Would it not be a good to either explicitly state that kld_list cannot = be > used with kern.securelevel, or have kld run before sysctl? >=20 > Best regards > Andreas > _______________________________________________ > freebsd-jail@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-jail > To unsubscribe, send any mail to "freebsd-jail-unsubscribe@freebsd.org"= >=20 It would seem that kld_list would need to be loaded before sysctl run anyway, since the sysctl you are trying to set might not exist until the kernel modules are loaded. Is the securelevel actually set by the sysctl service? --=20 Allan Jude --ZzRhyTPxTBY9Mkn80w2KObk5ISZAkvBdn-- --FhzckGNiZVS9FNjG4MBOHAUMp00nYKxZj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJa/tmaAAoJEBmVNT4SmAt+QPQQAKeagrzZPKl2SyflLjBTXVmu 0S+JuuLgKNr0e0QG528wfF9ZuT2fBJIlP4M+M4e52Z8Cmh0DdmmKBqalMoMECLmk q/iYBMfPZqqXEWy5s/uewBHx/WyjXMMb95Daz8ri4iFQI2wjwTnXqMiJOCbfXXAg RsSjHeh1luERMnvxmscsOqZad+A33GVfzUii+uIWWdO77In6kusjHrWRyFpnEsvL mDU8i9+0Tl6fDMymxXZZPVrBJrgCQC+GIqYIlG+v6onW8RSu5psqf9qD0pbDhLSn bX3mhigB64BL/JQvFWJuC6vr4uWipLNFceIbG6adGvs4bYmwGA2wEqUpQt3onEm6 DIntCd+PWT1v+aZ60VUi+1pFC1bS0Z1plRapOEkKv3XbHfjpj5Gtx7ZEY7920zh3 1CGZnct7I3BTKQzYWAATiCYInrV3/KZXBO0DnLDw5PQi45Qf8CqAvGCKuaNObSGY NQxCE8FkoiqlyGb7NcN6R01DUHmdOnYa9rlWbgLcLNNTwit7k+gX4cg8nhVgmEC0 XkSR/4Xx40PRsmgHfccte1+EiarmhLrdjUH9sT+7oc8nryWG/+c/r0AuLN/xcz1M 7nCoed330NwpDpWIKruet1bXnE6qdOozMThS9lhHipxAhuvPndMvkqNmZ1agVjFA xJ7PLMckTxAXnpag1YZ3 =t096 -----END PGP SIGNATURE----- --FhzckGNiZVS9FNjG4MBOHAUMp00nYKxZj-- From owner-freebsd-jail@freebsd.org Fri May 18 14:16:03 2018 Return-Path: Delivered-To: freebsd-jail@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 556B6EA988F for ; Fri, 18 May 2018 14:16:03 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (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 AF38877E9C; Fri, 18 May 2018 14:16:02 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x243.google.com with SMTP id m17-v6so14197223lfj.8; Fri, 18 May 2018 07:16:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=x+RtSI6xznAWycMo4Qjr7uJAsfpXUQ0OwUxT+uZjkRk=; b=HLwC/IdIEMrHAb1roGrXGKELTdHfS1mIGElB7tqSrFElJS0V+HClYo4yhJF9hZ6+cX hp2ZH+DmnaWeC9vUUH8YKywXPGL3e3AHKVdwqEyysJQOe9lHk6T7Fs74QRxLs9RFuOZo xqR4NSOcGtkDNWV4K8JfhvSxVbwS75b4G5rkcJfqUne1/MvaQ8Gxjd9GpJd1qkDyShDl RreaPBfi9j6eQIDGQ/0H0bARIou7J1zR/CSoRurGYzK5b50Jjw4y+vSsfZbqf8fd739m lHiVmTw+Dui6Q2dihY9d2AkF7xCYByYLG/QcFtzbslTK758+sH81YMmsgE4PaWQHGPJ5 sy0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=x+RtSI6xznAWycMo4Qjr7uJAsfpXUQ0OwUxT+uZjkRk=; b=Xkxwh+avDmORiRg9MwMBirOkoqyRRDGNpB2QJACPzeRR7ZTF5cAB9tkcNeybBT88O2 GymBvnXY0wmoRoCybM4DzBHQmbihgw/vQEV0riEsL4JC0q7hdFe/v4aCoVoSnPhQEBZg QgIswxLH124Kd/f0eHJ1ygpX29cC3FQQDmkpJpMn0bIO74I3yABQhZeYrIOkybfN8wCo VcO+BTCa7vBaEaeFCfRJ8G9cnueaql8/wfZfx4dvH4O3h/d/AyvLVc8+B8N13HfoX/Tg nmiaOH/Dq8KdbUk2LJMoeHidXu9fZIU0mzCVz+OXM4uU7wm6n/SXdxJ1+V8dXlYDW9dI RvEA== X-Gm-Message-State: ALKqPwd6xz3mm9+Nvs+meEWKucFnEUE/HzaE60N7u8D3nlu2FkUJybuI lMvEX4JKhlgxTeEe9VydsDOmBZsZlClcPsJcqpA= X-Google-Smtp-Source: AB8JxZr75GRcubBoFHGsS5Q6VM56/Du8MDggZOzc2IGyL2AtDp9kAo1iHvgxWv5xWSncUEHfIBD65NqDKTA71U4SkOU= X-Received: by 2002:a2e:4949:: with SMTP id b9-v6mr6211024ljd.116.1526652960969; Fri, 18 May 2018 07:16:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.131.76 with HTTP; Fri, 18 May 2018 07:16:00 -0700 (PDT) In-Reply-To: References: From: Andreas Nilsson Date: Fri, 18 May 2018 16:16:00 +0200 Message-ID: Subject: Re: rc.conf kld_list vs kern.securelevel To: Allan Jude Cc: Mailinglists FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 14:16:03 -0000 On Fri, May 18, 2018 at 3:48 PM, Allan Jude wrote: > On 2018-05-18 07:04, Andreas Nilsson wrote: > > Hello, > > > > I recently configured a system where kern.securelevel=1 would be good, > but > > noticed that modules listed in kld_list in rc.conf is then not loaded. > > Would it not be a good to either explicitly state that kld_list cannot be > > used with kern.securelevel, or have kld run before sysctl? > > > > Best regards > > Andreas > > _______________________________________________ > > freebsd-jail@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-jail > > To unsubscribe, send any mail to "freebsd-jail-unsubscribe@freebsd.org" > > > > It would seem that kld_list would need to be loaded before sysctl run > anyway, since the sysctl you are trying to set might not exist until the > kernel modules are loaded. Is the securelevel actually set by the sysctl > service? > > -- > Allan Jude > > Hello Seems I managed to send to wrong list :/ Yes, values from sysctl.conf are being applied, i guess by rc.d/sysctl script, so that seems to work. Adding # BEFORE: sysctl to rc.d/kld didn't help, does one have to do anything special to reevaluate rc-script order? Best regards Andreas From owner-freebsd-jail@freebsd.org Fri May 18 17:01:31 2018 Return-Path: Delivered-To: freebsd-jail@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 B6F3CEAE45C; Fri, 18 May 2018 17:01:31 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org (gritton.org [199.192.165.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gritton.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F3BC7F0CB; Fri, 18 May 2018 17:01:30 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org ([127.0.0.131]) by gritton.org (8.15.2/8.15.2) with ESMTP id w4IGnFl5033855; Fri, 18 May 2018 10:49:15 -0600 (MDT) (envelope-from jamie@freebsd.org) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 18 May 2018 10:49:15 -0600 From: James Gritton To: freebsd-jail@freebsd.org Cc: freebsd-hackers@freebsd.org, Fabian Freyer Subject: Re: sizeof jail parameter value strings Message-ID: X-Sender: jamie@freebsd.org User-Agent: Roundcube Webmail/1.3.6 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 17:01:31 -0000 [Sorry about bad headers and formatting - I took this off the archive page] "Fabian Freyer" wrote: > From jail(3): > >> The jail_getv() function takes a null-terminated list of name and >> value >> strings, and passes it to jail_get(2). It is the caller's >> responsibility >> to ensure that the value strings point to buffers large enough to >> hold >> the string representation of the returned parameters. > > What exactly does "large enough" mean here? Is there a way to query the > size of > the corresponding kernel buffers at runtime? Is there a maximum length > a la > MAX_JAIL_PARAM_LEN that the string representations of the returned > parameters > are guaranteed to be shorter than? > > I'm currently implementing a rust wrapper[1] around the jail(2) > interface, and am > not sure how large buffers for the string parameters I'm querying with > jail_get > jail_set have to be. There is a way to find the length of a string parameter, though there isn't a good library interface for it. The security.jail.param.* sysctls describe the form of the parameters, giving the type. The "contents" of these sysctls are generally unused (and set to zero), but for string parameters there's actually the max length of the string (itself in string form). For non-string parameters, the length in string form depends on the type of the parameters, so for an int you'll need as long as the string representation of an ant can be, etc. I don't know how much good C code will do for you for Rust work, but you might want to take a look at jailparam_type() in the libjail source code. It gets more complicated with array parameters, those that can hold an arbitrary number of values. The IP addresses are the best example of that. jail_getv() just isn't a good fit for such a parameter. I would recommend skipping out on jail_getv(), which is really only good for getting a few well-known parameters, and instead use the more complete but more complex jailparam_init/get/export/free. Again, if C helps, take a glance at the jls source. - Jamie From owner-freebsd-jail@freebsd.org Sat May 19 04:46:24 2018 Return-Path: Delivered-To: freebsd-jail@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 7A6F5EEDD5C for ; Sat, 19 May 2018 04:46:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 0E7467D20B for ; Sat, 19 May 2018 04:46:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id BC3F4EEDD59; Sat, 19 May 2018 04:46:23 +0000 (UTC) Delivered-To: jail@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 A9E67EEDD58 for ; Sat, 19 May 2018 04:46:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 35DC77D209 for ; Sat, 19 May 2018 04:46:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7F6BA266A9 for ; Sat, 19 May 2018 04:46:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4J4kMuh030834 for ; Sat, 19 May 2018 04:46:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4J4kMlt030833 for jail@FreeBSD.org; Sat, 19 May 2018 04:46:22 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 228351] cannot unhide log or tty with devfs.rules Date: Sat, 19 May 2018 04:46:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: jail@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 04:46:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228351 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |jail@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.=