SeaCat Starter Pack (iOS)

Foreword

SeaCat starter pack is a distribution package, prepared to allow quick evaluation and understanding of how SeaCat product works. It is also a boilerplate for new mobile applications equipped with SeaCat.

The package consists of a simple iOS application, pre-integrated with SeaCat framework (SDK) and pre-configured gateway. Beside configuration, the gateway contains a simple CSR utility that allows the gateway to approve newly connected users either automatically or from the command-line.

SeaCat license is pre-installed in the starter pack.

Users can start building their mobile application based on the code in the starter pack or use it purely for evaluation or educational purposes.

To start with SeaCat starter pack, for those who have requested the pack, you should receive an email with download links. If this is not the case, please contact us at support@teskalabs.com.

( If you want a similar starter pack, please send an email to above address with "Request for SeaCat Starter Pack" in the subject line. We will follow up with you immediately. )

Instructions

  1. Download and unpack "SeaCat Gateway Starter pack" using the link from our email.
  2. Open 'Terminal' application and go to 'seacat' directory that has been created in previous step.
  3. Launch SeaCat gateway by './run.sh' script:
    SeaCat gateway run
  4. Download and unpack "SeaCat iOS Starter pack" using the link from our email.
  5. Start Xcode and open the project file that has been unpacked in the previous step.
  6. Run mobile application in iPhone simulator:
    SeaCat eval app
    At this point, the mobile app waits for Certificate Signing Request approval at the gateway side.
    This process is typically integrated with a backend of the mobile application. However, we will manually approve CSR using seacat-csr utility.

  7. Open a new session of 'Terminal' and go to the folder where you unpacked "SeaCat Gateway Starter pack".

  8. Run './csr.sh' command - you should be asked to approve one CSR, press 'y' + ENTER:
    SeaCat CSR
  9. Mobile application progresses to its main window and displays the result of HTTP call.

Gateway configuration

The initial gateway network location is set to localhost (127.0.0.1) port 7443 (TCP).

Please let us know if you want a different setup by sending an email to support@teskalabs.com, please don't forget to include your application bundle ID.

Configuration of SeaCat gateway can be found at seacat/etc/seacat.conf

There are two hosts pre-configured in SeaCat gateway:

  • localhost.seacat points to http://localhost/
  • evalhost.seacat points to http://eval.teskalabs.com/

Client certificates are stored in seacat/var/cert directories. You can freely investigate details of these certificates using standard tools. By physically removing the certificate file, you remove a given client (mobile app instance) from the whitelist, and this client will lose access to SeaCat gateway. In that case, the Seacat starter pack application will automatically generate and submit a new CSR.

License remarks

There are no limitations in terms of number of devices, users whatsoever. However, there is an expiration time set in evaluation license.

The license is bound to one specific application id (bundle id on Apple iOS platform).

The license can be used both in a simulator and on a real device.

Users are prohibited and unauthorized to resell or pass this license to third parties.

Reach out to us via email or follow us on Twitter @TeskaLabs for additional updates.

About the Author

Ales Teska

TeskaLabs’ founder and CEO, Ales Teska, is a driven innovator who proactively builds things and comes up with solutions to solve practical IT problems.


TurboCat.io

Data encryption tool for GDPR

More information


You Might Be Interested in Reading These Articles

Q&A: Mobile App Developers Asked How SeaCat Will Protect Their Apps, Backend, and the Data. Here Are the Answers

We've spent a great deal of time talking to mobile app developers to understand their approach to handling mobile application security. In this Q&A, we put together the answers to the most common questions asked by these app developers.

Continue reading ...

tech

Published on May 07, 2015

SeaCat Mobile Secure Gateways' Performance Test

We decided to perform this test to validate our architectural, design and implementation decisions in regards to SeaCat performance. Our goal was to build the best-in-class product using the most advanced techniques to deliver highest possible throughput yet not compromising the security of the communication. Results of the test have been fed back into our development team to improve further overall performance characteristics of the solution.

Continue reading ...

tech

Published on July 21, 2014

What TCP port to use with SeaCat?

SeaCat requires to specify one TCP port that is eventually used for client-gateway communication. Clients connect to this port to establish TLS channel that is used to exchange requests and related responses. SPDY-based communication protocol is used for traffic in this channel.

Continue reading ...

tech

Published on May 23, 2014