This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Nick Mathewson wrote:
For example, see the memset calls at the end of: __md5_crypt_r __sha256_crypt_r __sha512_crypt_r The documented intent there is to clear data from the stack before returning, but the compiler is free to remove them IIUC.
Yes, that sounds like it could be a problem. Have you inspected the generated code to see whether the problem actually occurs? That would strengthen the case for a buffer-smushing primitive, even if it's only internal to glibc. (I still see no reason for guaranteeing that any such primitive sets the buffer's bytes to zero -- any value will do so long as it's independent of the buffer's previous contents.)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |