search for: nsbd

I was just building binary Solaris packages of OpenSSH for use at our company. While doing so, it occurred to me that the only thing that really stops me from being able to make a binary build totally relocatable in the filesystem tree is the default path. Other than that, I cannot think of any file path that cannot be modified with either a command line option or in a configuration file. Is

We're hoping to switch to updating a large software collection with rsync. Sometimes, we'll be using rsync to push security updates, say for setuid binaries with a security hole. In this case, we want rsync to get rid of the old executable, instead of creating a ~ file or whatever. Sometimes, we'll be using rsync to push updates to programs that people want to leave running a long

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