I've been working with the downloaded Crypto Toolbox plug-in, but haven't been able to get "confirmable" results. I base that statement on the fact that when I pass a published test vector to it, its encrypted RC4 result differs from what is expected.

I'm using the downloaded windows demo: Link

And the Wikipedia test vector #3: Link

Instead of: 45A01F645FC35B383552544B9BF5

I get: B24AC097402519B687451D870623

Anyone willing to speculate on what the problem might be? I have confirmed that the crypto.fmx can decrypt its own encrypted text, but I need to send the encrypted result to an external application.

Also, it would be helpful if someone with crypto.fmx installed could independently confirm my results.

Thanks for any help.

The mystery is solved. As it turns out, Crypto Toolbox doesn't supply an RC4-encrypted result -- at least not in any industry-compatible way. The answer was in one of the accompanying files:

S.everal L.ayered O.mnipurpose B.oring B.inary E.ncryption R.outine

How your data is encrypted, the SLOBBER way:

---- ----- ----- -- --------------

1) ROT encoded based on Key (for obscurity).

2) Encrypted using scheme selected by you, using a key of variable bit-length provided by you.

3) TextToASCII encoded (for portability and obscurity).

Too bad he didn't provide an option for true RC4. Oh, well ...