Code Lab
Pickle Credential Enclave Explained: Public Source and Security Boundaries
CODE LAB · PROJECT SPOTLIGHT
Pickle credential-enclave Rust / JavaScript · Apache 2.0
Follow delegated keys, time-limited grants and the limits of the public credential component.
Repository preview/artwork: pickle-com/credential-enclave · creator-supplied image.
Pickle’s credential-enclave repository exposes the component that holds and uses delegated account credentials. Its useful contribution is a concrete boundary to inspect: which keys stay on the device, which operations run inside an AWS Nitro Enclave, and which information still reaches the service operator.
This is a source walkthrough of pickle-com/credential-enclave, not a review of the complete assistant. The project says its app binary is not yet open source. Public credential-handling code therefore does not establish how every part of the shipped app behaves, whether an assistant action is appropriate, or whether a task was completed correctly.
What is actually public?
| Component | Role in the published design | Useful question |
|---|---|---|
| enclave/ | Credential operations inside the node. | What can enter or leave this boundary? |
| host/ | Starts the enclave and relays communication. | What happens if the relay withholds a message? |
| protocol/ | Shared keys, messages, records and attestation formats. | What is signed, encrypted or bound to an account? |
| verify/ | Checks node attestations and release proof. | Were expected build measurements supplied? |
| secure-program/ | Device-side JavaScript for this protocol. | Does the app binary execute that program unchanged? |
The README describes an iOS device that creates a master key and keeps it in iCloud Keychain. It derives separate account-signing, log-decryption and user keys. The node receives a sealed, time-limited delegation of the user key after the app verifies its attestation. The operator stores encrypted records and carries messages between the components.
How the architecture separates keys and requests
device of the account (the app)
master key (created on the device, kept in the iCloud Keychain)
├─ account signing key signs the commands grant and revoke
├─ log decryption key opens the log entries of the account
└─ user key encrypts and opens the records of the account
│
│ 1. the app verifies the attestation of a node: its measurements, its two public keys
│ 2. grant: the user key, sealed to the sealing key of that node, for at most 30 days
▼
operator domain (not trusted by the node) node (AWS Nitro Enclave, memory only)
backend calls the node, carries the signing key, sealing key (created at boot)
sealed messages of the app per account: the user key until the grant
storage records (ciphertext under the ends, and the end of the log chain
user key), log entries (sealed PKCE verifiers of pending authorizations
to the log key), public fields provider definitions (compiled in, measured)
host program starts the enclave, relays ◀──▶ calls: oauth/begin, oauth/complete, refresh,
the calls and the TLS bytes revoke-token, forward, release, ...
│ TLS that ends inside the node
▼
log store (Amazon S3, Object Lock) providers
1. the entry of an act 2. the act, after the
store confirmed 1The arrows matter because storing a token and using it are different events. The design aims to keep an OAuth token inside the node while it adds that token to an allowed provider request. The response to that request can still reach the operator domain. An email token can remain protected while the email content it retrieves becomes available to the assistant service.
Inside the Rust source: reject stale grants and cap their lifetime
The grant handler checks a node-issued challenge, compares it with the account’s revoke marker, rejects an expired grant, and caps the requested end time:
A missing or unusable challenge returns BadChallenge. After locking the account, the code rejects a challenge older than the node’s recorded revoke serial. That prevents an old sealed grant from simply restoring a delegation that this node has already revoked. An expiry at or before the node’s current time returns BadExpiry; a later expiry is limited with GRANT_MAX_MS, documented as 30 days.
This excerpt shows checks in one part of a larger protocol. Earlier code checks the account identity and log-store readiness; later code records the control event and handles concurrent revocation. Reading these lines is not a reproduction of those behaviors on a live enclave.
Actual source from pickle-com/credential-enclave at commit cff16a343bf5bb7953e5b65df6ab3600107e127d. Apache License 2.0. Original line numbers and syntax coloring added; source text unchanged. License ↗
Revocation still has a delivery boundary
The README explicitly limits its revocation claim: a revoke reaches nodes through the operator domain. The app counts withdrawal as complete after the nodes listed as alive return their signed replies. If a living node is omitted from that list, it can retain a key until its grant expires. The published design records uses in that node’s log chain; it does not turn an undelivered revoke into an instantaneous global erasure.
That distinction is useful when comparing agent products. “I disconnected an account,” “the interface showed success,” and “every component stopped using the credential” describe different observations. A source review should identify the mechanism and its stated limit rather than merge them into one assurance.
What the secret wrapper does—and what it cannot show
The protocol’s Secret type has explicit cleanup and debug-formatting behavior:
Dropping the wrapper invokes its value’s Wipe implementation. Debug formatting emits a fixed marker rather than formatting the contained value. Elsewhere, the wrapper exposes an explicit expose_secret method, and the project maintains a list of functions that call it.
These are reviewable code decisions. They are not proof that no copy can exist elsewhere in a process, that every logging path is correct, or that an unrelated part of the assistant never receives sensitive data. The value of the excerpt is that it makes a small claim inspectable.
Verification needs an expected identity
The documented verification workflow first builds an enclave image and its PCR0, PCR1 and PCR2 measurements, then compares those expected values with the measurements in a running node’s attestation. The README’s reference build environment is Linux x86_64 with git and Docker buildx; it also documents the Rust verification tool. These are developer verification steps, not a one-click consumer installation of Pickle.
cargo build --release --locked -p credential-enclave-verify
target/release/credential-enclave-verify \
--url https://{api host} --measurements out/measurements.jsonThis is the creator’s command pattern; the host is a placeholder and the measurements file must belong to the release being checked. We did not build the project, contact a live attestation endpoint or reproduce its release measurements.
One particularly useful detail: the README says the tool can exit successfully without expected measurements, while reporting that no measurement comparison ran. A successful exit alone therefore does not establish that a node matches the source release you intended to verify. Check what was actually compared.
The documented local platform also differs from a Nitro Enclave: the project states that no attestation verifies such a node, and distinguishes its key custody from enclave custody. Running a local process would not reproduce the hardware-isolation claim.
Read the limits alongside the mechanisms
| Boundary | What the project documents | Implication for the reader |
|---|---|---|
| Fetched content | Provider responses can reach the operator domain. | Protecting a token does not hide every retrieved document. |
| Application binary | The app binary is not yet public source. | This repository cannot establish the complete shipped app’s behavior. |
| Provider access | Allowed address definitions use path prefixes; some APIs can create lasting access. | Credential custody is separate from the breadth and consequences of permission. |
| Release changes | Delegations can transfer to a signed later release under the documented process. | Pin a source revision and check the release that actually runs. |
| Availability | The operator can stop communication or service. | Isolation does not guarantee that the assistant remains available. |
These limitations are stated by the project, not vulnerabilities demonstrated by us. They are a good starting point for more precise questions about an AI assistant. The repository’s Apache 2.0 license covers the published source; it does not imply that the commercial service, infrastructure or account access is free.
Read the pinned README ↗, egress policy ↗ and device-side secure-program documentation ↗ together. For service-level data handling, consult Pickle’s privacy policy ↗ separately; source-level custody and privacy-policy promises cover different questions.
Apache License 2.0 — source license
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Reviewed November 18, 2026. Discovery lead: Mindung’s Pickle overview ↗. Primary documentation and source inspected independently at the linked commit. This is a source walkthrough, not a live deployment test or an independent security audit.
