aboutsummaryrefslogtreecommitdiffstats
path: root/facebook/facebook-api.c
diff options
context:
space:
mode:
authordequis <dx@dxzone.com.ar>2015-12-20 04:12:21 -0300
committerdequis <dx@dxzone.com.ar>2015-12-20 15:27:50 -0300
commit0121bae03b6d545ff799f4b02c9b05becac1b78b (patch)
tree81683443fc75a5213f9c7f37cba16d7d47562157 /facebook/facebook-api.c
parent6056cc2235b2e9515008da5a07b5617228006365 (diff)
downloadbitlbee-facebook-0121bae03b6d545ff799f4b02c9b05becac1b78b.tar.gz
bitlbee-facebook-0121bae03b6d545ff799f4b02c9b05becac1b78b.tar.bz2
bitlbee-facebook-0121bae03b6d545ff799f4b02c9b05becac1b78b.tar.xz
facebook-json: Ensure data is null terminated for json-glib < 1.0.2
Older json-glib versions had a bug[1] in which the length parameter was ignored and this error happened if the input was not null-terminated: JSON data must be UTF-8 encoded Since these versions are expected to still be around in some distros, this commit makes a copy with g_strndup() to ensure that it's always null terminated. Thanks to advcomp2019 for reporting this bug and finding a test case where this issue is reproducible every time (receiving events of people joining or leaving in a groupchat) [1]: https://bugzilla.gnome.org/show_bug.cgi?id=727755
Diffstat (limited to 'facebook/facebook-api.c')
0 files changed, 0 insertions, 0 deletions