achamayou | 5 years ago | on: More patents disclosing a Sony medium format camera with curved sensor
A GS645w isn’t much larger than a modern 35mm digital, and is certainly lighter.
achamayou's comments
achamayou | 5 years ago | on: Pytest-austin: performance regression testing with no instrumentation
achamayou | 5 years ago | on: Nine in ten adults think buying latest smartphone is waste of money
More like 45k now (assuming you mean post tax, pre-tax is even higher of course): https://www.gov.uk/government/statistics/percentile-points-f...
achamayou | 5 years ago | on: Hermann Hauser: ‘It’s in Nvidia’s Interests to Destroy Arm’
achamayou | 5 years ago | on: Python Generated Sequence Diagrams
Mermaid (https://mermaid-js.github.io/) is excellent, easy to embed inline in Markdown or reStructuredText and to version with the rest of the documentation.
achamayou | 6 years ago | on: V0LTpwn: Attacking x86 Processor Integrity from Software
No, the user is still in control of what they execute on the machine, whether it is run in enclave or not. If anything, because it is deliberately unable to patch itself, software running in an enclave gives more control and auditability to a user who can know exactly what code they are running.
Importantly, a user who does not fully trust the machine administrator can still maintain integrity and confidentiality over their computation.
SGX memory encryption keys are ephemeral, they are generated at boot, and they do not need to be owned by anyone to be useful, on the contrary!
achamayou | 6 years ago | on: V0LTpwn: Attacking x86 Processor Integrity from Software
I don’t think it’s helpful to confuse side-channel or micro-architectural attacks with attacks on SGX itself. Stating that hardware enclaves don’t work and do not ship is absurd, they are present in virtually every modern phone for one thing.
Code running in an SGX enclave is measured and absolutely known at enclave launch. The fact that enclave memory is encrypted for confidentiality is unrelated.
I don’t understand why you think trusting the hyper visor is helping anything. You are still open to this attack, and to all side channel attacks as soon as you run any untrusted code.
achamayou | 6 years ago | on: Deprecating password authentication in GitHub API
The same person creating separate accounts for automation is explicitly permitted however: https://help.github.com/en/github/getting-started-with-githu...
achamayou | 6 years ago | on: V0LTpwn: Attacking x86 Processor Integrity from Software
I’m not sure why you think that SGX shows hardware enclaves “don’t work”. I also don’t see why you think enclaves “protect the malware from you”. Enclaves are created and started from host code, which can interrupt or terminate them at any time.
The scheme you suggest, which isn’t typically how TrustZone is used, gives zero integrity and confidentiality guarantees for applications. I don’t know if it’s “the right way” for some threat model, but for the most typical TEE use cases which are trying to establish strong integrity and confidentiality guarantees in the presence of an untrusted host, it’s absolutely not right nor useful.
achamayou | 6 years ago | on: V0LTpwn: Attacking x86 Processor Integrity from Software
Why not? An OS is a large beast, it’s a massive TCB. Much easier to audit a small amount of code running in an enclave with few dependencies.
achamayou | 6 years ago | on: V0LTpwn: Attacking x86 Processor Integrity from Software
Not that I know, I suspect a limiting factor is that there aren’t many cloud providers with good support for SGX at the moment.
achamayou | 6 years ago | on: V0LTpwn: Attacking x86 Processor Integrity from Software
There are many interesting uses for enclaves, most of which have nothing to do with DRM. A good example is Signal’s secure value recovery mechanism: https://signal.org/blog/secure-value-recovery/
achamayou | 6 years ago | on: Too Much Food in the Wrong Places
How do you distribute it out freely without affecting the market price?
If packaging and transport are a substantial part of the cost, which they are for milk, who’s going to pay that cost?
achamayou | 6 years ago | on: Tired Mountain Syndrome
Which is French for tired.
achamayou | 6 years ago | on: EU Commission to staff: Switch to Signal messaging app
Mistakes were made along the way: https://medium.com/@fs0c131y/tchap-the-super-not-secure-app-...
achamayou | 6 years ago | on: Past Time to Tell the Public:It Will Probably Go Pandemic, We Should Prepare Now
I suspect cases are even worse. Screens are at least smooth and easy to clean.
achamayou | 6 years ago | on: France fines Apple €25M for iOS software that slowed down older iPhones
A substantial difference as others pointed out is that Apple did this quietly, whereas limp mode is typically notified to the driver about loudly as anything can be.
achamayou | 6 years ago | on: Cryptic Rumblings Ahead of First 2020 Patch Tuesday
achamayou | 6 years ago | on: Open letter concerning Facebook's proposals to apply end-to-end encryption
Not the government, who was never using WhatsApp, the Tory Party.
achamayou | 6 years ago | on: “Rule the Waves”: a game of naval strategy (2016)
A Type 45 destroyer is almost 10000 tons though, a WWII destroyer would have been 2 to 3000. It’s probably difficult to come up with an accurate cost comparison, but I suspect the difference is even greater than for tonnage.
page 1