Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/buluma/ansible-role-proxychains
Install Proxychains forcing TCP connection to follow through proxy like TOR or any other SOCKS4, SOCKS5 or HTTP(S) proxy.
https://github.com/buluma/ansible-role-proxychains
ansible automation proxychains
Last synced: 9 days ago
JSON representation
Install Proxychains forcing TCP connection to follow through proxy like TOR or any other SOCKS4, SOCKS5 or HTTP(S) proxy.
- Host: GitHub
- URL: https://github.com/buluma/ansible-role-proxychains
- Owner: buluma
- License: apache-2.0
- Created: 2022-09-04T08:58:06.000Z (about 2 years ago)
- Default Branch: master
- Last Pushed: 2024-07-19T00:24:22.000Z (4 months ago)
- Last Synced: 2024-07-19T08:36:08.454Z (4 months ago)
- Topics: ansible, automation, proxychains
- Language: Jinja
- Homepage: https://galaxy.ansible.com/buluma/proxychains
- Size: 120 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
README
# Ansible role [proxychains](https://galaxy.ansible.com/ui/standalone/roles/buluma/proxychains/documentation)
Install Proxychains forcing TCP connection to follow through proxy like TOR or any other SOCKS4, SOCKS5 or HTTP(S) proxy.
|GitHub|Version|Issues|Pull Requests|Downloads|
|------|-------|------|-------------|---------|
|[](https://github.com/buluma/ansible-role-proxychains/actions/workflows/molecule.yml)|[](https://github.com/buluma/ansible-role-proxychains/releases/)|[](https://github.com/buluma/ansible-role-proxychains/issues/)|[](https://github.com/buluma/ansible-role-proxychains/pulls/)|[](https://galaxy.ansible.com/ui/standalone/roles/buluma/proxychains/documentation)|
## [Example Playbook](#example-playbook)
This example is taken from [`molecule/default/converge.yml`](https://github.com/buluma/ansible-role-proxychains/blob/master/molecule/default/converge.yml) and is tested on each push, pull request and release.
```yaml
---
- name: Converge
hosts: all
become: true
gather_facts: true
vars:
dynamic_chain: true
chain_len: 2
tcp_read_time_out: 16000
tcp_connect_time_out: 10000
pre_tasks:
- name: Update apt cache.
apt: update_cache=yes cache_valid_time=600
when: ansible_os_family == 'Debian'
changed_when: false
tasks:
- name: "Include buluma.python_pip"
ansible.builtin.include_role:
name: "buluma.python_pip"
- name: "Include buluma.epel"
ansible.builtin.include_role:
name: "buluma.epel"
- name: "Include buluma.pip"
ansible.builtin.include_role:
name: "buluma.pip"
- name: "Include buluma.proxychains"
ansible.builtin.include_role:
name: "buluma.proxychains"
```
The machine needs to be prepared. In CI this is done using [`molecule/default/prepare.yml`](https://github.com/buluma/ansible-role-proxychains/blob/master/molecule/default/prepare.yml):
```yaml
---
- name: Prepare
hosts: all
become: true
gather_facts: false
roles:
- role: buluma.bootstrap
```
Also see a [full explanation and example](https://buluma.github.io/how-to-use-these-roles.html) on how to use these roles.
## [Role Variables](#role-variables)
The default values for the variables are set in [`defaults/main.yml`](https://github.com/buluma/ansible-role-proxychains/blob/master/defaults/main.yml):
```yaml
---
# The option below identifies how the ProxyList is treated.
# only one option should be uncommented at time,
# otherwise the last appearing option will be accepted
#
# Dynamic - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# at least one proxy must be online to play in chain
# (dead proxies are skipped)
dynamic_chain: false
# Strict - Each connection will be done via chained proxies
# all proxies chained in the order as they appear in the list
# all proxies must be online to play in chain
strict_chain: false
# Round Robin - Each connection will be done via chained proxies
# of chain_len length
# all proxies chained in the order as they appear in the list
# at least one proxy must be online to play in chain
# (dead proxies are skipped).
# the start of the current proxy chain is the proxy after the last
# proxy in the previously invoked proxy chain.
# if the end of the proxy chain is reached while looking for proxies
# start at the beginning again.
# These semantics are not guaranteed in a multithreaded environment.
round_robin_chain: false
# Random - Each connection will be done via random proxy
# (or proxy chain, see chain_len) from the list.
# this option is good to test your IDS :)
random_chain: false
# Make sense only if random_chain or round_robin_chain
# chain_len = 2
# Quiet mode (false output from library)
# quiet_mode
# Set timeouts in milliseconds
tcp_read_time_out: 15000
tcp_connect_time_out: 8000
```
## [Requirements](#requirements)
- pip packages listed in [requirements.txt](https://github.com/buluma/ansible-role-proxychains/blob/master/requirements.txt).
## [State of used roles](#state-of-used-roles)
The following roles are used to prepare a system. You can prepare your system in another way.
| Requirement | GitHub | Version |
|-------------|--------|--------|
|[buluma.bootstrap](https://galaxy.ansible.com/buluma/bootstrap)|[](https://github.com/buluma/ansible-role-bootstrap/actions/workflows/molecule.yml)|[](https://github.com/shadowwalker/ansible-role-bootstrap)|
|[buluma.python_pip](https://galaxy.ansible.com/buluma/python_pip)|[](https://github.com/buluma/ansible-role-python_pip/actions/workflows/molecule.yml)|[](https://github.com/shadowwalker/ansible-role-python_pip)|
|[buluma.epel](https://galaxy.ansible.com/buluma/epel)|[](https://github.com/buluma/ansible-role-epel/actions/workflows/molecule.yml)|[](https://github.com/shadowwalker/ansible-role-epel)|
|[buluma.pip](https://galaxy.ansible.com/buluma/pip)|[](https://github.com/buluma/ansible-role-pip/actions/workflows/molecule.yml)|[](https://github.com/shadowwalker/ansible-role-pip)|
## [Context](#context)
This role is a part of many compatible roles. Have a look at [the documentation of these roles](https://buluma.github.io/) for further information.
Here is an overview of related roles:
## [Compatibility](#compatibility)
This role has been tested on these [container images](https://hub.docker.com/u/buluma):
|container|tags|
|---------|----|
|[Ubuntu](https://hub.docker.com/r/buluma/ubuntu)|focal, bionic, jammy|
|[Debian](https://hub.docker.com/r/buluma/debian)|all|
|[EL](https://hub.docker.com/r/buluma/enterpriselinux)|8|
|[Fedora](https://hub.docker.com/r/buluma/fedora)|all|
The minimum version of Ansible required is 2.1, tests have been done to:
- The previous version.
- The current version.
- The development version.
If you find issues, please register them in [GitHub](https://github.com/buluma/ansible-role-proxychains/issues)
## [Changelog](#changelog)
[Role History](https://github.com/buluma/ansible-role-proxychains/blob/master/CHANGELOG.md)
## [License](#license)
[Apache-2.0](https://github.com/buluma/ansible-role-proxychains/blob/master/LICENSE)
## [Author Information](#author-information)
[Shadow Walker](https://buluma.github.io/)