From nobody Sun May 11 11:20:05 2025 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 4ZwKz23MYmz5vjtZ for ; Sun, 11 May 2025 11:20:14 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout-a2-smtp.messagingengine.com (fout-a2-smtp.messagingengine.com [103.168.172.145]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZwKz10vDnz3mGZ for ; Sun, 11 May 2025 11:20:13 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b="jdHbkH/7"; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=fJeIVUk9; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.145 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-05.internal (phl-compute-05.phl.internal [10.202.2.45]) by mailfout.phl.internal (Postfix) with ESMTP id A76AD13801BE for ; Sun, 11 May 2025 07:20:12 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-05.internal (MEProxy); Sun, 11 May 2025 07:20:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1746962412; x=1747048812; bh=9WfTwSFQFY 87N+NqO13LuCW3WPHwJqOP86N3sQcezUo=; b=jdHbkH/7L9zCqxQtsBCCfexxjs fgAdR5XtlzQ5rwrrma7NZteCVzL+qVXhB1kw0X6Mm30GNUas9Kc6yT13OMgkxHbQ woWhBhS3j/5YdVolzY9LLNeIUUXMOO8lIM576bwOYpo/I0T5thaLUjxrQwQwUkbw WEejMnerDruj4iB8EAIMudB4iADLTY+fPbp0jfU17w4AG6MAWcvHrS082YPI+KAW SDbwMntQxgV7XgVAiqtOiFapqUScM7Nl67WSKcl/NpfSogKVQvpQqyoV2hH9A/nh CrFUllM/AIJYf8ZzrtBjRKm2LQUniKIZija12Ee8DgnuAxliHU+OP448MnaA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1746962412; x=1747048812; bh=9WfTwSFQFY87N+NqO13LuCW3WPHwJqOP86N 3sQcezUo=; b=fJeIVUk9s33Nj+8xF28Oh9kjYrXlcpboYzQ9FcuX+Bl0vqOEvhi TbtgD+pc9Rw5Wg5793CKm5fVH0HgeaqxkQ0A/S/GaHTUAsa9PqZa+ouuuqLhxFcU STJa9OVzMj8XkLY32Vo8dxRmCN71P9M1WKrMtGKpilm/UXeE6c5LmRyg+qr2gx8n mGQGcXZ7cfNUI6NltyjoQyOjeUQkjPlQRKqZsgjKbAoDmGozreqsEgfFiWq3htux cYDbBg0XXCZ3ulA8fiLNDY2NGhxTLo/VttE5oJUQbfX0GPFzxnj/K9P1QehoxO/V m2PtMC18kDk/GmcO+8VpFHWVFdSkeSliwqQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvleekvdegucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhf fvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehf qdhmrdhfmheqnecuggftrfgrthhtvghrnhepkeeluddvlefhieelfefggffhffektdehle elgfdugfdvgeekjeejuddtheehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepud dpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqshgvtghurhhi thihsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 11 May 2025 07:20:12 -0400 (EDT) Date: Sun, 11 May 2025 12:20:05 +0100 From: void To: freebsd-security@freebsd.org Subject: Re: Heads-up: DSA key support being removed from OpenSSH Message-ID: Mail-Followup-To: freebsd-security@freebsd.org References: <76933d66-eff5-4d43-a7a6-98a153e71d77@rlwinm.de> List-Id: Security issues List-Archive: https://lists.freebsd.org/archives/freebsd-security List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-security@freebsd.org Sender: owner-freebsd-security@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4ZwKz10vDnz3mGZ X-Spamd-Bar: / X-Spamd-Result: default: False [0.80 / 15.00]; NEURAL_SPAM_LONG(1.00)[0.998]; NEURAL_SPAM_MEDIUM(1.00)[0.997]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[103.168.172.145:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; NEURAL_HAM_SHORT(-0.19)[-0.192]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.145:from]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[freebsd-security@freebsd.org]; PREVIOUSLY_DELIVERED(0.00)[freebsd-security@freebsd.org]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; MISSING_XM_UA(0.00)[]; TO_DN_NONE(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+] On Thu, Apr 10, 2025 at 10:24:49PM +0000, Bjoern A. Zeeb wrote: > >Is there any chance to keep an openssh (client) port (possibly with known >security risks)? +1 to this. Just the client. Maybe call it openssh-vuln? I can appreciate it being removed in base, in server. But there's lots of otherwise-working gear around that only uses ssh-dss or ssh-rsa. We only need the client. --