Robert Schwebel <[EMAIL PROTECTED]> writes:
> next problem on my way to a working environment for my PC/104 system...
> When I try to start lshd it claims that I should run lsh-make-seed. I've
> tried that, but even with --sloppy the call simply doesn't return and
> the system waits forever (or ctrl-c). -v and --trace didn't give much
> more info:
...
> lsh-make-seed: Reading /dev/random...
> <waiting forever>
I'm not sure what is the best way to solve the problem. Some
workarounds:
* Wait even longer, and type like crazy (preferably on a different vt)
at the same time.
* Remove the /dev/random node, or link it to /dev/urandom, while
running lsh-make-seed.
* Hack lsh-make-seed.c, to not try reading /dev/random,
*** /home/nisse/hack/lsh/src/lsh-make-seed.c~ Sun Aug 25 22:16:27 2002
--- /home/nisse/hack/lsh/src/lsh-make-seed.c Thu Oct 3 22:32:55 2002
***************
*** 271,277 ****
get_dev_random(struct yarrow256_ctx *ctx, enum source_type source)
{
static const char *names[] =
! { "/dev/random", "/dev/urandom",
NULL };
int fd = -1;
--- 271,277 ----
get_dev_random(struct yarrow256_ctx *ctx, enum source_type source)
{
static const char *names[] =
! { "/dev/urandom",
NULL };
int fd = -1;
should do.
* Run lsh-make-seed on a different (trusted) machine with more
entropy, and transfer it by floppy or something.
> I know that the system will probably not have enough entropy, at least
> not at the moment (might change a bit when the application is actually
> running), but even a bad key would be better than telnet...
It would make sense to have --sloppy use a timeout, but that's not
entirely trivial to implement. Perhaps --sloppy should imply reading
/dev/urandom rather than /dev/random, that should be easier to
implement?
Regards,
/Niels
_______________________________________________
lsh-bugs mailing list
[EMAIL PROTECTED]
http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
