From 32d58a5276927892c16f17b3f5676fa0a067c19a Mon Sep 17 00:00:00 2001
From: Linus Nordberg <linus@nordu.net>
Date: Mon, 17 Oct 2016 08:52:33 +0200
Subject: Don't follow the NULL pointer, not even in debug printouts.

Bug reported by Leonhard Knauff.

Closes RADSECPROXY-68.
---
 ChangeLog | 1 +
 1 file changed, 1 insertion(+)

(limited to 'ChangeLog')

diff --git a/ChangeLog b/ChangeLog
index 10b294c..e3873f0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -3,6 +3,7 @@
 	- Use a listen(2) backlog of 128 (RADSECPROXY-72).
 
 	Bug fixes:
+	- Don't follow NULL the pointer at debug level 5 (RADSECPROXY-68).
 	- Completely reload CAs and CRLs with cacheExpiry (RADSECPROXY-50).
 	- Tie Access-Request log lines to response log lines (RADSECPROXY-60).
 	- Fix a couple of memory leaks and NULL ptr derefs in error cases.
-- 
cgit v1.1