pidgin/pidgin

Implement mitigation for GHSL-2021-045
release-2.x.y
2021-02-07, Gary Kramlich
fb2056ce3c58
Implement mitigation for GHSL-2021-045

This add a static inline version of `g_memdup2` if the version of glib we're
compiling against doesn't have the function.

GHSL-2021-045 was originally reported to glib at
https://gitlab.gnome.org/GNOME/glib/-/issues/2319.

More information about the entire situation can be found on the gnome
desktop-devel-list at
https://mail.gnome.org/archives/desktop-devel-list/2021-February/msg00000.html

Testing Done:
Compiled and ran tests locally.

Reviewed at https://reviews.imfreedom.org/r/483/
#ifndef DBUS_API_SUBJECT_TO_CHANGE
#define DBUS_API_SUBJECT_TO_CHANGE
#endif
#include <stdio.h>
#include <stdlib.h>
#include "purple-client.h"
/*
This example demonstrates how to use libpurple-client to communicate
with purple. The names and signatures of functions provided by
libpurple-client are the same as those in purple. However, all
structures (such as PurpleAccount) are opaque, that is, you can only
use pointer to them. In fact, these pointers DO NOT actually point
to anything, they are just integer identifiers of assigned to these
structures by purple. So NEVER try to dereference these pointers.
Integer ids as disguised as pointers to provide type checking and
prevent mistakes such as passing an id of PurpleAccount when an id of
PurpleBuddy is expected. According to glib manual, this technique is
portable.
*/
int main (int argc, char **argv)
{
GList *alist, *node;
purple_init();
alist = purple_accounts_get_all();
for (node = alist; node != NULL; node = node->next)
{
PurpleAccount *account = (PurpleAccount*) node->data;
char *name = purple_account_get_username(account);
g_print("Name: %s\n", name);
g_free(name);
}
g_list_free(alist);
return 0;
}