similar to: EGD-0.7 released (important security fix)

EGD 0.7 was released this weekend and I would highly recommend that everyone here that uses EGD upgrades. While doing some research last week I found a typo in the add_entropy() function that prevented any new entropy from being introduced into the system (in other words the entropy pool was a recursive hash of 0's). If the commands return in the same order, then the output bits are in

The usual suspects: Solaris 8 gcc 2.95.2 perl 5.60 egd 0.7 openssl 0.95.a openssh 1.2.3 # egd.pl /etc/entropy --- It works the first few minutes and then just stops working. OpenSSH connections started still work, ssh just hangs with a new connection. I've even tried --bottomless; no joy. 0.6 and Solaris 7 worked great. I'm going to try the /dev/random that was mentioned before. Any

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

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

Just tried out ssh in pre13, and still get the EGD problem? :( new-relay:/usr/slocal/src/openssh-1.2pre13> ./ssh -l marc atelier The authenticity of host 'atelier.acadiau.ca' can't be established. Key fingerprint is 1024 ef:36:b5:f8:a3:bb:14:4d:a9:4b:f2:90:9a:bd:bb:00. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added

Greetings, While attempting to build openssh for Solaris 2.6, I ran into a minor problem that should probably be corrected in the next release of openssh. The file pty.c does not #include <stropts.h> to define I_PUSH even though I_PUSH is used when HAVE_DEV_PTMX is defined. Platform: SunOS test01 5.6 Generic_105181-16 sun4u sparc SUNW,Ultra-60 Using: zlib 1.1.3

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

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:

[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

There are a couple of issues regarding egd support in OpenSSH. 1) SIGPIPE is not ignored for the master listener daemon. I put the signal() call early on since it needs to be before get_random_bytes() is called but it could also be placed in the EGD version of get_random_bytes(). For some reason, with prngd I am getting SIGPIPE even though the prngd processes is not dying.

http://cvs-mirror.mozilla.org/webtools/bugzilla/show_bug.cgi?id=380 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From djm at mindrot.org

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

I'm having a bit of trouble generating a host key on an x86 Solaris 8 system. I've gotten the following built and installed: egd-0.7 openssl-0.9.5a openssh-1.2.3 My perl version is 5.005_03. egd is running, and tests fine the egd "make test" and with: #./egd.pl /etc/entropy get 22 sources found forking into background... server starting But when I go to "make

On 22 Jul 2019, at 10.34, Lothar Schilling via dovecot <dovecot at dovecot.org> wrote: > > Hi Arnold, > > thanks for your assistance. I solved the issue right now by changing > > prefix = Shared/%%u/ > to > prefix = Shared/%%n/ > > This omits the @mydomain.de part which holds the dot causing the > trouble. Why this became a problem due to the update I

Hi Arnold, thanks for your assistance. I solved the issue right now by changing prefix = Shared/%%u/ to prefix = Shared/%%n/ This omits the @mydomain.de part which holds the dot causing the trouble. Why this became a problem due to the update I wouldn't know. Regards Lothar Am 22.07.2019 um 10:49 schrieb Arnold Opio Oree: > Hi Lothar, > > I haven't yet had the opportunity to

Am 11.08.2020 um 16:02 schrieb Rowland penny via samba: > On 11/08/2020 14:54, Lothar Schilling via samba wrote: >> Yep, that did it, thanks a lot, "-k yes" wasn't good enough. There now >> was another error, though: >> >> ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' >> object has no attribute

Yep, that did it, thanks a lot, "-k yes" wasn't good enough. There now was another error, though: ERROR(<type 'exceptions.AttributeError'>): uncaught exception - 'module' object has no attribute 'drs_utils' The solution offered and working is inserting ? import samba ? import samba.getopt as options ? import ldb +import samba.drs_utils ? from ldb

Thank you, that's it! virsh vol-list storage VM1   /dev/storage/VM1.img VM2   /dev/storage/VM2.img VM3   /dev/storage/VM3.img [dead] VM4   /dev/storage/VM4.img [dead] A last stupid question (I don't want to make a big mistake ...): Is virsh vol-delete VM3 virsh vol-delete VM4 the right command to get rid of the offending ones? Am 14.05.2020 um 19:10 schrieb Alvin Starr: > >

Hi Amos, I'm a libvirt QE, and I can not understand the setting on libvirt.org for rng device. Could you please help to explain a little? (The xml in https://libvirt.org/formatdomain.html#elementsRng) <devices> <rng model='virtio'> <rate period="2000" bytes="1234"/> <backend model='random'>/dev/random</backend>

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