river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Oliver (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-233) ComputeDigest instructions reference sha and sha1
Date Tue, 11 Mar 2008 18:02:46 GMT

    [ https://issues.apache.org/jira/browse/RIVER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577532#action_12577532

Fred Oliver commented on RIVER-233:

In a subsequent commit, I've change "sha1" to "SHA-1" for better consistency with other classes.

> ComputeDigest instructions reference sha and sha1
> -------------------------------------------------
>                 Key: RIVER-233
>                 URL: https://issues.apache.org/jira/browse/RIVER-233
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_tool
>    Affects Versions: jtsk_2.1
>            Reporter: Fred Oliver
>            Assignee: Fred Oliver
>            Priority: Trivial
>             Fix For: AR2
> Bugtraq ID [6325665|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6325665] 
> The example use of the ComputeDigest tool in the class javadoc uses 'sha' as an example
algorithm when the default algorithm is later specified to be 'sha1'.  My understanding is
that sha and sha1 are the same (they certainly produce the same digest).  Perhaps it would
be better for the example to use a non-sha algorithm (or at least a non-sha1 algorithm since
that is the default).
> ----
> Consistenly using "sha1" should be satisfactory.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message