lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 18 Feb 2013 14:40:29 -0600 (CST)
From: Steve Thomas <steve@...tu.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Q: int return from PHS()

> On February 18, 2013 at 1:00 PM Samuel Neves <sneves@....uc.pt> wrote:
>
>
> On 18-02-2013 18:46, Dennis E. Hamilton wrote:
> > Reference implementations for submissions are requested to provide an API
> > having signature int PHS( ...)
> >
> > What are the prescribed return values and their significance?
> >
> > - Dennis
> >
> > PS: Sorry if this has been asked. I haven't found the list archive yet.
> >
> It has not been asked.
>
> In typical C fashion, return value should be 0 for success, and
> otherwise for any error that may occur during computation. Error codes,
> if any, should be up to implementors, since sources of error may wildly
> vary between schemes/implementations.

I was under the impression that the return value was the amount of data copied
to the output buffer.
Content of type "text/html" skipped

Powered by blists - more mailing lists