From: Dave Taht <dave.taht@gmail.com>
To: "Joel Wirāmu Pauling" <joel@aenertia.net>
Cc: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] openwrt or "open" security cams?
Date: Fri, 3 Apr 2020 17:28:59 -0700 [thread overview]
Message-ID: <CAA93jw4JGs_XdEQ+8Gog++0qYN4sKAwaFC-kZJ4KGMrfL4A2bg@mail.gmail.com> (raw)
In-Reply-To: <CAKiAkGTBUmkZ2HUv4tUPL_-LA4jU=G-nNhxx-t5xgDkTqkLHiw@mail.gmail.com>
ya know, I am now mindblown by how little folk have paid attention to
security in security cams.
Stross's "scorpion stare" mod comes to mind. It's bad enough that
"Cloud support" is sold as
a "feature", merely being able to have some certainty the feed is
going to my cloud or the camera
is not a launch point for attacks within a network is kind of lacking
in what I've perused thus far.
I'd merely started with the thought that maybe I wanted ipv6 support,
and that physical security is
a problem in the first place for power and so on. I did find an
outdoor camera with potential - battery backup, wifi, and solar
support...
https://www.amazon.com/gp/product/B07GBRV8W5/ref=ox_sc_act_title_2?smid=A15NUCR7ITLOD6&psc=1
On Fri, Apr 3, 2020 at 4:36 PM Joel Wirāmu Pauling <joel@aenertia.net> wrote:
>
> Yeah - there is a full uboot replacement project (linked from that repo) - so you can basically build openwrt for it.
>
> That project I linked too is more designed at end users who just want to replace the userspace with somethat that isn't tied to xiaomi's cloud services. So is the best starting point.
>
> I didn't even bother looking at the firmware that comes with it; Serial uart is exposed so I wouldn't worry too much about the users harping on about not being able to install versions from newer factory firmwares ; serial allows you to push whatever you like.
>
> On Sat, 4 Apr 2020 at 12:32, Valdis Klētnieks <valdis.kletnieks@vt.edu> wrote:
>>
>> On Sat, 04 Apr 2020 12:08:48 +1300, Joel Wirāmu Pauling said:
>>
>> > The Xiaomi Dafang Cameras are good value and there is a completely open
>> > tool chain including uboot for them:
>>
>> Hopefully that security cam, having an open tool chain, isn't a security-disaster
>> cam like most of them are turning out to be (even the big-name ones from
>> companies that *really* should know better...)
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
prev parent reply other threads:[~2020-04-04 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:05 Dave Taht
2020-04-03 22:53 ` David P. Reed
2020-04-03 23:08 ` Joel Wirāmu Pauling
2020-04-03 23:10 ` Jonathan Morton
2020-04-03 23:15 ` Joel Wirāmu Pauling
2020-04-04 13:37 ` David P. Reed
2020-04-03 23:32 ` Valdis Klētnieks
2020-04-03 23:36 ` Joel Wirāmu Pauling
2020-04-04 0:28 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4JGs_XdEQ+8Gog++0qYN4sKAwaFC-kZJ4KGMrfL4A2bg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=joel@aenertia.net \
--cc=valdis.kletnieks@vt.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox