Skip to main content

Overview

Travel Fortress is a split-knowledge encryption system designed for scenarios where you might be compelled to unlock your vault (border crossings, device inspections, coercive situations). It cryptographically separates sensitive credentials behind a separate PIN-derived key, making them inaccessible even with your master password.

How it works

1

Mark sensitive items

Select which credentials, notes, and passkeys should be hidden during travel. These items are flagged as travel_safe: false.
2

Set a travel PIN

Choose a separate PIN. PassAgent derives a travel key from this PIN + a random salt using Argon2id (same parameters as your vault key).
3

Enable travel mode

Hidden items’ per-item keys are re-wrapped from your vault key to the travel key. The original vault-key wrapping is deleted. Your main vault key cannot access these items.
4

Travel

If compelled to unlock your vault, only non-sensitive items are visible. Hidden items are cryptographically inaccessible.
5

Disable on arrival

Enter your travel PIN to restore items. Keys are re-wrapped back to your vault key.

Split-knowledge architecture

ComponentHeld byPurpose
PINYou (memory)Useless without the salt
SaltServerUseless without the PIN
Travel keyDerived at runtimeWraps hidden item keys
Vault keyYour master passwordCannot access hidden items
Neither the PIN alone nor the salt alone can derive the travel key. Both components are required, providing split-knowledge security.

Duress PIN

You can set a separate duress PIN that, when entered:
  1. Displays a convincing fake vault with decoy data
  2. Silently alerts your trusted contacts
  3. Logs a duress event in the audit trail
  4. Does not reveal your actual hidden items

Time-lock

Configure a time-lock (0-720 hours) that prevents disabling travel mode before the timer expires. This protects against being forced to immediately disable the fortress.

Trusted contact approval

Optionally require a trusted contact to approve disabling travel mode. This adds a second layer of human verification before restoration.

Protected data types

Travel Fortress protects items across these tables:
  • Passwords — vault credentials
  • Secure notes — encrypted notes and documents
  • Vault items — general vault entries
  • Passkey credentials — WebAuthn passkeys

Cryptographic parameters

ParameterValue
KDFArgon2id
Memory64 MiB (fallback: 32 MiB)
Iterations3 (fallback: 4)
Key length256-bit AES
CipherAES-256-GCM
IV12 bytes (96 bits)
Tag128 bits

API reference

MethodEndpointDescription
GET/api/vault/travel-modeGet status, time-lock, counts, trusted contact
POST/api/vault/travel-modeSetup PIN, enable, disable, configure, mark items
GET/api/vault/travel-mode/hidden-itemsFetch items marked as hidden
If you forget your travel PIN and have not configured a trusted contact recovery path, hidden items are permanently inaccessible. Store your PIN securely outside your vault.