I was not aware that multi-precision floating-point was a requirement
in cryptography.
Although you did not mention your programming language, I think you
should have look at MPFR from http://www.mpfr.org/.
<quote>The MPFR library is a C library for multiple-precision
floating-point computations with correct rounding.</quote>
--
Do not use the e-mail address from the header! You can get a
valid address from http://home.netsurf.de/wolfgang.ehrhardt
(Free open source Crypto, CRC/Hash, MPArith for Pascal/Delphi)
> I was not aware that multi-precision floating-point was a requirement
> in cryptography.
In a running-key (pseudo-OTP) multiplicative implementation one might
want to rely on identically-computed least-significant computed bits
from floating-point operations.
Expensive to compute, but would it be at least as expensive to search
for the more significant truncated bits to achieve key recovery?
outer
One would not want to do that unless one did not care that one's
recipient could not read the messages. The truncation and roundoff error
could well vary from machine to machine or processor to processor.
A useful crypto system must be deterministic and the recipient must
obtain the same results as the sender.
> On 2010-02-06, Richard Outerbridge <ou...@interlog.com> wrote:
> > In article <hg5c65$pe8$1...@aioe.org>, Noob <ro...@127.0.0.1> wrote:
> >
> >> I was not aware that multi-precision floating-point was a requirement
> >> in cryptography.
> >
> > In a running-key (pseudo-OTP) multiplicative implementation one might
> > want to rely on identically-computed least-significant computed bits
> > from floating-point operations.
>
> One would not want to do that unless one did not care that one's
> recipient could not read the messages. The truncation and roundoff error
> could well vary from machine to machine or processor to processor.
> A useful crypto system must be deterministic and the recipient must
> obtain the same results as the sender.
Obviously. That's true of all mechanisms, from the Jeffersonian to the
Enigma, and to DEA and AES implementations. So my question remains:
If there are incompatibilites due to hardware and software/compiler,
some appropriate trials in the basic operations should reveal these,
I suppose. Due to the fall of costs, arrangement to have communication
partners to have compatible hard- software is fortunately no longer
a severe bottle neck now as compared to decades before in my humble
view.
M. K. Shen