[riot-devel] Riot Software Update
ludwig.ortmann at fu-berlin.de
Tue Mar 24 16:57:28 CET 2015
I see the upgrade distribution process as mostly independent from the
software infrastructure needed to activate new images.
Also, there are probably several ways to do this right (depending on the
requirements, environment, ...), so there will be no single best
In this sense: Knock yourselves out and create working groups for your
respective favorite protocols!
Cédric Adjih schrieb:
> Indeed, that presentation was rather interesting.
> and secure updates indeed as part of security;
> Looking at the OTA, the discussions are "excluding
> network protocol", so maybe one step in that direction
> would be to have some secure protocol for sending them ?
> Is there something already envisionned ?
> best regards,
> -- Cedric
> ----- Original Message -----
> | From: "Thomas C. Schmidt" <schmidt at informatik.haw-hamburg.de>
> | To: "RIOT OS kernel developers" <devel at riot-os.org>
> | Sent: Tuesday, March 24, 2015 10:01:01 AM
> | Subject: [riot-devel] Riot Software Update
> | Hi,
> | yesterday in the IAB technical plenary, Hannes Tschofening stressed
> | the
> | need for system software maintenance. This raises the question: Have
> | we
> | spent enough thoughts on automated secure software updates for RIOT,
> | are
> | we approaching this subject?
> | It might be some thing worth while considering??
> | Cheers,
> | Thomas
> | --
> | Prof. Dr. Thomas C. Schmidt
> | ° Hamburg University of Applied Sciences Berliner
> | Tor 7 °
> | ° Dept. Informatik, Internet Technologies Group 20099 Hamburg,
> | Germany °
> | ° http://www.haw-hamburg.de/inet Fon:
> | +49-40-42875-8452 °
> | ° http://www.informatik.haw-hamburg.de/~schmidt Fax:
> | +49-40-42875-8409 °
> | devel mailing list
> | devel at riot-os.org
> | https://lists.riot-os.org/mailman/listinfo/devel
> devel mailing list
> devel at riot-os.org
More information about the devel