aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2007-10-18 04:41:33 +0000
committerrussell <russell@f38db490-d61c-443f-a65b-d21fe96a405b>2007-10-18 04:41:33 +0000
commit892cec08215d16b2da5cf6b59487776573a3858e (patch)
tree8a3f5dc71811469988773976bf5e0c5c1cb87001
parent1b21154d71b72249c3a185a8bfaf2aa0f6ec1be4 (diff)
Merged revisions 86237 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r86237 | russell | 2007-10-17 23:40:52 -0500 (Wed, 17 Oct 2007) | 9 lines 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: http://svn.digium.com/svn/asterisk/trunk@86238 f38db490-d61c-443f-a65b-d21fe96a405b
-rw-r--r--main/utils.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/main/utils.c b/main/utils.c
index 25de47ef3..653c31312 100644
--- a/main/utils.c
+++ b/main/utils.c
@@ -352,9 +352,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;
}