On Tue, 15 Apr 2003 17:33:11 -0400
Tom Vier [EMAIL PROTECTED] wrote:
On Tue, Apr 15, 2003 at 06:50:24AM +0100, Francis Devereux wrote:
ssh needs a source of randomness to operate (/dev/random), which in
turn needs a pool of entropy which is fed from things like the
keyboard interrupt.
On Wed, Apr 16, 2003 at 08:14:49AM +0100, Francis Devereux wrote:
On Tue, 15 Apr 2003 17:33:11 -0400
Tom Vier [EMAIL PROTECTED] wrote:
On Tue, Apr 15, 2003 at 06:50:24AM +0100, Francis Devereux wrote:
ssh needs a source of randomness to operate (/dev/random), which in
turn needs a pool
Francis Devereux [EMAIL PROTECTED] writes:
No, I'm not sure. If it is using /dev/urandom then the lockups can't
be being caused by the entropy pool becoming empty, because /dev/urandom
won't block in this case like /dev/random would, right?
The symptoms didn't look consistent with ssh not
Since the only difference between your U5 and mine is that your physical
hardware is not mine (meaning maybe you have memory errors, or cpu/fpu
is too hot and is producing problems) and you are behind a firewire, I'd
go with one of those problems.
Of course I means a firewall.
--
Debian
Have you checked the duplex settings on the card? I saw similar things
with my Ultra 5's connecting to Cisco switches because autonegotiation
wasn't working properly, and the U5's were setting themselves to
half-duplex. If I pushed enough traffic across the line when the
duplexes didn't
On Tue, 15 Apr 2003 00:46:37 + (UTC)
Kristjan Onu [EMAIL PROTECTED] wrote:
Also for what it's worth, I haven't seen such problems into a U5,
either with the Woody libssl or later 0.9.6 ones with v9
optimization.
I'm glad to hear others are successfully using U5s. I'm leaning toward
fwiw, i haven't had any lockups, but ssh'ing from my 270mhz ultra5, it takes
much longer for the passwd prompt to appear than it does from even an old
166mhz pentium.
Same here, my Debian Ultra 60 has the slowest ssh-login on all the
machines I can login to. I've had a look at the logfiles and
On Tue, Apr 15, 2003 at 06:50:24AM +0100, Francis Devereux wrote:
ssh needs a source of randomness to operate (/dev/random), which in turn
needs a pool of entropy which is fed from things like the keyboard
interrupt. Your lockups could be caused by sshd stalling because the
entropy pool is
Ben Collins [EMAIL PROTECTED] writes:
You need the v8/v9 optimized libssl. They are in unstable, or check this
list's archives for pre-built ones for woody.
For what it's worth, it's in testing and just requires a libc upgrade
to install. (If you install unofficial debs, check that they're
Kristjan Onu [EMAIL PROTECTED] writes:
I'm glad to hear others are successfully using U5s.
Not conclusive of anything, of course.
I mentioned my problem in an OpenSSH bug report
(http://bugzilla.mindrot.org/show_bug.cgi?id=538), and one person
asked if my server uses ssh-rand-helper. I
fwiw, i haven't had any lockups, but ssh'ing from my 270mhz ultra5, it takes
much longer for the passwd prompt to appear than it does from even an old
166mhz pentium.
--
Tom Vier [EMAIL PROTECTED]
DSA Key ID 0xE6CB97DA
Kristjan Onu [EMAIL PROTECTED] writes:
With my Woody installation, the directories you mention did not
exist. Installing libssl0.9.7 (and ssh 3.6.1p1-1) did put files into
/usr/lib/v9. Moving them out of the way as you suggest seems to help
at least a little,
For what it's worth, the major
On Mon, Apr 14, 2003 at 05:32:48PM -0400, Tom Vier wrote:
fwiw, i haven't had any lockups, but ssh'ing from my 270mhz ultra5, it takes
much longer for the passwd prompt to appear than it does from even an old
166mhz pentium.
You need the v8/v9 optimized libssl. They are in unstable, or check
Also for what it's worth, I haven't seen such problems into a U5,
either with the Woody libssl or later 0.9.6 ones with v9 optimization.
I'm glad to hear others are successfully using U5s. I'm leaning toward
saying there's a hardware problem, but it must not be with the network
card since I've
I have Woody installed on an Ultra 5. Frequently SSH sessions to this
machine seem to lockup. Specifically, I have observed the following:
SSH connections to the U5 box using SSH Protocol 2 almost always fail
before the key exchange can complete.
With SSH Protocol 1 I can login and work for a
It looks to me like you are ssh'ing from behind a firewall (using ipv4)
that has a very short timeout for tcp connections. does this happen
between local machines as well???
If this is the case than it is not related to which ethernet card you use
or which protocol... but just to the firewall
On Sun, Apr 13, 2003 at 07:36:31AM +, Kristjan Onu wrote:
I have Woody installed on an Ultra 5. Frequently SSH sessions to this
machine seem to lockup. Specifically, I have observed the following:
I would blame ssh or libssl. You can also try disabling the v9
optimized ssl libraries by
17 matches
Mail list logo
