oct 8 battle notes

[pinheadmz]

--debug doesnt work on scenarios for user namespaces but logs -f does

deploy a network before warnet dashboard works

use tank name and namespace with addnode e.g. tank-0071-black.default:38333 onetry

warnet auth may fail if ./kube doesn't exist yet:

export KUBECONFIG=/tmp/kube/kube.yaml
Ohh maybe it's just that I don't have a kubernets directory inside ~/.config/

deploy scrimmage to remote cluster for testing (need to diff out the logging stack):

diff --git a/networks/scrimmage/network.yaml b/networks/scrimmage/network.yaml
index 2dbf613..3a4f94e 100644
--- a/networks/scrimmage/network.yaml
+++ b/networks/scrimmage/network.yaml
@@ -1,8 +1,8 @@
 caddy:
-  enabled: true
+  enabled: false
 fork_observer:
   configQueryInterval: 20
-  enabled: true
+  enabled: false
 nodes:
 - config: 'maxconnections=1000
 
diff --git a/networks/scrimmage/node-defaults.yaml b/networks/scrimmage/node-defaults.yaml
index c18725e..fc8fe33 100644
--- a/networks/scrimmage/node-defaults.yaml
+++ b/networks/scrimmage/node-defaults.yaml
@@ -1,6 +1,6 @@
 chain: regtest
-collectLogs: true
-metricsExport: true
+collectLogs: false
+metricsExport: false
 resources: {}
 image:
   repository: bitcoindevproject/bitcoin

[pinheadmz]

new vulnerable nodes should have distinct version numbers

[pinheadmz]

p2p messages not working:

(.venv) --> warnet bitcoin messages armada-0 miner.default
Error fetching messages between nodes armada-0 and miner: Error from server (Forbidden): pods "miner" is forbidden: User "system:serviceaccount:wargames-brown:warnet-user" cannot get resource "pods" in API group "" in the namespace "default"

[pinheadmz]

users can not overwrite configmaps deployed by admin. so if a user wants to warnet down and then re deploy their own armada they get:

(.venv) --> warnet deploy networks/armada/
Deploying node: armada-0
Error: UPGRADE FAILED: cannot patch "armada-0" with kind ConfigMap: configmaps "armada-0" is forbidden: User "system:serviceaccount:wargames-brown:warnet-user" cannot patch resource "configmaps" in API group "" in the namespace "wargames-brown"
Error: Error: UPGRADE FAILED: cannot patch "armada-0" with kind ConfigMap: configmaps "armada-0" is forbidden: User "system:serviceaccount:wargames-brown:warnet-user" cannot patch resource "configmaps" in API group "" in the namespace "wargames-brown"

a work-around for this is just change the name of the tanks when you redeploy

[pinheadmz]

armada tanks should connect= to victim nodes by default

[pinheadmz]

we should use addnode instead of connect in bitcoin.conf

[willcl-ark]

we should use addnode instead of connect in bitcoin.conf

Addressed in #643

[willcl-ark]

new vulnerable nodes should have distinct version numbers

Getting there slowly but surely:

[m3dwards]

For the sake of Galen Erso, I think we should have all setup instructions in one readme including warnet setup. Warnet setup docs includes running a network which we don't want people to follow.

[m3dwards]

On of the attendees tried to run warnet dashboard before running a network. Docs update?

[m3dwards]

Not really something for us to fix but one of the attendees couldn't install the logging helm charts while connected to their VPN.

[m3dwards]

Wantet dashboard took time to work even on Docker Desktop / minikube. Update message to say it could take a minute?

[pinheadmz]

@willcl-ark are you able to maintain version lists in the leaderboard (points per vuln) and battle plan?

https://github.com/bitcoin-dev-project/warnet-web/blob/main/config.json#L168-L171

https://github.com/bitcoin-dev-project/battle-of-galen-erso/blob/main/scripts/fleet.py#L29-L39

[m3dwards]

Do we need to add minikube addons enable ingress to our docs?

[pinheadmz]

For the sake of Galen Erso, I think we should have all setup instructions in one readme including warnet setup. Warnet setup docs includes running a network which we don't want people to follow.

@m3dwards i was trying to avoid this, but mainly bc we were in progress of changing the helm / kubectl installation stuff. So i just wanted to send people to warnet repo for installation

[pinheadmz]

Will:

• make more new versions
• addnode instead of connect (needs review and merge) Use addnode instead of connect #643

Zip:

• add complete addr to FO fork-observer: add reachable tank addr in description for each card #646
• add "see the test" hints to readme bitcoin-dev-project/battle-of-galen-erso@bd514b4
• faucet for thousands of utxos (script)

Max:

• stub out scenarios, get them to work on signet, add to galen eros
• modify scrimmage to work on signet, whicih also means removing logging (diff in that issue) bitcoin-dev-project/battle-of-galen-erso@bd514b4
• make reconnaisaince easier to pick your victim, and add to docs bitcoin-dev-project/battle-of-galen-erso@48375de

Grant:

• fix missing /.kube users: check for ~/.kube and create if needed #647
• fix --debug fix run --debug issue for service accounts #644

SOMEONE:

• might be possible with signetchallenge=op_true bitcoin-dev-project/battle-of-galen-erso@bd514b4