Re: Axcrypt program
ross_at_nospam.com
Date: 07/17/05
- Next message: steven: "Re: Mersenne Twister"
- Previous message: ross_at_nospam.com: "Re: Axcrypt program"
- In reply to:(deleted message) Sebastian Gottschalk: "Re: Axcrypt program"
- Next in thread: Paul Rubin: "Re: Axcrypt program"
- Reply: Paul Rubin: "Re: Axcrypt program"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 17 Jul 2005 13:46:23 +0800
Sebastian Gottschalk <seppi@seppig.de> wrote:
>Due to it's partially written in Delphi, the ABI compatibility is bad. You
>can't compile the C++ part without anything else other than Borland C++
>Builder, or it won't work. No, it's not just the calling convention thing.
I suppose it might be worth pointing that out - but remember that an executable
is provided, so the main role of source code is to allow the public assessment
of the algorithm. It really doesn't matter if a given reader doesn't have the
platform to build it, because that's not how you assess an algorithm.
In case this matter has distracted us, may I rephrase my original question:
is the this implementation of AES OK or not? In other words, is it a safe
thing to use for encrypting personal data? I am not talking about national
security here. I would be happy if the implementation was judged to be sound,
so I can focus on the non-cryptographic issues of key storage, etc, where I can
assess the risks for myself.
thanks
ross
- Next message: steven: "Re: Mersenne Twister"
- Previous message: ross_at_nospam.com: "Re: Axcrypt program"
- In reply to:(deleted message) Sebastian Gottschalk: "Re: Axcrypt program"
- Next in thread: Paul Rubin: "Re: Axcrypt program"
- Reply: Paul Rubin: "Re: Axcrypt program"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|