Home
Softono
t

trailofbits

Professional software vendor delivering innovative solutions on the Softono platform. Specialized in both open-source and proprietary software development.

Total Products
2

Software by trailofbits

trailofbits/algo
Open Source

trailofbits/algo

# Algo VPN [![Twitter](https://img.shields.io/twitter/url/https/twitter.com/fold_left.svg?style=social&label=Follow%20%40AlgoVPN)](https://x.com/AlgoVPN) Algo VPN is a set of Ansible scripts that simplify the setup of a personal WireGuard and IPsec VPN. It uses the most secure defaults available and works with common cloud providers. See our [release announcement](https://blog.trailofbits.com/2016/12/12/meet-algo-the-vpn-that-works/) for more information. ## Features * Supports only IKEv2 with strong crypto (AES-GCM, SHA2, and P-256) for iOS, MacOS, and Linux * Supports [WireGuard](https://www.wireguard.com/) for all of the above, in addition to Android and Windows 11 * Generates .conf files and QR codes for iOS, macOS, Android, and Windows WireGuard clients * Generates Apple profiles to auto-configure iOS and macOS devices for IPsec - no client software required * Includes helper scripts to add, remove, and manage users * Blocks ads with a local DNS resolver (optional) * Sets up limited SSH users for tunneling traffic (optional) * Privacy-focused with minimal logging, automatic log rotation, and configurable privacy enhancements * Based on Ubuntu 22.04 LTS with automatic security updates * Installs to DigitalOcean, Amazon Lightsail, Amazon EC2, Vultr, Microsoft Azure, Google Compute Engine, Scaleway, OpenStack, CloudStack, Hetzner Cloud, Linode, or [your own Ubuntu server (for advanced users)](docs/deploy-to-ubuntu.md) ## Anti-features * Does not support legacy cipher suites or protocols like L2TP, IKEv1, or RSA * Does not install Tor, OpenVPN, or other risky servers * Does not depend on the security of [TLS](https://tools.ietf.org/html/rfc7457) * Does not claim to provide anonymity or censorship avoidance * Does not claim to protect you from the [FSB](https://en.wikipedia.org/wiki/Federal_Security_Service), [MSS](https://en.wikipedia.org/wiki/Ministry_of_State_Security_(China)), [DGSE](https://en.wikipedia.org/wiki/Directorate-General_for_External_Security), or [FSM](https://en.wikipedia.org/wiki/Flying_Spaghetti_Monster) ## Deploy the Algo Server The easiest way to get an Algo server running is to run it on your local system or from [Google Cloud Shell](docs/deploy-from-cloudshell.md) and let it set up a _new_ virtual machine in the cloud for you. 1. **Setup an account on a cloud hosting provider.** Algo supports [DigitalOcean](https://m.do.co/c/4d7f4ff9cfe4) (most user friendly), [Amazon Lightsail](https://aws.amazon.com/lightsail/), [Amazon EC2](https://aws.amazon.com/), [Vultr](https://www.vultr.com/), [Microsoft Azure](https://azure.microsoft.com/), [Google Compute Engine](https://cloud.google.com/compute/), [Scaleway](https://www.scaleway.com/), [DreamCompute](https://www.dreamhost.com/cloud/computing/), [Linode](https://www.linode.com), other OpenStack-based cloud hosting, CloudStack-based cloud hosting, or [Hetzner Cloud](https://www.hetzner.com/). 2. **Get a copy of Algo.** The Algo scripts will be run from your local system. There are two ways to get a copy: - Download the [ZIP file](https://github.com/trailofbits/algo/archive/master.zip). Unzip the file to create a directory named `algo-master` containing the Algo scripts. - Use `git clone` to create a directory named `algo` containing the Algo scripts: ```bash git clone https://github.com/trailofbits/algo.git ``` 3. **Set your configuration options.** Open `config.cfg` in your favorite text editor. Specify the users you want to create in the `users` list. Create a unique user for each device you plan to connect to your VPN. You should also review the other options before deployment, as changing your mind about them later [may require you to deploy a brand new server](https://github.com/trailofbits/algo/blob/master/docs/faq.md#i-deployed-an-algo-server-can-you-update-it-with-new-features). 4. **Start the deployment.** Return to your terminal. In the Algo directory, run the appropriate script for your platform: **macOS/Linux:** ```bash ./algo ``` **Windows:** ```powershell .\algo.ps1 ``` The first time you run the script, it will automatically install the required Python environment (Python 3.11+). On subsequent runs, it starts immediately and works on all platforms (macOS, Linux, Windows via WSL). The Windows PowerShell script automatically uses WSL when needed, since Ansible requires a Unix-like environment. There are several optional features available, none of which are required for a fully functional VPN server. These optional features are described in the [deployment documentation](docs/deploy-from-ansible.md). That's it! You can now set up clients to connect to your VPN. Proceed to [Configure the VPN Clients](#configure-the-vpn-clients) below. ``` "# Congratulations! #" "# Your Algo server is running. #" "# Config files and certificates are in the ./configs/ directory. #" "# Go to https://whoer.net/ after connecting #" "# and ensure that all your traffic passes through the VPN. #" "# Local DNS resolver 172.16.0.1 #" "# The p12 and SSH keys password for new users is XXXXXXXX #" "# The CA key password is XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX #" "# Shell access: ssh -F configs/<server_ip>/ssh_config <hostname> #" ``` ## Configure the VPN Clients Certificates and configuration files that users will need are placed in the `configs` directory. Make sure to secure these files since many contain private keys. All files are saved under a subdirectory named with the IP address of your new Algo VPN server. **Important for IPsec users**: If you want to add or delete users later, you must select `yes` at the `Do you want to retain the keys (PKI)?` prompt during the server deployment. This preserves the certificate authority needed for user management. ### Apple WireGuard is used to provide VPN services on Apple devices. Algo generates a WireGuard configuration file, `wireguard/<username>.conf`, and a QR code, `wireguard/<username>.png`, for each user defined in `config.cfg`. On iOS, install the [WireGuard](https://itunes.apple.com/us/app/wireguard/id1441195209?mt=8) app from the iOS App Store. Then, use the WireGuard app to scan the QR code or AirDrop the configuration file to the device. On macOS, install the [WireGuard](https://itunes.apple.com/us/app/wireguard/id1451685025?mt=12) app from the Mac App Store. WireGuard will appear in the menu bar once you run the app. Click on the WireGuard icon, choose **Import tunnel(s) from file...**, then select the appropriate WireGuard configuration file. On either iOS or macOS, you can enable "Connect on Demand" and/or exclude certain trusted Wi-Fi networks (such as your home or work) by editing the tunnel configuration in the WireGuard app. (Algo can't do this automatically for you.) If you prefer to use the built-in IPsec VPN on Apple devices, or need "Connect on Demand" or excluded Wi-Fi networks automatically configured, see the [Apple IPsec client setup guide](docs/client-apple-ipsec.md) for detailed configuration instructions. ### Android WireGuard is used to provide VPN services on Android. Install the [WireGuard VPN Client](https://play.google.com/store/apps/details?id=com.wireguard.android). Import the corresponding `wireguard/<name>.conf` file to your device, then set up a new connection with it. See the [Android setup guide](docs/client-android.md) for detailed installation and configuration instructions. ### Windows WireGuard is used to provide VPN services on Windows. Algo generates a WireGuard configuration file, `wireguard/<username>.conf`, for each user defined in `config.cfg`. Install the [WireGuard VPN Client](https://www.wireguard.com/install/#windows-7-8-81-10-2012-2016-2019). Import the generated `wireguard/<username>.conf` file to your device, then set up a new connection with it. See the [Windows setup instructions](docs/client-windows.md) for more detailed walkthrough and troubleshooting. ### Linux Linux clients can use either WireGuard or IPsec: WireGuard: WireGuard works great with Linux clients. See the [Linux WireGuard setup guide](docs/client-linux-wireguard.md) for step-by-step instructions on configuring WireGuard on Ubuntu and other distributions. IPsec: For strongSwan IPsec clients (including OpenWrt, Ubuntu Server, and other distributions), see the [Linux IPsec setup guide](docs/client-linux-ipsec.md) for detailed configuration instructions. ### OpenWrt For OpenWrt routers using WireGuard, see the [OpenWrt WireGuard setup guide](docs/client-openwrt-router-wireguard.md) for router-specific configuration instructions. ### Other Devices For devices not covered above or manual configuration, you'll need specific certificate and configuration files. The files you need depend on your device platform and VPN protocol (WireGuard or IPsec). * ipsec/manual/cacert.pem: CA Certificate * ipsec/manual/<user>.p12: User Certificate and Private Key (in PKCS#12 format) * ipsec/manual/<user>.conf: strongSwan client configuration * ipsec/manual/<user>.secrets: strongSwan client configuration * ipsec/apple/<user>.mobileconfig: Apple Profile * wireguard/<user>.conf: WireGuard configuration profile * wireguard/<user>.png: WireGuard configuration QR code ## Setup an SSH Tunnel If you turned on the optional SSH tunneling role, local user accounts will be created for each user in `config.cfg`, and SSH authorized_key files for them will be in the `configs` directory (user.pem). SSH user accounts do not have shell access, cannot authenticate with a password, and only have limited tunneling options (e.g., `ssh -N` is required). This ensures that SSH users have the least access required to set up a tunnel and can perform no other actions on the Algo server. Use the example command below to start an SSH tunnel by replacing `<user>` and `<ip>` with your own. Once the tunnel is set up, you can configure a browser or other application to use 127.0.0.1:1080 as a SOCKS proxy to route traffic through the Algo server: ```bash ssh -D 127.0.0.1:1080 -f -q -C -N <user>@algo -i configs/<ip>/ssh-tunnel/<user>.pem -F configs/<ip>/ssh_config ``` ## SSH into Algo Server Your Algo server is configured for key-only SSH access for administrative purposes. Open the Terminal app, `cd` into the `algo-master` directory where you originally downloaded Algo, and then use the command listed on the success message: ``` ssh -F configs/<ip>/ssh_config <hostname> ``` where `<ip>` is the IP address of your Algo server. If you find yourself regularly logging into the server, it will be useful to load your Algo SSH key automatically. Add the following snippet to the bottom of `~/.bash_profile` to add it to your shell environment permanently: ``` ssh-add ~/.ssh/algo > /dev/null 2>&1 ``` Alternatively, you can choose to include the generated configuration for any Algo servers created into your SSH config. Edit the file `~/.ssh/config` to include this directive at the top: ``` Include <algodirectory>/configs/*/ssh_config ``` where `<algodirectory>` is the directory where you cloned Algo. ## Adding or Removing Users Algo makes it easy to add or remove users from your VPN server after initial deployment. For IPsec users: You must have selected `yes` at the `Do you want to retain the keys (PKI)?` prompt during the initial server deployment. This preserves the certificate authority needed for user management. You should also save the p12 and CA key passwords shown during deployment, as they're only displayed once. To add or remove users, first edit the `users` list in your `config.cfg` file. Add new usernames or remove existing ones as needed. Then navigate to the algo directory in your terminal and run: **macOS/Linux:** ```bash ./algo update-users ``` **Windows:** ```powershell .\algo.ps1 update-users ``` After the process completes, new configuration files will be generated in the `configs` directory for any new users. The Algo VPN server will be updated to contain only the users listed in the `config.cfg` file. Removed users will no longer be able to connect, and new users will have fresh certificates and configuration files ready for use. ## Privacy and Logging Algo takes a pragmatic approach to privacy. By default, we minimize logging while maintaining enough information for security and troubleshooting. What IS logged by default: * System security events (failed SSH attempts, firewall blocks, system updates) * Kernel messages and boot diagnostics (with reduced verbosity) * WireGuard client state (visible via `sudo wg` - shows last endpoint and handshake time) * Basic service status (service starts/stops/errors) * All logs automatically rotate and delete after 7 days Privacy is controlled by two main settings in `config.cfg`: * `strongswan_log_level: -1` - Controls StrongSwan connection logging (-1 = disabled, 2 = debug) * `privacy_enhancements_enabled: true` - Master switch for log rotation, history clearing, log filtering, and cleanup To enable full debugging when troubleshooting, set both `strongswan_log_level: 2` and `privacy_enhancements_enabled: false`. This will capture detailed connection logs and disable all privacy features. Remember to revert these changes after debugging. After deployment, verify your privacy settings: ```bash ssh -F configs/<server_ip>/ssh_config <hostname> sudo /usr/local/bin/privacy-monitor.sh ``` Perfect privacy is impossible with any VPN solution. Your cloud provider sees and logs network traffic metadata regardless of your server configuration. And of course, your ISP knows you're connecting to a VPN server, even if they can't see what you're doing through it. For the highest level of privacy, treat your Algo servers as disposable. Spin up a new instance when you need it, use it for your specific purpose, then destroy it completely. The ephemeral nature of cloud infrastructure can be a privacy feature if you use it intentionally. ## Additional Documentation * [FAQ](docs/faq.md) * [Troubleshooting](docs/troubleshooting.md) * How Algo uses [Firewalls](docs/firewalls.md) ### Setup Instructions for Specific Cloud Providers * Configure [Amazon EC2](docs/cloud-amazon-ec2.md) * Configure [Azure](docs/cloud-azure.md) * Configure [DigitalOcean](docs/cloud-do.md) * Configure [Google Cloud Platform](docs/cloud-gce.md) * Configure [Vultr](docs/cloud-vultr.md) * Configure [CloudStack](docs/cloud-cloudstack.md) * Configure [Hetzner Cloud](docs/cloud-hetzner.md) ### Install and Deploy from Common Platforms * Deploy from [macOS](docs/deploy-from-macos.md) * Deploy from [Windows](docs/deploy-from-windows.md) * Deploy from [Google Cloud Shell](docs/deploy-from-cloudshell.md) * Deploy from a [Docker container](docs/deploy-from-docker.md) ### Setup VPN Clients to Connect to the Server * Setup [Windows](docs/client-windows.md) clients * Setup [Android](docs/client-android.md) clients * Setup [Linux](docs/client-linux.md) clients with Ansible * Setup Ubuntu clients to use [WireGuard](docs/client-linux-wireguard.md) * Setup Linux clients to use [IPsec](docs/client-linux-ipsec.md) * Setup Apple devices to use [IPsec](docs/client-apple-ipsec.md) * Setup Macs running macOS 10.13 or older to use [WireGuard](docs/client-macos-wireguard.md) ### Advanced Deployment * Deploy to your own [Ubuntu](docs/deploy-to-ubuntu.md) server, and road warrior setup * Deploy from [Ansible](docs/deploy-from-ansible.md) non-interactively * Deploy onto a [cloud server at time of creation with shell script or cloud-init](docs/deploy-from-script-or-cloud-init-to-localhost.md) * Deploy to an [unsupported cloud provider](docs/deploy-to-unsupported-cloud.md) If you've read all the documentation and have further questions, [create a new discussion](https://github.com/trailofbits/algo/discussions). ## Endorsements > I've been ranting about the sorry state of VPN svcs for so long, probably about > time to give a proper talk on the subject. TL;DR: use Algo. -- [Kenn White](https://twitter.com/kennwhite/status/814166603587788800) > Before picking a VPN provider/app, make sure you do some research > https://research.csiro.au/ng/wp-content/uploads/sites/106/2016/08/paper-1.pdf ... – or consider Algo -- [The Register](https://twitter.com/TheRegister/status/825076303657177088) > Algo is really easy and secure. -- [the grugq](https://twitter.com/thegrugq/status/786249040228786176) > I played around with Algo VPN, a set of scripts that let you set up a VPN in the cloud in very little time, even if you don’t know much about development. I’ve got to say that I was quite impressed with Trail of Bits’ approach. -- [Romain Dillet](https://twitter.com/romaindillet/status/851037243728965632) for [TechCrunch](https://techcrunch.com/2017/04/09/how-i-made-my-own-vpn-server-in-15-minutes/) > If you’re uncomfortable shelling out the cash to an anonymous, random VPN provider, this is the best solution. -- [Thorin Klosowski](https://twitter.com/kingthor) for [Lifehacker](http://lifehacker.com/how-to-set-up-your-own-completely-free-vpn-in-the-cloud-1794302432) ## Contributing See our [Development Guide](docs/DEVELOPMENT.md) for information on: * Setting up your development environment * Using prek hooks for code quality * Running tests and linters * Contributing code via pull requests ## Support Algo VPN [![PayPal](https://www.paypalobjects.com/en_US/i/btn/btn_donate_SM.gif)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=CYZZD39GXUJ3E) [![Patreon](https://img.shields.io/badge/back_on-patreon-red.svg)](https://www.patreon.com/algovpn) All donations support continued development. Thanks! * We accept donations via [PayPal](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=CYZZD39GXUJ3E) and [Patreon](https://www.patreon.com/algovpn). * Use our [referral code](https://m.do.co/c/4d7f4ff9cfe4) when you sign up to Digital Ocean for a $10 credit. * We also accept and appreciate contributions of new code and bugfixes via Github Pull Requests. Algo is licensed and distributed under the AGPLv3. If you want to distribute a closed-source modification or service based on Algo, then please consider <a href="mailto:[email protected]">purchasing an exception</a> . As with the methods above, this will help support continued development.

VPN & Firewalls Tunnel & Remote Access
30.3K Github Stars
manticore
Open Source

manticore

# :warning: Project is in Maintenance Mode :warning: This project is no longer internally developed and maintained. However, we are happy to review and accept small, well-written pull requests by the community. We will only consider bug fixes and minor enhancements. Any new or currently open issues and discussions shall be answered and supported by the community. # Manticore <p align="center"> <img src="https://raw.githubusercontent.com/trailofbits/manticore/master/docs/images/manticore.png" width="256" title="Manticore"> </p> <br /> [![Build Status](https://img.shields.io/github/actions/workflow/status/trailofbits/manticore/ci.yml?branch=master)](https://github.com/trailofbits/manticore/actions?query=workflow%3ACI) [![Coverage Status](https://coveralls.io/repos/github/trailofbits/manticore/badge.svg)](https://coveralls.io/github/trailofbits/manticore) [![PyPI Version](https://badge.fury.io/py/manticore.svg)](https://badge.fury.io/py/manticore) [![Slack Status](https://slack.empirehacking.nyc/badge.svg)](https://slack.empirehacking.nyc) [![Documentation Status](https://readthedocs.org/projects/manticore/badge/?version=latest)](http://manticore.readthedocs.io/en/latest/?badge=latest) [![Example Status](https://img.shields.io/github/actions/workflow/status/trailofbits/manticore-examples/ci.yml?branch=master)](https://github.com/trailofbits/manticore-examples/actions?query=workflow%3ACI) [![LGTM Total Alerts](https://img.shields.io/lgtm/alerts/g/trailofbits/manticore.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/trailofbits/manticore/alerts/) Manticore is a symbolic execution tool for the analysis of smart contracts and binaries. ## Features - **Program Exploration**: Manticore can execute a program with symbolic inputs and explore all the possible states it can reach - **Input Generation**: Manticore can automatically produce concrete inputs that result in a given program state - **Error Discovery**: Manticore can detect crashes and other failure cases in binaries and smart contracts - **Instrumentation**: Manticore provides fine-grained control of state exploration via event callbacks and instruction hooks - **Programmatic Interface**: Manticore exposes programmatic access to its analysis engine via a Python API Manticore can analyze the following types of programs: - Ethereum smart contracts (EVM bytecode) - Linux ELF binaries (x86, x86_64, aarch64, and ARMv7) - WASM Modules ## Installation > Note: We recommend installing Manticore in a [virtual environment](https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/#installing-virtualenv) to prevent conflicts with other projects or packages Option 1: Installing from PyPI: ```bash pip install manticore ``` Option 2: Installing from PyPI, with extra dependencies needed to execute native binaries: ```bash pip install "manticore[native]" ``` Option 3: Installing a nightly development build: ```bash pip install --pre "manticore[native]" ``` Option 4: Installing from the `master` branch: ```bash git clone https://github.com/trailofbits/manticore.git cd manticore pip install -e ".[native]" ``` Option 5: Install via Docker: ```bash docker pull trailofbits/manticore ``` Once installed, the `manticore` CLI tool and Python API will be available. For a development installation, see our [wiki](https://github.com/trailofbits/manticore/wiki/Hacking-on-Manticore). ## Usage ### CLI Manticore has a command line interface which can perform a basic symbolic analysis of a binary or smart contract. Analysis results will be placed into a workspace directory beginning with `mcore_`. For information about the workspace, see the [wiki](https://github.com/trailofbits/manticore/wiki/What's-in-the-workspace%3F). #### EVM Manticore CLI automatically detects you are trying to test a contract if (for ex.) the contract has a `.sol` or a `.vy` extension. See a [demo](https://asciinema.org/a/154012). <details> <summary>Click to expand:</summary> ```bash $ manticore examples/evm/umd_example.sol [9921] m.main:INFO: Registered plugins: DetectUninitializedMemory, DetectReentrancySimple, DetectExternalCallAndLeak, ... [9921] m.e.manticore:INFO: Starting symbolic create contract [9921] m.e.manticore:INFO: Starting symbolic transaction: 0 [9921] m.e.manticore:INFO: 4 alive states, 6 terminated states [9921] m.e.manticore:INFO: Starting symbolic transaction: 1 [9921] m.e.manticore:INFO: 16 alive states, 22 terminated states [13761] m.c.manticore:INFO: Generated testcase No. 0 - STOP(3 txs) [13754] m.c.manticore:INFO: Generated testcase No. 1 - STOP(3 txs) ... [13743] m.c.manticore:INFO: Generated testcase No. 36 - THROW(3 txs) [13740] m.c.manticore:INFO: Generated testcase No. 37 - THROW(3 txs) [9921] m.c.manticore:INFO: Results in ~/manticore/mcore_gsncmlgx ``` </details> ##### Manticore-verifier An alternative CLI tool is provided that simplifies contract testing and allows writing properties methods in the same high-level language the contract uses. Checkout manticore-verifier [documentation](http://manticore.readthedocs.io/en/latest/verifier.html). See a [demo](https://asciinema.org/a/xd0XYe6EqHCibae0RP6c7sJVE) #### Native <details> <summary>Click to expand:</summary> ```bash $ manticore examples/linux/basic [9507] m.n.manticore:INFO: Loading program examples/linux/basic [9507] m.c.manticore:INFO: Generated testcase No. 0 - Program finished with exit status: 0 [9507] m.c.manticore:INFO: Generated testcase No. 1 - Program finished with exit status: 0 [9507] m.c.manticore:INFO: Results in ~/manticore/mcore_7u7hgfay [9507] m.n.manticore:INFO: Total time: 2.8029580116271973 ``` </details> ### API Manticore provides a Python programming interface which can be used to implement powerful custom analyses. #### EVM For Ethereum smart contracts, the API can be used for detailed verification of arbitrary contract properties. Users can set the starting conditions, execute symbolic transactions, and then review discovered states to ensure invariants for a contract hold. <details> <summary>Click to expand:</summary> ```python from manticore.ethereum import ManticoreEVM contract_src=""" contract Adder { function incremented(uint value) public returns (uint){ if (value == 1) revert(); return value + 1; } } """ m = ManticoreEVM() user_account = m.create_account(balance=10000000) contract_account = m.solidity_create_contract(contract_src, owner=user_account, balance=0) value = m.make_symbolic_value() contract_account.incremented(value) for state in m.ready_states: print("can value be 1? {}".format(state.can_be_true(value == 1))) print("can value be 200? {}".format(state.can_be_true(value == 200))) ``` </details> #### Native It is also possible to use the API to create custom analysis tools for Linux binaries. Tailoring the initial state helps avoid state explosion problems that commonly occur when using the CLI. <details> <summary>Click to expand:</summary> ```python # example Manticore script from manticore.native import Manticore m = Manticore.linux('./example') @m.hook(0x400ca0) def hook(state): cpu = state.cpu print('eax', cpu.EAX) print(cpu.read_int(cpu.ESP)) m.kill() # tell Manticore to stop m.run() ``` </details> #### WASM Manticore can also evaluate WebAssembly functions over symbolic inputs for property validation or general analysis. <details> <summary>Click to expand:</summary> ```python from manticore.wasm import ManticoreWASM m = ManticoreWASM("collatz.wasm") def arg_gen(state): # Generate a symbolic argument to pass to the collatz function. # Possible values: 4, 6, 8 arg = state.new_symbolic_value(32, "collatz_arg") state.constrain(arg > 3) state.constrain(arg < 9) state.constrain(arg % 2 == 0) return [arg] # Run the collatz function with the given argument generator. m.collatz(arg_gen) # Manually collect return values # Prints 2, 3, 8 for idx, val_list in enumerate(m.collect_returns()): print("State", idx, "::", val_list[0]) ``` </details> ## Requirements * Manticore requires Python 3.7 or greater * Manticore officially supports the latest LTS version of Ubuntu provided by Github Actions * Manticore has experimental support for EVM and WASM (but not native Linux binaries) on MacOS * We recommend running with increased stack size. This can be done by running `ulimit -s 100000` or by passing `--ulimit stack=100000000:100000000` to `docker run` ### Compiling Smart Contracts * Ethereum smart contract analysis requires the [`solc`](https://github.com/ethereum/solidity) program in your `$PATH`. * Manticore uses [crytic-compile](https://github.com/crytic/crytic-compile) to build smart contracts. If you're having compilation issues, consider running `crytic-compile` on your code directly to make it easier to identify any issues. * We're still in the process of implementing full support for the EVM Istanbul instruction semantics, so certain opcodes may not be supported. In a pinch, you can try compiling with Solidity 0.4.x to avoid generating those instructions. ## Using a different solver (Yices, Z3, CVC4) Manticore relies on an external solver supporting smtlib2. Currently Z3, Yices and CVC4 are supported and can be selected via command-line or configuration settings. If Yices is available, Manticore will use it by default. If not, it will fall back to Z3 or CVC4. If you want to manually choose which solver to use, you can do so like this: ```manticore --smt.solver Z3``` ### Installing CVC4 For more details go to https://cvc4.github.io/. Otherwise, just get the binary and use it. sudo wget -O /usr/bin/cvc4 https://github.com/CVC4/CVC4/releases/download/1.7/cvc4-1.7-x86_64-linux-opt sudo chmod +x /usr/bin/cvc4 ### Installing Yices Yices is incredibly fast. More details here https://yices.csl.sri.com/ sudo add-apt-repository ppa:sri-csl/formal-methods sudo apt-get update sudo apt-get install yices2 ## Getting Help Feel free to stop by our #manticore slack channel in [Empire Hacking](https://slack.empirehacking.nyc/) for help using or extending Manticore. Documentation is available in several places: * The [wiki](https://github.com/trailofbits/manticore/wiki) contains information about getting started with Manticore and contributing * The [API reference](http://manticore.readthedocs.io/en/latest/) has more thorough and in-depth documentation on our API * The [examples](examples) directory has some small examples that showcase API features * The [manticore-examples](https://github.com/trailofbits/manticore-examples) repository has some more involved examples, including some real CTF problems If you'd like to file a bug report or feature request, please use our [issues](https://github.com/trailofbits/manticore/issues/choose) page. For questions and clarifications, please visit the [discussion](https://github.com/trailofbits/manticore/discussions) page. ## License Manticore is licensed and distributed under the AGPLv3 license. [Contact us](mailto:[email protected]) if you're looking for an exception to the terms. ## Publications - [Manticore: A User-Friendly Symbolic Execution Framework for Binaries and Smart Contracts](https://arxiv.org/abs/1907.03890), Mark Mossberg, Felipe Manzano, Eric Hennenfent, Alex Groce, Gustavo Grieco, Josselin Feist, Trent Brunson, Artem Dinaburg - ASE 19 If you are using Manticore in academic work, consider applying to the [Crytic $10k Research Prize](https://blog.trailofbits.com/2019/11/13/announcing-the-crytic-10k-research-prize/). ## Demo Video from ASE 2019 [![Brief Manticore demo video](https://img.youtube.com/vi/o6pmBJZpKAc/1.jpg)](https://youtu.be/o6pmBJZpKAc) ## Tool Integrations - [MATE: Merged Analysis To prevent Exploits](https://github.com/GaloisInc/MATE) * [Mantiserve:](https://galoisinc.github.io/MATE/mantiserve.html) REST API interaction with Manticore to start, kill, and check Manticore instance * [Dwarfcore:](https://galoisinc.github.io/MATE/dwarfcore.html) Plugins and detectors for use within Mantiserve engine during exploration * [Under-constrained symbolic execution](https://github.com/GaloisInc/MATE/blob/main/doc/under-constrained-manticore.rst) Interface for symbolically exploring single functions with Manticore

Testing & QA Vulnerability Scanning
3.9K Github Stars