Problem with custom EventMachine and SSL

[Aaron Huber]

We're trying to switch out our Cloud Foundry environment to use an S3-compatible object store instead of NFS for the blobstore, and running into a problem with Iron Foundry not being able to download any objects due to not having SSL support.  When testing with a simple script using the EM HTTPRequest it just throws this error:

Encryption not available on this event-machine

We're able to get it working using the standard eventmachine x86-mingw32 but as soon as we replace it with the one custom compiled from your git fork the SSL support goes away.  So a couple of questions:

1) Is it really necessary to use the non-standard EM gem?  What will break if we don't?

2) Any idea how to compile your gem to get SSL support?  I've tried about 30 different combinations using everything I can find in Google today without any luck.  :-(

Aaron Huber

Intel Corporation

[Aaron Huber]

I got it working for anyone else that needs this:

1. Download the OpenSSL package from http://packages.openknapsack.org/openssl/openssl-1.0.0k-x86-windows.tar.lzma (using an older version to line up with what's in the Ruby 1.9.3 package that IF is using).
2. Extract the files to somewhere on your system.
3. When installing eventmachine, point to the OpenSSL files so it can compile against it:
   
   gem install eventmachine-1.0.3.gem -- --with-opt-dir=C:\openssl-1.0.0k-x86-windows
   
   
4. The eventmachine gem now has SSL support.

Aaron

[Brian Button]

Aaron,

I'm glad you found a fix for that, and thanks for posting it. 

I'm assuming you're installing our fork of eventmachine, right? We had to make some changes in it to work correctly on Windows, which is why I'm asking. If you're using the stock one, you might see some issues.

bab

--
You received this message because you are subscribed to the Google Groups "Iron Foundry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ironfoundry...@googlegroups.com.
To post to this group, send email to ironf...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ironfoundry/05bbb3cb-1f00-441b-be2a-da23b69cf8da%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Brian Button

Product Manager, Application Services

CenturyLink Cloud

http://agileprogrammer.com

@brianbuttonxp

[Aaron Huber]

Yep, we're still using your forked code.  The only difference from your instructions is pointing it at the OpenSSL headers at install time so it compiles in the HTTPS support.

Aaron