Rijndael encryption

You would probably need to bring the entire 160MB framework into your application bundle for it to work as-is.

OpenSSL is in no way dependent upon Ruby however, so I'm not sure what that include statement has to do with this.

openssl is not available on the iPhone.

The supported libraries are in CommonCrypo, and they may not do everything the openssl libraries do depending on your needs.

rob.

Where is XCode supposed to look for a framework that isn't installed on the device?

If you can't find a ready-made framework then I'd say download and compile OpenSSL yourself. It's very portable and it's not that big.

Is anything this application does worth nearly 200MB of space? If not, I'd look for a non-Ruby solution. If so, then I'd ask a lawyer whether or not you can actually re-distribute the thing. Ruby's free but Ruby.framework is maintained by Apple and may not be.

But again, Ruby has nothing to do with OpenSSL. If that's the only thing you need, then grab it yourself.

If a program at App Store includes encryption software, Apple wants some signed paper
from US Export regulators.

http://www.bis.doc.gov/encryption/default.htm

As I understand, the US government has less restrictions on open source (and Rijndael lib), and allow export for 128 bit
in code exported from US. At the moment Apple does not in the Interface at App Store upload, allow us to select this open source option.

I requested Apple some time ago about this issue, but they have never returned with an answer.

Before you use more time on Rijndael code, I will suggest you get a green light from Apple. And tell us if you get it 🙂

This is what they say in iTunes if you select encryption:

"A copy of the commodity classification ruling (CCATS) confirming classification of the Product under ECCN 5D992, as a mass market encryption item under section 742.15(b)(2) of the Export Administration Regulations OR a copy of the “Notification” described in 742.15(b)(1), must be attached."

The notification described in 742.15(b)(1) is, from what I can tell, simply:

http://www.bis.doc.gov/encryption/pubavailencsourcecodenofify.html

Whic is just an email to BIS following a pretty basic template.

Apple isn't particularly clear about what they're willing to accept.

It's all a little annoying that they have been so vague on the requirements. I get the sense it's lawyers and make work, but hey, what do I know.

No kidding. My app's been stuck there for 15 days now with "Waiting for Export Compliance Sign Off". For all I know 15 days will become 15 weeks before I hear back from dear Apple. Wish I hadn't used encryption at all.

To blazespinnaker

you are correct using open source should be easy. Special if you just wants to link an existing library.

The problem is Apple wants a document, and as I can see BIS does not offer an official document for open source. They just ask us to send an email telling where the source is, and thats all.

Apple needs an option in the registration interface, to select open source without BIS restrictions.

I asked Apple for advice 3 July 2008, and all I have seen is a standard mail confirmation with ID 50789051

Wonder if Apple reads this Discussion board.

Yeah, I put my TSU NOTIFICATION in a pdf (via Google Docs) and uploaded that.

I've seen Apache do TSU NOTIFICATIONs as well, and all they do is publish the basic template described in the link above with name of the product (Apache, etc) and link to the source files.

I'm going to try calling the BIS and see what they say. Perhaps I should just get it reviewed. The process seems pretty murky unfortunately.