arrdalan

7 ms·

1.
by arrdalan 4mo ago
Our on-device AI is able to detect people, pets, and vehicles. We have tested people detection and it works well. We haven't really tested the other two.
2.
by arrdalan 4mo ago
Will do. Thanks for the suggestion.
3.
by arrdalan 4mo ago
ESP32: We haven't tested them. I would guess that they won't be able to handle the workload (on-device AI, encryption, and video encoding if there's no hardware encoder). Ciphersuite: We use OpenMLS and we can choose any of t
4.
by arrdalan 4mo ago
There are two comments/questions here and I'll try to address them one by one. Secluso vs. Frigate: I think you correctly mentioned some of the differences. We intend Secluso to be replacement for Ring-like WiFi cameras. Therefore
5.
by arrdalan 4mo ago
The videos are stored in the mobile app and you can view them when you need. The camera captures videos when it detects an event, e.g., a person, encrypts them, and sends them to the mobile app. The app decrypts them and stores them locally
6.
by arrdalan 4mo ago
The camera_hub runs in the camera. It records videos, encrypts them, and sends them to the mobile app. The server is a relay in the cloud. It transfers encrypted videos from the camera to the mobile app.
7.
Show HN: Open-source private home security camera system (end-to-end encryption)(github.com)
137 points by arrdalan 4mo ago|28 comments
8.
by arrdalan 1y ago
One can use Frigate + Home Assistant + some secure remote access solution (e.g., VPN) to get a usage model similar to Secluso. Secluso however provides the following advantages: 1) You'll get advanced end-to-end encryption (MLS). 2) Yo
9.
by arrdalan 1y ago
There are several differences. 1) Usage model: RTSP cameras can be used for on-demand livestreaming. In contrast, the usage model of our camera is similar to a Ring camera: not only does it support livestreaming, but also it detects events
10.
Show HN: Update: Open-source private home security camera(end-to-end encryption)(github.com)
17 points by arrdalan 1y ago|4 comments
11.
by arrdalan 2y ago
Yes, we have different approaches/designs. In fact, I don't even of think of Privastead as an NVR solution. The choice of using a hub is mainly because I didn't have control of the camera firmware. As I've mentioned in o
12.
by arrdalan 2y ago
I have mentioned the unencrypted traffic between the camera and hub here: https://github.com/privastead/privastead/blob/main/HOW_TO.md (Step 4, second paragraph)
13.
by arrdalan 2y ago
Privastead/OpenMLS erases past keys from persistent storage in order not to suffer from the vulnerability you mentioned.
14.
by arrdalan 2y ago
Interesting. I think the usage model provided by Privastead is reliable enough (at least for me). I have access to my videos on my phone. If losing the phone is a concern (which should be rare), we can easily add a feature that keeps a copy
15.
by arrdalan 2y ago
The end-to-end encryption part is clear IMO: it's between the hub and the app, both of which are trusted. This is different from an untrusted server decrypting the messages.
16.
by arrdalan 2y ago
Sorry, which question did I miss?
17.
by arrdalan 2y ago
This is a reasonable setup. We discussed it in other comments as well
18.
by arrdalan 2y ago
Correct, that would be even better, but I didn't have control over the camera firmware. Someone mentioned OpenMiko, which I plan to investigate and see if it can allow me to effectively run the hub inside the camera itself and achieve
19.
by arrdalan 2y ago
I haven't designed Privastead for continuous recording/streaming. It's mainly to receive motion/event-triggered videos and occasional live streaming. The usage model is more like Ring cameras.
20.
by arrdalan 2y ago
The server only stores encrypted videos until they're fetched by the app. It can't decrypt the videos and hence is not meant as a storage space for decrypted videos.
21.
by arrdalan 2y ago
That is correct. The goal is to be able to use the cloud to host the server without having to trust it. I personally use a cheap DigitalOcean VM.
22.
by arrdalan 2y ago
Thanks for the pointers. Frigate, Home Assistant, and HomeKit were mentioned in other comments and we had some discussions there. They're certainly good setups. A key design decision for me was using a strong end-to-end encryption sche
23.
by arrdalan 2y ago
I did not, but I will. I would just point out that Privastead assumes the the push notification infrastructure is untrusted anyway.
24.
by arrdalan 2y ago
Push notifications are for notifying the apps of events (e.g., motion). The actual encrypted video (either motion-triggered video or livestreams) are transferred through the server.
25.
by arrdalan 2y ago
That's right. My assumption is that the server is untrusted and that's why I use end-to-end encryption. This allows me to use any server, possibly even one operated by a third-party service in the future.
26.
by arrdalan 2y ago
Privastead relies on event detection by the camera itself. The Amcrest camera that I've used so far only does motion detection (which is all I needed on my end). There are IP cameras, however, that do human detection. I've purchas
27.
by arrdalan 2y ago
Using Pi's to run the hub is technically feasible (and I do plan on trying it on my end). Port forwarding is not needed. The Pi only needs to be able to initiate a connection to the server. Google FCM is used for delivering notificatio
28.
by arrdalan 2y ago
The traffic is encrypted between the hub and the app. The camera is connected to the hub.
29.
by arrdalan 2y ago
Yes, indeed. Using WebRTC and MLS together should provide good performance and privacy. In fact, Discord recently did that: https://discord.com/blog/meet-dave-e2ee-for-audio-video It's something I plan to look int
30.
by arrdalan 2y ago
That's definitely better, if done right. I still prefer to avoid port forwarding on my router if possible. The fewer attack surfaces I have to worry about, the better.

More ›