On Mon, 2016-10-03 at 21:42 -0600, Rich Megginson wrote:
> On 10/03/2016 09:34 PM, William Brown wrote:
> > On Mon, 2016-10-03 at 21:26 -0600, Rich Megginson wrote:
> >> On 10/03/2016 08:58 PM, William Brown wrote:
> >>> Hi,
> >>>
> >>> I want to close #48241 [0] as "wontfix". I do not believe
On 10/03/2016 09:34 PM, William Brown wrote:
On Mon, 2016-10-03 at 21:26 -0600, Rich Megginson wrote:
On 10/03/2016 08:58 PM, William Brown wrote:
Hi,
I want to close #48241 [0] as "wontfix". I do not believe that it's
appropriate to provide SHA3 as a password hashing algorithm.
The SHA3
On Mon, 2016-10-03 at 21:26 -0600, Rich Megginson wrote:
> On 10/03/2016 08:58 PM, William Brown wrote:
> > Hi,
> >
> > I want to close #48241 [0] as "wontfix". I do not believe that it's
> > appropriate to provide SHA3 as a password hashing algorithm.
> >
> > The SHA3 algorithm is designed to be
On 10/03/2016 08:58 PM, William Brown wrote:
Hi,
I want to close #48241 [0] as "wontfix". I do not believe that it's
appropriate to provide SHA3 as a password hashing algorithm.
The SHA3 algorithm is designed to be fast, and cryptographically secure.
It's target usage is for signatures and
