similar to: [Bug 323] New: arp -n flag doesn't exist under Solaris, ssh_prng_cmds still uses it

http://bugzilla.mindrot.org/show_bug.cgi?id=323 ------- Additional Comments From luc at suryo.com 2002-06-30 05:40 ------- A better solution is to install the pacthes that will support /dev/random and /dev/urandom. Then recompile openssl and then openssh. Solaris 8: 112438-01 patch for Sparc 112439-01 patch for x86 Solaris 9: has standard /dev/random and /dev/urandom Not sure if one can

http://bugzilla.mindrot.org/show_bug.cgi?id=323 tim at multitalents.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |keith at ajmani.org ------- Additional Comments From tim at multitalents.net 2002-12-05 16:03 ------- *** Bug 449 has been marked as

http://bugzilla.mindrot.org/show_bug.cgi?id=449 Summary: ssh_prng_cmds has malformed arp command Product: Portable OpenSSH Version: 3.4p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

Gidday, I've just tried installing openssh-2.2.0p1 and found that it globbers my ssh_prng_cmds file which has been customised from the normally installed one. On BSDi 4.0.1 it doesn't detect enough commands for ssh-keygen to be happy. Most of the commands do actually exist, but I have to specify where they are. Could someone please modify the installation scripts to either backup this

Hi, I'm trying to build an openssh pkgadd package which is portable across Solaris 2.6,7 & 8, so I can't rely on /dev/random support and must instead fall back to ssh_prng_cmds for collecting entropy. One of the default commands in ssh_prng_cmds "arp -a -n" is a problem for any (2.6, at least) host which doesn't have an efficient/working DNS or other name resolution

http://bugzilla.mindrot.org/show_bug.cgi?id=449 ------- Additional Comments From keith at ajmani.org 2002-12-01 04:43 ------- Aside: this bug also existed in previous versions of opensshd. My bad for not reporting it earlier. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Nico-- SSH is trying to "get entropy" by taking the (somewhat-deterministic) output of a bunch of system commands, on those OSs that don't provide a /dev/random or its equivalent. The commands that it uses are in /etc/ssh_prng_cmds or its equivalent on your system; just comment out any of the lines (and stop/restart SSHd) in order to change which system commands are used as inputs

The following patch against openssh-SNAP-20000823 allows to override the compile-time "ssh_prng_cmds" file at run time by adding new options to the server and client configurations. (We move binaries around a bit, and this was the only absolute path that couldn't be fixed at run-time). Regards Jan diff -ur openssh-SNAP-20000823.orig/entropy.c openssh-SNAP-20000823.new/entropy.c

Hello, I'm not sure if this is the correct place to send this, but perhaps you can forward it to the proper folks if not... The Solaris port of OpenSSH includes an ssh_prng_cmds file used for collecting entropy, however many of the commands listed in the file are incompatible with Solaris command syntax. Not knowing much about entropy or random numbers, I've modified the file a bit to

This question is primarily for Damien, but if anybody else knows the answer please chime in. Why is it that on systems with no /dev/random or PRNGD or EGD (and I have a lot of Solaris systems in this situation because I don't have root access on them) that the OpenSSH 'ssh' command has to run through all those ssh_prng_cmds every time it starts up? Why doesn't ~/.ssh/prng_seed

Hi people, Please excuse this rather long debug output... $ uname -a SunOS echelon 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-Enterprise $ /usr/local/openssh/bin/ssh -v x.x.x.x SSH Version OpenSSH_2.1.1, protocol versions 1.5/2.0. Compiled with SSL (0x0090581f). debug: Reading configuration data /usr/local/etc/ssh_config debug: Applying options for * debug: ssh_connect: getuid 1002 geteuid 0

My ISP supports connections via ssh. I was using OpenSSH 1.2.3 (portable) on Solaris 2.5.1 (with EGD), and I could connect to my ISP just fine. They're using the proprietary sshd version 1.2.26 as far as I can tell. A connect session looks like: $ ssh-1.2.3 -v -l foobar xx.xx.xx.xx SSH Version OpenSSH-1.2.3, protocol version 1.5. Compiled with SSL. debug: ssh_connect: getuid 390

Heya, I have compiled and installed OpenSSH on a Solaris/Sparc machine and whenever I try to start any of the ssh programs I get "fatal: PRNG initialisation failed -- exiting" Now, I have looked through the mailing lists and have seen some mention that this indicates it can't open the ssh_prng_cmds file, which entropy.c also seems to indicate the problem is. However, this snippet

http://bugzilla.mindrot.org/show_bug.cgi?id=318 Summary: Install failure creating ssh_prng_cmds Product: Portable OpenSSH Version: -current Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

I just finished compiling openssh-2.1.0p3 on a SCO openserver system. I generated the keys fine and genereated the host keys both rsa and dsa without problems. ssh (version1) works great. I tried to use ssh (version 2) and after being prompted to login, it quits. I am attaching a script file of... ssh -v -2 root at sco to see if you can find the problem. Let me know how I can help. [root at

Hi all. I experienced a strange behaviour in the "arp" command when I use the "pub" (publishing) flag. This is the scenario (I know it''s an unusual one, but it''s just for a test): __________ | | | host C | | | |__________| | __________|________________________________

> -----Urspr?ngliche Nachricht----- > Von: Andre Lucas [SMTP:andre.lucas at dial.pipex.com] > Gesendet am: Freitag, 12. Mai 2000 16:37 > An: Bladt Norbert > Cc: 'Karsten Thygesen'; 'openssh-unix-dev at mindrot.org'; > 'carl at bl.echidna.id.au' > Betreff: Re: Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and > other systems, too > > Well

Hi ! Karsten Thygesen wrote: >>>>> "carl" == carl <carl at bl.echidna.id.au> writes: > carl> Marc, I'm seeing the same problem if I use the inbuilt entropy > carl> generator, but if I use SUNWski's /dev/random, it's fine. > carl> ssh also coredumps if I use the built in entropy generator if I > carl> run it in verbose mode.

Two small problems with 2.2.0p1 on BSD/OS 4.0.1, both invoving the internal entropy collector: 1) The ``ls'' commands in ssh_prng_cmds.in all use -n, which isn't valid on BSD/OS and thus caused them all to fail when fixprogs checked them. BSD/OS does, however, have a -T flag which gives complete timestamp information (month, day, year, hour, minute, and second), which seems like a

I have a need to provide ssh client binaries for use elsewhere on several platforms, some without /dev/random support. I can't assume that users will know how to install/run prngd or egd, so I was planning to rely on the builtin prng code. However this require the ssh_prng_cmds file to exist in a fixed location -- which would mean making binaries which either look for it in . or other