On 2022-04-28 Daniel Kahn Gillmor wrote:
> On Fri 2022-04-22 12:04:15 +0900, NIIBE Yutaka wrote:
>> I found an issue of scdaemon. At upstream development, it is tracked by:
>> https://dev.gnupg.org/T5935
>> When the data is not so large (smaller than the buffer size of token),
>> it works
Control: forwarded 1008573 https://dev.gnupg.org/T5935
Control: tags 1008573 + upstream
Control: severity 1008573 important
This bug report was tagged severity "serious"
https://www.debian.org/Bugs/Developer#severities says that severity
level means:
> is a severe violation of Debian policy (r
On Mon, 11 Apr 2022 11:00:55 -0700 Vagrant Cascadian wrote:
> Same problem with Gnuk, presumably multiple or all smartcards are
> affected?
I found an issue of scdaemon. At upstream development, it is tracked by:
https://dev.gnupg.org/T5935
When the data is not so large (smaller than t
On 2022-04-18, Shengjing Zhu wrote:
> For anyone who suffers this, the workaround is:
>
> Add `KexAlgorithms=-sntrup761x25519-sha...@openssh.com` to ~/.ssh/config
> or `-o KexAlgorithms=-sntrup761x25519-sha...@openssh.com` to the command.
Thanks! That works for me with openssh-client 1:9.0p1-1 an
Hi,
For anyone who suffers this, the workaround is:
Add `KexAlgorithms=-sntrup761x25519-sha...@openssh.com` to ~/.ssh/config
or `-o KexAlgorithms=-sntrup761x25519-sha...@openssh.com` to the command.
--
Shengjing Zhu
On 2022-04-11, Vagrant Cascadian wrote:
> On 2022-03-28, Philippe Grégoire wrote:
>> After upgrading openssh-client to 8.9p1, Yubikey-managed SSH keys
>> can no longer be used. After downgrading to 1:8.4p1-5, it works.
>> I believe this is due to recent changes in OpenSSH 8.9 regarding
>> ssh-agent
On 2022-03-28, Philippe Grégoire wrote:
> After upgrading openssh-client to 8.9p1, Yubikey-managed SSH keys
> can no longer be used. After downgrading to 1:8.4p1-5, it works.
> I believe this is due to recent changes in OpenSSH 8.9 regarding
> ssh-agent communication protocol which GnuPG hasn't yet
7 matches
Mail list logo