alby-hub/service
Roland 3b3c37dd0c
fix: remove legacy acceptance of empty unlock password check (#2534)
* fix: remove legacy acceptance of empty unlock password check

CheckUnlockPassword previously treated a missing or empty
UnlockPasswordCheck value as a match — a legacy compatibility path from
before the canary was always written. It now requires the stored value
to be present and to equal the expected string.

StartApp checks for the canary up front and, if it is missing, stops
with a message asking the user to restore from a backup rather than
continuing. A new IsUnlockPasswordCheckSet helper reports whether the
value is present.

keys.Init now returns the error from reading NostrSecretKey instead of
ignoring it, so a read failure aborts instead of generating and saving a
new key.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: add operation context to unlock password check errors

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-08-12 14:48:06 +07:00
..
keys fix: remove legacy acceptance of empty unlock password check (#2534) 2026-08-12 14:48:06 +07:00
create_app_consumer.go fix: update to alby go-nostr fork which reconnects after receiving CLOSED message (#2331) 2026-05-11 12:34:56 +07:00
delete_app_consumer.go fix: slow app deletion due to unnecessary key derivation (#2342) 2026-05-14 20:34:59 +07:00
models.go feat: support multiple relays (#1802) 2025-11-06 18:01:09 +07:00
payment_forwarded_consumer.go feat: track forwards to display on a home page widget (#1623) 2025-08-21 16:39:03 +05:30
profiler.go chore: remove datadog profiling (#1406) 2025-07-29 16:20:29 +05:30
service.go fix: fetch currencies through alby backend api (#2212) 2026-04-09 23:03:26 +05:30
start.go fix: remove legacy acceptance of empty unlock password check (#2534) 2026-08-12 14:48:06 +07:00
stop.go fix: prevent LN client access during shutdown (#2096) 2026-02-27 15:45:09 +07:00
update_app_consumer.go fix: update to alby go-nostr fork which reconnects after receiving CLOSED message (#2331) 2026-05-11 12:34:56 +07:00