From 85c4fe2adf917df6caa343131d0b161e077f8c30 Mon Sep 17 00:00:00 2001
From: Scott Kitterman <scott@kitterman.com>
Date: Wed, 28 Mar 2018 06:51:35 -0400
Subject: [PATCH]     - Fix typo in dknewky(1) for k= tag (Thanks to Andreas
 Schulze for       reporting)

---
 ChangeLog      | 2 ++
 man/dknewkey.1 | 4 ++--
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 543a35f..7b59d69 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -3,6 +3,8 @@ Unreleased Version 0.8.0
       future
     - Use install_requires and extras_requires to document external
       dependencies for dkimpy (LP: #1227526)
+    - Fix typo in dknewky(1) for k= tag (Thanks to Andreas Schulze for
+      reporting)
 
 2018-02-17 Version 0.7.1
     - Update ed25519 tests, including using sample keys from RFC 8032 Section
diff --git a/man/dknewkey.1 b/man/dknewkey.1
index c136205..f8c8af9 100644
--- a/man/dknewkey.1
+++ b/man/dknewkey.1
@@ -135,7 +135,7 @@ dknewkey
 Generates new DKIM public/private key pairs
 .SH "VERSION"
 .IX Header "VERSION"
-0\.7\.1
+0\.8\.0
 
 .SH "DESCRIPTION"
 .IX Header "DESCRIPTION"
@@ -148,7 +148,7 @@ BITS_REQUIRED variable. ed25519 keys do not have a variable size.
 For RSA keys, it uses openssl to do the generation.  By default it assumes
 this is located at /usr/bin/openssl.  This is controlled by the OPENSSL_BINARY
 variable.  For ed25519 keys, PyNaCl (python-nacl in Debian and derivatives) is
-used.  For RSA keys k=2ha256 is now included in the public DNS record to
+used.  For RSA keys k=sha256 is now included in the public DNS record to
 prevent inadvertent use with the now obsolete sha1 hash algorithm (See RFC
 8301).