TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Toward Confidential Cloud Computing

42 点作者 hacksilver大约 4 年前

5 条评论

eqvinox大约 4 年前
&gt; <i>At the lowest level of the stack, the hardware must be able to provide a TEE (trusted execution environment) that isolates the code and data of a given confidential workload from any other code running in a system—including code running at the highest privilege levels. [...] This in turn requires a hardware root of trust to hold the platform root secrets and signing keys, and a public-key infrastructure to endorse these keys. [...]</i><p>Uh... no... what &quot;the hardware must be able to provide&quot; is a platform that <i>I</i>, the cloud user, trust. It&#x27;s nice that the manufacturer installed some hardware key somewhere, but that just means the manufacturer can maybe trust this key. If the NSA or China wants my data, they&#x27;ll just supply-chain-attack and replace whatever entity contains these keys with something else. The manufacturer might be able to determine that this replacement happened &#x2F; trust is no longer established, but <i>I can&#x27;t</i>.<p>And, unfortunately, supply chain attacks like this are exactly what we&#x27;re seeing, e.g. <a href="https:&#x2F;&#x2F;arstechnica.com&#x2F;tech-policy&#x2F;2014&#x2F;05&#x2F;photos-of-an-nsa-upgrade-factory-show-cisco-router-getting-implant&#x2F;" rel="nofollow">https:&#x2F;&#x2F;arstechnica.com&#x2F;tech-policy&#x2F;2014&#x2F;05&#x2F;photos-of-an-nsa...</a><p>NB: you don&#x27;t even have to replace the TPM&#x2F;Processor&#x2F;... with an identical, tampered component. You just need something that behaves the same as far as I can see. It could be some huge-ass FPGA board programmed to emulate shit and I wouldn&#x27;t be able to tell as long as they got the emulation right. After all I can&#x27;t go physically inspect the server...
评论 #26448890 未加载
评论 #26449719 未加载
评论 #26449342 未加载
jnwatson大约 4 年前
Confidential computing is one of those “nerd snipes”. It is really interesting from a technical challenges and academic research perspective.<p>Practically, hyperjacking or compromise through the cloud provider is really low on the list of security issues.
评论 #26449726 未加载
doodlebugging大约 4 年前
Good paper so far but I wonder whether we got the final version of it.<p>In the Confidential AI section we encounter ??? as if there is an incomplete thought or more to be added here.<p>&gt;The enclave may, for example, enforce differential privacy by limiting the number of times the model is queried and adding noise to their results. ????<p>I thought this might be a one-off but I made it into the Key Management and Attestation Services section and found several more clustered.<p>&gt;The TEE may then use these credentials to access tenant data. It may, for example, present a token issued by the attestation service to obtain the current decryption key from an HSM. ????<p>This one even has an incomplete sentence at the start.<p>&gt;Thus, the service can support precise, stateful policy statements of the form, ???This task must run within an SGX enclave, on an Intel SGX v2.1 platform, deployed in the German Azure data center, in a VM allocated to the tenant, supported by certificates that are valid as of today,??? rather than just, ???This task must run within an enclave.???<p>Near the end in the Code Transparency discussion there is another case where perhaps they intended to phrase something differently.<p>&gt;The code transparency service can also be used to mitigate software supply chain?? attacks, because it provides auditable provenance and chain-of-custody for a software bill of materials (SBoM).<p>There is a lot of great information in this paper about the direction that is currently being taken to build a system where cloud data can be reliably guaranteed to be encrypted and protected from unauthorized access using hardware and software tools. I am no expert on this but I do follow emerging trends and research just for the opportunity to learn outside my own discipline.<p>I see in the biographies that most of the authors are associated with Microsoft. Perhaps the corrected version of this will come on the next Patch Tuesday? (LOL)<p>That is not intended as a knock on Microsoft. I have used Microsoft OSes, software tools, and hardware (still use a Windows Phone in fact) since the mid-1980&#x27;s when I was in college. When I saw Russinovich on the author list I knew that the quality of the work would be pretty high. I have a high level of trust in him and the tools that he has built over the years.
评论 #26447444 未加载
jiehong大约 4 年前
A few days ago, a post about Intel hardware accelerated homomorphic encryption might show a better way: if an OS is running but the server cannot know what’s running, then you no longer need to trust that hardware.<p>It’s trusted computing on untrusted hardware.<p>It’s similar to how you send encrypted TLD traffic over untrusted networks.
throwawaysea大约 4 年前
We need not just confidential computing but censorship proof computing. I don’t think the “cloud” is the model to grant either because it is centralized.
评论 #26452434 未加载
评论 #26449745 未加载