Gloridust 8fd147bccc fix(P0): unique persistent machine-id per instance + manual reset ...

All instances shared the image-baked machine-id (a67bf09f...), so Tencent
saw every WechatOnCloud account worldwide as one "device" — a textbook
device-farm signal triggering risk control and the forced-logout loop
reported across old and new versions.

- docker/woc-identity.sh: new /custom-cont-init.d/00-woc-identity hook —
  generates a unique machine-id on first start, persists it in the data
  volume (survives restart/upgrade/recreate), writes /etc/machine-id +
  /var/lib/dbus/machine-id, removes /.dockerenv. Existing instances get a
  fresh unique id on first upgraded start (volume lacks the file).
- regenInstanceMachineId + POST /api/admin/instances/:id/regen-machine-id:
  roll a brand-new device id and restart, for accounts re-flagged by risk
  control. Gated on the hook being present (old image → instructs upgrade).
- Admin 实例卡片「安全」弹窗新增「重置设备 ID 并重启」。

Verified: two fresh containers get distinct machine-ids; id persists across
restart; regen (rm persisted file + restart) yields a new persistent id.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

8fd147bccc · 2026-06-06 01:41:45 +08:00

History

..

autostart

fix autostart

2026-06-01 19:42:35 +08:00

Dockerfile

fix(P0): unique persistent machine-id per instance + manual reset

2026-06-06 01:41:45 +08:00

wechat-ctl.sh

update

2026-05-29 22:00:23 +08:00

woc-identity.sh

fix(P0): unique persistent machine-id per instance + manual reset

2026-06-06 01:41:45 +08:00

woc-ime.pl

fix: add CJK IME paste fallback

2026-06-03 00:08:47 +08:00

woc-update-autostart

fix autostart

2026-06-01 19:42:35 +08:00

woc-www-patch.sh

fix: add CJK IME paste fallback

2026-06-03 00:08:47 +08:00