powered by Jive Software

As3crypto source


#1

From what I’ve read in this discussion group, the as3crypto.swc that’s included with the xiff download seems to have been branched and patched quite a bit from the original on Google Code. I can only find the .swc file in the download and in svn for XIFF. Is the source available somewhere here? Thanks.


#2

as3crypto


http://code.google.com/p/as3crypto

Originally added 2010-02-25, via

http://issues.igniterealtime.org/browse/XIFF-69

Then patched via

http://issues.igniterealtime.org/browse/XIFF-73

Fix for as3crypto issue 22: flex2.compiler.as3.SignatureExtension.SignatureGenerationFailed when compiling com.hurlant.crypto.symmetric.AESKey

http://code.google.com/p/as3crypto/issues/detail?id=22

Fix for as3crypto compile error: A file found in a source-path ‘pkcs9unstructuredString’ must have the same name as the class definition inside the file ‘universalString’.

Fix for as3crypto issue 25: TLSSocket “pure virtual function call”

http://code.google.com/p/as3crypto/issues/detail?id=25


#3

Added an issue for explaining 3rd party libs

http://issues.igniterealtime.org/browse/XIFF-113


#4

There are definitely a lot more differences/additions than the couple of minor issues you have listed here. I decompiled the xiff .swc and found quite a few more classes in the xiff version of as3cypto than in the original version. Unfortunately I can’t quite get the decompiled version to compile back. Looks like the decompiler generated a few lines of syntactically incorrect code, but I’m not quite sure what the problem is yet.

Note the xiff version of as3cypto works fine for me. I just need to be able to reproduce it myself from source.

Will the source for this customized version of as3crypto be released in svn in 3.2?

Thanks


#5

In that case, could it be this?

https://github.com/timkurvers/as3-crypto

I could not find any reference to it from SVN log, but it is mentioned in these forums…


#6

Yeap, that’s it. Like you, I found a link to it in another post. So far, it seems to work.

Thanks!


#7

Just updated the SVN version to match the one in Github.


#8

Excellent! Thanks again.


#9

hi!

if you are going to use xiff+as3crypto on iOS device for TLS connection you should apply a patch from upstream issue list http://code.google.com/p/as3crypto/issues/detail?id=72 to as3-crypto fork by tim kurvers


#10

Nice catch,

Could you open an issue at https://github.com/timkurvers/as3-crypto/issues for that?


#11

Talked earlier about including this patch with Tim Kurvers… but it seems that root cause for this is a bug in AIR SDK, and may have been fixed in version 3.3.

Here are some links about the bug:

http://blog.flexibleair.pl/2012/02/adobe-air-ios-packager-bug/

http://zonmobiledev.com/index.php/blog/80-signednot-signed-compare-issue-in-air- packager-for-ios

https://bugbase.adobe.com/index.cfm?event=bug&id=3010515

https://bugbase.adobe.com/index.cfm?event=bug&id=3155649


#12

We have been testing with this version (https://github.com/timkurvers/as3-crypto) on our internal LAN ever since I found it, but when I take it out to the internet and test with, say, Google talk, it doesn’t work. The only way I can get it to work with Google talk is with the as3crypto.swc that was included with the nightly builds. So I’m thinking that .swc included with your distribution was not compiled with the Kurvers version you referenced. I even tried going back to the 1.3a Kurvers version in case a bug was introduced in 1.4.0 that he has as his latest.

So you may have replaced the as3crypt.swc you already had with a less patched version when you updated your Subversion at revision 13288 with the Kurves build. I cannot find any more update to date source code versions though, so I was thinking you may have one internally.