scispace - formally typeset
B

Branden Ghena

Researcher at University of California, Berkeley

Publications -  23
Citations -  520

Branden Ghena is an academic researcher from University of California, Berkeley. The author has contributed to research in topics: Software deployment & Wireless network. The author has an hindex of 9, co-authored 22 publications receiving 383 citations. Previous affiliations of Branden Ghena include University of Michigan & University of California.

Papers
More filters

Green lights forever: analyzing the security of traffic infrastructure

TL;DR: This work investigates a networked traffic signal system currently deployed in the United States and discovers a number of security flaws that exist due to systemic failures by the designers, and leverages these flaws to create attacks which gain control of the system.
Proceedings ArticleDOI

Multiprogramming a 64kB Computer Safely and Efficiently

TL;DR: Tock isolates software faults, provides memory protection, and efficiently manages memory for dynamic application workloads written in any language while retaining the dependability requirements of long-running applications.
Proceedings ArticleDOI

Challenge: Unlicensed LPWANs Are Not Yet the Path to Ubiquitous Connectivity

TL;DR: Using bit flux, it is found that the combination of low bit rate and long range restricts the use case of LPWANs to sparse sensing applications and a lack of coexistence mechanisms causes poor performance in the presence of multiple, independently-administered networks.
Proceedings ArticleDOI

The Case for Writing a Kernel in Rust

TL;DR: This paper describes how three sample kernel mechanisms---DMA, USB, and buffer caches---can be built using these abstractions and concludes that no changes to Rust are needed and a kernel can be implemented with a very small amount of unsafe code.
Proceedings ArticleDOI

Ownership is theft: experiences building an embedded OS in rust

TL;DR: In the experience developing an operating system for embedded systems in Rust, it is found that Rust's ownership model prevents otherwise safe resource sharing common in the embedded domain, conflicts with the reality of hardware resources, and hinders using closures for programming asynchronously.