- Arrakeen
- https://antonlivaja.com
-
Co-Founder & Security Engineer https://caution.co & https://distrust.co
-
Joined on
2023年01月23日
Fix prepaid credit mint via Paddle custom_data
not really an issue but a few numbers were skipped here
d42c6106e5
add http port
38a65ef561
use caution.hcl instead of Procfile
cli: add debug flag for verify and send-shard
cli: add debug flag for verify and send-shard
0002d2a37d
feat: support multiple users per org
No proper error handling for failed commit pulls from upstream
Error when trying to deploy to fully managed
b9c9640de2
Procfile: remove binary field
CLI breaks on
git push... when using caution.hcl
CLI breaks on
git push... when using caution.hcl
This was because code was not deployed to prod
User should be logged in when running
caution init --byoc
User should be logged in when running
caution init --byoc
User should be logged in when running
caution init --byoc
If someone wants to run this from CI/CD that would be a problem. The use-case is a company that wants to host many BYOC apps, for example where they need 1 enclave per user of their product.
demo-hello-world-enclave does not pass caution verify attestation
demo-hello-world-enclave does not pass caution verify attestation
Closing this as nobody has been able to reproduce this.
source reproduction can default to unencrypted http
source reproduction can default to unencrypted http
Similar to the previous finding. The trust is based on your checking that the source code you are building is what you expect to be running in the enclave. It's not about trusting HTTPS.
Support deploying many apps using BYOC