Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kerberos: Open-Source Video Surveillance

kerberos.io

Post reply on HN
Print view View original

91–96 of 96 posts

Re: Kerberos: Open-Source Video Surveillance

#91

Post by marcosdumay »

natch wrote: post #85
marcosdumay wrote: post #59

Earlier quoted context omitted.

It's surprising that anybody working on something related to security and computers would have to Google that name. But yeah, goes to show that Windows is not absolutely omnipresent.

I don’t follow the Windows reference since my understanding was that Kerberos (the authentication protocol and associated project and software) is not platform specific, and also works on UNIX and macOS and other systems where it’s implemented for that matter. Did you think Kerberos was only on Windows?

It's not platform specific, but everything on Windows uses it, while on other platforms it's a decision people have to make (and often decide for something else, because they don't understand kerberos and it's not trivial to setup). Thus, if you haven't heard of it, you are not on Windows.

Re: Kerberos: Open-Source Video Surveillance

#92

Post by Abishek_Muthian »

whalesalad wrote: post #47

Interesting. I’ve been building a home camera network and the state of this space (the nvr software) is pretty abysmal: zoneminder, blueiris, shinobi, etc… gonna take this for a spin. This is a terrible name for an open source project though.

> the state of this space (the nvr software) is pretty abysmal: zoneminder, blueiris, shinobi, etc

Can you be specific on what you found to be the issue? Did you try MotionEye? They're just a front-end for motion which by itself is very configurable (I recently enabled encoding using vaapi driver for some good performance gains for multiple camera detection/recording), But you need to get past the Python 2 mess of MotionEye but the community is very active and soon I expect the Python 3 branch to reach stability.

> This is a terrible name for an open source project though.

Guess, What's the name for their management system repository is[1]

[1] https://github.com/kerberos-io/opensource

Re: Kerberos: Open-Source Video Surveillance

#93

Post by natch »

marcosdumay wrote: post #91
natch wrote: post #85

Earlier quoted context omitted.

I don’t follow the Windows reference since my understanding was that Kerberos (the authentication protocol and associated project and software) is not platform specific, and also works on UNIX and macOS and other systems where it’s implemented for that matter. Did you think Kerberos was only on Windows?

It's not platform specific, but everything on Windows uses it, while on other platforms it's a decision people have to make (and often decide for something else, because they don't understand kerberos and it's not trivial to setup). Thus, if you haven't heard of it, you are not on Windows.

Where I’ve used it, it was not a decision I had to make (OS X, UNIX). It was a decision made by the IT departments at my organizations. So I’ve most certainly heard of it. No Windows anywhere in the picture. But I get what you are saying, you’re talking about people who have not heard of it.

Re: Kerberos: Open-Source Video Surveillance

#94

Post by Saris »

acidburnNSA wrote: post #55
jzawodn wrote: post #49

Earlier quoted context omitted.

I'm happy with Amcrest cameras, both for indoor and outdoor use. They have some very affordable 4k options with PoE if that matters to you.

I love their cameras but the app is so abysmal. Whenever I connect over vpn to access the cams remotely it goes effectively into a boot loop. I hate it. I keep reporting the crashes on android but no updates come.

Any app that supports RTSP will work too, you're not stuck on the official app!

Re: Kerberos: Open-Source Video Surveillance

#95

Post by ghastmaster »

kristianpaul wrote: post #48

How this could be named open source but actually be licensed under a creative commons non comercial license (BY-NC-SA 4.0) https://doc.kerberos.io/opensource/license/

"Open Source" means the source code is accessible, usually to the entire public. "Closed Source" means the source code is not accessible.

Whether the source is open or not does not limit what type of license that can be applied to it. For example, I can write a program and not release it to any other soul and give it an MIT license. Conversely I could publish code on github available to the public and apply a very strict license.

Re: Kerberos: Open-Source Video Surveillance

#96

Post by eeZah7Ux »

Keyb0ardWarr10r wrote: post #21
eeZah7Ux wrote: post #15

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

No thanks.
Post reply on HN