HackerTubewatch
Surprise me
Frame from BlueHat IL 2023 - David Weston - Default Security Plays via YouTube's privacy-enhanced embed

BlueHat IL 2023 - David Weston - Default Security

Microsoft Israel R&D Center
Talks
YouTube
3 HN users recommended this talk2 months2023–2025 score 2
Years with an HN recommendation, 2007–2026

HN uses it as the primary source for Microsoft's Rust adoption and its reasoning on TPM and security requirements.

David Weston's BlueHat IL 2023 talk traces the evolution of Windows security and previews Windows 11 and hardware advances. It ends with upcoming changes such as Rust in the kernel and fonts, signed binaries and adminless Windows.

“The speaker covers a bunch of areas and the final part of the talk (around 10 minutes) is about Microsoft introducing Rust in some self-contained areas in Windows.” (HN, 2023)

4 recommendations · 8 citations · Talks · intermediate · partly dated

12 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@nindalf Apr 2023 Recommends
on HN thread Microsoft is to enable Rust use for Windows 11 kernel
Read more
Link to the talk - [this video] (timestamped to the part about Rust) The speaker covers a bunch of areas and the final part of the talk (around 10 minutes) is about Microsoft introducing Rust in some self-contained areas in Windows. Some highlights: - Their focus is on "killing bug classes". More context in this post by Microsoft Research from 2019 - A proactive approach to more secure code. - They want to do this with memory safe languages, CPU architectural changes and safer language subsets. This talk focussed on memory safe languages, specifically Rust. - First area they've introduced Rust in - a cross platform rewrite of a font parser called DWriteCore. The team reported that parsing was "incredibly easy". Font shaping performance increased by 5-15% compared to the C++ version. - It took about 2 devs working for half a year to complete this. The speaker says this is pretty good value for an area that is notorious for security bugs. - Second area is the REGION data type in Win32k GDI. Currently in consumer Windows, disabled by feature flag. Will be enabled in insider builds soon. Performance has been good, some small wins for the Rust version. - There is now a Windows SysCall implemented in completed safe Rust. TLDR - Rust is inside the Windows Kernel, will be enabled widely soon.
Rust in font parser and Win32k, plus killing bug classes
@Hawxy Apr 2023 Recommends
on HN thread Microsoft quietly supported legislation to make it easier to fix devices
> just to make existing CPUs obsolete and keep Intel in business. Bizarre take. It's not random, it's specifically CPUs that support modern hardware security mitigations. There's a pretty great talk from Bluehat a few days ago that goes into why Microsoft is doing this: [this video]
Explains why Microsoft requires modern security CPUs

Citations, criticism and jokes

@mustache_kimono Apr 2023 Cites it
on HN thread BlueHat IL 2023: Microsoft rewriting core Windows libraries in Rust
Rust discussion starts at: [this video] Highlights: * 2 projects: dwrite and Win32k * 2 devs, 6 months to rewrite 152KLOC C++ to 90KLOC Rust re dwrite * Performance increases of 5-15% re dwrite * Only about 10% of Win32k code is unsafe * No perf regressions re Win32k * Syscall in the Windows kernel now written in Rust
Microsoft rewriting Windows components in Rust with performance gains
@mustache_kimono Apr 2023 Cites it
on HN thread Microsoft is to enable Rust use for Windows 11 kernel
> BlueHat IL 2023: Microsoft rewriting core Windows libraries in Rust (youtube.com) 89 points by mustache_kimono 23 hours ago | past | 45 comments The primary source material is this talk: [this video]
Primary source on Rust in Windows
@pl4nty Apr 2023 Cites it
on HN thread Microsoft quietly supported legislation to make it easier to fix devices
David Weston was very involved in the TPM decision, and spoke about it here: [this video] After msft's experiences with Win10, they decided Windows wouldn't become more secure unless they enabled features by default. And the majority of high-impact features depend on a TPM. I'd argue that home users do need these features in the current security environment. TPMs have been required in new devices since 2016, so people are more likely to have thrown out incompatible devices already (CPU/RAM if not disk)
Weston explains the TPM decision
@pjmlp May 2023 Cites it
on HN thread Win32 App Isolation
This is the continuation of bringing UWP security model into Win32, and make Windows security features all enabled by default. See BlueHat IL talk on the matter, [this video] There are no plans for Windows 10, beyond security fixes until 2025, it is done. EDIT: There is a BUILD 2023 talk on the matter as well. [link]
Context on bringing UWP security model to Win32

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close