827 is a random number.
To be precise, I meant a pseudo-random number. Computers won't ever generate that number in a range of [1, 2^256], even if it's random, because it doesn't
look random.
My point is not that all SHA256 outputs are insecure, but rather you might very well generate one which is not nearly as secure as you think it is.
Okay, I now think I understand what you're saying. Yes. There's a chance it returns me a number that doesn't look random.
Correct me if I'm wrong, but I've never seen an expert say to feed some dice rolls to SHA256 and use the output to generate a wallet.
Depends on the expert. Is it a cryptography expert? If that's so, I don't know any such person who's designing software. If it's a software engineering expert, there is one implementation of the function that takes the dice rolls as an input, and uses the SHA256 of that as a seed.
SeedSigner.
Both using HMAC-SHA(x), which is different from SHA(x).
Both of which, though, are hash functions. Would you feel more confident if you had the dice rolls hashed by HMAC-SHA?