Re: agent draft updated
Mouse <[email protected]> Wed, 23 Aug 2023 20:39:27 -0400 (EDT)
| Newsgroups | gmane.ietf.secsh |
|---|---|
| Message-ID | <[email protected]> |
>> AFAIK the existing protocol uses @openssh.com names, which don't >> need to be registered. Looking at moussh's code, I find it uses [email protected], then [email protected], then auth-agent-req. In the other direction, it uses [email protected] or auth-agent. I don't see any @openssh.com anywhere here. (The only @openssh.com name moussh understands in any sense is [email protected] as a channel request, which moussh never generates and rejects whenever it is attempted by the peer.) It is however possible that, as a consequence, moussh agent forwarding doesn't interoperate; I haven't done detailed interop testing with OpenSSH. I no longer recall where I got the idea that auth-agent-req and auth-agent, without any @domain, were appropriate names. /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML [email protected] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B