本文介绍了“安全操作系统"同时只允许C.缺少安全故事.的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

从安全性的角度来看,Azure Sphere是一个非常有趣的产品,但作为关注安全性的开发人员,我一直认为Microsoft一直在避开安全性方面的障碍,即C作为平台编程语言.

Azure Sphere is a very interesting product from the point of view of security, yet as security conscious developer I keep thinking that Microsoft keeps avoiding the elephant in the room regarding security, namely C as the platform programming language.

在MSDN文档,Linux Kernel Summit或任何其他演示文稿中,没有任何地方解释了如何支持Azure Sphere处理使用C之类的语言引起的安全性问题.

Nowhere across the MSDN documentation, Linux Kernel Summit or any other presentation it is explained how Azure Sphere is support to handle the security issues that come from using a language like C.

即由于越界访问,堆栈损坏,隐式转换,UB,双重free(),在free()之后使用而导致的内存损坏....

Namely memory corruption due to out-of-bounds accesses, stack corruption, implicit conversions, UB, double free(), use after free(), ....

自然,gcc具有一些可选的静态分析工具,以及一些在调试模式下启用边界检查的功能,但甚至没有对此进行解释.

Naturally gcc has some optional static analysis tooling, and some facilities to enable bounds checking in debug mode, but not even those get explained.

因此操作系统的安全性归结为将每个应用程序放入自己的应用程序沙箱中并希望获得最好的效果吗?!

So the OS security boils down to put each app into their own app sandbox and hope for the best?!

推荐答案

我们正在为此积极努力,并且还注意到提交了类似的功能请求这里.

We are actively working on this and also noticed that a similar feature request was submittedhere.

我们将尽快回复您的问题.感谢您的耐心等候.

We will reply back to your questions soon. Thanks for your patience.


这篇关于“安全操作系统"同时只允许C.缺少安全故事.的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-30 01:43