Hi Peter!
just to avoid confusion: Didn't we agree to have the meeting tomorrow at 2pm
CET?
Thanks for asking: Yes, we did, but I think no one cared to update the
calendar. PlaceCam will be on at 2pm CET!
Cheers,
Oleg
--
I'm working on a bittorrent joke, but I only have about 30% and
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
Hello,
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
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
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
X-GOOGLE-CALID:k3ql8setv7l48ofnol0tfuu...@group.calendar.google.com
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
Hi all,
just to avoid confusion: Didn't we agree to have the meeting tomorrow at
2pm CET?
Best,
Peter
Am 24.03.2015 um 09:59 schrieb Google Calendar:
more details »
Hey guys,
I agree with Hauke on the LPM pull request from the thirdparty-repo. It is an interesting approach but the PR is based on STs standard library and therefore would need to be completely rewritten.
I think RIOT is currently missing an implementation for the RTC periph low-level
Hi,
now that we start to get in IEEE 802.15.4/6LoWPAN territory with
netdev/netapi [1-3] I wonder if it makes sense to not have 2
(16-bit/64-bit) but 3 addressing modes:
* 16-bit short address
* 32-bit (16-bit PAN ID + 16-bit short address) as originally introduced to
RIOT, but somehow ignored
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
