Re: svn commit: r362191 - head/sbin/md5
On Mon, Jun 15, 2020, 3:12 PM Rodney W. Grimes
wrote:
> > On Mon, Jun 15, 2020 at 7:34 AM Mateusz Piotrowski <0...@freebsd.org>
> wrote:
> >
> > > Hi,
> > >
> > > On 6/15/20 2:33 PM, Rodney W. Grimes wrote:
> > > > [ Charset UTF-8 unsupported, converting... ]
> > > >> Author: fernape (ports committer)
> > > >> Date: Mon Jun 15 10:08:02 2020
> > > >> New Revision: 362191
> > > >> URL: https://svnweb.freebsd.org/changeset/base/362191
> > > >>
> > > >> Log:
> > > >> md5(1): fix style in man page
> > > >
> > > > Mandoc is fine to ignore this, but it is wrong to call it useless.
> > > >
> > > > I really wish that this stop. .Tn might be useless to mandoc,
> > > > but it is a very usable thing if your formatting to something
> > > > other than txt, as in a ps or pdf.
> > >
> > > In that case I would consider patching our in-tree mandoc to not warn
> > > about Tn. Or request support for Tn or a well-defined replacement
> upstream.
> > >
> > > I can see the benefit of keeping Tn around, as it /might/ potentially
> > > create nice formatting for HTML. On the other hand, I don't like the
> > > idea of not following the linter.
> > >
> >
> > I thought that Tn thing was the general consensus thing and added to the
> > linter because of that. The man page explains why it's problematic:
> >
> > Tn word ...
> > Supported only for compatibility, do not use this in new
> manuals.
> > Even though the macro name ("tradename") suggests a semantic
> > function, historic usage is inconsistent, mostly using it as a
> > presentation-level macro to request a small caps font.
>
> I believe that comes about because of confusion over trade name vs
> trademark. They are not defined as the same thing.
>
> > It was useful for the Unix trademark, but was tailor towards AT's
> > preferred dressing for the Unix trademark, not for trademarks in general.
>
> Crossing tradename with trademark?
>
> > In this case, there were several instances of abuse:
> >
> > -.Tn RSA .
> > +key under a public-key cryptosystem such as RSA.
>
> trade name: noun
> 1. the name used by a manufacturer, merchant, service company,
> farming business, etc., to identify itself individually
> as a business.
> 2. a word or phrase used in a trade to designate a business,
> service, or a particular class of goods, but that is not
> technically a trademark, either because it is not
> susceptible of exclusive appropriation as a trademark or
> because it is not affixed to goods sold in the market.
> 3. the name by which an article or substance is known to the trade.
>
> I would say RSA defanitly meets 3, and probably 2.
>
> >
> > Not a trademark in this context. RSA is a trademark for the RSA
> corporation
> > and it uses it in various other contexts.
> >
> > -The
> > -.Tn MD5
> > -and
> > -.Tn SHA-1
> > -algorithms have been proven to be vulnerable to practical collision
> > -attacks and should not be relied upon to produce unique outputs,
> > +The MD5 and SHA-1 algorithms have been proven to be vulnerable to
> practical
> > +collision attacks and should not be relied upon to produce unique
> outputs,
> >
> > MD5 and SHA-1 are not trade names in this context. The rest seem similar,
> > though I've not gone to the trouble to look them all up.
>
> I would disagree under the definition of trade name above,
> you seem to be applying the definition of trade mark.
>
None of these are trade names. They are all simple names used to describe
different algorithms. They are no more trade names than bubble sort or
radix tree.
>
> > All in all, while I have some sympathy to Rod's view that we're losing
> > semantic information by these changes in general, this particular one
> > actually fixes the abuse talked about in the mdoc manual, IMHO.
>
> Only if the macro is rigidly defined as "trademark" and it
> is not.
>
The macro is obsoleted in upstream. Splitting hairs on this isn't going to
change that. Time has passed this one by.
Warner
> Warner
> --
> Rod Grimes
> rgri...@freebsd.org
>
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r362191 - head/sbin/md5
> On Mon, Jun 15, 2020 at 7:34 AM Mateusz Piotrowski <0...@freebsd.org> wrote:
>
> > Hi,
> >
> > On 6/15/20 2:33 PM, Rodney W. Grimes wrote:
> > > [ Charset UTF-8 unsupported, converting... ]
> > >> Author: fernape (ports committer)
> > >> Date: Mon Jun 15 10:08:02 2020
> > >> New Revision: 362191
> > >> URL: https://svnweb.freebsd.org/changeset/base/362191
> > >>
> > >> Log:
> > >> md5(1): fix style in man page
> > >
> > > Mandoc is fine to ignore this, but it is wrong to call it useless.
> > >
> > > I really wish that this stop. .Tn might be useless to mandoc,
> > > but it is a very usable thing if your formatting to something
> > > other than txt, as in a ps or pdf.
> >
> > In that case I would consider patching our in-tree mandoc to not warn
> > about Tn. Or request support for Tn or a well-defined replacement upstream.
> >
> > I can see the benefit of keeping Tn around, as it /might/ potentially
> > create nice formatting for HTML. On the other hand, I don't like the
> > idea of not following the linter.
> >
>
> I thought that Tn thing was the general consensus thing and added to the
> linter because of that. The man page explains why it's problematic:
>
> Tn word ...
> Supported only for compatibility, do not use this in new manuals.
> Even though the macro name ("tradename") suggests a semantic
> function, historic usage is inconsistent, mostly using it as a
> presentation-level macro to request a small caps font.
I believe that comes about because of confusion over trade name vs
trademark. They are not defined as the same thing.
> It was useful for the Unix trademark, but was tailor towards AT's
> preferred dressing for the Unix trademark, not for trademarks in general.
Crossing tradename with trademark?
> In this case, there were several instances of abuse:
>
> -.Tn RSA .
> +key under a public-key cryptosystem such as RSA.
trade name: noun
1. the name used by a manufacturer, merchant, service company,
farming business, etc., to identify itself individually
as a business.
2. a word or phrase used in a trade to designate a business,
service, or a particular class of goods, but that is not
technically a trademark, either because it is not
susceptible of exclusive appropriation as a trademark or
because it is not affixed to goods sold in the market.
3. the name by which an article or substance is known to the trade.
I would say RSA defanitly meets 3, and probably 2.
>
> Not a trademark in this context. RSA is a trademark for the RSA corporation
> and it uses it in various other contexts.
>
> -The
> -.Tn MD5
> -and
> -.Tn SHA-1
> -algorithms have been proven to be vulnerable to practical collision
> -attacks and should not be relied upon to produce unique outputs,
> +The MD5 and SHA-1 algorithms have been proven to be vulnerable to practical
> +collision attacks and should not be relied upon to produce unique outputs,
>
> MD5 and SHA-1 are not trade names in this context. The rest seem similar,
> though I've not gone to the trouble to look them all up.
I would disagree under the definition of trade name above,
you seem to be applying the definition of trade mark.
>
> All in all, while I have some sympathy to Rod's view that we're losing
> semantic information by these changes in general, this particular one
> actually fixes the abuse talked about in the mdoc manual, IMHO.
Only if the macro is rigidly defined as "trademark" and it
is not.
> Warner
--
Rod Grimes rgri...@freebsd.org
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r362191 - head/sbin/md5
On Mon, Jun 15, 2020 at 7:34 AM Mateusz Piotrowski <0...@freebsd.org> wrote:
> Hi,
>
> On 6/15/20 2:33 PM, Rodney W. Grimes wrote:
> > [ Charset UTF-8 unsupported, converting... ]
> >> Author: fernape (ports committer)
> >> Date: Mon Jun 15 10:08:02 2020
> >> New Revision: 362191
> >> URL: https://svnweb.freebsd.org/changeset/base/362191
> >>
> >> Log:
> >> md5(1): fix style in man page
> >
> > Mandoc is fine to ignore this, but it is wrong to call it useless.
> >
> > I really wish that this stop. .Tn might be useless to mandoc,
> > but it is a very usable thing if your formatting to something
> > other than txt, as in a ps or pdf.
>
> In that case I would consider patching our in-tree mandoc to not warn
> about Tn. Or request support for Tn or a well-defined replacement upstream.
>
> I can see the benefit of keeping Tn around, as it /might/ potentially
> create nice formatting for HTML. On the other hand, I don't like the
> idea of not following the linter.
>
I thought that Tn thing was the general consensus thing and added to the
linter because of that. The man page explains why it's problematic:
Tn word ...
Supported only for compatibility, do not use this in new manuals.
Even though the macro name ("tradename") suggests a semantic
function, historic usage is inconsistent, mostly using it as a
presentation-level macro to request a small caps font.
It was useful for the Unix trademark, but was tailor towards AT's
preferred dressing for the Unix trademark, not for trademarks in general.
In this case, there were several instances of abuse:
-.Tn RSA .
+key under a public-key cryptosystem such as RSA.
Not a trademark in this context. RSA is a trademark for the RSA corporation
and it uses it in various other contexts.
-The
-.Tn MD5
-and
-.Tn SHA-1
-algorithms have been proven to be vulnerable to practical collision
-attacks and should not be relied upon to produce unique outputs,
+The MD5 and SHA-1 algorithms have been proven to be vulnerable to practical
+collision attacks and should not be relied upon to produce unique outputs,
MD5 and SHA-1 are not trade names in this context. The rest seem similar,
though I've not gone to the trouble to look them all up.
All in all, while I have some sympathy to Rod's view that we're losing
semantic information by these changes in general, this particular one
actually fixes the abuse talked about in the mdoc manual, IMHO.
Warner
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r362191 - head/sbin/md5
Mateusz Piotrowski wrote: Hi, On 6/15/20 2:33 PM, Rodney W. Grimes wrote: [ Charset UTF-8 unsupported, converting... ] Author: fernape (ports committer) Date: Mon Jun 15 10:08:02 2020 New Revision: 362191 URL: https://svnweb.freebsd.org/changeset/base/362191 Log: md5(1): fix style in man page Mandoc is fine to ignore this, but it is wrong to call it useless. I really wish that this stop. .Tn might be useless to mandoc, but it is a very usable thing if your formatting to something other than txt, as in a ps or pdf. In that case I would consider patching our in-tree mandoc to not warn about Tn. Or request support for Tn or a well-defined replacement upstream. I can see the benefit of keeping Tn around, as it /might/ potentially create nice formatting for HTML. On the other hand, I don't like the idea of not following the linter. It's marked as obsolete exactly because it's misused, quoting mdoc(7): Even though the macro name (“tradename”) suggests a semantic function, historic usage is inconsistent, mostly using it as a presentation-level macro to request a small caps font. If we want to somehow emphasize the text, .Sy, .Em, or similar macros should be used instead, I don't see why though, it certainly doesn't help the readability (IMO, of coursE). ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r362191 - head/sbin/md5
Hi, On 6/15/20 2:33 PM, Rodney W. Grimes wrote: > [ Charset UTF-8 unsupported, converting... ] >> Author: fernape (ports committer) >> Date: Mon Jun 15 10:08:02 2020 >> New Revision: 362191 >> URL: https://svnweb.freebsd.org/changeset/base/362191 >> >> Log: >> md5(1): fix style in man page > > Mandoc is fine to ignore this, but it is wrong to call it useless. > > I really wish that this stop. .Tn might be useless to mandoc, > but it is a very usable thing if your formatting to something > other than txt, as in a ps or pdf. In that case I would consider patching our in-tree mandoc to not warn about Tn. Or request support for Tn or a well-defined replacement upstream. I can see the benefit of keeping Tn around, as it /might/ potentially create nice formatting for HTML. On the other hand, I don't like the idea of not following the linter. Cheers, Mateusz ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r362191 - head/sbin/md5
[ Charset UTF-8 unsupported, converting... ] > Author: fernape (ports committer) > Date: Mon Jun 15 10:08:02 2020 > New Revision: 362191 > URL: https://svnweb.freebsd.org/changeset/base/362191 > > Log: > md5(1): fix style in man page > > Fix a bunch of style problems reported by mandoc(1) and igor: > > mandoc: ./md5.1:19:71: STYLE: no blank before trailing delimiter: Nm ... > rmd160, > mandoc: ./md5.1:20:23: STYLE: no blank before trailing delimiter: Nm ... > skein512, > mandoc: ./md5.1:33:2: STYLE: useless macro: Tn > mandoc: ./md5.1:33:2: STYLE: useless macro: Tn > mandoc: ./md5.1:33:2: STYLE: useless macro: Tn > mandoc: ./md5.1:33:2: STYLE: useless macro: Tn > mandoc: ./md5.1:35:2: STYLE: useless macro: Tn > mandoc: ./md5.1:42:2: STYLE: useless macro: Tn > mandoc: ./md5.1:45:2: STYLE: useless macro: Tn > mandoc: ./md5.1:47:2: STYLE: useless macro: Tn > mandoc: ./md5.1:56:2: STYLE: useless macro: Tn > mandoc: ./md5.1:58:2: STYLE: useless macro: Tn > mandoc: ./md5.1:61:2: STYLE: useless macro: Tn > mandoc: ./md5.1:66:2: STYLE: useless macro: Tn > mandoc: ./md5.1:68:2: STYLE: useless macro: Tn Mandoc is fine to ignore this, but it is wrong to call it useless. I really wish that this stop. .Tn might be useless to mandoc, but it is a very usable thing if your formatting to something other than txt, as in a ps or pdf. > mandoc: ./md5.1:104:24: STYLE: no blank before trailing delimiter: Nm > skein512, > mandoc: ./md5.1:117:6: STYLE: referenced manual not found: Xr sha224 3 > > igor: > md5.1:46:no comma after "i.e.":either algorithm, [i.e.] to find an input > that produces a specific > > Approved by:bcr@ > Differential Revision: https://reviews.freebsd.org/D25277 > > Modified: > head/sbin/md5/md5.1 > > Modified: head/sbin/md5/md5.1 > == > --- head/sbin/md5/md5.1 Mon Jun 15 03:10:53 2020(r362190) > +++ head/sbin/md5/md5.1 Mon Jun 15 10:08:02 2020(r362191) > @@ -1,5 +1,5 @@ > .\" $FreeBSD$ > -.Dd July 9, 2018 > +.Dd June 15, 2020 > .Dt MD5 1 > .Os > .Sh NAME > @@ -16,8 +16,8 @@ > (All other hashes have the same options and usage.) > .Sh DESCRIPTION > The > -.Nm md5 , sha1 , sha224 , sha256 , sha384 , sha512, sha512t256, rmd160, > -.Nm skein256, skein512, > +.Nm md5 , sha1 , sha224 , sha256 , sha384 , sha512 , sha512t256 , rmd160 , > +.Nm skein256 , skein512 , > and > .Nm skein1024 > utilities take as input a message of arbitrary length and produce as > @@ -29,43 +29,29 @@ of the input. > It is conjectured that it is computationally infeasible to > produce two messages having the same message digest, or to produce any > message having a given prespecified target message digest. > -The > -.Tn SHA-224 , SHA-256 , SHA-384 , SHA-512, RIPEMD-160, > -and > -.Tn SKEIN > +The SHA-224 , SHA-256 , SHA-384 , SHA-512, RIPEMD-160, > +and SKEIN > algorithms are intended for digital signature applications, where a > large file must be > .Dq compressed > in a secure manner before being encrypted with a private > (secret) > -key under a public-key cryptosystem such as > -.Tn RSA . > +key under a public-key cryptosystem such as RSA. > .Pp > -The > -.Tn MD5 > -and > -.Tn SHA-1 > -algorithms have been proven to be vulnerable to practical collision > -attacks and should not be relied upon to produce unique outputs, > +The MD5 and SHA-1 algorithms have been proven to be vulnerable to practical > +collision attacks and should not be relied upon to produce unique outputs, > .Em nor should they be used as part of a cryptographic signature scheme. > As of 2017-03-02, there is no publicly known method to > .Em reverse > -either algorithm, i.e. to find an input that produces a specific > +either algorithm, i.e., to find an input that produces a specific > output. > .Pp > -.Tn SHA-512t256 > -is a version of > -.Tn SHA-512 > -truncated to only 256 bits. > -On 64-bit hardware, this algorithm is approximately 50% faster than > -.Tn SHA-256 > -but with the same level of security. > +SHA-512t256 is a version of SHA-512 truncated to only 256 bits. > +On 64-bit hardware, this algorithm is approximately 50% faster than SHA-256 > but > +with the same level of security. > The hashes are not interchangeable. > .Pp > -It is recommended that all new applications use > -.Tn SHA-512 > -or > -.Tn SKEIN-512 > +It is recommended that all new applications use SHA-512 or SKEIN-512 > instead of one of the other hash functions. > .Pp > The following options may be used in any combination and must > @@ -101,7 +87,7 @@ Run a built-in test script. > .Sh EXIT STATUS > The > .Nm md5 , sha1 , sha224 , sha256 , sha512 , sha512t256 , rmd160 , > -.Nm skein256 , skein512, > +.Nm skein256 , skein512 , > and > .Nm skein1024 > utilities exit 0 on success, > @@ -114,7 +100,6 @@ option. > .Xr md5 3 , > .Xr ripemd 3 , > .Xr sha 3 , > -.Xr sha224 3 , > .Xr
Re: svn commit: r362191 - head/sbin/md5
Fernando Apesteguía wrote: Author: fernape (ports committer) Date: Mon Jun 15 10:08:02 2020 New Revision: 362191 URL: https://svnweb.freebsd.org/changeset/base/362191 Log: md5(1): fix style in man page Fix a bunch of style problems reported by mandoc(1) and igor: mandoc: ./md5.1:19:71: STYLE: no blank before trailing delimiter: Nm ... rmd160, mandoc: ./md5.1:20:23: STYLE: no blank before trailing delimiter: Nm ... skein512, mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:35:2: STYLE: useless macro: Tn mandoc: ./md5.1:42:2: STYLE: useless macro: Tn mandoc: ./md5.1:45:2: STYLE: useless macro: Tn mandoc: ./md5.1:47:2: STYLE: useless macro: Tn mandoc: ./md5.1:56:2: STYLE: useless macro: Tn mandoc: ./md5.1:58:2: STYLE: useless macro: Tn mandoc: ./md5.1:61:2: STYLE: useless macro: Tn mandoc: ./md5.1:66:2: STYLE: useless macro: Tn mandoc: ./md5.1:68:2: STYLE: useless macro: Tn mandoc: ./md5.1:104:24: STYLE: no blank before trailing delimiter: Nm skein512, mandoc: ./md5.1:117:6: STYLE: referenced manual not found: Xr sha224 3 igor: md5.1:46:no comma after "i.e.":either algorithm, [i.e.] to find an input that produces a specific Approved by: bcr@ Differential Revision: https://reviews.freebsd.org/D25277 Modified: head/sbin/md5/md5.1 Modified: head/sbin/md5/md5.1 == --- head/sbin/md5/md5.1 Mon Jun 15 03:10:53 2020(r362190) +++ head/sbin/md5/md5.1 Mon Jun 15 10:08:02 2020(r362191) @@ -1,5 +1,5 @@ .\" $FreeBSD$ -.Dd July 9, 2018 +.Dd June 15, 2020 .Dt MD5 1 .Os .Sh NAME @@ -16,8 +16,8 @@ (All other hashes have the same options and usage.) .Sh DESCRIPTION The -.Nm md5 , sha1 , sha224 , sha256 , sha384 , sha512, sha512t256, rmd160, -.Nm skein256, skein512, +.Nm md5 , sha1 , sha224 , sha256 , sha384 , sha512 , sha512t256 , rmd160 , +.Nm skein256 , skein512 , and .Nm skein1024 utilities take as input a message of arbitrary length and produce as @@ -29,43 +29,29 @@ of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given prespecified target message digest. -The -.Tn SHA-224 , SHA-256 , SHA-384 , SHA-512, RIPEMD-160, -and -.Tn SKEIN +The SHA-224 , SHA-256 , SHA-384 , SHA-512, RIPEMD-160, +and SKEIN algorithms are intended for digital signature applications, where a large file must be .Dq compressed in a secure manner before being encrypted with a private (secret) -key under a public-key cryptosystem such as -.Tn RSA . +key under a public-key cryptosystem such as RSA. .Pp -The -.Tn MD5 -and -.Tn SHA-1 -algorithms have been proven to be vulnerable to practical collision -attacks and should not be relied upon to produce unique outputs, +The MD5 and SHA-1 algorithms have been proven to be vulnerable to practical +collision attacks and should not be relied upon to produce unique outputs, .Em nor should they be used as part of a cryptographic signature scheme. As of 2017-03-02, there is no publicly known method to .Em reverse -either algorithm, i.e. to find an input that produces a specific +either algorithm, i.e., to find an input that produces a specific output. .Pp -.Tn SHA-512t256 -is a version of -.Tn SHA-512 -truncated to only 256 bits. -On 64-bit hardware, this algorithm is approximately 50% faster than -.Tn SHA-256 -but with the same level of security. +SHA-512t256 is a version of SHA-512 truncated to only 256 bits. +On 64-bit hardware, this algorithm is approximately 50% faster than SHA-256 but +with the same level of security. The hashes are not interchangeable. .Pp -It is recommended that all new applications use -.Tn SHA-512 -or -.Tn SKEIN-512 +It is recommended that all new applications use SHA-512 or SKEIN-512 instead of one of the other hash functions. .Pp The following options may be used in any combination and must @@ -101,7 +87,7 @@ Run a built-in test script. .Sh EXIT STATUS The .Nm md5 , sha1 , sha224 , sha256 , sha512 , sha512t256 , rmd160 , -.Nm skein256 , skein512, +.Nm skein256 , skein512 , and .Nm skein1024 utilities exit 0 on success, @@ -114,7 +100,6 @@ option. .Xr md5 3 , .Xr ripemd 3 , .Xr sha 3 , -.Xr sha224 3 , .Xr sha256 3 , .Xr sha384 3 , .Xr sha512 3 , I think we should create sha256.3 -> sha224.3 instead of removing the reference, as done for sha512.3 -> sha384.3 -- if you look at the sha256.3 man page, it documents all of the SHA224_* functions; i.e.,: Index: Makefile === --- Makefile(revision 362145) +++ Makefile(working copy) @@ -40,7 +40,7 @@ MLINKS+=sha256.3 SHA224_Init.3 sha256.3
svn commit: r362191 - head/sbin/md5
Author: fernape (ports committer) Date: Mon Jun 15 10:08:02 2020 New Revision: 362191 URL: https://svnweb.freebsd.org/changeset/base/362191 Log: md5(1): fix style in man page Fix a bunch of style problems reported by mandoc(1) and igor: mandoc: ./md5.1:19:71: STYLE: no blank before trailing delimiter: Nm ... rmd160, mandoc: ./md5.1:20:23: STYLE: no blank before trailing delimiter: Nm ... skein512, mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:33:2: STYLE: useless macro: Tn mandoc: ./md5.1:35:2: STYLE: useless macro: Tn mandoc: ./md5.1:42:2: STYLE: useless macro: Tn mandoc: ./md5.1:45:2: STYLE: useless macro: Tn mandoc: ./md5.1:47:2: STYLE: useless macro: Tn mandoc: ./md5.1:56:2: STYLE: useless macro: Tn mandoc: ./md5.1:58:2: STYLE: useless macro: Tn mandoc: ./md5.1:61:2: STYLE: useless macro: Tn mandoc: ./md5.1:66:2: STYLE: useless macro: Tn mandoc: ./md5.1:68:2: STYLE: useless macro: Tn mandoc: ./md5.1:104:24: STYLE: no blank before trailing delimiter: Nm skein512, mandoc: ./md5.1:117:6: STYLE: referenced manual not found: Xr sha224 3 igor: md5.1:46:no comma after "i.e.":either algorithm, [i.e.] to find an input that produces a specific Approved by: bcr@ Differential Revision: https://reviews.freebsd.org/D25277 Modified: head/sbin/md5/md5.1 Modified: head/sbin/md5/md5.1 == --- head/sbin/md5/md5.1 Mon Jun 15 03:10:53 2020(r362190) +++ head/sbin/md5/md5.1 Mon Jun 15 10:08:02 2020(r362191) @@ -1,5 +1,5 @@ .\" $FreeBSD$ -.Dd July 9, 2018 +.Dd June 15, 2020 .Dt MD5 1 .Os .Sh NAME @@ -16,8 +16,8 @@ (All other hashes have the same options and usage.) .Sh DESCRIPTION The -.Nm md5 , sha1 , sha224 , sha256 , sha384 , sha512, sha512t256, rmd160, -.Nm skein256, skein512, +.Nm md5 , sha1 , sha224 , sha256 , sha384 , sha512 , sha512t256 , rmd160 , +.Nm skein256 , skein512 , and .Nm skein1024 utilities take as input a message of arbitrary length and produce as @@ -29,43 +29,29 @@ of the input. It is conjectured that it is computationally infeasible to produce two messages having the same message digest, or to produce any message having a given prespecified target message digest. -The -.Tn SHA-224 , SHA-256 , SHA-384 , SHA-512, RIPEMD-160, -and -.Tn SKEIN +The SHA-224 , SHA-256 , SHA-384 , SHA-512, RIPEMD-160, +and SKEIN algorithms are intended for digital signature applications, where a large file must be .Dq compressed in a secure manner before being encrypted with a private (secret) -key under a public-key cryptosystem such as -.Tn RSA . +key under a public-key cryptosystem such as RSA. .Pp -The -.Tn MD5 -and -.Tn SHA-1 -algorithms have been proven to be vulnerable to practical collision -attacks and should not be relied upon to produce unique outputs, +The MD5 and SHA-1 algorithms have been proven to be vulnerable to practical +collision attacks and should not be relied upon to produce unique outputs, .Em nor should they be used as part of a cryptographic signature scheme. As of 2017-03-02, there is no publicly known method to .Em reverse -either algorithm, i.e. to find an input that produces a specific +either algorithm, i.e., to find an input that produces a specific output. .Pp -.Tn SHA-512t256 -is a version of -.Tn SHA-512 -truncated to only 256 bits. -On 64-bit hardware, this algorithm is approximately 50% faster than -.Tn SHA-256 -but with the same level of security. +SHA-512t256 is a version of SHA-512 truncated to only 256 bits. +On 64-bit hardware, this algorithm is approximately 50% faster than SHA-256 but +with the same level of security. The hashes are not interchangeable. .Pp -It is recommended that all new applications use -.Tn SHA-512 -or -.Tn SKEIN-512 +It is recommended that all new applications use SHA-512 or SKEIN-512 instead of one of the other hash functions. .Pp The following options may be used in any combination and must @@ -101,7 +87,7 @@ Run a built-in test script. .Sh EXIT STATUS The .Nm md5 , sha1 , sha224 , sha256 , sha512 , sha512t256 , rmd160 , -.Nm skein256 , skein512, +.Nm skein256 , skein512 , and .Nm skein1024 utilities exit 0 on success, @@ -114,7 +100,6 @@ option. .Xr md5 3 , .Xr ripemd 3 , .Xr sha 3 , -.Xr sha224 3 , .Xr sha256 3 , .Xr sha384 3 , .Xr sha512 3 , ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
