|
1 | 1 | # CanaryiOS |
2 | 2 |
|
3 | | -An iOS library designed to power iOS apps. Based on the [original project](https://github.com/OperatorFoundation/CanaryLibrary.git) written in Swift. |
| 3 | +An example iOS application to demonstrate one way to use the [Canary Library for iOS](https://github.com/OperatorFoundation/CanaryLibraryiOS.git). |
4 | 4 |
|
5 | | -Canary is a tool for testing transport connections and gathering the packets for analysis. |
| 5 | +Canary is a tool for testing transport connections and recording the results in an easy to share csv format. |
6 | 6 |
|
7 | 7 | Canary will run a series of transport tests based on the configs that you provide. It is possible to test each transport on a different transport server based on what host information is provided in the transport config files. |
8 | 8 |
|
9 | | -Currently only [Shadow](https://github.com/OperatorFoundation/ShapeshifterAndroidKotlin.git) tests are supported. Replicant support is underway, and will be capable of mimicking other transports when it is complete. |
10 | | - |
11 | | -## Generate Shadow config files |
12 | | -Go to: [ShadowSwift](https://github.com/OperatorFoundation/ShadowSwift.git). |
| 9 | +Currently [Shadow](https://github.com/OperatorFoundation/ShadowSwift.git) and [Starbridge](https://github.com/OperatorFoundation/Starbridge.git) tests are supported. Replicant support is underway, and will be capable of mimicking other transports when it is complete. |
13 | 10 |
|
14 | 11 | ## Running Canary |
15 | | -Transport configs should include their transport server IP and port, and should include the transport name in the name of the file. |
16 | | -Canary client config files must be saved in the file management system of the device. Config files must conform to the following convention: |
17 | 12 |
|
18 | | - {"serverIP":"127.0.0.1","password":"enterYourClientConfigPassword","cipherName":"DarkStar","port":1234} |
| 13 | +*This example app requires iOS 16 or higher.* |
| 14 | + |
| 15 | +### To run Canary transport connection tests: |
| 16 | +- In the app select the directory that has the config files for the transports that you want to use for connection tests (transport client config files must be saved in the file management system of the device). |
| 17 | +- Select the number of times you would like the tests to be repeated. |
| 18 | +- Tap the "Run Tests" button to start the connection tests. |
| 19 | + |
| 20 | +### To view transport connection test results: |
| 21 | +- Tap the "view results" button |
| 22 | +- Tap the result file of your choice (A list of file names will be shown, each file is named with the day the tests were run) |
| 23 | +- The following screen will show the results of each test in the file in text format. |
| 24 | +- Tap the share button in the top right-hand corner to share the results as a csv file. |
| 25 | + |
| 26 | +## Transport config files |
| 27 | + |
| 28 | +See the documenation for a specific transport if you need instructions on how to generate config files for Canary supported transports: |
| 29 | +- [Starbridge](https://github.com/OperatorFoundation/Starbridge.git) |
| 30 | +- [ShadowSwift](https://github.com/OperatorFoundation/ShadowSwift.git) |
19 | 31 |
|
20 | | -Once configured, Canary iOS allows users to run tests, view results, and share results. |
| 32 | +Config files must conform to the following convention: |
| 33 | +- They must be valid JSON files that conform to the specific transport requirements (e.g. Shadow, Starbridge). |
| 34 | +- File names must include the name of the specific transport (e.g. "ShadowClientConfig.json", "StarbridgeClientConfig.json"). |
0 commit comments