Re: Access control for IoT

--===============1752609653253535824==
Content-Type: multipart/alternative; boundary=089e0112cd4a16f3cd0529a739ee

--089e0112cd4a16f3cd0529a739ee
Content-Type: text/plain; charset=UTF-8

First time you try to flash and brick it because there was a power outage
or EPROMs fail due to too many write cycles people will not be very happy
...So what people do is NOT change the HW but do flash the OS / app (eg all
phones)  however the smaller devices do not have this "double"  system.

"I would argue it's irresponsible to put any device on the Internet which
is not capable of receiving software updates." , there is some validity in
this  .. but it may be construed as   "I would argue it's irresponsible to
put any device on the Internet which is not capable of receiving software
updates and hence IOT devices should not be very small / fixed embedded
systems." . Though contentious It maybe valid and for non security reasons
as well eg ipv4 phasing out vs ip6 in the future  .   ..  The other side of
the coin is such small devices may have a very small surface area to attack
, personally im undecided ( though leaning to large devices)  though
practically a lot of the HW being used is the same HW for the last 10- 20
years just now connected to a internet  server.

Ben



On Tue, Jan 19, 2016 at 12:30 PM, Tony Arcieri <[email protected]> wrote:

>
>
> There are certainly many applications of hardware for which updates are a
> bad idea, or devices which are too small or constrained to support
> automatic updates. But you have to Venn Diagram that with the types of
> devices it's reasonably responsible to connect to the Internet and assign
> an IP address to.
>
> I would argue it's irresponsible to put any device on the Internet which
> is not capable of receiving software updates.
>
> --
> Tony Arcieri
>
> _______________________________________________
> cap-talk mailing list
> [email protected]
> http://www.eros-os.org/mailman/listinfo/cap-talk
>
>

--089e0112cd4a16f3cd0529a739ee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div>First time you try to flash and brick =
it because there was a power outage or EPROMs fail due to too many write cy=
cles people will not be very happy ...So what people do is NOT change the H=
W but do flash the OS / app (eg all phones) =C2=A0however the smaller devic=
es do not have this &quot;double&quot; =C2=A0system.=C2=A0<br></div><div><b=
r></div><div>&quot;I would argue it&#39;s irresponsible to put any device o=
n the Internet which is not capable of receiving software updates.&quot; , =
there is some validity in this=C2=A0=C2=A0.. but it may be construed as =C2=
=A0 &quot;I would argue it&#39;s irresponsible to put any device on the Int=
ernet which is not capable of receiving software updates and hence IOT devi=
ces should not be very small / fixed embedded systems.&quot; . Though conte=
ntious It maybe valid and for non security reasons as well eg ipv4 phasing =
out vs ip6 in the future =C2=A0. =C2=A0 ..=C2=A0 The other side of the coin=
 is such small devices may have a very small surface area to attack , perso=
nally im undecided ( though leaning to large devices) =C2=A0though practica=
lly a lot of the HW being used is the same HW for the last 10- 20 years jus=
t now connected to a internet =C2=A0server.=C2=A0</div><div><br></div><div>=
<div>Ben<br><div><br></div><div><br><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Tue, Jan 19, 2016 at 12:30 PM, Tony Arcieri <span dir=
=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">bascule=
@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><br><div><br></div><div>Th=
ere are certainly many applications of hardware for which updates are a bad=
 idea, or devices which are too small or constrained to support automatic u=
pdates. But you have to Venn Diagram that with the types of devices it&#39;=
s reasonably responsible to connect to the Internet and assign an IP addres=
s to.</div><div><br></div><div>I would argue it&#39;s irresponsible to put =
any device on the Internet which is not capable of receiving software updat=
es.</div><span class=3D""><font color=3D"#888888"><div><br></div></font></s=
pan></div><span class=3D""><font color=3D"#888888">-- <br><div>Tony Arcieri=
<br></div>
</font></span></div></div>
<br>_______________________________________________<br>
cap-talk mailing list<br>
<a href=3D"mailto:[email protected]">[email protected]</a><=
br>
<a href=3D"http://www.eros-os.org/mailman/listinfo/cap-talk" rel=3D"norefer=
rer" target=3D"_blank">http://www.eros-os.org/mailman/listinfo/cap-talk</a>=
<br>
<br></blockquote></div><br></div></div></div></div></div>

--089e0112cd4a16f3cd0529a739ee--

--===============1752609653253535824==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk

--===============1752609653253535824==--