Project

General

Profile

Actions

Feature #595

closed

Add AES handling to sensor

Added by Hammel over 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
Software
Target version:
Start date:
28 Jul 2017
Due date:
% Done:

100%

Estimated time:
Severity:
01 - Critical

Description

This is discussed in the communications protocols section of the MVP design document on the wiki.

Actions #1

Updated by Hammel over 3 years ago

  • Status changed from New to In Progress
  • Priority changed from Normal to Immediate
  • % Done changed from 0 to 10
  • Severity changed from 03 - Medium to 01 - Critical

Bumping up because this is what will be implemented next.

Actions #2

Updated by Hammel over 3 years ago

  • Description updated (diff)
Actions #3

Updated by Hammel over 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 10 to 100

AES encryption and Base64 encoding added to the GET handler in imlightsw. Verified that it appears to do the right thing by using wget via the monitor to get the values manually. I can see the returned JSON string and it looks correct.

This is sufficient for this task. I'll need to create another task that allows Jarvis to request a state retrieval. RM #624 is for getting a device list. This new task will have to be done before that one is done. Or I might do them in parallel since they're very similar.

This other task will validate if the data returned can actually be deciphered.

Actions

Also available in: Atom PDF