Date: Sun, 25 Jun 2000 17:12:50 +0200 From: Mark Murray <mark@grondar.za> To: "Jacques A . Vidrine" <n@nectar.com> Cc: freebsd-current@freebsd.org, imp@freebsd.org Subject: Re: HEADS UP! New (incomplete) /dev/random device! Message-ID: <200006251512.RAA17563@grimreaper.grondar.za> In-Reply-To: <20000625100334.C16657@bone.nectar.com> ; from "Jacques A . Vidrine" <n@nectar.com> "Sun, 25 Jun 2000 10:03:34 EST." References: <20000625100334.C16657@bone.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I guess it follows that it is not a good idea to generate keys or > certificates on -CURRENT for a while (until entropy comes back to town)? Correct if they rely on /dev/random for entropy. > I don't know which applications depend on /dev/random providing entropy > and which gather their own. Right. > If so, I think this needs an UPDATING entry, particularly since the > symptoms could outlive the cause. i.e. something to the effect of > ``Keys and certificates generated on -CURRENT on or after m/d/y should > not be used'' and updated again when the entropy is again available. Agreed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006251512.RAA17563>