Displaying 3 results from an estimated 3 matches for "entropy_source_t".
2001 Mar 11
4
prng_cmds/init_rng() question/patch
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
2000 May 12
1
Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and other systems , too
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.
2000 May 12
1
Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and other sys tems, too
...o
>
> Well spotted. Doh.
No problem. I had to use the debug mode to find out why the
X11 forwarding didn't work. Finally, the problem was in the client,
though.
> I think an even better way to fix this would be to save the string as
> parsed from ssh_prng_cmds in the command's entropy_source_t, and print
> that in debug messages. It's a tiny amount of memory for what is, as you
> say, useful debugging info.
Sure. I did look at the sources for the first time and
do not know a lot of OpenSSH, yet.
So, just go ahead and apply your suggested fix for the next release
and we are all...