Re: SecSH Server functionality on Windows - incomplete

[Markus Friedl <markus%openbsd.org@localhost>]

On Tue, Nov 27, 2001 at 04:03:04PM +0000, Peter M Boyd wrote:
> ---- even if a *N*X Shell is used in Windows instead
> of CMD.EXE, the ablove deficiencies still apply
> [..]
> Is this of any concern to the IETF?

i don't see how this applies to the protocol. have you
checked that the protocol disallows CTRL-C on Windows? have
you checked your implementation for a bug?

it seems this is an implementation issue and not a protocol issue.