Displaying 20 results from an estimated 4000 matches similar to: "[Bug 435] internal entropy gatherer"
2002 Jul 22
1
Antwort: Re: Problem with SSHD-Daemon (OpenSSH)
Hi Ben,
here is the output from sshd -d -d -d:
mvs2:sygm:/usr/local/sbin:#./sshd -d -d -d
debug3: Reading output from 'ls -alni /var/log'
debug3: Time elapsed: 459 msec
debug2: Command 'ls -alni /var/log' timed out
debug3: Got 0.00 bytes of entropy from 'ls -alni /var/log'
debug3: Reading output from 'ls -alni /var/adm'
debug3: Time elapsed: 143 msec
debug2:
2002 Nov 14
0
[Bug 435] New: internal entropy gatherer
http://bugzilla.mindrot.org/show_bug.cgi?id=435
Summary: internal entropy gatherer
Product: Portable OpenSSH
Version: 3.5p1
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: ssh
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: udo_guenthner at
2001 Feb 19
7
Packet integrity error. (34)
Hi,
I am using Van Dyke SecureCRT 3.2.1 to access an AIX server running
OpenSSH-2.5.0p1. Using ssh1 with X11 forwarding enabled, the server
reports the following error (in the client session):
Packet integrity error. (34)
This problem was not evident in 2.3.0p1. Running sshd in debug gives the
output:
debug1: sshd version OpenSSH_2.5.1p1
debug1: load_private_key_autodetect: type 0 RSA1
2002 Jul 22
0
Antwort: Re: Problem with SSHD-Daemon (OpenSSH)
Hi Ben,
I test the command sshd -d -d -d several times and mostly the sshd-Daemon not started and sometimes the sshd-Daemon started, with the message:
debug1: Seeded RNG with 16 bytes from programs
debug1: Seeded RNG with 3 bytes from system calls
debug1: sshd version OpenSSH_2.9p1
debug1: private host key: #0 type 0 RSA1
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
2001 Sep 28
0
Not enough entropy in RNG
I have been experiencing problems with remote data collection systems
reporting not enough entropy in RNG. It mostly seems to be self correcting
since a retry of the data transport succeeds. One system however shows
the following everytime an ssh connection is attempted. Interactive
commands do not seem to be affected. I have perused the code but the
entropy gatherer seems to be fairly simple and
2000 May 19
2
Solved: on Solaris, "couldn't wait for child '...' completion: No child processes"
> John Horne [SMTP:J.Horne at plymouth.ac.uk] wrote:
>
> Emanuel Borsboom <emanuel at heatdeath.org> wrote:
>> Trying to install the portable OpenSSH on Solaris 2.6. Compiling from
>> openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd
>> starts fine. First connection from another system works. Child sshd is
>> forked, but the parent dies
2001 Nov 15
0
Case where ssh hangs on exit with 2.9.9p2 on Sol8
Here's the appropriate output with blow-by-blow explanation embedded...
I start by making a connection with X11 forwarding enabled:
polycut:~> ssh -v -v -v -X dazel
OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /opt/openssh-2.9.9p2/etc/ssh_config
debug3: Reading output from 'ls -alni /var/log'
debug3: Time elapsed: 23 msec
debug3:
2017 Oct 13
2
X11forwarding yes: how to debug/setup after xauth fix
On 13/10/2017 08:03, Damien Miller wrote:
> On Thu, 12 Oct 2017, Michael Felt wrote:
>
>> On 08/10/2017 23:32, Michael Felt wrote:
>>> On 04/10/2017 11:07, Michael Felt wrote:
>>>> I do not often use X11 - but when I do I prefer to enable
>>>> X11forwarding, and when finished - turn it off. This is preferable,
>>>> imho, to having
2001 Oct 02
2
New feature: remote entropy gatherer port
[NOTE: I'm new to this list and this is my first
approach to OpenSSH code.]
I've enhanced "--with-prngd-port=PORT" flag to accept an
optional hostname as in "myhost:myport", e.g.:
% ./configure --with-prngd-port=example.com:12345
Although I'm certain that this may cause big trouble if remote
gatherer isn't online (ssh will refuse to open any connection)
I
2000 May 16
1
on Solaris, "couldn't wait for child '...' completion: No child processes"
Trying to install the portable OpenSSH on Solaris 2.6. Compiling from
openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd
starts fine. First connection from another system works. Child sshd is
forked, but the parent dies and logs:
May 16 11:40:56 qtrade-dev sshd[6510]: error: Couldn't wait for child '/usr/bin/
ls -alni' completion: No child processes
May 16 11:40:56
2001 Oct 23
1
ssh/sshd go off in limbo-land after closing remote session (v2.9.9p2)
When I run a remote xterm, the ssh hangs even after I quit the xterm.
Below is the output for the following sequence:
client> ssh -v -v -v dazel xterm
xterm> exit
client> ^C
The outcome is always the same - the ssh doesn't exit with I quit the
xterm... I have to hit CTRL-C on the client side.
polycut:~> ssh -v -v -v dazel xterm
OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL
2000 May 10
3
Trying to build OpenSSH-2.1.0 on HP-UX 10.20
Hi,
I just tried building of OpenSSH-2.1.0 on HP-UX 10.20 and found the following
items:
- The configure command I used at the beginning:
CC=cc CFLAGS="-Ae +O2 +DAportable" CPPFLAGS="-I/usr/local/include -I/usr/local/s
sl/include -I/usr/include/X11R6" LDFLAGS="-L/usr/local/lib -L/usr/local/ssl/lib
-L/usr/lib/X11R6" ./configure --prefix=/usr/local/openssh
2000 Apr 10
1
ls -alni /var/mail
Using the trial internal entropy gathering routines Damien so
kindly provided, I noticed stuff happening slowly. I think I've
traced this to the 'ls -alni /var/mail' taking a long time.
Given that this is likely to hurt a few sites similar to mine
(large number of users with an NFS-mounted /var/mail directory) is
it sensible to put a configure option in to disable this part?
I attach
2000 May 11
1
OpenSSH 2.1.0 under Solaris 8 ...
Compiled great, got both my RSA and DSA keys' generated for Protocol 1/2,
started up fine ... try to connect and get a bunch of errors:
May 11 14:01:47 iris sshd[8578]: error: Couldn't wait for child '/bin/ls -alni' completion: No child processes
May 11 14:01:47 iris last message repeated 3 times
May 11 14:01:47 iris sshd[8578]: error: Command '/bin/ls -alni': select()
2000 Jul 20
3
fatal: Not enough entropy in RNG
Hi,
I'm running openssh 2.1.1p4 on Solaris 7 (sparc). Occationally, when I
boot up the server, the startup script I wrote to start sshd fails to start
sshd with the following error:
fatal: Not enough entropy in RNG
What am I doing wrong??
Is there anything I can do to prevent this from happening?
Is just restarting sshd a valid thing to do??
Thanks for any thoughts,
David
2001 Feb 05
1
I have an odd OpenSSH compatablity issue
I am on Solaris 2.8 with openssh 2.3.0p1 and openssl 0.9.6.
The remote machine is running ssh.com 1.2.20 and Solaris 2.6.
I think the problem has to do with the 1.2.20 KeyRegeneration, because in
the next hour I will beable to get into the machine ok with openssh and
then later in the day I will not beable to ssh in again for another hour.
ssh -v -v sa at myhost.com
SSH Version OpenSSH_2.3.0p1,
2012 May 14
14
[Bug 2008] New: IPV6 Bind to port 22 failed
https://bugzilla.mindrot.org/show_bug.cgi?id=2008
Bug #: 2008
Summary: IPV6 Bind to port 22 failed
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.9p1
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P2
Component: sshd
AssignedTo:
2013 Jul 20
7
Failure to Launch (was override -q option)
Attached is the very verbose ssh output. Just to be perverse, this time two
nodes lost connectivity. The only thing I see is lines saying that the two
connections are lost, although being honest I have no idea what everything
else means. For reference, 8 ssh cinnections were being made at the same
time for a 8x8mpi task.
N.B., since the OS I am using does not have rsh, I am currently using the
2004 May 06
2
ID mismatch
Hi,
When do the sftp to remote server with file system full, sftp connection
get "ID mismatch"
and connection closed. Is it supposed to get the "sftp>" prompt back? I try
with V3.7.1p2 and V3.8.1p1 and have the same result.
Please help.
rdsosl.sef_cdf-831# sftp -v edosuser at rdsosl
Connecting to rdsosl...
OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading
2023 Jun 30
1
Subsystem sftp invoked even though forced command created
On 30/06/2023 09:56, Damien Miller wrote:
> It's very hard to figure out what is happening here without a debug log.
>
> You can get one by stopping the listening sshd and running it manually
> in debug mode, e.g. "/usr/sbin/sshd -ddd"
Or starting one in debug mode on a different port, e.g. "-p99 -ddd"