From owner-freebsd-hackers@freebsd.org Wed May 15 17:15:45 2019 Return-Path: Delivered-To: freebsd-hackers@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 CFA001599D56 for ; Wed, 15 May 2019 17:15:44 +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 4C2AB962D5 for ; Wed, 15 May 2019 17:15:44 +0000 (UTC) (envelope-from jhs@berklix.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0C8041599D54; Wed, 15 May 2019 17:15:44 +0000 (UTC) Delivered-To: hackers@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 DDCA81599D52; Wed, 15 May 2019 17:15:43 +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 78AA8962D2; Wed, 15 May 2019 17:15:41 +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 x4FHFY5i020724 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2019 19:15:38 +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 x4FHFXlO072830; Wed, 15 May 2019 19:15:34 +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 x4FHF4eC068579; Wed, 15 May 2019 19:15:21 +0200 (CEST) (envelope-from jhs@berklix.com) Message-Id: <201905151715.x4FHF4eC068579@fire.js.berklix.net> To: Matt Garber cc: Will Andrews , FreeBSD Stable ML , "freebsd-hackers@freebsd.org" , FreeBSD Core Team , Alan Somers 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 12:16:37 -0400." <6CE35CEB-C2AB-47B1-AA86-BC9C91B2B8A6@gmail.com> Date: Wed, 15 May 2019 19:15:04 +0200 X-Rspamd-Queue-Id: 78AA8962D2 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.93 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_FIVE(0.00)[6]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: slim.berklix.com]; FREEMAIL_TO(0.00)[gmail.com]; 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]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.88)[0.883,0]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[berklix.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.37)[0.365,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.65)[0.647,0]; RCVD_IN_DNSWL_NONE(0.00)[68.90.185.94.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; IP_SCORE(0.15)[ip: (0.54), ipnet: 94.185.88.0/22(0.27), asn: 33824(-0.07), country: DE(-0.01)] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 May 2019 17:15:45 -0000 Thanks Will, You make some good points, but all depend on variant circustances. I prefer to be informed ASAP, to make my own decisons with max info ASAP, Not delayed. I want freebsd.org to Not Delay fix announcements into batches. If other admins want to delay being told told to do upgrades until there's lots more to consider & upgrade, they can dummy the delay their receive end, just filtering announcements into their own special box they read once per period. As soon as exploits are in the wild, some will exploit, not announcing until binary updates are ready gives black hats more time. > Whatever other negative things you can say about them, I don't hear enterprise admins begging that Microsoft/Oracle/whoever would dribble out patches one at a time each week instead of combining them like they do; it seems like it works just fine for everyone else. MS make lots of money from the addicted cluless, despite MS loosers frequently complain eg that PCs are locked up again in mid auto update & owner can't shut down to catch a plane or train. MS servers I avoid like the plague. PS Here seems (*) an example of something in text config didnt even need to wait for src/ let alone bin. * Not sure, I'll try it later, got to dash off line. https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/001878.html ] IV. Workaround ] Use 'restrict noquery' in the ntpd configuration to limit addresses that ] can send mode 6 queries. 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.