Capability Hardware Enhanced RISC Instructions: Difference between revisions

Revision as of 15:26, 24 January 2025

Revision as of 15:26, 24 January 2025

Line 1:

{{Short description|Computer architecture for security}}

{{Draft topics|software|computing|technology}}

{{AfC topic|stem}}

{{AfC submission|||ts=20250124122634|u=David Chisnall|ns=118}}

{{AFC submission|d|reason|I'm not sure that this very detailed, highly technical article has a place in wikipedia. If it does, it needs a much better layman's introduction so that any 15 year old kid can understand it.|u=BenLaurie|ns=118|decliner=Stuartyeates|declinets=20250121085633|ts=20250120180647}} <!-- Do not remove this line! -->

{{AFC submission|d|context|u=BenLaurie|ns=118|decliner=Ktkvtsh|declinets=20250111155748|small=yes|ts=20250111145736}} <!-- Do not remove this line! -->

{{AFC submission|d|nn|u=BenLaurie|ns=118|decliner=Beachweak|declinets=20250109180146|small=yes|ts=20250109163712}} <!-- Do not remove this line! -->

{{AFC comment|1=Noting that this looks notable, I've done a swipe to remove a ton of the more indepth technical content. I think this draft's author(s) are looking at it from the POV of writing a technical report or research paper, leading to somewhat unencyclopedic language. You do not need to explain every nook and cranny of your design here. High-level overviews and a lack of repetition are the meta (except for the first paragraph which should summarize the rest of the article). Also, please make sure that every paragraph/idea/statement is backed up by a source that is not the original research group for University of Cambridge (see [[WP:THIRDPARTYSOURCES]]). I think that is the major issue that is currently blocking this article. [[User:Sohom Datta|<b class="skin-invert" style="color:#795cb2; display: inline-block; transform: rotate(1deg)">Sohom</b>]] ([[User talk:Sohom Datta|<span class="skin-invert" style="color: #36c;">talk</span>]]) 16:18, 21 January 2025 (UTC)}}

{{AFC comment|1=A general reader will have no clue what this article is about in its current state. It needs to explain in lamens terms in the beginning the topic. [[User:Ktkvtsh|Ktkvtsh]] ([[User talk:Ktkvtsh|talk]]) 15:57, 11 January 2025 (UTC)}}

{{AFC comment|1=GitHub is generally unacceptable as a source as it is made up of [[WP:UGC|user-generated content]]. Aside from that, more sourcing would be ideal as the current sourcing fails to establish ''how'' this software is notable. [[User:beachweak|<span style="color: #E50160; font-family: Courier; font-weight: bold;">Beachweak</span>]] [[User_talk:beachweak|<span style="color: #E50160; font-family: Courier;">(talk)</span>]] 18:01, 9 January 2025 (UTC)}}

----

'''CHERI''' (Capability Hardware Enhanced RISC Instructions) is a computer processor technology designed to improve security. CHERI aims to address the root cause of the problems that are caused by a lack of [[memory safety]] in common implementations of languages such as [[C (programming language)|C]]/[[C++]], which are responsible for around 70% of security vulnerabilities in modern systems.<ref>{{cite web |url=https://www.zdnet.com/article/chrome-70-of-all-security-bugs-are-memory-safety-issues/ |publisher=ZDNet |title=Chrome: 70% of all security bugs are memory safety issues | date=22 May 2020 | access-date=24 January 2025}}</ref><ref>{{cite web |url=https://www.zdnet.com/article/microsoft-70-percent-of-all-security-bugs-are-memory-safety-issues/ |title= Microsoft: 70 percent of all security bugs are memory safety issues |publisher=ZDNet | date=11 February 2019 | access-date=24 January 2025}}</ref>

Line 78 ⟶ 62:

= References =

<!-- Inline citations added to your article will automatically display here. See en.wikipedia.org/wiki/WP:REFB for instructions on how to add citations. -->

{{reflist}}

[[Category:Computer architecture]]