• 0 Posts
  • 480 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle
  • That enables an amplification attack.

    Technically, you’re right.

    An amplification attack is just telling the server to respond to a different/wrong ip with the response to a query than the actual asking request. This is solved generally with DNSSEC verifying the origin and requester ips match, if not, the request is dumped.

    However, if your authoritative server doesn’t have records for the request, it will simply forward it (if configured to do so) to an upstream and probably hardened server, or drop the request. Either way, it becomes not your problem.

    So unless the amplification attack is asking for records your server is actually hosting and for which your server is authoritative, this isn’t a huge concern.











  • Frigate is popular.

    I used to use ZoneMinder, it worked well, but you must be very familiar with onvif, primary/secondary channels, and key frames for it to work well.

    I only switched to frigate because of the person/animal detection. It’s ok, but it does need some polish in a few areas like event retention, and it could stand some more approachable documentation.










  • Permissive licensing can create what is effectively “software tivoization” (the restriction or dirty interpretation of distribution and modification rights of software by the inclusion of differently-licensed components).

    The Bitwarden case is a good example of how much damage can be done to a brand with merely the perception of restrictive licensing. obviously, bitwarden has clarified the mess, but not before it was being called ‘proprietary’ by the whole oss community.

    So I don’t think op is referring to direct corporate takeover, but damage caused by corporate abuse of a fork.