docker pull kerberos/kerberos Should I trust a whole image from docker hub with access to a security camera? No. I'd rather trust a Linux distribution to do a reproducible build.
build from source then https://github.com/kerberos-io/opensource
Kerberos: Open-Source Video Surveillance
21–30 of 96 posts
Re: Kerberos: Open-Source Video Surveillance
#22> Single camera per instance (e.g. One Docker container per camera). One camera per Docker instance? This is going to eat up hardware resources like Fat Albert.
What kind of hardware resource would this eat up? Maybe on non-linux where docker isn't as efficient? There is next to zero extra memory overhead on Linux, as the static parts are shared. Computational overhead is also linear with work, which would mostly be the case regardless.
The other cool thing, to me, is you can keep adding cameras and do not have to replace hardware, just add more.
Re: Kerberos: Open-Source Video Surveillance
#23Re: Kerberos: Open-Source Video Surveillance
#24Interesting! I was just setting up Shinobi but this looks really good too. I don't like the idea of having one docker per camera though.. But I'll give it a try.
I tried Shinobi but gave up, I even spent some time on bug reports/issues/with their community. My major issue with Shinobi was each stream is processed by ffmpeg and I had 10+ cameras all requiring 10% cpu each to handle any object/motion detection. The cameras had object/motion detection functionality built in so I figured it made more sense to just do that work on the camera and not on CPU. I also tried offloading…
The problem with offloading that to the camera is that onvif doesn't seem to have a standard way to report this. I only need motion detection on one cam so it wasn't an issue.
But good point, I wonder how Kerberos does this
Re: Kerberos: Open-Source Video Surveillance
#25Does it support Kerberos authentication?
To add on to this -- the about page acknowledges how "many are confused" about the name but effectively brushes it off because "kerberos is a good name", then "it's not actually kerberos, but kerberos.io", followed by "it's a mouthful so we'll just say kerberos" (and the HN submission just says kerberos) I feel like the name really might be an impediment to the project. Not that people can't ever re-use names, but th…
Much ado about nothing. We're adults and tech literate people and we can juggle more than one conflicting identifier in our heads considering we deal with stuff like C++ routinely.
If the project is technically good and they market it well, people will get used to the name and learn to distinguish between this and the auth protocol.
Re: Kerberos: Open-Source Video Surveillance
#26> Single camera per instance (e.g. One Docker container per camera). One camera per Docker instance? This is going to eat up hardware resources like Fat Albert.
It's not just the use of Docker, the infrastructure they're using is heavier than necessary. Quite a bit.
Re: Kerberos: Open-Source Video Surveillance
#27Does it support Kerberos authentication?
To add on to this -- the about page acknowledges how "many are confused" about the name but effectively brushes it off because "kerberos is a good name", then "it's not actually kerberos, but kerberos.io", followed by "it's a mouthful so we'll just say kerberos" (and the HN submission just says kerberos) I feel like the name really might be an impediment to the project. Not that people can't ever re-use names, but th…
just rename as Fluffy
Re: Kerberos: Open-Source Video Surveillance
#28Re: Kerberos: Open-Source Video Surveillance
#29Does it support Kerberos authentication?
To add on to this -- the about page acknowledges how "many are confused" about the name but effectively brushes it off because "kerberos is a good name", then "it's not actually kerberos, but kerberos.io", followed by "it's a mouthful so we'll just say kerberos" (and the HN submission just says kerberos) I feel like the name really might be an impediment to the project. Not that people can't ever re-use names, but th…
Changing the name would be excellent marketing.
Re: Kerberos: Open-Source Video Surveillance
#30> Single camera per instance (e.g. One Docker container per camera). One camera per Docker instance? This is going to eat up hardware resources like Fat Albert.
I’ve noticed that software more and more being designed that way. Multi-tenancy is out the window, just run multiple instances. For some applications it’s certainly easier, but as with so many other things it’s overused.