From: Globemaker on
On Jul 6, 8:52 am, Noob <r...(a)127.0.0.1> wrote:
> Globemaker wrote:
> > Please recommend where I can download an AES program with the
> > following attributes:
> > 1 The program should allow me to enter the key, not a passphrase.
> > 2 It should be free
> > 3 For Windows XP
> > 4 The ciphertext must have the same number of bytes as the plaintext
> > that is padded to 128 bit blocks
> > 5 The ciphertext must succeed in one test vector from NIST for
> > Electronic Code Book mode
> > KEY = 00000000000000000000000000000000
> > PLAINTEXT = 80000000000000000000000000000000
> > CIPHERTEXT expected = 3ad78e726c1ec02b7ebfe92b23d9ec34
>
> OpenSSL perhaps?http://en.wikipedia.org/wiki/OpenSSL
>
> $ openssl aes-128-ecb -e -in temp.in -out temp.out -nosalt -nopad -iv 0 -K 0
> $ hexdump -C temp.in
> 00000000  80 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |.................|
> $ hexdump -C temp.out
> 00000000  3a d7 8e 72 6c 1e c0 2b  7e bf e9 2b 23 d9 ec 34  |:..rl...+~..+#..4|

Thank you, OpenSSL looks like the right tool for controlling AES at
the level of detail that I want.
From: Tom St Denis on
On Jul 7, 12:06 pm, Globemaker <alanfolms...(a)cabanova.com> wrote:
> I downloaded the OpenSSL software and validated its AES function.
> The publisher of (snipped) (me) is using OpenSSL
> to encrypt files. It was tested for being a valid AES program. The
> need for compatability of AES programs is motivated by the goal of
> this Magazine to post encrypted essays that strangers can decrypt
> using any valid AES software. Some AES software is not compatible with
> other AES software.

If that's your goal, if it's truly your goal to encourage people to
use crypto why not use GPG in conventional mode with a known
password? it's actually easier... e.g.

gpg -c plaintext

Produces plaintext.gpg

gpg -d plaintext.gpg

Produces plaintext.

At the very least promoting that would show people how they could
encrypt their own files (with appropriately chosen passwords) as
opposed to encrypting files in ECB mode which is NOT recommended.

Tom
From: Tom St Denis on
On Jul 7, 2:40 pm, Globemaker <alanfolms...(a)cabanova.com> wrote:
> If AES ciphertext cannot be handled by various software products, that
> is a problem. My goal is to identify incompatible AES software and
> highlight AES software that allows interoperability.

I have no idea what you're rambling about. I'm fairly certain GPG
won't decrypt some random ECB encrypted data. That doesn't mean that
GPG is broken, it means the authors of GPG know more about
cryptography than you because they're not using a cipher in ECB mode
to encrypt a message longer than the block size of the cipher.

Cheers,

Tom
From: Bruce Stephens on
Globemaker <alanfolmsbee(a)cabanova.com> writes:

[...]

> Ciphertext produced by OpenSSL should be ready to be decrypted by gpg.

Why? Ciphertext produced by GPG ought to be decryptable by PGP (and
vice versa), I think, because (AIUI) they both implement OpenPGP. But I
don't think GPG is intended to offer raw AES (as OpenSSL does).

I imagine one could use cryptlib, Crypto++, Bouncy Castle, etc., to
write something that does raw AES and that ought to work. I'm not sure
whether command lines to do that exist; it seems likely they're rare.

[...]