[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stand-alone code for scrypt
- To: danielw@emaildoge.com, scrypt@tarsnap.com
- Subject: Re: Stand-alone code for scrypt
- From: Colin Percival <cperciva@tarsnap.com>
- Date: Mon, 24 Nov 2014 10:39:13 -0800
- In-reply-to: <b1828b47519d3d99b31abab307216fe5.squirrel@lelantoss7bcnwbv.onion>
- References: <25a746b729fff103f222d87631f4afa0.squirrel@lelantoss7bcnwbv.onion> <bc58d34b4191efe679959927a95d09b1.squirrel@lelantoss7bcnwbv.onion> <919c252530a984ba5f2cf224e15002d1.squirrel@lelantoss7bcnwbv.onion> <b1828b47519d3d99b31abab307216fe5.squirrel@lelantoss7bcnwbv.onion>
On 11/24/14 03:12, danielw@emaildoge.com wrote:
> I have one particular question: Why did the be64dec(), be64enc(),
> le64dec(), le64enc() functions end up being unused? Only the "32" ones
> were used. This confuses me because I'm on a 64-bit OS X platform.
They're in sysendian.h, which is shared with other software I wrote.
--
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid