The description of kn_encode_base64() in keynote(3) is inaccurate: Since the function is a simple wrapper around b64_ntop(), there is no restriction on the possible lengths of the raw data in `src'. This is likely a confusion with kn_decode_base64(), where there is such a restriction on the `src' string, but only after removal of whitespace. Since the length of `src' is not part of the function call, this doesn't seem to be worth mentioning.
Index: keynote.3 =================================================================== RCS file: /cvs/src/lib/libkeynote/keynote.3,v retrieving revision 1.46 diff -u -p -r1.46 keynote.3 --- keynote.3 16 Jul 2013 15:21:11 -0000 1.46 +++ keynote.3 16 Sep 2014 12:29:28 -0000 @@ -602,8 +602,6 @@ is returned. should be long enough to also contain the trailing string terminator. If -.Fa srclen -is not a multiple of 4, or .Fa dst is not long enough to contain the encoded data, this function returns \-1 and sets