From nobody Tue Feb 22 06:34:07 2022 X-Original-To: freebsd-questions@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 1E3E919DE9CE for ; Tue, 22 Feb 2022 06:34:21 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) (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 4K2qC002bZz3HhT for ; Tue, 22 Feb 2022 06:34:20 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: by mail-pj1-x1033.google.com with SMTP id j10-20020a17090a94ca00b001bc2a9596f6so1556070pjw.5 for ; Mon, 21 Feb 2022 22:34:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=koR0HNrhlY4KTLLuUA6OO0m+hBW/Jb4aU/H5mbS1cyk=; b=Huxhbvfsmp5TTa8+N9Zc+KxGrnkJC/okBNXr4mJYdFQOHpZZh5MMlflBOFv271fw4J gHtw4HxbzViHGk0UCS7oMJXXvqGLFPSIK2dF+yd8W56iTOPCY3bNH+N8VYonaJWjYzH9 wcTq4sL7klfBzPgmFhMHNV1LJUmGQz5XXianiSdnDbv5NOc10h0cZCQrM1b2+cZ4hFQ2 Jwd60M/3Ns+/BRP1qSSJ4jabjhtjorlvW4RofbvY9NJGQXyCMrYnUxwZx1ITFg5EO7sR ZjIvr/ma5Dgf8will7FAcwh2plOWDu9IuKc1Rlz9Fy2ViiXJ2Zw4iB5+pMVtzm0vvb20 T3yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=koR0HNrhlY4KTLLuUA6OO0m+hBW/Jb4aU/H5mbS1cyk=; b=Os1gtokdoQcFrDTMl1yuBHh0saOdmDClRuLag23ety5MoGr6N0XlEj5dPxsEL0WoV8 kSBTgV3QDdolnjRGUGdRLW5LpCH5I4n1mlJFs9+Bxt1s1S5p/Xxpj6AAR1AaPsbPKyQI i5MgkIde1iMYgq5nhmUC5KcRjRQ+lPcL/tPT4XPAbLiQSEImVxcaMwGtTsztE82duXXW ZHMaaDdpyd/8NG9ZotUsttlbLZufHRK+2LiSHppexilRVK526kG1DeLAf3e6lFkjO27/ I1zp30ZA5kGv21N9QLS0EfiOKfd7BZtk/dt+3O1PeRr0opY5sVFz6KVWFj2bCuB96rU0 4Isg== X-Gm-Message-State: AOAM531IltNiuaKTsMT8DbwSqM+ht6da3D5uwWX8iPLZCtxZFJqpKLt3 epLDRUeh6uHTgJOxZKQnLpmuxq+wkdFmgYeNO9SwESyzMg== X-Google-Smtp-Source: ABdhPJx0MQI7bjX7ULq4qFg0KqiFVl/pCaJF5anty+yxvXPRFalqZe+HttdqyEojjLJEl/tdGSf5GrlF46bGWb/TibY= X-Received: by 2002:a17:90b:30c9:b0:1bc:43:11f1 with SMTP id hi9-20020a17090b30c900b001bc004311f1mr2676358pjb.86.1645511658863; Mon, 21 Feb 2022 22:34:18 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 References: <20220222011846.76558bae4f153f024cae3349@3dresearch.com> In-Reply-To: <20220222011846.76558bae4f153f024cae3349@3dresearch.com> From: Paul Procacci Date: Tue, 22 Feb 2022 01:34:07 -0500 Message-ID: Subject: Re: sshd refuses connection To: Janos Dohanics Cc: FreeBSD Questions Content-Type: multipart/alternative; boundary="000000000000e67e8805d895897f" X-Rspamd-Queue-Id: 4K2qC002bZz3HhT X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=Huxhbvfs; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of pprocacci@gmail.com designates 2607:f8b0:4864:20::1033 as permitted sender) smtp.mailfrom=pprocacci@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_SHORT(1.00)[0.997]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1033:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-ThisMailContainsUnwantedMimeParts: N --000000000000e67e8805d895897f Content-Type: text/plain; charset="UTF-8" Hi Janos, The best advice is probably making plans to get a KVM on the machine ahead of time. Barring this, if you already installed the world libs/sshd binary ... keep your current ssh session active and restart the sshd daemon only to see if that solves your problem. Also ensure the config is proper and that all referenced paths resolve correctly and anything referenced has been rebuilt against the new libs as well. If that fails, adding -vvv flags to the sshd upon startup would provide not only you, but us further information as well. Ultimately, I believe if you simply restart the daemon, the problem will resolve itself. ~Paul On Tue, Feb 22, 2022 at 1:20 AM Janos Dohanics wrote: > Hello, > > after rebuilding+installing world+kernel, sshd refuses connection. > > # uname -Kor > FreeBSD 12.3-STABLE 1203506 > > # tail -n 3 /var/log/auth.log > Feb 22 00:59:35 sacada sshd[73065]: fatal: recv_rexec_state: parse config: > incomplete message > Feb 22 01:00:51 sacada sshd[73078]: fatal: recv_rexec_state: parse config: > incomplete message > Feb 22 01:00:56 sacada sshd[73079]: fatal: recv_rexec_state: parse config: > incomplete message > > I'd need to reboot to finish updating, but I'm afraid I'll be locked > out after reboot. > > Would you please advise? > > -- > Janos Dohanics > > -- __________________ :(){ :|:& };: --000000000000e67e8805d895897f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Janos,

The best advice is= probably making plans to get a KVM on the machine ahead of time.
=
Barring this, if you already installed the world libs/sshd binary ... keep your current ssh session active and restart the sshd daemon only to see if=20 that solves your problem.
Also ensure the config is proper and that all referenced paths resolve correctly and anything referenced has been rebuilt against the new libs as well.
If that fails, adding= -vvv flags to the sshd upon startup would provide not only you, but us fur= ther information as well.

Ultimately, I believe if= you simply restart the daemon, the problem will resolve itself.

~= Paul

On Tue, Feb 22, 2022 at 1:20 AM Janos Dohanics <web@3dresearch.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">Hello,

after rebuilding+installing world+kernel, sshd refuses connection.

# uname -Kor
FreeBSD 12.3-STABLE 1203506

# tail -n 3 /var/log/auth.log
Feb 22 00:59:35 sacada sshd[73065]: fatal: recv_rexec_state: parse config: = incomplete message
Feb 22 01:00:51 sacada sshd[73078]: fatal: recv_rexec_state: parse config: = incomplete message
Feb 22 01:00:56 sacada sshd[73079]: fatal: recv_rexec_state: parse config: = incomplete message

I'd need to reboot to finish updating, but I'm afraid I'll be l= ocked
out after reboot.

Would you please advise?

--
Janos Dohanics



--
__________________

:(){ :|:& };:
--000000000000e67e8805d895897f--