From 71ae0c724dd49d493621b367d17079f8cc70443c Mon Sep 17 00:00:00 2001 From: Rich Felker Date: Sat, 20 Apr 2013 14:07:01 -0400 Subject: comment potentially-confusing use of struct crypt_data type --- src/crypt/crypt.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'src/crypt/crypt.c') diff --git a/src/crypt/crypt.c b/src/crypt/crypt.c index f1e310f6..46500737 100644 --- a/src/crypt/crypt.c +++ b/src/crypt/crypt.c @@ -5,7 +5,12 @@ char *__crypt_r(const char *, const char *, struct crypt_data *); char *crypt(const char *key, const char *salt) { - /* Note: update this size when we add more hash types */ + /* This buffer is sufficiently large for all + * currently-supported hash types. It needs to be updated if + * longer hashes are added. The cast to struct crypt_data * is + * purely to meet the public API requirements of the crypt_r + * function; the implementation of crypt_r uses the object + * purely as a char buffer. */ static char buf[128]; return __crypt_r(key, salt, (struct crypt_data *)buf); } -- cgit v1.2.1