disable WITH_KILL compile-time flag by default

closes #573
2026-08-19 11:06:15 +00:00 · 2026-07-28 14:21:59 +02:00
parent 69ccbe3226
commit fd32509e3b
5 changed files with 5 additions and 5 deletions
@@ -22,7 +22,7 @@ Implementing HTTP caused a whole slew of additional issues we needed to resolve,

 Very specifically we need to warn Recorder users using HTTP:
 - any client permitted to access the `/pub` endpoint can publish data to the Recorder
- any client permitted to access the `/api` endpoint can access any user's data, and even destroy it, depending on whether or not the Recorder was built with the `WITH_KILL` flag.
+- any client permitted to access the `/api` endpoint can access any user's data, and even destroy it, depending on whether or not the Recorder was built with the `WITH_KILL` flag. (Since July 2026, our packages are built with this setting set to `no`, i.e. disabled.)
 - any client permitted to access the `/ws` endpoint can access users' LAST locations

 ## payload encryption
@@ -9,7 +9,7 @@ WITH_HTTP ?= yes
 WITH_TOURS ?= yes
 WITH_LUA ?= yes
 WITH_PING ?= yes
-WITH_KILL ?= yes
+WITH_KILL ?= no
 WITH_ENCRYPT ?= yes

 STORAGEDEFAULT = /var/spool/owntracks/recorder/store
@@ -9,7 +9,7 @@ WITH_HTTP ?= yes
 WITH_TOURS ?= yes
 WITH_LUA ?= yes
 WITH_PING ?= yes
-WITH_KILL ?= yes
+WITH_KILL ?= no
 WITH_ENCRYPT ?= yes
 WITH_TZ ?= yes

@@ -10,7 +10,7 @@ WITH_HTTP ?= yes
 WITH_TOURS ?= yes
 WITH_LUA ?= yes
 WITH_PING ?= yes
-WITH_KILL ?= yes
+WITH_KILL ?= no
 WITH_ENCRYPT ?= yes
 WITH_TZ ?= yes

@@ -9,7 +9,7 @@ WITH_HTTP ?= yes
 WITH_TOURS ?= yes
 WITH_LUA ?= yes
 WITH_PING ?= yes
-WITH_KILL ?= yes
+WITH_KILL ?= no
 WITH_ENCRYPT ?= yes
 WITH_TZ ?= yes