Displaying 20 results from an estimated 9000 matches similar to: "troubles with ssh daemon"
2000 Jan 13
3
/dev/urandom
on solaris7/sparc this device doesn't exists
i can use EGD but he very big (perl script!) - in memory it take about
4mb! apache use the same!
why ssh1.27 doesn't requre /dev/urandom on solaris?
what alternatives exists?
2000 Jan 27
6
EGD requirement a show stopper for me
On Thu, Jan 13, 2000 at 17:34:10, Andre Lucas wrote:
> Subject: /dev/urandom
> On Thu, Jan 13, 2000 at 09:24:01AM -0700, SysProg - Nathan Paul Simons wrote:
> > On Thu, 13 Jan 2000, Ben Taylor wrote:
> >
> > > On Thu, 13 Jan 2000, Max Shaposhnikov wrote:
> > > > why ssh1.27 doesn't requre /dev/urandom on solaris?
> >
> > i think the
2001 Jun 07
2
Patch to enable multiple possible sources of entropy
I have a need to have the same OpenSSH binaries run on multiple machines
which are administered by different people. That means on Solaris, for
example, there will be some with /dev/random, some on which I can run prngd
because they'll be installing my binaries as root, and some which will have
neither because they will be only installed as non-root. Below is a patch
to enable choosing all 3
2000 Jan 18
1
Error when compiling for Solaris7
I cannot make openssh on Solaris.
The 'make' fails on the first file.
Here are the commands and the output.
Essentially, I pre-built EGD, SSL, and ran:
configure
make
make errors are listed at the bottom.
Can anyone help me get this compiled on Solaris7?
Steve
sdn at sprintlabs.com
./configure --prefix=/common --sysconfdir=/etc/ssh
--with-egd-pool=/common/bin/egd.pl
loading cache
2000 Apr 21
2
OpenSSH and Irix?
I'd like to install openssh across an Irix cluster where I work, but its
dependency on an "entropy pool" like /dev/urandom is making this
problematic -- especially because EGD has issues with Irix that making it
largely unusable.
Obviously, the original ssh relied on its own random number
generator. While this may not have provided the same degree of randomness
that is provided by
2002 Jan 17
0
[Bug 71] New: configure is looking for zlib but I don't have one and I can't turn zlib off.
http://bugzilla.mindrot.org/show_bug.cgi?id=71
Summary: configure is looking for zlib but I don't have one and I
can't turn zlib off.
Product: Portable OpenSSH
Version: 3.0.2p1
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: critical
Priority: P2
Component: Build
2000 Nov 15
4
Openssh-2.3.0p1 protocol 2 problem
Hi all,
I just implemented (compiled from tarball) Openssh-2.3.0p1 on two different
platform: an HP-UX 11.00 (the client) and a Redhat 6.2 (the server).
On server (Linux RH-6.2) side the following compile options are considered:
# CC="egcs" \
> ./configure \
> --prefix=/opt/openssh \
> --sysconfdir=/etc/opt/openssh \
> --with-tcp-wrappers \
> --with-ipv4-default \
>
1999 Nov 19
1
Fwd: Re: status of openssh for solaris?
Regarding /tmp/random:
Someone has made the same quick&dirty fix as my AIX compile fix, for a lack
of /dev/urandom.
ssh expects some random bytes to be available in that file. I, or someone
else should probably create a more portable way of generating entropy. ;)
//Tor-?ke
>From: Niels Provos <provos at outguess.org>
>To: openssh-unix-dev at mindrot.org
>Subject: Fwd: Re:
2001 Jan 18
1
Announcement: PRNGD 0.9.0 available
Hi!
I have just made the 0.9.0 release of PRNGD available.
PRNGD is the Pseudo Random Number Generator Daemon.
It has an EGD compatible interface and is designed to provide entropy
on systems not having /dev/*random devices.
Software supporting EGD style entropy requests are openssh, Apache/mod_ssl,
Postfix/TLS... Automatic querying of EGD sockets at fixed locations has
been introduced in the
2002 Mar 25
0
buildpkg on solaris 8 OK BUT?..
Hello all,
I was finally able to create the OpenSSH package for Solaris 8 10/01.
The problem I have now is that I will still need to have entropy ready
prior to openssh-3.1p1 package installation. Otherwise there is no entropy
pool available (with the new servers) and key generation fails.
With the previous versions of openssh, I used SUN's
"makeOpenSSHPackage.ksh" script and was
1999 Dec 21
0
Problem with UTMP recording
Hello to all!
I have problem with OpenSSH 1.2.1pre18 on Linux (kernel 2.2.13,
distribution Slackware 4.0). When someone login using ssh, there is no way
to see his presentance with some 'standard' tools (finger, who, w,
users...). Of course, his proccesses are in ps, and so. I've tried to see
/etc/utmp using vi, and there is some entry, but maybe invalid, or
something.
When I enable
2001 Feb 28
2
small patch for configure.in
a small fix for the PRNG/EGD section
--
Tim Rice Multitalents (707) 887-1469
tim at multitalents.net
-------------- next part --------------
--- openssh_cvs/configure.in.old Tue Feb 27 12:56:06 2001
+++ openssh_cvs/configure.in Tue Feb 27 16:54:48 2001
@@ -5,6 +5,7 @@
AC_CONFIG_HEADER(config.h)
AC_PROG_CC
AC_CANONICAL_HOST
+AC_C_BIGENDIAN
# Checks for programs.
AC_PROG_CPP
@@ -1279,14
2000 Apr 03
0
EGD-0.7 released (important security fix)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Howdy all. I've just released version 0.7 ("the Brown Paper Bag" release) of
EGD. The Entropy Gathering Daemon is primarily intended as a source of
randomness for GnuPG, for use on systems which lack a /dev/random device.
version 0.6, which has been available for about 8 months, had a serious and
embarrasing bug in which the gathered
2010 Jun 14
3
[Bug 1781] New: Document how to use Solaris 10 /dev/random
https://bugzilla.mindrot.org/show_bug.cgi?id=1781
Summary: Document how to use Solaris 10 /dev/random
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
AssignedTo: unassigned-bugs at mindrot.org
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 Jan 05
3
openssh-1.2.1pre24 on SCO
Yo All!
Sorry if this is obvious but I am new to openssh. I have used the
original ssh for a while and am familiar with it (and it's
restrictive license).
I am trying to port openssh-1.2.1pre24 on to SCO UnixWare 7.1.0. I
will post the small patches when it is really running.
Two problems, SCO has no /dev/random so I installed egd-0.6. It
usually works but sometimes dies. I have sent
2003 Dec 01
0
No subject
is turned on. Can anybody
kind to confirm with me?
Our network is using a mix of Win2k server, Win2k Pro, Win98, Win95 and
WinMe machines, where the
Win2k server is the domain controller and terminal service applications
server and the Samba is a member
fileserver of the domain. All workstations logon and mount the samba file
services.
We'd like to check if the problem could be solved by
2001 Jan 11
0
OpenSSH 2.3.0p1 on Compaq Alpha
Hello,
I have installed OpenSSH 2.3.0p1 on a DEC AlphaServer 4000 under Tru64 UNIX 4.0F
and on a DEC AlphaStation 200 under Tru64 UNIX 5.1.
I tested Protocol 2 and 1 with RAS authentication resp. DSA authentication an
both work well.
There is one bug: I cannot view the man pages for OpenSSH under Compaq Tru64
UNIX. Are they in a special format which is not understood by the Tru64 UNIX man
2002 Aug 04
0
[Bug 380] New: SSH compiled to use EGD.PL won't start without it!!
http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=380
Summary: SSH compiled to use EGD.PL won't start without it!!
Product: Portable OpenSSH
Version: -current
Platform: UltraSparc
OS/Version: Solaris
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo:
2000 Jun 20
2
Critical EGD handling in 2.1.1p1
Hi,
when running OpenSSH with EGD as entropy source, the sshd server connects
to the EGD socket and leaves it open to re-seed on the fly.
Unfortunately the connection is not checked when re-seeding, so that
a failure or restart of EGD will lead to a "fatal()" abort of the sshd
server process.
Since a dying server process can not be accepted, I would recommend to
not have sshd call it