From b96e3ee2717531e842c492c3a6799d1d0c3e51cb Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher
Date: Wed, 28 Feb 2018 09:02:18 +0100
Subject: tlog: stop embedding log.Logger to prevent mistakes

A few places have called tlog.Warn.Print, which directly
calls into log.Logger due to embedding, losing all features
of tlog.

Stop embedding log.Logger to make sure the internal functions
cannot be called accidentially and fix (several!) instances
that did.
---
 internal/cryptocore/cryptocore.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'internal/cryptocore')

diff --git a/internal/cryptocore/cryptocore.go b/internal/cryptocore/cryptocore.go
index bd30029..d66f390 100644
--- a/internal/cryptocore/cryptocore.go
+++ b/internal/cryptocore/cryptocore.go
@@ -163,7 +163,7 @@ func (c *CryptoCore) Wipe() {
 		w := c.AEADCipher.(wiper)
 		w.Wipe()
 	} else {
-		tlog.Debug.Print("CryptoCore.Wipe: Only nil'ing stdlib refs")
+		tlog.Debug.Printf("CryptoCore.Wipe: Only nil'ing stdlib refs")
 	}
 	// We have no access to the keys (or key-equivalents) stored inside the
 	// Go stdlib. Best we can is to nil the references and force a GC.
-- 
cgit v1.2.3