data loss with ssh -n

[Pekka Savola]

On Fri, 20 Jul 2001, Dan Kaminsky wrote:
> 1) I have way too much fun with ProxyCommand
> 2) Unless you give a user a *really* restricted shell, sshd_config will
> *never* be the right place to put your security constraints.

Perhaps these should be restricteable.

> As for the larger issues...does the incorrect buffering behavior still
> manifest itself without the -n?  In SSH1 and SSH2?  With and without TTY?

As for SSH2, I don't know unfortunately.  Impossible to test at the
moment.  I could try to get this done if there aren't any other ways to
trace the problem.

So, with SSH1 (tried all combinations of -, -t, -n, -t -n):

 When run as user, problem _appears to_ exist only if:
  1) -n

 When run from cron, problem _appears to_ exist always except if:
  1) -t

(I wouldn't call the tests scientific, but should give the idea)

So there's a hack of using '-t' as a workaround; it works with both.

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords