SiMU Pro released to the App Store!

  • Download SiMU Pro at:
  • Visit the forum at:
  • SiMU works with the UCS Simulator available at
  • This software is not sponsored by or supported by Cisco Systems.
  • Read-write usernames are now usable. Some options can be changed in the system. PLEASE be careful, and use a RO username if you are worried about making a human error.

Monday, January 17, 2011

SiMU Pro - Released!

SiMU Pro was released on the iTunes App Store today.  SiMU Pro is almost identical to SiMU Lab, with the exception of being able to do SSL encryption.  SiMU Pro can securely be used to connect to a production system.  As always, please test SiMU with a Read Only username if you are not comfortable with the security and or the testing that I have completed.  I make no promises as to the stability or safety of this application.  I've done the best I can to make sure it won't do anything unexpected, but that doesn't mean there isn't a problem that either myself or my beta testers didn't find.

A note about the security of SiMU Pro.  The application will ignore all warnings of a self signed certificates. Basically, I don't look at certificates at all.

Thanks for using SiMU Pro!

Thursday, January 13, 2011

Things are going well

Today my app changed from "Waiting for export compliance" to "waiting for review". I don't want to get my hopes up too much, but that sure seems like I have passed the requirements to export my app with encryption.

I have a ucsm simulator running in a virtual machine at my house now with a dynamic dns hostname pointed to my router with the proper inbound rules to allow the app to be tested by Apple. It only took a day to two last time to test the app.

Once I know for sure that my method of getting encryption export authorization works I'll make a full post of how it's done.

Update:  I posted my instructions here in my other blog.


Wednesday, January 12, 2011

Crossing Fingers

I finally read a few more obscure sections of the BIS web site, tried calling the person at the bottom of the message I received (he never answered or returned my calls), and finally came to the conclusion that I was rejected because I didn't need to get a CCATS number.

With that in mind I started looking around more and I noticed that I could also submit an ERN number to Apple. I had read a few things about ERN (Encryption Registration Number), and was already investigating how to get this.  An ERN number allows you to export standard encryption technology, and report each year on your product (software). This is the notice on the Apple encryption page:

So I went back to the SNAP-R site and found how to do this here:

I filled out the short form they wanted and submitted it. I received instant approval. I took that approval and pasted the web screen into a word document along with the information that I was using HTTPS/SSL in the app and submitted the entire thing to Apple.

This is a copy of the message a received back from BIS that I pasted into the document for Apple.

I'll update the blog again when/if I get approval from Apple.  Hopefully that will be soon.  It in "Waiting for Export Compliance" right now after I uploaded the binary.