- when adding a new SSL/TLS library it should be created inside the agent/ssl_lib folder as
<library-name>.ts. Than the actual invocation should be done for the appropriate operating system. This means when creating boringssl support for Android we develop our approach inside agent/ssl_lib folder, but its invocation will be handled by the android_agent.ts inside theangent/android/folder. In order to invocate our new library we need to extend from its superclass (s. openssl_boringssl_android.ts). All classes of a "library-hook" for an operating system following the same structure and get registered in android_agent.ts. - for each new library we want to build a ground truth so that we can ensure that the library is working at least when it is compiled by default
- to get a better understanding of the internals of friTap have look at this blog post explaining the program flow
- while debugging your new library we suggest using the debugging feature of friTap. Moure about this in our wiki