From nobody Mon Dec 12 19:53:48 2022 X-Original-To: freebsd-security@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 4NWC4T4R3jz4Y0T1 for ; Mon, 12 Dec 2022 19:54:01 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NWC4S6Jz0z42Lt for ; Mon, 12 Dec 2022 19:54:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.216.51 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com; dmarc=none Received: by mail-pj1-f51.google.com with SMTP id n65-20020a17090a2cc700b0021bc5ef7a14so1150467pjd.0 for ; Mon, 12 Dec 2022 11:54:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YEDESPhNYryjLNpJ/YYbbVrP8Mh5u2tPkZZuRQbH8mQ=; b=w/bvr4SsZKhbNIbXyy0ORQ7pzPQIeLpcm4QBSv9KBsYXOk2h2Y0/xLHaWB9D6FUV6X pcPx/NQ5R9D8z/bgOoTiZx5zg98HU2iUT80dJztlwIbQXrNWveozbKi8yPkvEw/gGBoL dsrQvxIF7ISAAa+kK8gyy+Dcvwo8Al1X0T7znQbYh+TTU+8HxAUjS9YE0mLr3n+f6i3i KaLqnVZDsghwyrX0Wef9Ag80bPd9VDQ4j4kvHic8FSw/1YNasEsjHJLF9i5oCgXwGA/R oDmi9Feik+F3oCGmh64S8MLgj098IrJwqECyN4TF4PM0T48QH3bsxVQ/YB7JS17FKxCb ALig== X-Gm-Message-State: ANoB5pkrYPC2CvC632x9XsOI0ZhNV3wQ0SzPqFmK7vXYDcEawWBc9sAf aFZgz7+9cUbGtxegG+ZlKBce27CaD2ZFJ0JYcXA= X-Google-Smtp-Source: AA0mqf4TbjCfAVYzJr7Z6p/rW3azc0QiwuxfPJVe2WRQ7GcCI7GKD8J74sjuuydjwyxFvjWDjq5yx5IxTykLAKzF2i4= X-Received: by 2002:a17:90b:818:b0:221:5315:1bf4 with SMTP id bk24-20020a17090b081800b0022153151bf4mr22176pjb.240.1670874839656; Mon, 12 Dec 2022 11:53:59 -0800 (PST) List-Id: Security issues List-Archive: https://lists.freebsd.org/archives/freebsd-security List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org MIME-Version: 1.0 References: <20221130004601.043CE1C623@freefall.freebsd.org> <3dc86282-165d-8562-5cba-0da9896557b9@sentex.net> <2b590fd0-8b02-1344-d501-005c6cd9fb8f@sentex.net> <20221130223855.GA89753@spindle.one-eyed-alien.net> <4ce47f73-c48f-22f6-e0c0-0bd03452bcda@sentex.net> In-Reply-To: <4ce47f73-c48f-22f6-e0c0-0bd03452bcda@sentex.net> From: Ed Maste Date: Mon, 12 Dec 2022 14:53:48 -0500 Message-ID: Subject: Re: FreeBSD Security Advisory FreeBSD-SA-22:15.ping To: mike tancsa Cc: freebsd-security@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-3.06 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.960]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; RWL_MAILSPIKE_GOOD(-0.10)[209.85.216.51:from]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-security@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[209.85.216.51:from]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[carpeddiem]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-security@freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4NWC4S6Jz0z42Lt X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Thu, 1 Dec 2022 at 10:28, mike tancsa wrote: > > My concern is the "evil server in the middle" ... Things like route > highjacking are not that uncommon. I have a number of IoT devices out > there I will need to patch, some still based on RELENG_11. The bug was introduced after releng/11, so those ones won't be affected.