DandelionNStuff/dkimpy-smtputf8
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- Fix typo in dknewky(1) for k= tag (Thanks to Andreas Schulze for

Browse Source 
reporting)
This commit is contained in:
Scott Kitterman
2018-03-28 06:51:35 -04:00
parent 3020b0e6d6
commit 85c4fe2adf
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ChangeLog
+2
View File
@@ -3,6 +3,8 @@ Unreleased Version 0.8.0
future future
- Use install_requires and extras_requires to document external - Use install_requires and extras_requires to document external
dependencies for dkimpy (LP: #1227526) 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 2018-02-17 Version 0.7.1
- Update ed25519 tests, including using sample keys from RFC 8032 Section - Update ed25519 tests, including using sample keys from RFC 8032 Section
man/dknewkey.1
+2 -2
View File
@@ -135,7 +135,7 @@ dknewkey
Generates new DKIM public/private key pairs Generates new DKIM public/private key pairs
.SH "VERSION" .SH "VERSION"
.IX Header "VERSION" .IX Header "VERSION"
0\.7\.1 0\.8\.0
.SH "DESCRIPTION" .SH "DESCRIPTION"
.IX Header "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 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 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 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 prevent inadvertent use with the now obsolete sha1 hash algorithm (See RFC
8301). 8301).