<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: zorgmonkey</title><link>https://news.ycombinator.com/user?id=zorgmonkey</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 12 Apr 2026 14:37:48 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=zorgmonkey" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by zorgmonkey in "TPM on embedded systems: Pitfalls and caveats to watch out for"]]></title><description><![CDATA[
<p>Their have been many vulnerabilities in TrustZone implementations and both Google and Apple now use separate secure element chips. In Apple's case they put the secure element as part of their main SoC, but on devices where that wasn't designed in house like Intel they had the T2 Security Chip. On all Pixel devices I'm pretty sure the Titan has been a separate chip (at least since they started including it at all).<p>So yes incorporating a separate secure element\TPM chip into a design is probably more secure, but ultimately the right call will always depend on your threat model.</p>
]]></description><pubDate>Wed, 21 Jan 2026 17:43:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=46708866</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=46708866</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46708866</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Sony PS5 ROM keys leaked – jailbreaking could be made easier with BootROM codes"]]></title><description><![CDATA[
<p>Here's an excerpt about the anti-rollback feature from Nvidia's docs on how the Tegra X1 SoC in the switch 1 boots [0] (called Tegra210 in the document)<p>> By default, the boot ROM will only consider bootloader entries with a version field that matches the version field of the first entry, and will stop iterating through the entries is a mismatch is found. The intent is to ensure that if some subset of the bootloader entries are upgraded, and hence the version field of their entries is modified, then the boot ROM will only boot the most recent version of the bootloader. This prevents an accidental rollback to an earlier version of the bootloader in the face of boot memory read errors, corruption, or tampering. Observe that this relies on upgraded bootloader entries being placed contiguously at the start of the array.<p>[0] <a href="https://http.download.nvidia.com/tegra-public-appnotes/tegra-boot-flow.html#_bootloader_redundancy" rel="nofollow">https://http.download.nvidia.com/tegra-public-appnotes/tegra...</a></p>
]]></description><pubDate>Thu, 01 Jan 2026 18:58:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=46456916</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=46456916</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46456916</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Sony PS5 ROM keys leaked – jailbreaking could be made easier with BootROM codes"]]></title><description><![CDATA[
<p>It isn't that wild; the typical name for it is anti-rollback, and you probably have at least one device that implements it. Most Android devices have anti-rollback efuses to prevent installing older versions of the bootchain\bootloader; they might still allow you to downgrade the OS (depends on the vendor, if memory serves). Instead of using efuse counters, anti-rollback counters can also be implemented by Replay Protected Memory Block (RPMB), which is implemented by many flash storage (eMMC often supports RPMB, but other storage types can as well). It is possible to implement anti-rollback mechanisms on x86_64 by utilizing a TPM [0], but as far as I know, only Chrome OS does this.<p>[0]: <a href="https://www.chromium.org/developers/design-documents/tpm-usage/#rollback-prevention" rel="nofollow">https://www.chromium.org/developers/design-documents/tpm-usa...</a></p>
]]></description><pubDate>Thu, 01 Jan 2026 18:36:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=46456709</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=46456709</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46456709</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Google unkills JPEG XL?"]]></title><description><![CDATA[
<p>It looks very likely chromium will be using jxl-rs crate for this feature [0]. My personal suspicion is that they've just been waiting for it to good enough to integrate and they didn't want to promise anything until it was ready (hence the long silence).<p>[0] <a href="https://issues.chromium.org/issues/40168998#comment507" rel="nofollow">https://issues.chromium.org/issues/40168998#comment507</a></p>
]]></description><pubDate>Mon, 01 Dec 2025 17:58:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=46110608</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=46110608</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46110608</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Pebble Watch software is now open source"]]></title><description><![CDATA[
<p>Pebble watches run on Cortex-M microcontrollers which have less than 1MB of flash storage and RAM, I like Kotlin multiplatform but getting it to run on them is extremely unlikely. I assume that for the foreseeable future Pebble apps will be only written in languages which are traditionally used for MCUs like Rust and C\C++</p>
]]></description><pubDate>Tue, 25 Nov 2025 06:46:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=46043000</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=46043000</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46043000</guid></item><item><title><![CDATA[New comment by zorgmonkey in "NTSB Preliminary Report – UPS Boeing MD-11F Crash [pdf]"]]></title><description><![CDATA[
<p>Yeah working again for me too, they're probably having some sort of server problems</p>
]]></description><pubDate>Thu, 20 Nov 2025 21:07:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=45997753</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45997753</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45997753</guid></item><item><title><![CDATA[New comment by zorgmonkey in "NTSB Preliminary Report – UPS Boeing MD-11F Crash [pdf]"]]></title><description><![CDATA[
<p>I found a link to the PDF that seems to work <a href="https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201958/pdf" rel="nofollow">https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/G...</a><p>Also in case that link stops working I got it from this page <a href="https://www.ntsb.gov/investigations/Pages/DCA26MA024.aspx" rel="nofollow">https://www.ntsb.gov/investigations/Pages/DCA26MA024.aspx</a><p>EDIT: nevermind immediately after posting this comment it is now giving a 403 error</p>
]]></description><pubDate>Thu, 20 Nov 2025 20:52:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=45997543</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45997543</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45997543</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Android 16 QPR1 is being pushed to the Android Open Source Project"]]></title><description><![CDATA[
<p>They still use gerrit, that site is a code search UI that they have that is also a very nice way to navigate the code.</p>
]]></description><pubDate>Thu, 13 Nov 2025 20:07:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=45919846</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45919846</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45919846</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Futurelock: A subtle risk in async Rust"]]></title><description><![CDATA[
<p>Rust moves are a memcpy where the source becomes effectively unitialized after the move (that is say it is undefined to access it after the move). The copies are often optimized by the compiler but it isn't guaranteed.<p>This actually caused some issues with rust in the kernel because moving large structs could cause you to run out the small amount of stack space availabe on kernel threads (they only allocate 8-16KB of stack compared to a typical 8MB for a userspace thread). The pinned-init crate is how they ended solving this [1].<p>[1] <a href="https://crates.io/crates/pinned-init" rel="nofollow">https://crates.io/crates/pinned-init</a></p>
]]></description><pubDate>Fri, 31 Oct 2025 23:39:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=45777909</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45777909</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45777909</guid></item><item><title><![CDATA[New comment by zorgmonkey in "PlayStation 3 Architecture (2021)"]]></title><description><![CDATA[
<p>With enough effort you could definitely do it. Just remember it is a device that came out in 2006 and it has 256MB of system RAM and 256MB of VRAM, at best you're running a quite small model after a lot work trying to port some inference code to CELL processors. Honestly it does sound a cool excuse to write code for the CELL processors, but don't expect amazing performance or anything.</p>
]]></description><pubDate>Sat, 18 Oct 2025 01:59:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=45624242</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45624242</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45624242</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Garbage collection for Rust: The finalizer frontier"]]></title><description><![CDATA[
<p>This is a very important point, careful use of GCs for a special subset of allocations that say have tricky lifetimes for some reason and aren't performance critical could have a much smaller impact on overall application performance than people might otherwise expect.</p>
]]></description><pubDate>Wed, 15 Oct 2025 18:22:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=45596549</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45596549</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45596549</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Garbage collection for Rust: The finalizer frontier"]]></title><description><![CDATA[
<p>It looks like the API of Alloy was at least designed in such a way that can somewhat easily change the GC implementation out down the line and I really hope they do cause Boehm GC and conservative GC in general is much too slow compared to state of the art precise GCs.</p>
]]></description><pubDate>Wed, 15 Oct 2025 18:20:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=45596519</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45596519</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45596519</guid></item><item><title><![CDATA[New comment by zorgmonkey in "PYREX vs. pyrex: What's the difference?"]]></title><description><![CDATA[
<p>If you're curious the only brand I could find easily purchasable in the USA that uses borosilicate glass is oxo. Their are some other results if you do a search on amazon, but I'm not very convinced those are really borosilicate glass.</p>
]]></description><pubDate>Sat, 20 Sep 2025 08:56:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=45311632</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45311632</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45311632</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Signal Secure Backups"]]></title><description><![CDATA[
<p>Why wouldn't it be possible? All it really means is that you need to do the work to make incremental entirely on the local side and not on the remote side.</p>
]]></description><pubDate>Tue, 09 Sep 2025 17:20:22 +0000</pubDate><link>https://news.ycombinator.com/item?id=45185207</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45185207</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45185207</guid></item><item><title><![CDATA[New comment by zorgmonkey in "PinePhone Pro [GNU/Linux smartphone] has been discontinued"]]></title><description><![CDATA[
<p>The answer is boring and annoying, they almost certainly want it to work with TVs and cheap monitors both of which commonly only have HDMI inputs. It has been my experience that you typically have to pay more for a USB-C dock with displayport outputs, even though they don't have the chip just cause of economies of scale.</p>
]]></description><pubDate>Thu, 28 Aug 2025 18:38:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=45055477</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=45055477</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45055477</guid></item><item><title><![CDATA[New comment by zorgmonkey in "I made a real-time C/C++/Rust build visualizer"]]></title><description><![CDATA[
<p>You can make an email you don't care about with protonmail, I recommend them cause they don't require you to enter an existing email address or a phone number when signing up.</p>
]]></description><pubDate>Fri, 15 Aug 2025 21:44:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=44917612</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=44917612</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44917612</guid></item><item><title><![CDATA[New comment by zorgmonkey in "The hidden JTAG in a Qualcomm/Snapdragon device’s USB port"]]></title><description><![CDATA[
<p>yeah EDL loaders for a bunch of production devices exist here [0] also more on various XDA Forum posts for stuff like unbricking guides. It is worth noting for people who don't<p>[0]: <a href="https://github.com/bkerler/Loaders">https://github.com/bkerler/Loaders</a></p>
]]></description><pubDate>Mon, 30 Jun 2025 21:11:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=44427931</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=44427931</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44427931</guid></item><item><title><![CDATA[New comment by zorgmonkey in "HCP Vault Secrets End of Life"]]></title><description><![CDATA[
<p>I haven't tried it out, but it looks they recently added PKCS#11 which should make it possible to use it with devices like HSMs and cloud KMS solutions.</p>
]]></description><pubDate>Fri, 20 Jun 2025 18:33:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=44330574</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=44330574</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44330574</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Why Android can't use CDC Ethernet (2023)"]]></title><description><![CDATA[
<p>UAC is not a security boundary, it is instead considered a defense-in-depth feature (aka best effort but bypassable). This is officially documented by Microsoft in multiple places.
[0] <a href="https://www.microsoft.com/en-us/msrc/windows-security-servicing-criteria" rel="nofollow">https://www.microsoft.com/en-us/msrc/windows-security-servic...</a>
[1] <a href="https://learn.microsoft.com/en-us/troubleshoot/windows-server/windows-security/disable-user-account-control" rel="nofollow">https://learn.microsoft.com/en-us/troubleshoot/windows-serve...</a></p>
]]></description><pubDate>Mon, 09 Jun 2025 16:24:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=44226098</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=44226098</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44226098</guid></item><item><title><![CDATA[New comment by zorgmonkey in "Cloud Run GPUs, now GA, makes running AI workloads easier for everyone"]]></title><description><![CDATA[
<p>The price of that system is unfortunately going to end up being a lot more than 4k, you'd need a CPU that has at least 64 lanes of PCIe. That's going to be either a Xeon W or a Threadripper CPU, with the motherboard RAM, etc you're probably looking at least another 2k.<p>Also kind of a nitpick, but I'd call that 8 GPU system, each BMG-G21 die has 20 Xe2 cores. Also even though it would be 4 PCIe cards it is probably best to think of it as 8 GPUs (that's how it will show up in stuff like pytorch), especially because their is no high-speed interconnect between the GPU dies colocated on the card. Also if you're going to do this make sure you get a motherboard with good PCIe bifurcation support.</p>
]]></description><pubDate>Wed, 04 Jun 2025 16:44:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=44182670</link><dc:creator>zorgmonkey</dc:creator><comments>https://news.ycombinator.com/item?id=44182670</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44182670</guid></item></channel></rss>