Revert a change that I made for issue #10979 which, as has been pointed out to

me in issue #11018, doesn't really make sense.  There is no reason to have
the base64 decode function force a '\0' terminated buffer, when the result is
almost always binary, anyway.  In fact, this caused some breakage, as some code
in res_crypto passed in a buffer exactly the right size to get its binary
result, which got stomped on by this patch.

(closes issue #11018, reported by dimas)


git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@86237 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Russell Bryant
2007-10-18 04:40:52 +00:00
parent cb55155ef1
commit 9fcc010cce

View File

@@ -347,9 +347,6 @@ int ast_base64decode(unsigned char *dst, const char *src, int max)
cnt++;
}
}
if (cnt == max)
dst--;
*dst = '\0';
/* Dont worry about left over bits, they're extra anyway */
return cnt;
}