Privastead offers a privacy-preserving home security camera solution leveraging end-to-end encryption for secure video streaming and motion detection notifications. It targets users concerned about data privacy and surveillance, providing strong security guarantees against untrusted servers and cloud providers.

How It Works

Privastead utilizes the Messaging Layer Security (MLS) protocol, specifically the OpenMLS implementation, to establish end-to-end encrypted communication channels between a local camera hub and a mobile application. The system consists of a camera hub that interfaces with IP cameras via RTSP and MJPEG, a mobile app for remote viewing and notifications, and an untrusted server that relays encrypted messages. This architecture minimizes trust assumptions on the camera hardware and external services like Firebase Cloud Messaging (FCM), ensuring only the hub and app can decrypt video feeds.

Quick Start & Requirements

• Installation: Instructions are available via a provided link.
• Prerequisites: IP cameras with RTSP and MJPEG support (tested with Amcrest IP4M-1041W). Mobile app requires Android (tested on Android 14/15). Hub runs on Ubuntu.
• Setup: No specific time or resource estimates are provided.

Highlighted Details

• End-to-end encryption via OpenMLS implementation of the Messaging Layer Security (MLS) protocol.
• Software-only solution compatible with existing IP cameras.
• Rust implementation for hub, mobile app MLS, and untrusted server.
• Provides forward secrecy and post-compromise security for video streams.

Maintenance & Community

• Project is a side project by Ardalan Amiri Sani (UC Irvine professor) and John Kaczman.
• Contributions are welcomed via email: privastead@proton.me.
• Mailing list sign-up available for updates.

Licensing & Compatibility

• Contributions are made under Privastead's license. The specific license type is not detailed in the README.
• Compatibility for commercial use or closed-source linking is not specified.

Limitations & Caveats

The camera hub's custom motion detection relies on MJPEG rather than H.264, and it currently supports pairing with only one app instance. Performance may be impacted by high camera resolutions and frame rates. The project authors disclaim guarantees of privacy or home security.