<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hello,</p>
<p><br /></p>
<p>accidently I identified the root cause for this issue.</p>
<p>I executed this SSH command:</p>
<p>ssh <remoteserver></p>
<p><br /></p>
<p>I didn't use ssh <user>@<remoteserver> on purpose because I'm used to use the same user on remoteserver as on client.</p>
<p><br /></p>
<p>After executing SSH command</p>
<p>ssh <user>@<remoteserver></p>
<p>gpg-agent works as expected and I can login with public key.</p>
<p><br /></p>
<p>One may consider this as a bug, however I'm happy that I found a solution for my issue.</p>
<p>Now I can proceed to next issue: SSH forward</p>
<p><br /></p>
<p>Thanks for your great support!</p>
<p><br /></p>
<p>Thomas</p>
<div id="signature"></div>
<p><br /></p>
<p id="reply-intro">Am 2024-01-16 18:50, schrieb Werner Koch:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">On Mon, 15 Jan 2024 20:03, Thomas Schneider said:<br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">And ssh-pageant is not available for Win 11, but pageant is included<br />in PuTTY.</blockquote>
<br />I didn't implemented or tested the newer --enable-w32-openssh-support so<br />I don't have first have experience. However, Windows comes with an sssh<br />server and an client, which are slighly modified OpenSSH versions. Thus<br />you should be able to simply run<br /><br /> c:\ ssh -v <a href="mailto:snowden@hawaii.nsa.gov">snowden@hawaii.nsa.gov</a><br /><br />The ssh diagnostics enabled with -v should show you what's going on and<br />whether ssh tries to use an ssh-agent implementation.<br /><br />You need to start gpg-agent first, of course:<br /><br /> gpgconf --launch gpg-agent<br /><br />or run any gpg command or kleopatra, etc.)<br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Could you please share some details of your working setup (scripts<br />connecting from Win 10/11 to other servers using SSH).</blockquote>
<br />Okay, let's try it: I just installed a gpg4win 4.3.0-beta and tried it<br />on my testbox (Windows 10.0 build 19045) using my regular token:<br /><br />debug1: Next authentication method: publickey<br />debug1: Offering public key: cardno:FFFE_xxxxxxx ED25519 SHA256:tXYM7ne2kI+ZUw7jGii9LBhoz8uB0ucKv28OSSW6a/g agent<br />debug1: Server accepts key: cardno:FFFE_xxxxxxx ED25519 SHA256:tXYM7ne2kI+ZUw7jGii9LBhoz8uB0ucKv28OSSW6a/g agent<br />debug1: Authentication succeeded (publickey).<br />Authenticated to ftp.gnupg.org ([217.69.76.55]:22).<br /><br />But that should also work with your gpg4win version.<br /><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">the native client you need to add *enable-w32-openssh-support* to your</blockquote>
</blockquote>
<br />Oops, the option is actually *enable-win32-openssh-support*. I try to<br />get it into the Kleopatra config dialog with gnupg 2.4.4 - right now<br />kleopatra can only enable the Unix style ssh support.<br /><br /><br />Shalom-Salam,<br /><br /> Werner</div>
</blockquote>
</body></html>