security: don't use printf() for debugging
commitba36bf6ea0335c9c16383d606be5fc0e307c977b
authorStefan Becker <chemobejk@gmail.com>
Fri, 22 Feb 2013 13:58:46 +0000 (22 15:58 +0200)
committerStefan Becker <chemobejk@gmail.com>
Sat, 23 Feb 2013 15:16:11 +0000 (23 17:16 +0200)
tree6cda1e39c8ae75ac9cb90e1d2bbb9134b7e4294c
parentb8b0145aeab5e92536c63c3f69db4c561ee48646
security: don't use printf() for debugging

sip-sec-krb5.c and sip-sec-sspi.c were still using printf() instead of
the correct SIPE_DEBUG_XXX() calls. That explains the strange contents
in the debug logs from Kerberos users.
src/core/sip-sec-krb5.c
src/core/sip-sec-sspi.c