Lines Matching refs:we

302    the kernel's entropy pool to be initialized, which is the whole problem we
312    for the `uuidd.service` start we already need a UUID that the service is
343    it gets that from `getrandom()`, and thus we have to wait for random pool
349    it's not supported by glibc. And as long as that's the case we are not keen
350    on using it, as we'd have to maintain that on our own, and we don't want to
351    maintain our own cryptographic primitives if we don't have to. Since
354    call these functions. That said, if glibc learns these APIs one day, we'll
371    That's a good question. Ideally the kernel would do that on its own, and we
379    similar for them. Ideally, we'd have an official way to pass such a seed as
401     That said, we actually do implement this with the `systemd.random_seed=`
410     hence we shouldn't write them too often. Writing them once during
412     boot would probably wear the chip out too much, and we shouldn't risk that.