Justin Patriquin

Consider a way to generate all release artifacts before uploading them

1

From @ianlivingstone: > the primary concern is that we'll end up with a mess on our hands if one build passes but the other fails. We could store the built...

Asylo 0.4.0 was recently released we should upgrade to his latest version. Could be as simple as updating the `WORKSPACE` file but I imagine something else will be needed.

We're currently not testing, linting or running the code through Continuous Integration. Once we have some linting or testing set up it should be fairly straight forward to set up...

Whenever exits (e.g. print statements) or other system calls happen it causes the SGX program to be slower than it needs to be. We can audit the code to make...

Remote Attestation allows an SGX/enclave device to prove that it is a trusted device. Currently Asylo does not have remote attestation implemented. Further details [here](https://groups.google.com/d/msg/asylo-users/Xqc5x_en74E/ZbMMdG6qBAAJ). Another route we could take...

This generates a AWS KMS key with a policy that has the PCRs required by the KMS to perform attestation against decrypt requests. Example coming soon.

 ### Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project. #### Snyk changed the following file(s): - `packages/isomorphic/package.json` #### Note for [zero-installs](https://yarnpkg.com/features/zero-installs)...