aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMartin Willi <martin@revosec.ch>2014-02-10 11:07:50 +0100
committerMartin Willi <martin@revosec.ch>2014-02-10 11:07:50 +0100
commit144f1d70410eafa5a5e2327f06b0129380c10e6c (patch)
tree3cd5318309bb65ec8d2535196ad8ac2af32669ae
parentac2dc3b726b43910c2b8dd1d13c62a76315ccd23 (diff)
downloadstrongswan-144f1d70410eafa5a5e2327f06b0129380c10e6c.tar.bz2
strongswan-144f1d70410eafa5a5e2327f06b0129380c10e6c.tar.xz
rdrand: Move RDRAND detection log to level 2
When having RDRAND support, these log messages might be confusing when using pki or other tools.
-rw-r--r--src/libstrongswan/plugins/rdrand/rdrand_plugin.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libstrongswan/plugins/rdrand/rdrand_plugin.c b/src/libstrongswan/plugins/rdrand/rdrand_plugin.c
index 4bdfc258e..bb540648d 100644
--- a/src/libstrongswan/plugins/rdrand/rdrand_plugin.c
+++ b/src/libstrongswan/plugins/rdrand/rdrand_plugin.c
@@ -77,11 +77,11 @@ static bool have_rdrand()
cpuid(1, &a, &b, &c, &d);
if (c & CPUID_RDRAND)
{
- DBG1(DBG_LIB, "detected RDRAND support on %s CPU", vendor);
+ DBG2(DBG_LIB, "detected RDRAND support on %s CPU", vendor);
return TRUE;
}
}
- DBG1(DBG_LIB, "no RDRAND support on %s CPU, disabled", vendor);
+ DBG2(DBG_LIB, "no RDRAND support on %s CPU, disabled", vendor);
return FALSE;
}