<p align="center">
<img src="https://raw.githubusercontent.com/fkie-cad/friTap/main/assets/logo.png" alt="friTap logo" width="50%" height="50%"/>
</p>
# friTap
 [](https://badge.fury.io/py/friTap)
friTap is a powerful tool designed to assist researchers in analyzing network traffic encapsulated in SSL/TLS. With its ability to automate key extraction, friTap is especially valuable when dealing with malware analysis or investigating privacy issues in applications. By simplifying the process of decrypting and inspecting encrypted traffic, friTap empowers researchers to uncover critical insights with ease.
Key features include seamless support for automated SSL/TLS key extraction, making it an ideal choice for scenarios requiring rapid and accurate traffic analysis. Whether you’re dissecting malicious network behavior or assessing data privacy compliance, friTap streamlines your workflow.
For more details, explore the [OSDFCon webinar slides](assets/friTapOSDFConwebinar.pdf) or check out our [blog post](https://lolcads.github.io/posts/2022/08/fritap/).
This project was inspired by [SSL_Logger](https://github.com/google/ssl_logger ) and currently supports all major operating systems (Linux, Windows, Android). More platforms and libraries will be added in future releases.
## Key Features
The main features of friTap are:
- TLS key extraction in real time (`-k key.log`)
- Decryption of TLS payload as PCAP in real time (`-p plaintext.pcap`)
- Integration with Python. [Learn more](https://github.com/fkie-cad/friTap/blob/main/INTEGRATION.md)
- Support for custom Frida scripts. [Details](https://github.com/fkie-cad/friTap/blob/main/USAGE.md#Using-friTap-with-a-custom-Frida-scripts)
- Support of most common SSL libraries (OpenSSL, BoringSSL, NSS, GnuTLS, etc.)
## Installation
Installation is simply a matter of `pip3 install fritap`. This will give you the `fritap` command. You can update an existing `fritap` installation with `pip3 install --upgrade fritap`.
## Usage
On Linux/Windows/MacOS we can easily attach to a process by entering its name or its PID:
```bash
$ sudo fritap --pcap mycapture.pcap thunderbird
```
For mobile applications we just have to add the `-m` parameter to indicate that we are now attaching (or spawning) an Android or iOS app:
```bash
$ fritap -m -k keys.log com.example.app
```
Further ensure that the frida-server is running on the Android/iOS device.
Remember when working with the pip installation you have to invoke the `fritap` command with sudo a little bit different. Either as module:
```bash
$ sudo -E python3 -m friTap.friTap --pcap mycapture.pcap thunderbird
```
or directly invoking the script:
```bash
$ which friTap
/home/daniel/.local/bin/friTap
$ sudo -E /home/daniel/.local/bin/friTap
```
friTap can also be used as a Python library within your project:
```python
from friTap import SSL_Logger
```
For more details on integrating friTap into your Python project, check out the [INTEGRATION.md](./INTEGRATION.md) guide.
friTap allows you to enhance its functionality by providing a custom Frida script during your session. This custom script will be invoked just before friTap applies its own hooks. To do so, use the `-c` parameter ([more](./USAGE.md#Using-friTap-with-a-custom-Frida-scripts)).
More examples on using friTap can be found in the [USAGE.md](./USAGE.md). A detailed introduction using friTap on Android is under [EXAMPLE.md](./EXAMPLE.md) as well.
## Hooking Libraries Without Symbols
In certain scenarios, the library we want to hook offers no symbols or is statically linked with other libraries, making it challenging to directly hook functions. For example Cronet (`libcronet.so`) and Flutter (`libflutter.so`) are often statically linked with **BoringSSL**.
Despite the absence of symbols, we can still use friTap for parsing and hooking.
### Hooking by Byte Patterns
To solve this, we can use friTap with byte patterns to hook the desired functions. You can provide friTap with a JSON file that contains byte patterns for hooking specific functions, based on architecture and platform using the `--patterns <byte-pattern-file.json>` option.
In order to apply the apprioate hooks for the various byte patterns we distinguish between different hooking categories.
These categories include:
- Dump-Keys
- Install-Key-Log-Callback
- KeyLogCallback-Function
- SSL_Read
- SSL_Write
Each category has a primary and fallback byte pattern, allowing flexibility when the primary pattern fails.
For libraries like BoringSSL, where TLS functionality is often statically linked into other binaries, we developed a tool called [BoringSecretHunter](https://github.com/monkeywave/BoringSecretHunter). This tool automatically identifies the necessary byte patterns to hook BoringSSL by byte-pattern matching. Specifically, BoringSecretHunter focuses on identifying the byte patterns for functions in the Dump-Keys category, allowing you to extract encryption keys during TLS sessions with minimal effort. More about the different hooking categories can be found in [usage of byte-patterns in friTap](./USAGE.md#hooking-by-byte-patterns).
### Hooking by Offsets
Alternatively, you can use the `--offsets <offset-file.json>` option to hook functions using known offsets. friTap allows you to specify user-defined offsets (relative to the base address of the targeting SSL/socket library) or absolute virtual addresses for function resolution. This is done through a JSON file, which is passed using the `--offsets` parameter.
If the `--offsets` parameter is used, friTap will only overwrite the function addresses specified in the JSON file. For functions that are not specified, friTap will attempt to detect the addresses automatically (using symbols).
## Problems
The absence of traffic or incomplete traffic capture in the resulting pcap file (-p <your.pcap>) may stem from various causes. Before submitting a new issue, consider attempting the following solutions:
### Default Socket Information
There might be instances where friTap fails to retrieve socket information. In such scenarios, running friTap with default socket information (`--enable_default_fd`) could resolve the issue. This approach utilizes default socket information (127.0.0.1:1234 to 127.0.0.1:2345) for all traffic when the file descriptor (FD) cannot be used to obtain socket details:
```bash
fritap -m --enable_default_fd -p plaintext.pcap com.example.app
```
### Handling Subprocess Traffic
Traffic originating from a subprocess could be another contributing factor. To capture this traffic, friTap can leverage Frida's spawn gating feature, which intercepts newly spawned processes using the `--enable_spawn_gating` parameter:
```bash
fritap -m -p log.pcap --enable_spawn_gating com.example.app
```
### Library Support exist only for Key Extraction
In cases where the target library solely supports key extraction (cf. the table below), you can utilize the `-k <key.log>` parameter alongside full packet capture:
```bash
fritap -m -p log.pcap --full_capture -k keys.log com.example.app
```
### Seeking Further Assistance
If these approaches do not address your issue, please create a detailed issue report to aid in troubleshooting. To facilitate a more effective diagnosis, include the following information in your report:
- The operating system and its version
- The specific application encountering the issue or a comparable application that exhibits similar problems
- The output from executing friTap with the specified parameters, augmented with friTap's debug output:
```bash
fritap -do -v com.example.app
```
## Supported SSL/TLS implementations and corresponding logging capabilities
```markdown
| Library | Linux | Windows | MacOSX | Android | iOS |
|---------------------------|---------------|---------------|----------|----------|--------------|
| OpenSSL | Full | R/W-Hook only | TBI | Full | TBI |
| BoringSSL | Full | R/W-Hook only | KeyEo | Full | KeyEo |
| NSS | Full | R/W-Hook only | TBI | TBA | TBI |
| GnuTLS | R/W-Hook only | R/W-Hook only | TBI | Full | TBI |
| WolfSSL | R/W-Hook only | R/W-Hook only | TBI | Full | TBI |
| MbedTLS | R/W-Hook only | R/W-Hook only | TBI | Full | TBI |
| Bouncycastle/Spongycastle | TBA | TBA | TBA | Full | TBA |
| Conscrypt | TBA | TBA | TBA | Full | TBA |
| S2n-tls | Full | LibNO | TBA | Full | LibNO |
```
**R/W-Hook only** = Logging data sent and received by process<br>
**KeyEo** = Only the keying material can be extracted<br>
**Full** = Logging data send and received by process + Logging keys used for secure connection<br>
**TBA** = To be answered<br>
**TBI** = To be implemented<br>
**LibNO** = This library is not supported for this plattform<br>
**We verified the Windows implementations only for Windows 10**
## Dependencies
- [frida](https://frida.re)
- `>= python3.7`
- click (`python3 -m pip install click`)
- hexdump (`python3 -m pip install hexdump`)
- scapy (`python3 -m pip install scapy`)
- watchdog (`python3 -m pip install watchdog`)
- importlib.resources (`python3 -m pip install importlib-resources`)
- AndroidFridaManager (`python3 -m pip install AndroidFridaManager`)
- for hooking on Android ensure that the `adb`-command is in your PATH
## Planned features
- [ ] add the capability to alter the decrypted payload
- integration with https://github.com/mitmproxy/mitmproxy
- integration with http://portswigger.net/burp/
- [ ] add wine support
- [x] <strike>add Flutter support</strike>
- [ ] add further libraries (have a look at this [Wikipedia entry](https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations)):
- Botan (BSD license, Jack Lloyd)
- LibreSSL (OpenBSD)
- Cryptlib (Peter Gutmann)
- JSSE (Java Secure Socket Extension, Oracle)
- [MatrixSSL](https://github.com/matrixssl/matrixssl)
- ...
- [x] <strike>Working with static linked libraries</strike>
- [x] <strike>Add feature to prototype TLS-Read/Write/SSLKEY functions</strike>
- [ ] improve iOS/MacOS support (currently under development)
## Contribute
Contributions are always welcome. Just fork it and open a pull request!
More details can be found in the [CONTRIBUTION.md](./CONTRIBUTION.md).
___
## Changelog
See the wiki for [release notes](https://github.com/fkie-cad/friTap/wiki#news).
## Support
If you have any suggestions, or bug reports, please create an issue in the Issue Tracker.
In case you have any questions or other problems, feel free to send an email to:
[daniel.baier@fkie.fraunhofer.de](mailto:daniel.baier@fkie.fraunhofer.de).
Raw data
{
"_id": null,
"home_page": "https://github.com/fkie-cad/friTap",
"name": "friTap",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.6",
"maintainer_email": null,
"keywords": "mobile, instrumentation, frida, hook, SSL decryption",
"author": "Daniel Baier, Francois Egner, Max Ufer",
"author_email": "daniel.baier@fkie.fraunhofer.de",
"download_url": "https://files.pythonhosted.org/packages/8b/90/2758fdd45ac164d5cb26c43e7f0bcb81afefcdcf60c83c3254a1955c99af/fritap-1.2.6.6.tar.gz",
"platform": null,
"description": "<p align=\"center\">\n <img src=\"https://raw.githubusercontent.com/fkie-cad/friTap/main/assets/logo.png\" alt=\"friTap logo\" width=\"50%\" height=\"50%\"/>\n</p>\n\n# friTap\n [](https://badge.fury.io/py/friTap)\n\nfriTap is a powerful tool designed to assist researchers in analyzing network traffic encapsulated in SSL/TLS. With its ability to automate key extraction, friTap is especially valuable when dealing with malware analysis or investigating privacy issues in applications. By simplifying the process of decrypting and inspecting encrypted traffic, friTap empowers researchers to uncover critical insights with ease.\n\nKey features include seamless support for automated SSL/TLS key extraction, making it an ideal choice for scenarios requiring rapid and accurate traffic analysis. Whether you\u2019re dissecting malicious network behavior or assessing data privacy compliance, friTap streamlines your workflow.\n\nFor more details, explore the [OSDFCon webinar slides](assets/friTapOSDFConwebinar.pdf) or check out our [blog post](https://lolcads.github.io/posts/2022/08/fritap/).\n\n\nThis project was inspired by [SSL_Logger](https://github.com/google/ssl_logger ) and currently supports all major operating systems (Linux, Windows, Android). More platforms and libraries will be added in future releases.\n\n## Key Features\n\nThe main features of friTap are:\n\n- TLS key extraction in real time (`-k key.log`)\n- Decryption of TLS payload as PCAP in real time (`-p plaintext.pcap`)\n- Integration with Python. [Learn more](https://github.com/fkie-cad/friTap/blob/main/INTEGRATION.md)\n- Support for custom Frida scripts. [Details](https://github.com/fkie-cad/friTap/blob/main/USAGE.md#Using-friTap-with-a-custom-Frida-scripts)\n- Support of most common SSL libraries (OpenSSL, BoringSSL, NSS, GnuTLS, etc.)\n\n## Installation\n\nInstallation is simply a matter of `pip3 install fritap`. This will give you the `fritap` command. You can update an existing `fritap` installation with `pip3 install --upgrade fritap`.\n\n## Usage\n\nOn Linux/Windows/MacOS we can easily attach to a process by entering its name or its PID:\n\n```bash\n$ sudo fritap --pcap mycapture.pcap thunderbird\n```\n\nFor mobile applications we just have to add the `-m` parameter to indicate that we are now attaching (or spawning) an Android or iOS app:\n\n```bash\n$ fritap -m -k keys.log com.example.app\n```\n\nFurther ensure that the frida-server is running on the Android/iOS device. \n\n\nRemember when working with the pip installation you have to invoke the `fritap` command with sudo a little bit different. Either as module:\n```bash\n$ sudo -E python3 -m friTap.friTap --pcap mycapture.pcap thunderbird\n```\nor directly invoking the script:\n```bash\n$ which friTap\n/home/daniel/.local/bin/friTap\n\n$ sudo -E /home/daniel/.local/bin/friTap\n```\n\nfriTap can also be used as a Python library within your project:\n```python\nfrom friTap import SSL_Logger\n```\nFor more details on integrating friTap into your Python project, check out the [INTEGRATION.md](./INTEGRATION.md) guide.\n\nfriTap allows you to enhance its functionality by providing a custom Frida script during your session. This custom script will be invoked just before friTap applies its own hooks. To do so, use the `-c` parameter ([more](./USAGE.md#Using-friTap-with-a-custom-Frida-scripts)).\nMore examples on using friTap can be found in the [USAGE.md](./USAGE.md). A detailed introduction using friTap on Android is under [EXAMPLE.md](./EXAMPLE.md) as well.\n\n## Hooking Libraries Without Symbols\n\nIn certain scenarios, the library we want to hook offers no symbols or is statically linked with other libraries, making it challenging to directly hook functions. For example Cronet (`libcronet.so`) and Flutter (`libflutter.so`) are often statically linked with **BoringSSL**.\n\nDespite the absence of symbols, we can still use friTap for parsing and hooking.\n\n### Hooking by Byte Patterns\n\nTo solve this, we can use friTap with byte patterns to hook the desired functions. You can provide friTap with a JSON file that contains byte patterns for hooking specific functions, based on architecture and platform using the `--patterns <byte-pattern-file.json>` option.\nIn order to apply the apprioate hooks for the various byte patterns we distinguish between different hooking categories.\nThese categories include:\n\n - Dump-Keys\n - Install-Key-Log-Callback\n - KeyLogCallback-Function\n - SSL_Read\n - SSL_Write\n\nEach category has a primary and fallback byte pattern, allowing flexibility when the primary pattern fails.\nFor libraries like BoringSSL, where TLS functionality is often statically linked into other binaries, we developed a tool called [BoringSecretHunter](https://github.com/monkeywave/BoringSecretHunter). This tool automatically identifies the necessary byte patterns to hook BoringSSL by byte-pattern matching. Specifically, BoringSecretHunter focuses on identifying the byte patterns for functions in the Dump-Keys category, allowing you to extract encryption keys during TLS sessions with minimal effort. More about the different hooking categories can be found in [usage of byte-patterns in friTap](./USAGE.md#hooking-by-byte-patterns).\n\n### Hooking by Offsets\n\nAlternatively, you can use the `--offsets <offset-file.json>` option to hook functions using known offsets. friTap allows you to specify user-defined offsets (relative to the base address of the targeting SSL/socket library) or absolute virtual addresses for function resolution. This is done through a JSON file, which is passed using the `--offsets` parameter.\n\nIf the `--offsets` parameter is used, friTap will only overwrite the function addresses specified in the JSON file. For functions that are not specified, friTap will attempt to detect the addresses automatically (using symbols).\n\n\n## Problems\n\nThe absence of traffic or incomplete traffic capture in the resulting pcap file (-p <your.pcap>) may stem from various causes. Before submitting a new issue, consider attempting the following solutions:\n\n### Default Socket Information\n\nThere might be instances where friTap fails to retrieve socket information. In such scenarios, running friTap with default socket information (`--enable_default_fd`) could resolve the issue. This approach utilizes default socket information (127.0.0.1:1234 to 127.0.0.1:2345) for all traffic when the file descriptor (FD) cannot be used to obtain socket details:\n\n```bash\nfritap -m --enable_default_fd -p plaintext.pcap com.example.app\n```\n\n### Handling Subprocess Traffic\n\nTraffic originating from a subprocess could be another contributing factor. To capture this traffic, friTap can leverage Frida's spawn gating feature, which intercepts newly spawned processes using the `--enable_spawn_gating` parameter:\n\n```bash\nfritap -m -p log.pcap --enable_spawn_gating com.example.app\n```\n\n### Library Support exist only for Key Extraction\n\nIn cases where the target library solely supports key extraction (cf. the table below), you can utilize the `-k <key.log>` parameter alongside full packet capture:\n\n```bash\nfritap -m -p log.pcap --full_capture -k keys.log com.example.app\n```\n\n### Seeking Further Assistance\n\nIf these approaches do not address your issue, please create a detailed issue report to aid in troubleshooting. To facilitate a more effective diagnosis, include the following information in your report:\n\n- The operating system and its version\n- The specific application encountering the issue or a comparable application that exhibits similar problems\n- The output from executing friTap with the specified parameters, augmented with friTap's debug output:\n```bash\nfritap -do -v com.example.app\n```\n\n\n## Supported SSL/TLS implementations and corresponding logging capabilities\n\n```markdown\n| Library | Linux | Windows | MacOSX | Android | iOS |\n|---------------------------|---------------|---------------|----------|----------|--------------|\n| OpenSSL | Full | R/W-Hook only | TBI | Full | TBI |\n| BoringSSL | Full | R/W-Hook only | KeyEo | Full | KeyEo |\n| NSS | Full | R/W-Hook only | TBI | TBA | TBI |\n| GnuTLS | R/W-Hook only | R/W-Hook only | TBI | Full | TBI |\n| WolfSSL | R/W-Hook only | R/W-Hook only | TBI | Full | TBI |\n| MbedTLS | R/W-Hook only | R/W-Hook only | TBI | Full | TBI |\n| Bouncycastle/Spongycastle | TBA | TBA | TBA | Full | TBA |\n| Conscrypt | TBA | TBA | TBA | Full | TBA |\n| S2n-tls | Full | LibNO | TBA | Full | LibNO |\n```\n**R/W-Hook only** = Logging data sent and received by process<br>\n**KeyEo** = Only the keying material can be extracted<br>\n**Full** = Logging data send and received by process + Logging keys used for secure connection<br>\n**TBA** = To be answered<br>\n**TBI** = To be implemented<br>\n**LibNO** = This library is not supported for this plattform<br>\n\n**We verified the Windows implementations only for Windows 10**\n\n## Dependencies\n\n- [frida](https://frida.re)\n- `>= python3.7`\n- click (`python3 -m pip install click`)\n- hexdump (`python3 -m pip install hexdump`)\n- scapy (`python3 -m pip install scapy`)\n- watchdog (`python3 -m pip install watchdog`)\n- importlib.resources (`python3 -m pip install importlib-resources`)\n- AndroidFridaManager (`python3 -m pip install AndroidFridaManager`)\n- for hooking on Android ensure that the `adb`-command is in your PATH\n\n## Planned features\n\n- [ ] add the capability to alter the decrypted payload\n - integration with https://github.com/mitmproxy/mitmproxy\n - integration with http://portswigger.net/burp/\n- [ ] add wine support\n- [x] <strike>add Flutter support</strike>\n- [ ] add further libraries (have a look at this [Wikipedia entry](https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations)):\n - Botan (BSD license, Jack Lloyd)\n - LibreSSL (OpenBSD)\n - Cryptlib (Peter Gutmann)\n - JSSE (Java Secure Socket Extension, Oracle)\n - [MatrixSSL](https://github.com/matrixssl/matrixssl) \n - ...\n- [x] <strike>Working with static linked libraries</strike>\n- [x] <strike>Add feature to prototype TLS-Read/Write/SSLKEY functions</strike>\n- [ ] improve iOS/MacOS support (currently under development)\n\n## Contribute\n\nContributions are always welcome. Just fork it and open a pull request!\nMore details can be found in the [CONTRIBUTION.md](./CONTRIBUTION.md).\n___\n\n## Changelog\n\nSee the wiki for [release notes](https://github.com/fkie-cad/friTap/wiki#news).\n\n## Support\n\nIf you have any suggestions, or bug reports, please create an issue in the Issue Tracker.\n\nIn case you have any questions or other problems, feel free to send an email to:\n\n[daniel.baier@fkie.fraunhofer.de](mailto:daniel.baier@fkie.fraunhofer.de).\n",
"bugtrack_url": null,
"license": "GPL v3",
"summary": "Simplifying SSL/TLS traffic analysis for researchers by making SSL/TLS decryption effortless. Decrypts and logs a process's SSL/TLS traffic on all major platforms. Further it allows the SSL/TLS key extraction.",
"version": "1.2.6.6",
"project_urls": {
"Homepage": "https://github.com/fkie-cad/friTap"
},
"split_keywords": [
"mobile",
" instrumentation",
" frida",
" hook",
" ssl decryption"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "05c5c7ce38601d1d9da149587d698a198a70255add4a8f7b4cb2f107074ca0cf",
"md5": "db46abc9ecd4ae47774a45dc2bc9f5a9",
"sha256": "e6de15b8bf5402ff913e20c21bfcf92a3b93399be7766c86bcce37f887a7cce0"
},
"downloads": -1,
"filename": "friTap-1.2.6.6-py3-none-any.whl",
"has_sig": false,
"md5_digest": "db46abc9ecd4ae47774a45dc2bc9f5a9",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.6",
"size": 5378825,
"upload_time": "2024-12-23T12:53:07",
"upload_time_iso_8601": "2024-12-23T12:53:07.577336Z",
"url": "https://files.pythonhosted.org/packages/05/c5/c7ce38601d1d9da149587d698a198a70255add4a8f7b4cb2f107074ca0cf/friTap-1.2.6.6-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "8b902758fdd45ac164d5cb26c43e7f0bcb81afefcdcf60c83c3254a1955c99af",
"md5": "dbb2bffaf90cacc97ea337941efb0e1a",
"sha256": "af919c10504953fa9ddff8fc5c0cd866e5304e01bd1c334c9e270f64c6125f2a"
},
"downloads": -1,
"filename": "fritap-1.2.6.6.tar.gz",
"has_sig": false,
"md5_digest": "dbb2bffaf90cacc97ea337941efb0e1a",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.6",
"size": 5366131,
"upload_time": "2024-12-23T12:53:26",
"upload_time_iso_8601": "2024-12-23T12:53:26.182557Z",
"url": "https://files.pythonhosted.org/packages/8b/90/2758fdd45ac164d5cb26c43e7f0bcb81afefcdcf60c83c3254a1955c99af/fritap-1.2.6.6.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-12-23 12:53:26",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "fkie-cad",
"github_project": "friTap",
"travis_ci": false,
"coveralls": false,
"github_actions": false,
"requirements": [
{
"name": "frida",
"specs": [
[
">=",
"15.0.0"
]
]
},
{
"name": "frida-tools",
"specs": [
[
">=",
"10.0.0"
]
]
},
{
"name": "AndroidFridaManager",
"specs": []
},
{
"name": "hexdump",
"specs": []
},
{
"name": "scapy",
"specs": []
},
{
"name": "watchdog",
"specs": []
},
{
"name": "click",
"specs": []
},
{
"name": "importlib-resources",
"specs": []
}
],
"lcname": "fritap"
}
JSON
