On Mon, Sep 22, 2003 at 10:23:59AM -0700, Steve Stancliff wrote: >Package: beecrypt2 >Version: 2.2.0-pre1-3 >Severity: important > >ARM machines have a screwy endianness. I thought I had found a >way to deal with it by using beecrypt functions, but I >discovered that beecrypt fails to deal with it. > >For instance, the number 1.0000 as a double is stored in memory >on x86 as >0:0:0:0:0:0:240:63 > and on the arm as >0:0:0:0:63:240:0:0 > >Using the beecrypt function encodeDouble should convert both to >the same "network order." Instead it gives: > >(x86) 63:240:0:0:0:0:0 >(arm) 0:0:0:0:63:240:0:0 > >The whole purpose of the function encodeDouble is to allow >doubles to be encoded in a machine-agnostic way, so this >functionality is broken.
Steve, Please let me know if this problem is fixed with libbeecrypt6 4.1.2-1. Thanks, Anibal Monsalve Salazar -- .''`. Debian GNU/Linux : :' : Free Operating System `. `' http://debian.org/ `- http://v7w.com/anibal
signature.asc
Description: Digital signature
