similar to: [Bug 323] 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 Summary: arp -n flag doesn't exist under Solaris, ssh_prng_cmds still uses it Product: Portable OpenSSH Version: -current Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system

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.

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:

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

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=107 tim at multitalents.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From tim at multitalents.net

http://bugzilla.mindrot.org/show_bug.cgi?id=229 tim at multitalents.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From tim at multitalents.net

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 | | | |__________| | __________|________________________________

Here is a small patch for OpenSSH 3.2.3p1.. When the package postinstall script runs, it presumes that the package will be installed relative to the current / directory.. If this package is installed as part of a Solaris Jumpstart installation, this will not be the case. Consequentially, the /etc/ssh/sshd_config.default will never get copied to /etc/ssh/sshd_config on the new operating system.

Can''t get proxy arp with arp -s <IPaddr> <MACaddr> pub to work with a 2.4 kernel. I see some evidence in the archive that this was broken in the 2.0.x timeframe and never fixed. Anyone know for sure if it''s broken or working ? (I''m attempting to route a few addresses into a routed network, from the ethernet side of a DSL router that has a /29 public

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

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 found the problem! It was me and it was dumb... This was the network layout: 10.10.10.0/24 1.2.3.0/27 10.10.10.n internal hosts | <----+-----+--------+ +-------+------>to the Internet | | | | Proxied | | | H.323 device Firewall Router eth1 eth0 1.2.3.11

Woops - my fat fingers hit the send key before I could put in a subject a minute ago. Hello - I am using kernel 2.4.27 and running into behavior I don''t know how to explain. I have 2 relevant interfaces. eth0 is external, eth1 is internal. My internal LAN is 10.10.10.0/24. My External range is 1.2.3.0/27 (dummied up). I have an H.323 videoconference device inside my internal

Hi there, I have all my additional software mounted from one central place. Therefore I'm trying to limit all unnecessary local files. Local config files are ok... e.g. keys, ssh_config etc, but why needs ssh_prng_cmds to be in /etc? So why not put it into $bindir? There are no problems doing this with a few manual fixes. So are there any security concerns? Is it possible to make this a

http://bugzilla.mindrot.org/show_bug.cgi?id=318 ------- Additional Comments From dtucker at zip.com.au 2003-05-04 19:12 ------- Does anyone see any problems with the patch id #186? It seems OK to me. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

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

http://bugzilla.mindrot.org/show_bug.cgi?id=318 ------- Additional Comments From dtucker at zip.com.au 2002-11-10 09:11 ------- errno 13 == EACCES. Did you do the "make install" as root? If so did you do it on an NFS filesystem that maps root -> nobody? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.