IETF-SSH archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
last-call issues..
I believe that this is the current list of issues raised in the last
call on the core documents. If I missed anything, let me know.
Issues in core documents:
- Trademark verbiage needs to be struck completely.
(editorial change only)
- Niels Moeller: RSA signature encoding should be described as mpuint
rather than as "string"
(editorial change only; touches architecture and transport drafts)
- Subsystem robustness:
The ".cshrc output mixed into subsystem output" issue is purely a
local implementation issue; subsystem cookie text should be deleted.
Advice to implementors should state that server implementations which
allow for subsystems to be "plugged in" in should to define an
interface to subsystem implementations to prevent any extraneous
output (perhaps from a shell) from being mixed into the subsystem
output sent over the wire. (no wire protocol change involved)
Resolution:
need volunteer to provide text for this.
- Wei Dai pointed out a discrepancy between the zlib spec and the
code actually in use which needs to be documented for interoperability
reasons relating to zlib partial flush.
Resolution: wei dai provided corrected text (see archive)
this corrects the spec to match what people have actually
implemented and deployed.
- Wei Dai pointed out that the compression system should be referred
to as "zlib", not "GNU zlib"
resolution: trivial editorial change.
- Darren Moffat: Should be rationale for why every message gets a
language tag.
- Niels M. pointed out that there are current interop problems
between OpenSSH and lsh relating to channel EOF and channel close;
lshd attempts graceful shutdown but doesn't ever get an EOF from
OpenSSH's client.
Resolution: the "forward output until EOF, then close channel"
behavior should be documented as an implementors note.
(need volunteer to supply text)
Possible additional work items raised in last call.
- "denis bider" <denis.bider%globera.com@localhost> mentioned the lack of a
standard for presenting key fingerprints.
Resolution: need volunteer to write a draft for this.
- Wei Dai requested an extension to allow for forwarding of a
server-chosen port ("pick a port, forward it to me, and tell me what
it is").
Resolution: Unresolved. Do we need a new opcode for this or can we
overload the meaning of "forward port zero"?
Home |
Main Index |
Thread Index |
Old Index