miniblog.

List Oriented Buffer Operations for Emacs. Contribute to phillord/m-buffer-el development by creating an account on GitHub.

programming, language design, and human factors

Hi! I'm glad to announce the first nightly build of IntelliJ-Rust plugin. You can grab it here. It is really far from being complete, but it is already quite usable! My single most favorite feature is "go to symbol" (Ctrl+Alt+Shift+N), which allows you to quickly navigate to any item in the local crate or in a dependency (standard library is not yet supported because it's a bit of a hassle to download its source code). We also have "go to definition" for local crate (Ctrl+B), file overview (Ct...

Classic paper describing thie history and design of Multics Emacs.

RFCs for changes to Rust. Contribute to rust-lang/rfcs development by creating an account on GitHub.

In this paper, we focus on a class of buffer overflow vulnerabilities that occur due to the "placement new'' expression in C++. "Placement new'' facilitates placement of an object/array at a specific memory location. When appropriate bounds checking is not in place, object overflows may occur. Such overflows can lead to stack as well as heap/data/bss overflows, which can be exploited by attackers in order to carry out the entire range of attacks associated with buffer overflow. Unfortunately, buffer overflows due to "placement new'' have neither been studied in the literature nor been incorporated in any tool designed to detect and/or address buffer overflows. In this paper, we show how the "placement new'' expression in C++ can be used to carry out buffer overflow attacks - on the stack as well as heap/data/bss. We show that overflowing objects and arrays can also be used to carry out virtual table pointer subterfuge, as well as function and variable pointer subterfuge. Moreover, we show how "placement new" can be used to leak sensitive information, and how denial of service attacks can be carried out via memory leakage.