On 1/16/07, Darren Tucker <[EMAIL PROTECTED]> wrote:
OpenSSH's client traditionally set TCP_NODELAY for "interactive" sessions
(where "interactive" means "has requested a pty", although that's
becoming less and less useful as an indicator). You can try forcing
pty allocation by adding "-tt" to
On Mon, Jan 15, 2007 at 05:52:50AM -0600, Chris Nystrom wrote:
> I have an interactive application including mouse events that I want
> to be secure. I have configured the system to use an openssh subsystem
> and it works well except that we have noticed some inconsistent
> performance. We have fix
You can also try ANDIrand http://www.cosy.sbg.ac.at/~andi/SUNrand/
Regards
Markus
"Geoff Collis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Joel
>
> Sorry I no longer have SunOS binaries, but if I remember correctly the OS
> lacked /dev/random and /dev/urandom so you had to us
It can also be set per socket with setsockopt(2).
How to do something similar in an ssh subsystem, I'm afraid I don't know
Regards
Mark
On 1/15/07, olaf weiser wrote:
Hallo to all,
so far I know, this is a system wide parameter You could set this
per interface or for all connections
I'm upgrading my systems from Slackware-10.2 to Slackware-11.0 and have
come across a ssh/scp error that I cannot resolve.
The network has one server/workstation (running Slackware-11.0 with a
2.6.19.2 kernel), one notebook (running Slackware-11.0 with a 2.6.18.6
kernel), and one laptop (runn
