LumoSQL Encrypted Permissions Minutes

Meeting started by dan-shearer[m] at 2022-05-10 09:24:53+0000 (full logs).

Attendees

  1. dan-shearer[m] (aka Dan) - 15 lines (50%)
  2. lumosql-meetbot` - 5 lines (17%)
  3. rubdos[m] (aka Ruben) - 10 lines (33%)

Meeting Summary

  1. Prologue (dan-shearer[m], 09:24:53)
    1. MEETING_NAME: LumoSQL Encrypted Permissions (dan-shearer[m], 09:25:30)
  2. Decisions/Observations (dan-shearer[m], 09:25:55)
    1. INFO: Naming Decision: The names are: LumoSQL EP for "Encrypted Privileges". SQL-EP layer system maps SQL to formalised EP attributes and keys. ABE-SSS layer is the encryption primitive. (dan-shearer[m], 09:26:19)
    2. INFO: Decision: no need for Datalog to expose Pg-derived SQL-expressed permissions control system for LumoSQL (dan-shearer[m], 09:26:36)
    3. INFO: Observation: Lumions and their RFC have little to do with the LumoSQL EP. They meet where it comes to storage and pointers between Lumions and keys. (dan-shearer[m], 09:27:00)
    4. INFO: Lumions encode keys and potentially encrypted data in a standardised way (rubdos[m], 09:29:13)
    5. ACTION: @rubdos:rubdos.be to define LumoSQL EP interface between ABE-SSS and SQL-EP. Including Ruben to define what parts of the privileges for the EP should be stored (rubdos[m], 09:31:51)
    6. ACTION: @rubdos:rubdos.be to define list of EP-related metadata that needs to be stored such as keys etc (rubdos[m], 09:32:28)
    7. ACTION: Martina Palmucci and @rubdos:rubdos.be to implement code expressing ABE permissions system: public keys of users in, access tree(s), decisions out. This will involve SSS. This is called the ABE-SSS layer. (rubdos[m], 09:33:55)
    8. ACTION: @rubdos:rubdos.be designing the SQLite/Pg permissions system mapping on to the interface for Martina's work. This is called the SQL-EP system, for SQL encrypted privileges (rubdos[m], 09:34:19)
    9. ACTION: Dan to define where the parser changes go for the SQL interface to EP system (dan-shearer[m], 09:34:38)
    10. ACTION: Dan and Claudio to define Lumion metadata, eg what does a Lumion envelope look like (dan-shearer[m], 09:35:11)
    11. ACTION: @rubdos:rubdos.be discuss with Claudio and Dan where the LumoSQL EP code goes in the LumoSQL tree (rubdos[m], 09:35:11)
  3. Committments and Deadlines etc (dan-shearer[m], 09:36:59)
    1. INFO: Dan and Martina have agreed to speak Friday 13th May (dan-shearer[m], 09:37:23)
    2. INFO: Ruben to propose Martina Palmucci a weekly meeting date, suggesting Thursday 11AM CEST. (rubdos[m], 09:38:16)
    3. ACCEPTED: Dan will add to next LumoSQL meeting agenda: Where does LumoEP code go in the Lumo tree? (dan-shearer[m], 09:38:17)
Meeting ended at 2022-05-10 09:39:05+0000 (full logs).

Action Items

  1. @rubdos:rubdos.be to define LumoSQL EP interface between ABE-SSS and SQL-EP. Including Ruben to define what parts of the privileges for the EP should be stored (link)
  2. @rubdos:rubdos.be to define list of EP-related metadata that needs to be stored such as keys etc (link)
  3. Martina Palmucci and @rubdos:rubdos.be to implement code expressing ABE permissions system: public keys of users in, access tree(s), decisions out. This will involve SSS. This is called the ABE-SSS layer. (link)
  4. @rubdos:rubdos.be designing the SQLite/Pg permissions system mapping on to the interface for Martina's work. This is called the SQL-EP system, for SQL encrypted privileges (link)
  5. Dan to define where the parser changes go for the SQL interface to EP system (link)
  6. Dan and Claudio to define Lumion metadata, eg what does a Lumion envelope look like (link)
  7. @rubdos:rubdos.be discuss with Claudio and Dan where the LumoSQL EP code goes in the LumoSQL tree (link)

Action Items by Attendee

Generated by HCoop Meetbot v0.5.0 (05 Mar 2022)