From 3b061a00e39d2e4ad524ff01cbdc0c53fe8171ee Mon Sep 17 00:00:00 2001 From: Rich Salz Date: Sat, 2 May 2015 10:01:33 -0400 Subject: RT2547: Tighten perms on generated privkey files When generating a private key, try to make the output file be readable only by the owner. Put it in CHANGES file since it might be noticeable. Add "int private" flag to apps that write private keys, and check that it's set whenever we do write a private key. Checked via assert so that this bug (security-related) gets fixed. Thanks to Viktor for help in tracing the code-paths where private keys are written. Reviewed-by: Viktor Dukhovni --- apps/s_cb.c | 1 - 1 file changed, 1 deletion(-) (limited to 'apps/s_cb.c') diff --git a/apps/s_cb.c b/apps/s_cb.c index 44e70f2..a14e00c 100644 --- a/apps/s_cb.c +++ b/apps/s_cb.c @@ -111,7 +111,6 @@ /* callback functions used by s_client, s_server, and s_time */ #include #include -#include #include /* for memcpy() and strcmp() */ #define USE_SOCKETS #include "apps.h" -- cgit v1.1