Date: Mon, 20 Aug 2018 18:35:55 +0200 From: Stefan Bethke <stb@lassitu.de> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: Bind to port <1024 in jail Message-ID: <E6A93DBC-80B4-405E-89E4-77F11B57379B@lassitu.de> In-Reply-To: <30A6405A-6DC1-461E-B45D-CFFF659F80F8@lists.zabbadoz.net> References: <75536186-7D58-498C-BFC6-9284EB7CB444@lassitu.de> <D9F9531F-6EB5-44F9-B8F3-523C0C2E0E44@lists.zabbadoz.net> <2FA29D2E-7C15-4C9D-A59B-98E9EA916891@lassitu.de> <30A6405A-6DC1-461E-B45D-CFFF659F80F8@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 20.08.2018 um 18:32 schrieb Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net>: > > On 20 Aug 2018, at 16:22, Stefan Bethke wrote: > >>>> Is there a way to allow regular processes to bind to low ports? >>> >>> you have to set it on the base system; alternatively with vnet you might be able to change it per-jail. >> >> Do you feel it’s OK to enable VIMAGE in -stable? When I tried last in 2016, I had stability issues, I think related to pf. > > “If you know what you are doing it won’t panic” ;-) I think with 12 I’d be a lot more confident about stability. Most fixes could not and were not MFCed. OK then, should I move to -current and try there? I’ve not tracked -current on a production box in years (I think the last time was around 3 or 4), but I’m willing to give it a go, seeing that the code freeze is about to start. Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E6A93DBC-80B4-405E-89E4-77F11B57379B>