From nobody Fri Nov 10 09:07:30 2023 X-Original-To: freebsd-arch@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 4SRXzN1mlpz512C5 for ; Fri, 10 Nov 2023 09:08:00 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SRXzM5n8lz4sCd; Fri, 10 Nov 2023 09:07:59 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1699607267; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OmRgE6haUY6cRcQc19M1+LCR92NlW8sP1QiaBpgvitU=; b=HkVbsYRIEmEmIRtZ6TEvlLLv1BfmKVKt/SbAkyuT50NqijwUTG6wiR0jpOsSxHFWby+cb5 tkSN/C+FitqIfq5v6zfFoI7mzZ2oLfqL2FrSOafoZ2ihaofAVXptxDqoG/krE/2FlYLz0c 66wqxUsM/ytsRs5s7vuSQoIOPQSrIYOi5TeOgHTAWY46dbdeVi7Q39VFBWq5cX0U4QlqQf OF9G0nWodAMYU1DcifWnZoOnWWeEaoOgS3BFeDUQypXSwAbl4/PbKfrSisg13CdmRqCqEq j08Gd88zxNJoHgZOLYFmm+MFDvUbvvHbvB+MynpEs0+JJGxowtdcAqXdZIduSw== Date: Fri, 10 Nov 2023 10:07:30 +0100 From: Alexander Leidinger To: Philip Paeps Cc: freebsd-arch@freebsd.org Subject: Re: Any particular reason we don't have sshd oomprotected by default? In-Reply-To: <5F066A40-CD1D-4D32-850E-0A85D86AE499@freebsd.org> References: <8b9484ba83e373ece0e322e14c924da6@Leidinger.net> <5F066A40-CD1D-4D32-850E-0A85D86AE499@freebsd.org> Message-ID: X-Sender: Alexander@Leidinger.net Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_7d939384733ee467b14b759bc28f552f"; micalg=pgp-sha256 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4SRXzM5n8lz4sCd This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_7d939384733ee467b14b759bc28f552f Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2023-11-09 12:18, schrieb Philip Paeps: > On 2023-11-09 15:54:22 (+0800), Alexander Leidinger wrote: >> We have syslogd oomprotected by default (/etc/defaults/rc.conf). Is >> there a particular reason we don't have sshd protected the same way? >> >> Any objections if I would commit such a change (sshd_oomprotect=YES in >> defaults/rc.conf)? > > I don't have feelings about it either way. It probably makes sense to > optimise for installations that don't have out of band access. > >> I was also thinking about which other daemon we should protect by >> default, but apart from the need to make sure important logs are >> written to find issues which may have caused the oom trigger, and the >> need to be able to login to such a troubled system, I didn't see any >> other service as such critical (we could argue about ntpd, but I send >> to be on the "may be protected" (not for my use cases) and not to be >> on the "has to be protected" side) to include it in this proposal. > > In the FreeBSD.org cluster, we set local_unbound_oomprotect="YES" too. > Without DNS, everything grinds to a halt. Including SSH. https://reviews.freebsd.org/D42544 Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_7d939384733ee467b14b759bc28f552f Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmVN8uAACgkQEg2wmwP4 2IYPHA//SuvdPb34B7t9bLoXk4WdWfYxC7+Msfo+8ewdxA3F2JQ+2BOeVDGm3Psb rcOS46goBpG7ksQpg+0CCfh1Po8xOSJoUpKePHE9xdYCwj+hMVz50pElhEunHYN6 Ws/vKSpX+S/yGcFNheoLWUMT6SGutJq1gIjc7nGDccjl9rafxoFpuKur4erm/lyM nreRYmdFfuEwkgYK4ekzbFWh5WTbcxx0dArd7MtjfGFR+V4PwtzZ24jHiq58W6m6 RudkuLM5Bidh5NCBSejQjHqGLY9+Fa90Qnja7RK2hV9DMJ8MRDWGqLRByuGP92Ot 1CRLoU46DcUCmGi7M+4pWBVpd6Wh2hpADnR1JJXbUYj2kDLi4z6LkX//kuczma78 dqZsCgwJxBxovEte9ElxFparS6U6YU0bJpsnyody3oS7kxpZ7UoZ4m2Mn/uvQ1n5 7/PWzgimjDuElOKXONmDCIN+Fq2qHzmmBLbAhrcemFs9S5jLKkCyRApuXKcO8APy v88oT4qk02ANQpMW/0bKgih9hTGq6B3BBU2th1e3zmMbJLK6N5vCnyxo7eJ/2xLu mqOoLKCBUwCBADanTi6zIZdt1s0NPAFU67EtfHK8OM1E7gB+AB2VwdNsoZIOJMa8 4LUF05c/Xoh0ONt97jJx9KGNgMZymuhRk0G5ROHArM0kVHJO5lI= =PSYD -----END PGP SIGNATURE----- --=_7d939384733ee467b14b759bc28f552f--