Saturday, April 8, 2023

Ghosts and podcasts

When the topic of banned function like memcpy come up I have to smile since sometimes 'compatibility' (aka 'the software you choose to run) argues that this is still inherent service for software. This includes 'copymem', the UEFI variant of memcpy, as a fundamental system service in UEFI and encouraged in

So if existing software still uses these services, what to do? One option is to provide isolation to contain the damage, viz,

with EBC or ring's

or virtualization

Moving forward, though, leveraging modern languages and types to enforce safety still feels like the right trend. Speaking of Rust in firmware, the GSOC produced first-class UEFI support in Rust in the form of the UEFI crate for applications. As noted in the above prezo, the retrofit is touch for a large codebase, but a smaller unit of execution like a UEFI application, namely OS loaders, makes sense, especially in light of incidents like

And it looks like beyond all-Rust efforts like, coreboot is now pursuing adding Rust support The mention of payloads first makes sense since this is a stand-alone entity and doesn't entail the challenges of mixing non-borrow-checker aware C code with Rust. 

This Rust-as-a-payload aligns with POL thinking, too

I cannot recall if I mentioned in the past how even chatting w/ the Google Chrome folks from Kirkland WA and VMWare Research guy from their Bellevue office during UW lunch event how they eschew the mixing and instead are targeting Rust for more stand-alone execution regimes like plug-ins for the browser and a service for the virtualization environment, respectively. 

As noted in the Stanford lecture, types can help but there has been a complaint that subsets of type-safe languages like Ada Spark are the true gold standard. That's where work on 'Ghost types' is so interesting with the Rust community. I first heard about this from Parno and followed-up on some of this work in and discussions with the community in Ghost types will allow for no-harm source augmentation to have more verification-ready language conditions, as opposed to going to some intermediate or non-standard verification-friendly language like Dafny or F*. The important part of adding software assurance is to avoid taxing the developer as much as possible. 

As always, keep watching the Rust space for firmware.

Beyond languages, I recently received

shirt in the mail. 

That same day I was listening to the podcast on PTAB on commute back from the office. My tidy cube is shown below with my friendly panopticon image nearby.

A few interesting fragments caught my attention, such as hedge funds bringing cases to PTAB. This reminded me of Trammell Hudson and his Two Sigma hedge fund and some of the rationale for research like Thunderstrike agsint folks like Apple when we chatted in person years back.

Other discussions about recusal for conflict of interest made me smile. I hearken back in the mid 90's when in my Compaq Computer Corporation new employee orientation down in Houston how I was chided not to transact stocks in 'customer, competitor, supplier,...' of Compaq. At the time this pretty much covered most companies on the stock exchanges. This early career lesson has stuck with me in that for the past 30 years working in tech I have been afraid to buy any shares outside of my employer and outside of my employer's stock program.

The other interesting podcast I caught was Hearing the director of the NSA casually opine on large language models and post-quantum cryptography is such an amazing change from my recollection of the NSA growing up. In my early years it was 'no such agency' typified by reading books like Quite the change.

Well, so much for banned functions, Rust, and podcasts. On to the next weekend to-do's.

No comments: