From: Bagas Sanjaya <bagasdotme@gmail.com>
To: youngbludproductions <youngbludproductions@proton.me>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux Networking <netdev@vger.kernel.org>
Subject: Re: [PATCH] Update: Fixing SSH Hardware Key Issue
Date: Thu, 31 Aug 2023 12:59:47 +0700 [thread overview]
Message-ID: <ZPAsU4Ywy44gqlt5@debian.me> (raw)
In-Reply-To: <TQT4YufaV3YuStoFkD5gAcplDIsO76FYEqGQqYzLxrWzgNJ2FwqI__DjgyBZlPSOV6BVJXE54Wf8zroK728hlDXV2Mn5wt9kw2iovRBGPuI=@proton.me>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Thu, Aug 31, 2023 at 05:20:19AM +0000, youngbludproductions wrote:
> Hey folks,
>
> I've been experiencing some weird behavior with SSH and my hardware key. After some investigation, I've identified the root cause and prepared a patch to address the issue.
>
> The patch modifies the SSH code to ensure proper handling of hardware keys, resolving the unexpected behavior. I've tested it extensively and it seems to resolve the problem on my end.
>
> Please find the patch below:
>
> diff --git a/net/ssh.c b/net/ssh.c
> index 1234567..abcdefg 100644
> --- a/net/ssh.c
> +++ b/net/ssh.c
> @@ -123,7 +123,7 @@ static int ssh_handle_key(struct ssh_session *session, struct ssh_key *key)
> /* Code to handle key goes here */
> return 0;
> }
>
> -// Additional changes go here
> +// Additional changes go here to fix the hardware key issue
What? Dummy diff?
Does configuring openssh not fix your issue so that you have to resort
to patching openssh package?
Confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2023-08-31 5:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <TQT4YufaV3YuStoFkD5gAcplDIsO76FYEqGQqYzLxrWzgNJ2FwqI__DjgyBZlPSOV6BVJXE54Wf8zroK728hlDXV2Mn5wt9kw2iovRBGPuI=@proton.me>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZPAsU4Ywy44gqlt5@debian.me \
--to=bagasdotme@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=youngbludproductions@proton.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).