Alex-Devera/tpotce
1
0
Fork 0
mirror of https://github.com/telekom-security/tpotce.git synced 2025-05-03 05:38:52 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Comment ENV opt-in for SentryPeer

Browse source
This commit is contained in:
t3chn0m4g3 2022-06-08 11:09:29 +00:00
parent dcf15ca489
commit 15f7a17935
4 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docker/sentrypeer/docker-compose.yml
View file

@ -13,9 +13,9 @@ services:
# cpu_count: 1 # cpu_count: 1
# cpus: 0.25 # cpus: 0.25
environment: environment:
- SENTRYPEER_WEB_GUI=1 # - SENTRYPEER_WEB_GUI=0
- SENTRYPEER_PEER_TO_PEER=1 - SENTRYPEER_PEER_TO_PEER=false
- SENTRYPEER_BOOTSTRAP_NODE=bootstrap.sentrypeer.org # - SENTRYPEER_BOOTSTRAP_NODE=bootstrap.sentrypeer.org
- SENTRYPEER_VERBOSE=1 - SENTRYPEER_VERBOSE=1
- SENTRYPEER_DEBUG=1 - SENTRYPEER_DEBUG=1
networks: networks:

10
etc/compose/hive_sensor.yml
View file

@ -374,11 +374,11 @@ services:
sentrypeer: sentrypeer:
container_name: sentrypeer container_name: sentrypeer
restart: always restart: always
## SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1) # SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
## In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show # In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
## the bad actors in its logs. Therefore this option is opt-in based. # the bad actors in its logs. Therefore this option is opt-in based.
environment: # environment:
- SENTRYPEER_PEER_TO_PEER=0 # - SENTRYPEER_PEER_TO_PEER=0
networks: networks:
- sentrypeer_local - sentrypeer_local
ports: ports:

10
etc/compose/sensor.yml
View file

@ -374,11 +374,11 @@ services:
sentrypeer: sentrypeer:
container_name: sentrypeer container_name: sentrypeer
restart: always restart: always
## SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1) # SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
## In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show # In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
## the bad actors in its logs. Therefore this option is opt-in based. # the bad actors in its logs. Therefore this option is opt-in based.
environment: # environment:
- SENTRYPEER_PEER_TO_PEER=0 # - SENTRYPEER_PEER_TO_PEER=0
networks: networks:
- sentrypeer_local - sentrypeer_local
ports: ports:

10
etc/compose/standard.yml
View file

@ -374,11 +374,11 @@ services:
sentrypeer: sentrypeer:
container_name: sentrypeer container_name: sentrypeer
restart: always restart: always
## SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1) # SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
## In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show # In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
## the bad actors in its logs. Therefore this option is opt-in based. # the bad actors in its logs. Therefore this option is opt-in based.
environment: # environment:
- SENTRYPEER_PEER_TO_PEER=0 # - SENTRYPEER_PEER_TO_PEER=0
networks: networks:
- sentrypeer_local - sentrypeer_local
ports: ports: