3 ms·
Simple but not 100% foolproof, you can mutate your source code and verify the changes propagate. Note the endpoint does a DYNAMIC lookup of source code. So you
by tlarkworthy 6y ago
Simple but not 100% foolproof, you can mutate your source code and verify the changes propagate.
Note the endpoint does a DYNAMIC lookup of source code. So you can kinda reassure yourself the endpoint is executing dynamic code just by providing your own source code.
It might be more obvious the runtime does nothing much if you see the runtime https://github.com/endpointservices/serverlesscells https://github.com/endpointservices/serverlesscells
The clever bits that actually implement services are all in the notebooks.
- mulmen 6y agoThat doesn't seem to provide any meaningful indication the endpoint runs the code it claims. Can't I just create an evil endpoint that links to legit code?
- tlarkworthy 6y agoNo the endpoint is shared across all customers, the service providers do not self host, generally. The end point is the infra provider. Later I might try to code sign that and open up the cloud console for visibility, but not short term
- yjftsjthsd-h 6y ago> Simple but not 100% foolproof, you can mutate your source code and verify the changes propagate. If I was evil, I wouldn't have a totally separate source tree and binary that I shipped; I'd have my CI process inject a patch file. As a result, everything would work as expected - including getting any changes from the public source code - but the created binaries would be backdoored.
- pluies 6y agohttps://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_Ref... :)
- tlarkworthy 6y agoYeah I can fix this with work but just getting some users would be helpful first