Cyclone: A Safe Dialect of C

By Trevor Jim, G. Morrisett, D. Grossman, Michael W. Hicks, J. Cheney, Yanling Wang. USENIX ATC, General Track, 2002

903 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/0a9c29dd4d1dad7a13d828913a7b2e2da4f557ac

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

The New C Standard (Excerpted material) An Economic and Cultural Commentary (2008, unknown): “Cyclone C[2] supports tagged union types, which contain information that identifies the current member.”
CHERI: A Hybrid Capability-System Architecture for Scalable Software Compartmentalization (2015, methodology): “This paper builds on that approach by describing how CHERI memory protection can also be used as the foundation for an object-capability model for use in fine-grained software compartmentalization, protecting application-layer constructs and able to express mature policies concerning control and…”
Efficient Techniques for Comprehensive Protection from Memory Error Exploits (2005, background): “Approaches such as CCured [24] and Cyclone [17] can bring down this overhead significantly , but aren't compatible with legacy C code.”
SoK: Eternal War in Memory (2013, background): “CCured [49] and Cyclone [50] use “fat-pointers” by extending the pointer representation to a structure which includes the extra information.”
Aegis: A Single-Chip Secure Processor (2007, background): “Safe languages such as Java, and safe dialects of C such as CCured [91] and Cyclone [55] can eliminate most software vulnerabilities using strong type systems and run-time checks.”
A Practical Dynamic Buffer Overflow Detector (2004, background): “Some bounds checkers modify the representation of C pointers[9] [17] [19].”
Backward-compatible constant-time exception-protected memory (2009, methodology): “In Cyclone, dangling pointers are prevented through region analysis and growable regions and garbage collection.”
Enhancing Server Availability and Security Through Failure-Oblivious Computing (2004, background): “Recently, several research groups have developed compilers that augment programs written in unsafe languages such as C with dynamic checks that intercept out of bounds array accesses and accesses via invalid pointers (we call such a compiler a safe-C compiler) [17] [58] [45] [36] [50] [37].”
DieHard: probabilistic memory safety for unsafe languages (2006, background): “Cyclone augments C with an advanced type system that allows programmers direct but safe control over memory [21].”
Data-Oriented Programming: On the Expressiveness of Non-control Data Attacks (2016, background): “For example, Cyclone and CCured introduce a safe type system to the type-unsafe C language [51], [52].”
Securing software by enforcing data-flow integrity (2006, background): “There are many proposals to prevent attacks on software, for example, [30, 24, 27, 5, 18, 34, 31, 16, 19, 13, 37].”
Code-pointer integrity (2014, methodology): “Cy-clone [25] and CCured [36] extend C with a safe type system to enforce memory safety features.”
Automatically patching errors in deployed software (2009, background): “Researchers have also built compilers that insert bounds checks to detect memory addressing errors in C programs [2, 49, 7, 20, 37, 21, 23].”
CCured: type-safe retrofitting of legacy software (2005, methodology): “The Cyclone language [Jim et al. 2002] is expressive, gives programmers a high degree of control, and has been used on similar types of programs (e.g., device drivers).”
Baggy Bounds Checking: An Efficient and Backwards-Compatible Defense against Out-of-Bounds Errors (2009, methodology): “CCured [24] and Cyclone [18] are memory safe dialects of C.”
Countering code-injection attacks with instruction-set randomization (2003, background): “Cyclone: A safe dialect of C.”