concealer 1.2.0__tar.gz → 1.2.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {concealer-1.2.0 → concealer-1.2.2}/CHANGELOG.md +136 -0
- {concealer-1.2.0 → concealer-1.2.2}/PKG-INFO +6 -1
- {concealer-1.2.0 → concealer-1.2.2}/README.md +5 -0
- {concealer-1.2.0 → concealer-1.2.2}/concealer +254 -35
- {concealer-1.2.0 → concealer-1.2.2}/extension/README.md +10 -3
- {concealer-1.2.0 → concealer-1.2.2}/mobile/README.md +20 -2
- concealer-1.2.2/mobile/android/app/src/main/java/org/concealer/mobile/AutofillActivity.java +14 -0
- concealer-1.2.2/mobile/android/app/src/main/java/org/concealer/mobile/AutofillPlugin.java +85 -0
- concealer-1.2.2/mobile/android/app/src/main/java/org/concealer/mobile/BiometricPlugin.java +134 -0
- concealer-1.2.2/mobile/android/app/src/main/java/org/concealer/mobile/ConcealerAutofillService.java +166 -0
- {concealer-1.2.0 → concealer-1.2.2}/mobile/android/app/src/main/java/org/concealer/mobile/MainActivity.java +2 -0
- {concealer-1.2.0 → concealer-1.2.2}/webui.html +274 -50
- {concealer-1.2.0 → concealer-1.2.2}/.gitignore +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/LICENSE +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/concealer_win.py +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/mobile/android/app/src/main/java/org/concealer/mobile/DiscoveryPlugin.java +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/mobile/store/README.md +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/packaging/pypi/pkg_init.py +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/packaging/winget/README.md +0 -0
- {concealer-1.2.0 → concealer-1.2.2}/pyproject.toml +0 -0
|
@@ -7,6 +7,142 @@ its first public release at **`1.0.0`** (alongside the mobile app) and follows
|
|
|
7
7
|
[semver](https://semver.org/) from there; the desktop tool and mobile app share
|
|
8
8
|
the same version line. Dates are UTC.
|
|
9
9
|
|
|
10
|
+
## [1.2.2] — 2026-11-18
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- Mobile: a Lock button sits next to the auto-lock countdown on the secrets list.
|
|
15
|
+
- Mobile: a dice button on password and other secret fields generates a strong 20-character password (it's left off TOTP seeds).
|
|
16
|
+
- **A short film for every interface** — Chrome extension, CLI, Web UI, TUI, MCP and mobile — on
|
|
17
|
+
each one's page of the website, plus a "What's new" section and a changelog page with
|
|
18
|
+
screenshots of the new features.
|
|
19
|
+
- The Chrome extension offers to **save sign-ins** you type, password-manager style: after you
|
|
20
|
+
sign in, a prompt asks to save the site (or to update the password when it changed). Extra
|
|
21
|
+
fields on the page, such as the AWS console's account ID, come along, and you can add more
|
|
22
|
+
before saving. Multi-step sign-ins (account → username → password) are merged into one record.
|
|
23
|
+
"Never for this site" stops the prompt for that site.
|
|
24
|
+
- Filling a sign-in now fills every field of the record: each saved field name is looked up on
|
|
25
|
+
the page (label, name or id) and that field gets the value, so region, account ID or any other
|
|
26
|
+
extra field you saved comes back. The password only ever goes into the password box.
|
|
27
|
+
- **Unlock with a passkey: Touch ID, Windows Hello, a security key, or an Apple Watch where
|
|
28
|
+
macOS allows it.** Add one in Settings → Security & lock (master password once), then use
|
|
29
|
+
"Unlock with passkey / Touch ID" on the unlock screen or 👆 in the extension. The passkey is one
|
|
30
|
+
more key slot, like an agent token: after the fingerprint the authenticator produces a secret
|
|
31
|
+
(WebAuthn PRF) that unwraps the vault key; the secret is never stored and the master password
|
|
32
|
+
keeps working. Passkeys belong to `http://localhost`, so the page switches there when opened on
|
|
33
|
+
127.0.0.1. Needs a browser with PRF support (current Chrome, Edge, Safari).
|
|
34
|
+
- Mobile app: **unlock with Face ID, Touch ID or fingerprint.** Turn it on in Settings →
|
|
35
|
+
Security & lock; the app then asks for your face or finger at launch and when you come back to
|
|
36
|
+
it. The master password is kept in the phone's secure hardware (iOS Keychain / Android Keystore)
|
|
37
|
+
and released only after a match; enrolling a new face or finger turns it off. The cursor goes
|
|
38
|
+
straight to the master password box, Enter unlocks, and Settings is grouped into Security & lock,
|
|
39
|
+
Sync, Appearance and About like the web UI.
|
|
40
|
+
- Android app: **concealer as the system password autofill service.** Turn it on in Settings →
|
|
41
|
+
Password autofill. Sign-in fields in other apps and browsers then offer "Fill with concealer": you
|
|
42
|
+
unlock (fingerprint works), pick the sign-in (the site's or app's own come first) and it's filled.
|
|
43
|
+
After you sign in somewhere new, Android offers to save it to concealer, or to update the password
|
|
44
|
+
of the saved one.
|
|
45
|
+
- The extension can join a vault that is already unlocked in the browser (used after a passkey
|
|
46
|
+
unlock), so it doesn't ask for the master password a second time.
|
|
47
|
+
- **Saving a sign-in never asks for the master password.** While the vault is locked, the sign-in
|
|
48
|
+
is encrypted to the vault's public key (no unlock needed, nothing in plaintext on disk) and
|
|
49
|
+
waits in `keys/pending/`; the next unlock adds every waiting sign-in and says how many. If the
|
|
50
|
+
vault is open in the web UI, it is saved straight away. Only the extension can do this (the
|
|
51
|
+
request must come from a trusted extension ID, which a web page can't fake), and it returns no
|
|
52
|
+
vault data.
|
|
53
|
+
- **Save a sign-in by hand**: right-click any page → "Save sign-in to concealer", or 💾 in the
|
|
54
|
+
extension. It takes what is typed on the page right now, and every field stays editable.
|
|
55
|
+
- AWS's new sign-in host (`*.signin.aws`) matches records saved for the older
|
|
56
|
+
`signin.aws.amazon.com` host, and the other way round.
|
|
57
|
+
- `./dev.sh` (or `npm run dev`) runs this checkout as a separate development instance: port 18787,
|
|
58
|
+
its own vault in `~/.concealer-dev` with sample data, master password `demo`. The extension's ⚙
|
|
59
|
+
menu has an **App port** setting to point it at that instance.
|
|
60
|
+
- A **Created** column in the secrets list, shown by default next to Updated and sortable.
|
|
61
|
+
The app's sort menu gains "Created" too.
|
|
62
|
+
|
|
63
|
+
### Changed
|
|
64
|
+
|
|
65
|
+
- Mobile: no pinch or double-tap zoom anymore; the app behaves like an app, not a web page.
|
|
66
|
+
- Passkey / Touch ID / Face ID unlock buttons use theme-colored fingerprint and face icons instead of
|
|
67
|
+
the 👆 emoji (web UI, Chrome extension, mobile).
|
|
68
|
+
- **Faster opening on a big vault.** The web UI and the extension popup now open almost
|
|
69
|
+
instantly on a vault with hundreds of secrets (the requests fired on open went from ~1 s to
|
|
70
|
+
~20 ms on 480 records). While the vault is unlocked in the web app, the decrypted vault stays
|
|
71
|
+
in its memory until the file changes, so each open no longer decrypts it again; locking or the
|
|
72
|
+
idle lock drops it. The last-access column no longer re-reads the whole audit log on every list.
|
|
73
|
+
- The extension popup opens on your **20 most used secrets** (recent and frequent use ranked
|
|
74
|
+
together) instead of the first 50 by name; typing searches the whole vault as before.
|
|
75
|
+
|
|
76
|
+
- **Settings** is reorganised into sections with a side menu: Security & lock, Appearance, AI
|
|
77
|
+
agents (MCP), Browser extension, Integrations, Sync, Portability, Backup and About. Auto-lock is
|
|
78
|
+
now a list of durations (or a custom number of seconds). The MCP access limits moved here from
|
|
79
|
+
the Policy tab. Two options that were CLI-only can now be set here too: the audit log anchor and
|
|
80
|
+
whether deletions from synced devices are applied. Theme and language can be changed here as
|
|
81
|
+
well as from the header.
|
|
82
|
+
- The mobile app's auto-lock list gains 15 minutes, 30 minutes and 1 hour.
|
|
83
|
+
- The extension's on-page autofill menu shows the concealer logo instead of the lock emoji.
|
|
84
|
+
|
|
85
|
+
### Fixed
|
|
86
|
+
|
|
87
|
+
- Mobile: the footer shows the installed app's real version instead of a fixed v1.0.0.
|
|
88
|
+
- iOS: "Rate concealer" now opens the App Store's review page directly. Before, it went through Safari, which couldn't open it.
|
|
89
|
+
- Mobile: the concealer logo and name stay pinned at the top, below the Dynamic Island / notch,
|
|
90
|
+
even while the keyboard is open. The app now resizes above the keyboard instead of sliding the page up.
|
|
91
|
+
- `cer run [scope] -- <cmd>` treated the `--` separator as the command to run.
|
|
92
|
+
- Sorting the secrets list by a date column (Updated, Last access) did nothing: every row
|
|
93
|
+
compared equal. Dates now sort in order.
|
|
94
|
+
- The filter dropdowns (Type, Collection, …) are no longer covered by the list's table header.
|
|
95
|
+
- The extension no longer opens its autofill menu on concealer's own unlock page.
|
|
96
|
+
- After a successful fill the extension no longer warns that the password was "copied into another
|
|
97
|
+
field" when that field is one concealer filled itself (a username equal to the password). Success
|
|
98
|
+
messages are green and errors red.
|
|
99
|
+
- Right-click → "Fill with concealer" now works anywhere on the page, not only on an input field.
|
|
100
|
+
- The extension's master password boxes (popup and the on-page unlock) get the cursor as soon as
|
|
101
|
+
they appear, and the on-page unlock no longer sits on "unlocking…" after a successful unlock.
|
|
102
|
+
- When a site has no saved sign-in, the extension's on-page menu says so and offers to save one.
|
|
103
|
+
- Sites on `localhost` or an IP address are matched by their full host (an IP used to be cut to
|
|
104
|
+
its last two numbers, e.g. "0.1").
|
|
105
|
+
- The extension's helper no longer stops a newer concealer, or one on another port, that happens
|
|
106
|
+
to be running: it only replaces an older copy of itself on the default port.
|
|
107
|
+
- Sign-in matching no longer treats every `.com.tr` site (or every `*.herokuapp.com`,
|
|
108
|
+
`*.github.io`, `*.vercel.app` … app) as the same site. Two-label suffixes and shared hosts
|
|
109
|
+
now count one more label, in the app and the extension alike.
|
|
110
|
+
- Records saved with the service URL now match the company's separate sign-in host: Office 365
|
|
111
|
+
(`login.microsoftonline.com`), ChatGPT (`auth.openai.com`), Gmail (`accounts.google.com`),
|
|
112
|
+
iCloud, Proton.
|
|
113
|
+
- Multi-step sign-ins whose password step moves to a sibling host of the same company
|
|
114
|
+
(`login.microsoftonline.com` → `login.microsoft.com`) now get the password filled too.
|
|
115
|
+
- The on-page menu was slow or missing after the app had been idle for 15 minutes: the
|
|
116
|
+
background service now brings the web instance back within ~5 s instead of up to 60 s, and
|
|
117
|
+
the menu starts the app itself (then retries) when it finds it down. The in-page unlock no
|
|
118
|
+
longer spawns the native helper when the app is already running.
|
|
119
|
+
- The in-page unlock box no longer logs a "Blocked autofocusing" error on the extensions page.
|
|
120
|
+
- An agent's `request_web_login` could drop the connection ("app isn't reachable") when one
|
|
121
|
+
browser session had locked while another was still open: the request now uses a live
|
|
122
|
+
session's key and never exits the handler on a decrypt error.
|
|
123
|
+
- The page menu no longer opens on ordinary inputs (search bars, a share dialog's "add user or
|
|
124
|
+
email" box). Without a password box on the page, a field must declare itself a credential
|
|
125
|
+
through its own name, id or autocomplete (user, email, login, account, tenant, alias); search
|
|
126
|
+
fields never count.
|
|
127
|
+
- An approved agent fill is claimed exactly once (it could be delivered twice when two polls
|
|
128
|
+
raced).
|
|
129
|
+
- After you approve an agent's sign-in request, the fill now starts right away instead of
|
|
130
|
+
waiting up to 30 s for the next background poll.
|
|
131
|
+
- The page menu no longer asks for the master password again while the vault is still
|
|
132
|
+
unlocked. The popup's short countdown used to lock the menu too (and the popup re-locked the
|
|
133
|
+
vault when reopened after it ran out); now only the app's own idle-lock ends the session.
|
|
134
|
+
- If the extension auto-locks between opening the menu and picking an entry, the menu reopens
|
|
135
|
+
with the unlock box instead of failing silently.
|
|
136
|
+
- The in-page unlock box was blank on most sites: its frame was declared with a per-session
|
|
137
|
+
dynamic URL, which Chrome refuses to load from the extension's regular URL.
|
|
138
|
+
|
|
139
|
+
## [1.2.1] — 2026-11-17
|
|
140
|
+
|
|
141
|
+
### Fixed
|
|
142
|
+
|
|
143
|
+
- Web UI: the secrets table header no longer paints over the open filter dropdowns
|
|
144
|
+
(Type, Collection, Tenant, …), which blocked their search box and options.
|
|
145
|
+
|
|
10
146
|
## [1.2.0] — 2026-11-16
|
|
11
147
|
|
|
12
148
|
### Added
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.5
|
|
2
2
|
Name: concealer
|
|
3
|
-
Version: 1.2.
|
|
3
|
+
Version: 1.2.2
|
|
4
4
|
Summary: Local‑only, single‑file secret manager for the AI‑coding era. CLI, TUI, Web UI, MCP server.
|
|
5
5
|
Project-URL: Homepage, https://fxerkan.github.io/concealer/
|
|
6
6
|
Project-URL: Documentation, https://fxerkan.github.io/concealer/getting-started
|
|
@@ -62,6 +62,11 @@ Description-Content-Type: text/markdown
|
|
|
62
62
|
<b><a href="https://fxerkan.github.io/concealer/">📖 Documentation</a> · <a href="https://github.com/fxerkan/concealer/issues/new">🐛 Report a bug</a> · ⭐ <a href="https://github.com/fxerkan/concealer/stargazers">Star this repo</a> if it helps you!</b>
|
|
63
63
|
</p>
|
|
64
64
|
|
|
65
|
+
<p align="center">
|
|
66
|
+
<a href="https://youtu.be/zVDCiGC-bS8"><img src="https://raw.githubusercontent.com/fxerkan/concealer/main/docs/assets/video-tour-poster.jpg" alt="Watch the 2-minute concealer tour on YouTube" width="820"></a>
|
|
67
|
+
<br><sub>▶ <a href="https://youtu.be/zVDCiGC-bS8">2-minute tour</a> · <a href="https://youtu.be/HNTiNCzyjJw">Chrome extension & AutoFill (46 s)</a> · <a href="https://youtube.com/shorts/Ljskzot1gOk">Short</a></sub>
|
|
68
|
+
</p>
|
|
69
|
+
|
|
65
70
|
`concealer` is a thin, auditable wrapper around two battle‑tested tools — it does **not** implement its own cryptography. Everything is encrypted by `sops`/`age`; concealer only adds the UX: typed secrets, scoping, tags, a professional web UI, tamper‑evident audit logs, and an MCP server so AI agents can *use* secrets without ever *seeing* them.
|
|
66
71
|
|
|
67
72
|
**Agents use a secret (token) without ever seeing it:**
|
|
@@ -20,6 +20,11 @@
|
|
|
20
20
|
<b><a href="https://fxerkan.github.io/concealer/">📖 Documentation</a> · <a href="https://github.com/fxerkan/concealer/issues/new">🐛 Report a bug</a> · ⭐ <a href="https://github.com/fxerkan/concealer/stargazers">Star this repo</a> if it helps you!</b>
|
|
21
21
|
</p>
|
|
22
22
|
|
|
23
|
+
<p align="center">
|
|
24
|
+
<a href="https://youtu.be/zVDCiGC-bS8"><img src="https://raw.githubusercontent.com/fxerkan/concealer/main/docs/assets/video-tour-poster.jpg" alt="Watch the 2-minute concealer tour on YouTube" width="820"></a>
|
|
25
|
+
<br><sub>▶ <a href="https://youtu.be/zVDCiGC-bS8">2-minute tour</a> · <a href="https://youtu.be/HNTiNCzyjJw">Chrome extension & AutoFill (46 s)</a> · <a href="https://youtube.com/shorts/Ljskzot1gOk">Short</a></sub>
|
|
26
|
+
</p>
|
|
27
|
+
|
|
23
28
|
`concealer` is a thin, auditable wrapper around two battle‑tested tools — it does **not** implement its own cryptography. Everything is encrypted by `sops`/`age`; concealer only adds the UX: typed secrets, scoping, tags, a professional web UI, tamper‑evident audit logs, and an MCP server so AI agents can *use* secrets without ever *seeing* them.
|
|
24
29
|
|
|
25
30
|
**Agents use a secret (token) without ever seeing it:**
|