Darren J Moffat writes: > The reason for increasing CRYPT_MAXCIPHERTEXTLEN is because crypt_sha512 > produces output greater than 100 chars in some cases. This requires an > updated libc for testing on a live system (and will require that > crypt_sha512 depends on the libc patch for S10 delivery).
It's not quite clear to me how this is supposed to work, but the <crypt.h> CRYPT_MAXCIPHERTEXTLEN constant is described in shadow(4), so it appears it might possibly have been intended as a constant for public use. It's certainly mixed in with a bunch of other public symbols in the same header file, How can we change this constant if we don't know who previously used it and why wasn't this change mentioned in 2007/642? Won't existing callers that sized buffers based on that constant break when faced with an unexpected SHA512 digest? -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
