dimstav23/GDPRuler

Issues

• Automate the AMD-SEV runs of multiple clients and the server for each DB backend

  #46 opened 10 months ago
  0

• Logging workload crashes

  #44 opened a year ago
  1

• Move the default policy setup on the client side

  #43 opened 2 years ago
  0

• Secure the TCP channels

  #40 opened 2 years ago
  0

• Multithreaded-controller

  #38 opened a year ago
  0

• Encryption keys separation

  #37 opened 2 years ago
  0

• Define gdpr_controller config file

  #34 opened 2 years ago
  0

• The `monitor_is_needed` function can return incorrect results

  #30 opened 2 years ago
  0

• Put operation should not update the gdpr metadata of a value

  #28 opened 2 years ago
  0

• Log file stream compression & path configuration

  #27 opened 2 years ago
  0

• Implement the functionality to return the logs requested by an authority

  #26 opened 2 years ago
  0

• Implement GDPR metadata queries

  #25 opened 2 years ago
  0

• Create benchmarking framework & meaningful workloads

  #24 opened 9 months ago
  0

• Consider Origin & Share metadata conditional queries in the filtering

  #22 opened 2 years ago
  0

• KV client instance information

  #19 opened 2 years ago
  1

• Simplify the AMD SEV-SNP and remove svsm dependencies

  #17 opened 2 years ago
  0

• Encryption layer

  #14 opened 2 years ago
  0

• Logging layer

  #13 opened 2 years ago
  1

• Query filtering based on GDPR metadata

  #12 opened 2 years ago
  1

• Metadata encoding and parsing

  #11 opened 2 years ago
  2

• Provision of suitable image w/ GDPRuler dependencies

  #10 opened 2 years ago
  0

• Creation of AMD SEV-SNP VMs & provision of image w/ GDPRuler

  #8 opened 2 years ago
  0

• Multithreaded RocksDB server

  #7 opened 2 years ago
  0

• Correctness tests

  #6 opened 2 years ago
  0

• Add extra argument for native_ctl.py and GDPRuler.py to choose the appropriate DB

  #3 opened 2 years ago
  0

• RocksDB integration

  #2 opened 2 years ago
  0