You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Throughout codebase (no Firebase Auth sign-in anywhere)
Problem
There is no user authentication visible in the codebase. Security relies entirely on:
Firestore security rules (which are gitignored and not auditable by users)
Knowledge of the pairingId to query relevant documents
AES-GCM encryption of content
If the Firestore rules are permissive, anyone who discovers a pairingId could read encrypted clipboard data (though they couldn't decrypt it without the key). Without auth, there's no way to enforce per-user access controls at the database level.
Recommendation
Add anonymous Firebase Auth at minimum for the default hosted backend — this gives each device a UID that Firestore rules can enforce
Allow users to bring their own Firebase project — let users provide their own google-services.json (Android) / GoogleService-Info.plist (macOS) with their own auth configuration. This gives security-conscious users full control over their backend, auth rules, and data residency
Publish Firestore rules — consider committing a reference copy of the Firestore security rules so users can audit the access controls
Severity: MODERATE
Affected Files
Problem
There is no user authentication visible in the codebase. Security relies entirely on:
pairingIdto query relevant documentsIf the Firestore rules are permissive, anyone who discovers a
pairingIdcould read encrypted clipboard data (though they couldn't decrypt it without the key). Without auth, there's no way to enforce per-user access controls at the database level.Recommendation
google-services.json(Android) /GoogleService-Info.plist(macOS) with their own auth configuration. This gives security-conscious users full control over their backend, auth rules, and data residencyNote
Responses generated with Claude