Viewing profile — MagicalTux

So I tried feeding Claude all of MtGox's original (2011) sourcecode, git history and other relevant information, and asked for a report. Here's the result which isn't news for me b…

Battering RAM has been demonstrated to work well against Intel's "Scalable SGX" which is also known as SGX 2, and uses static encryption key to allow SGX to use more of the system'…

The SGX certificate is signed by intel and includes a certification of the hash of the code loaded in the secure enclave ("MRENCLAVE"). When the client connects to the server, the …

The comment was added before the implementation of the IPC buffer & shuffling and was left there, sorry about that. In an older version packets were sent back in sequence to their …

Similar to TLS, the attestation includes a signature and a x509 certificate with a chain of trust to Intel's CA. The whole attestation is certified by Intel to be valid and details…

Intel SGX comes with an attestation process aiming at exactly that. The attestation contains a number of details, such as the hardware configuration (cpu microcode version, BIOS, e…

This is the server-side part of things. It receives encrypted traffic from your (and other customers) device, and routes it to the Internet. This guarantees that your traffic isn't…

The way this works is by generating a private key inside the enclave and having the CPU attest its public key. This allows generating a self signed TLS certificate that includes th…

Let me clarify, it guarantees your connection is being served by the enclave itself. The TLS encryption keys are kept inside the enclave, so whatever data is exchanged with the hos…

You're welcome to use cryptocurrencies (we have a page for that), and our system only links your identity at connection time to ensure you have a valid subscription. Your traffic i…

Intel audits configuration on system launch and verifies it runs something they know safe. That involves CPU, CPU microcode, BIOS version and a few other things (SGX may not work i…

The US government might be able to pressure Intel into doing something with SGX, but there are way too many eyes on this for it to go unnoticed in my opinion, especially considerin…

Yes crypto payments, a bit difficult to find since you need to look at the bottom of the page however, but we have some plans to improve that in the coming days.

Intel will not attest insecure configurations. Our client will automatically verify the attestation it receives to make sure the certificate isn't expired and has a proper signatur…

The enclave fingerprint is generated as part of the attestation. The way this works is the enclave on launch generates a ECDSA key (which only exists inside the enclave and is neve…

As far as I know SGX has no 0-day exploits live today. sgx.fail was the largest collection of attacks and have all been resolved. What this tells me however is there are a lot of p…

Seems fairly similar, ARM's response to TEE basically. We started with SGX because it is battle tested and has a lot of people still trying to find issues, meaning any issue is lik…

Not an oversight, one of SGX's features is MRENCLAVE measurement, a hash of the code running inside the enclave that can be compared with the value obtained at build time.

SGX's original goal of being used for DVD DRMs has been deprecated because it turns out people don't keep their BIOS up to date and didn't all get Intel's latest CPUs, making the u…

At VP.NET we just released the source code of our VPN server. We're using SGX to make it possible to confirm our servers are indeed running the very code you're looking at

I didn't initially, but if you're reading that far in the comments I guess it can't be avoided. People need to know what CoinLab is trying to do.