v0.2: covered codes, service marks, and an audit log
Codes are covered until revealed. A reveal is a server-side, per-session
window (60 s, two periods): POST /api/accounts/{id}/reveal opens it and
returns the code, GET /api/codes only ever returns codes for accounts in
that window, and /hide closes it early. The browser therefore never holds
a code it has not asked for by name, which is what makes the log honest.
Settings -> Log is an audit trail in the style of Daito: one line per
event with who, how long ago and from which address. It records what the
server observed - sign-ins and failed attempts (under the name tried),
reveals, accounts added / renamed / removed, delivery and credential
changes, test messages. Entries are JSON lines in audit.jsonl (owner-only,
newest 5,000 kept, compacted at twice that). The address comes from
X-Forwarded-For / X-Real-IP when parseable, else the TCP peer via
ConnectInfo; in Docker bridge networking that peer is the gateway, which
the README and template now say.
The account list shows each service's mark instead of an initial. The
pack (crates/webui/src/icons.js, generated by scripts/fetch-icons.py) is
~175 marks from Simple Icons (CC0) plus Font Awesome Free brands (CC BY
4.0) for Amazon, AWS, Microsoft, LinkedIn, Slack, Xbox, Salesforce and
Yahoo, which Simple Icons no longer carries. Matching is by issuer name,
then shorter word prefixes, then the label's mail domain; unmatched
accounts keep the initial tile. Marks that would vanish against a theme's
tile fall back to ink for that theme only.
The setup and Delivery platform pickers are plain text; the coloured dots
are gone.
Router tests cover the reveal window, session scoping, 401s, and the
forwarded address landing in the log.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
This commit is contained in:
1 parent
3c83cd9928
commit
04a86ead95
20 files changed
+1802
-118
No files matched your search
@@ -27,8 +27,11 @@
|
||||
Add accounts by uploading a QR code, scanning with the camera, pasting an
|
||||
otpauth:// link, or importing a Google Authenticator export (one export QR
|
||||
carries many accounts; you get a checklist, and duplicates are detected).
|
||||
The web UI lists every account with its rotating code, the way Google or
|
||||
Microsoft Authenticator does.
|
||||
The web UI lists every account behind its service mark, the way Google or
|
||||
Microsoft Authenticator does. Codes stay covered until you reveal one, and
|
||||
Settings -> Log records every reveal and sign-in with who and from where.
|
||||
(In bridge networking the address is Docker's gateway; use a reverse proxy
|
||||
or host/br0 networking to see real LAN addresses.)
|
||||
|
||||
The distinctive part: each account keeps ONE message in your chosen
|
||||
channel, rewritten in place every time the code rolls. Three accounts means
|
||||
|
||||
Reference in new issue
Block a user