A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1926 ====================================================================== Reported By: dannyniu Assigned To: ====================================================================== Project: 1003.1(2024)/Issue8 Issue ID: 1926 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: New Name: DannyNiu/NJF Organization: Individual User Reference: C243.pdf Section: <limits.h> :: Other Invariant Values :: {GETENTROPY_MAX} Page Number: 293 Line Number: 10226-10228 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2025-05-31 15:24 UTC Last Modified: 2025-05-31 15:38 UTC ====================================================================== Summary: Nobody has mistaken bytes for bits when deciding value for GETENTROPY_MAX do we? ======================================================================
---------------------------------------------------------------------- (0007192) dannyniu (reporter) - 2025-05-31 15:38 https://www.austingroupbugs.net/view.php?id=1926#c7192 ---------------------------------------------------------------------- I'd like to amend the desired action to a clarification that explains GETENTROPY_MAX is not meant to indicate the actual entropy that one can obtain from the call, but as a limit which when exceeded, the implementation is allowed to fail. Issue History Date Modified Username Field Change ====================================================================== 2025-05-31 15:24 dannyniu New Issue 2025-05-31 15:38 dannyniu Note Added: 0007192 ======================================================================
