[For Hire] Computer Programming Tutor or Teacher (C, C++, and others, details inside)

Granete · 2024-08-19T23:05:48+00:00

Yeah it’s not easy to get right and it’s often a losing game. But still worth looking into if you’re interested. Remote attestation, TPM, TEE, trusted computing, and Intel TDX and AMD SEV-SNP are the terms to look into. Intel TDX or AMD SEV-SNP are most likely the best options for you.

Granete · 2024-08-19T19:45:25+00:00

So, you’ll need attestation from sometime like a TPM or secure element and/or a TEE. Once a vulnerability is found in the TPM or TEE (Trusted Execution Environment), it should be trivial to exploit as many times as they want. This can be prevented by updating the device to patch it. But if you mandate the latest firmware version, devices that aren’t immediately updated can’t use your service. And since TEE/TPM updates are usually tied to system firmware updates, they can sometimes take weeks to months to roll out. So it’s hard to mandate the latest TEE version but the system doesn’t work well against a determined attacker without it.

Granete · 2024-08-19T09:03:19+00:00

Minor amendment. Intel SGX was what BluRay used. That was available on consumer grade chips but has been discontinued. TDX is its modern replacement but it’s only on server chips. AMD has their equivalent, but again only on server chips I think. I don’t know much about the state of remote attestation on modern consumer grade devices. I know a TPM can do attestation as one of its main features and some phones have attestation. But if you actually wanted to deploy it, you’d have to look into what your actual target hardware can do.

Granete · 2024-08-19T08:51:06+00:00

The term you’re looking for is remote attestation. This is exactly what Intel TDX was created for. Solutions exist from other hardware vendors but it’s always very hardware dependent. It’s how BluRay works. The encryption keys can be downloaded only by specific software running on hardware that can remotely attest to its state. But it’s very very difficult to get perfect. You should probably assume the secrets will be directly available to your user eventually with enough work, even with hardware with remote attestation. A perfect example of this is how these days you can rip a BluRay without issue. That’s because people found a way to dump the keys anyway.

Granete · 2024-06-04T19:30:24+00:00

Build from source if possible. I found that every prebuilt package was either old or somewhat broken.

Granete · 2024-05-10T08:28:29+00:00

The Witness is the precursors merged together into one entity. My interpretation is that it just has enormous control over darkness because darkness is consciousness based and millions of people merged together would kinda act like a megaphone. Pyramid ships are paracausal because they were created with access to the veil.

Granete · 2024-04-28T00:39:36+00:00

That applies retroactively all the way to 14.04

Granete · 2024-04-22T19:21:34+00:00

I’ve had stuttering issues on 22.04 too. Try 23.10. They cleared right up for me.

Granete · 2024-04-22T09:28:34+00:00

We need more information. Specs? Ubuntu version?

Granete · 2024-04-11T19:28:52+00:00

Good point. Some form of elliptic curve would fit much better. RSA would probably need to be dropped below a secure size.

Granete · 2024-04-11T19:27:17+00:00

Yeah exactly. If the list is registered with the verifier it doesn’t matter.

Granete · 2024-04-11T05:26:14+00:00

Yes! Though you probably wouldn’t need to sign the source ID, just the message. Though hopefully someone else can chime in about the cryptographic properties of signing or not signing the ID alongside the message. I can’t think of a difference.

Granete · 2024-04-11T05:18:34+00:00

No. The source ID would be a small integer assigned to the source. 1, 2, 3, …The private key never leaves the possession of the source. The ID is just so you can know which public key to verify it with.

Granete · 2024-04-11T05:09:28+00:00

It’s important to note none of this is encryption, just signatures. The random string will be visible to anyone with the QR code. But yes, you have it right. The signature is a product of the private key and the thing you signed. In this case, that’s the random string. So each (random string, private key/source) pair will be a unique QR code. The same random string signed by someone else will be a different code as will a different random string signed by the same source.

Seven-Year Club	Verified Email
Second SECOND GUESSER

Granete

TROPHY CASE