purple: full debug when unsafe flag is enabled
commit6a40815e6534379a88acced3a2fd14a19382235d
authorStefan Becker <chemobejk@gmail.com>
Wed, 26 Oct 2016 14:53:11 +0000 (26 17:53 +0300)
committerStefan Becker <chemobejk@gmail.com>
Wed, 26 Oct 2016 14:53:11 +0000 (26 17:53 +0300)
tree36f5f93eea12d90fd4487d26f17f87c276984179
parentd9f1c934303badb640e534a7538e7a2ef0129840
purple: full debug when unsafe flag is enabled

If supported by the libpurple API we now use purple_debug_is_unsafe()
as the flag to indicate full debugging. This can be enabled by calling
pidgin like this

   PURPLE_UNSAFE_DEBUG=1 pidgin ...

This means that message contents, which can contain secret information,
will only be dumped to the debug log if enabled explicitly by the user.
src/purple/purple-debug.c