From owner-freebsd-stable@freebsd.org Wed May 15 15:51:20 2019 Return-Path: Delivered-To: freebsd-stable@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 80B961596556 for ; Wed, 15 May 2019 15:51:20 +0000 (UTC) (envelope-from jhs@berklix.com) 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 E30F79152B for ; Wed, 15 May 2019 15:51:19 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id A07681596421; Wed, 15 May 2019 15:51:19 +0000 (UTC) Delivered-To: stable@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 7C72E1596420 for ; Wed, 15 May 2019 15:51:19 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from slim.berklix.org (slim.berklix.org [94.185.90.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "slim.berklix.org", Issuer "slim.berklix.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9EC9F91526; Wed, 15 May 2019 15:51:18 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from mart.js.berklix.net (p2E52CF95.dip0.t-ipconnect.de [46.82.207.149]) (authenticated bits=128) by slim.berklix.org (8.15.2/8.15.2) with ESMTPSA id x4FFpCGO020019 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 17:51:16 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id x4FFpCAP072297; Wed, 15 May 2019 17:51:12 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id x4FFp0UP067236; Wed, 15 May 2019 17:51:12 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151551.x4FFp0UP067236@fire.js.berklix.net> To: Kurt Jaeger cc: stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. From: "Julian H. Stacey" Organization: http://berklix.com/jhs http://stolenvotes.uk User-agent: EXMH on FreeBSD http://berklix.com/free/ X-From: http://www.berklix.org/~jhs/ In-reply-to: Your message "Wed, 15 May 2019 17:38:36 +0200." <20190515153836.GU20962@fc.opsec.eu> Date: Wed, 15 May 2019 17:51:00 +0200 X-Rspamd-Queue-Id: 9EC9F91526 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.73 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.83)[0.834,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.19)[0.189,0]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; IP_SCORE(0.15)[ip: (0.57), ipnet: 94.185.88.0/22(0.28), asn: 33824(-0.07), country: DE(-0.01)]; MX_GOOD(-0.01)[cached: slim.berklix.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.66)[0.659,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:33824, ipnet:94.185.88.0/22, country:DE]; RCVD_TLS_LAST(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[149.207.82.46.zen.spamhaus.org : 127.0.0.10] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 15:51:20 -0000 Hi, Reference: > From: Kurt Jaeger > Date: Wed, 15 May 2019 17:38:36 +0200 Kurt Jaeger wrote: > Hi! > > > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > > > > Volunteers who contribute actual fixes are very much appreciated; > > > > But those styled as 'management' who delay announcements to batch floods > > > > damage us. > > > > > > 8 announcements and one freebsd-update is easier on the > > > admin and the re-team than 8 announcements and 8 freebsd-update runs. > > > > > > That's probably why they are batched. Because all of the fixes > > > are bundled in one update. > > > > > > If the re-team-capacity is limited, what would be the alternative? > > > Alternative is to for announcers to do Less work: > > Send each announcement when ready. > > The problem is not the announcement, the problem is providing > the freebsd-update. > > If announcements are send when ready, and the freebsd-update is > not ready, therefore, the timeframes to attack systems with unpatched > problems are much longer. True as far as that goes for binary users, but often source patches are available faster, which begs the question: when to announce ? When there's diffs ? When diffs are commited to src/ (used to be the norm *) ? When there's some binary update ? Whne a whole bunch of 8 arrive in 3 minutes ? Gasp ! * I happen to use src/ never use freebsd-update. Equally bound to be some who use binary updates & not source Cheers, Julian -- Julian Stacey, Consultant Systems Engineer, BSD Linux Unix, Munich Aachen Kent http://stolenvotes.uk Brexit ref. stole votes from 700,000 Brits in EU. Lies bought; Groups fined; 1.9 M young had no vote, 1.3 M old leavers died.