From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: "David P. Reed" <dpreed@deepplum.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] openwrt or "open" security cams?
Date: Sat, 4 Apr 2020 12:36:11 +1300 [thread overview]
Message-ID: <CAKiAkGTBUmkZ2HUv4tUPL_-LA4jU=G-nNhxx-t5xgDkTqkLHiw@mail.gmail.com> (raw)
In-Reply-To: <253151.1585956770@turing-police>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
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...)
>
[-- Attachment #2: Type: text/html, Size: 1749 bytes --]
next prev parent reply other threads:[~2020-04-03 23:36 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 [this message]
2020-04-04 0:28 ` Dave Taht
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='CAKiAkGTBUmkZ2HUv4tUPL_-LA4jU=G-nNhxx-t5xgDkTqkLHiw@mail.gmail.com' \
--to=joel@aenertia.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--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