[riot-devel] Riot Software Update

2015-03-24 Thread Thomas C. Schmidt
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

Re: [riot-devel] Riot Software Update

2015-03-24 Thread C├ędric Adjih
already envisionned ? best regards, -- Cedric - Original Message - | From: Thomas C. Schmidt schm...@informatik.haw-hamburg.de | To: RIOT OS kernel developers devel@riot-os.org | Sent: Tuesday, March 24, 2015 10:01:01 AM | Subject: [riot-devel] Riot Software Update | | Hi, | | yesterday

Re: [riot-devel] Riot Software Update

2015-03-24 Thread Ludwig Ortmann
Hi, yes, we agreed that in order to get software updates we need a foundation for activating new firmware images first. The working assumption for the first incarnation/iteration of this is that an image has been saved to some memory of the device already. Cheers, Ludwig Oleg Hahm schrieb: Hi!

Re: [riot-devel] Riot Software Update

2015-03-24 Thread Emmanuel Baccelli
Hi Thomas, there are some initial efforts on-going in the community, such as [1] [2] [3], and upcoming GSOC projects on implementing LWM2M amd dynamic linking. However, this is not sufficient to get the whole nine yards. To have the full picture, there lacks security/crypto aspects, software

Re: [riot-devel] Riot Software Update

2015-03-24 Thread Oleg Hahm
Hi Ludwig! yes, we agreed that in order to get software updates we need a foundation for activating new firmware images first. The working assumption for the first incarnation/iteration of this is that an image has been saved to some memory of the device already. Okay, basically my question