Skip to content

Data61 Meeting Notes nov19

Perry Alexander edited this page Nov 11, 2019 · 1 revision

Data61 Meeting Notes

Notes

Attestation Transform

  • Performed only on the UAV
    • Ground station is a black box and is not transformed, but must be present
    • The transform inserts a filter, cache, attestation manager component into the signal path
    • The component inserted is one box, but must be provisioned as defined below
  • Discussion of putting an attestation manager on the UAV, but not at this time
    • This is interesting having the UAV participating in the attestation
    • May be harder than it sounds at first

Attestation Transform Component

  • Filter
    • Receives commands and AM ID
    • Sends AM ID to cache
    • Receives Go/no-go signal from cache
      • Blocks commands when negative
      • Passes commands when positive ::OR::
    • Receives attestation result
    • Sends attestation result to AM
  • Cache
    • Receives attestation request from Filter
    • Checks for cached appraisal result by looking up AM ID
    • Sends AM ID to AM on cache miss
      • Receives results from AM
      • Caches attestation results from AM
    • Generates Go/No-go signal from cache
    • Asynchronously clears cache on clear signal
  • AM
    • Receives AM ID from cache
    • Generates attestation request from AM ID
      • AM ID -> public keys for appraisal ::User AM public key, Platform AM public key, seL4 AM public key::
      • AM ID -> evidence values for appraisal ::UserAM measurement, PlatformAM measurement, seL4AM measurement::
      • AM ID -> address for messages ::IP Address::
    • Send requests to ground station
    • Receives evidence
    • Appraises result
    • Generates Go/No-go signal for cache
  • Cache structure
    • Size input from attestation transform
    • Indexed on ground station UserAM public key
    • Stores last Go/No-go result ::could store evidence as well::
  • Ground Station Table structure
    • Size input from attestation transform
    • Indexed on ground station UserAM public key
    • Stores for UserAM, PlatformAM, seL4AM:
      • Public key for appraisal
      • Evidence value for appraisal
      • Address for attestation messages
  • Transform provisioning
    • Table size
    • Table contents
      • Public keys
      • Evidence values
      • IP address for UserAM
  • Questions remaining
    • How do we associate messages with ground stations?
      • Maintaining an ID of some kind ::This is another data item to store::
      • Public key ::This is likely too big::
      • IP address ::Would need to pull IP address of communication port, but might work::
      • Hash of something ::This is likely too big::
    • How do we handle communication control?
      • Asynchronous with no clock - likely
      • Synchronous on a clock signal - unlikely
      • Will CAmkES component handle this for us?

Demos

  • Looks like next demo in late February in San Diego
    • Also a technology demonstration for the Navy
    • Visit NIWC at the same time?
  • June demonstration of the whole thing
    • The whole shootin’ match

February Demo Goals

  • Key release to the various AMs
  • UAV AM -> UserAM -> PlatformAM -> seL4AM hashing and signing
  • Transform component prototype with provisioning
  • Dummy or simplistic measurements

June Demonstration Goals

  • Measurements performed
  • Transform component final form with provisioning
Clone this wiki locally