Re: FORWARDING_NOTICE: IP-specific

[der Mouse <mouse%Rodents.Montreal.QC.CA@localhost>]

> First of all, the most recent agent draft appears to be -02, which
> was published over a year ago.  It's unfortunate that there doesn't
> seem to have been any more recent work on this; I'd very much like to
> see an extensible, interoperable agent protocol.

Well, you could always adopt it, since Ylonen/Rinne/Lehtinen seem to
have abandoned it. :-)

> Second, it looks like it actually needs a fair bit of work before it
> will really be ready.  In addition to the problem you point out,
> there's also another issue with forwarding.  The normal case is that
> [...].  Now, who is supposed to insert the forwarding notice?  The
> ssh server? The ssh client?  Both?  This does not appear to be
> well-specified.

| 1.2.  Forwarding Notices
| 
| If the agent connection is forwarded through intermediate hosts (using
| the SSH Connection Protocol agent forwarding feature (described in
| Section ``Agent Forwarding With Secure Shell'' of this document), or
| some other means), each intermediate node (Secure Shell client) should
| insert the following message into the agent channel before forwarding
| any other messages.

Note that "(Secure Shell client)" parenthesis.

> There's also a significant problem with the extension mechanism.
> According to section 1.1, SSH_AGENT_EXTENSION is packet type 301.

!!  That provision is obviously dead in the water, yes. :-)

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse%rodents.montreal.qc.ca@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B