TAI/TA-ProxMenu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
David Schroeder
2026-07-28 20:02:42 -05:00
parent 8f8002f33e
commit eca9bd2be2
4 changed files with 19 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11 -10
View File
@@ -178,14 +178,15 @@ a default company URL.
V2 creates a random installation UUID and 256-bit credential in
`/var/lib/ta-proxmenu/identity.env`. The directory is mode `0700` and the file
is mode `0600`. On each interactive launch, TA-ProxMenu makes best-effort HTTPS
calls to the configured broker to record installation/upgrade state, start and
completion status, duration, TA-ProxMenu and Git versions, PVE/OS/kernel
versions, architecture, and whether the host is clustered. No background
service is installed, and broker availability never prevents the menu from
running.
calls to the configured broker to record the hostname, installation/upgrade
state, start and completion status, duration, TA-ProxMenu and Git versions,
PVE/OS/kernel versions, architecture, and whether the host is clustered. No
background service is installed, and broker availability never prevents the
menu from running.
The registry does not send hostnames, machine IDs, MAC addresses, usernames,
customer names, VM/container inventory, deployment codes, authorization
tokens, or command output. The broker stores only a digest of the random host
credential. A successful deployment-code exchange links the already-random
installation ID to a verified registry entry.
The hostname is treated as a limited operational identifier. The registry does
not send machine IDs, MAC addresses, usernames, VM/container inventory,
deployment codes, authorization tokens, credentials, or command output. The
broker stores only a digest of the random host credential. A successful
deployment-code exchange carrying the same random installation ID marks that
registry entry as verified.