<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: aliceryhl</title><link>https://news.ycombinator.com/user?id=aliceryhl</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 06 Apr 2026 09:32:26 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=aliceryhl" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by aliceryhl in "Linux Internals: How /proc/self/mem writes to unwritable memory (2021)"]]></title><description><![CDATA[
<p>Interesting. Though looking at the code, it does still check VM_MAYWRITE, so the mapping needs to be something you could remap as writable.</p>
]]></description><pubDate>Mon, 09 Mar 2026 07:14:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=47305722</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=47305722</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47305722</guid></item><item><title><![CDATA[New comment by aliceryhl in "Trump's global tariffs struck down by US Supreme Court"]]></title><description><![CDATA[
<p>Ah thanks for clarifying.</p>
]]></description><pubDate>Mon, 23 Feb 2026 20:12:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=47128083</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=47128083</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47128083</guid></item><item><title><![CDATA[New comment by aliceryhl in "What not to write on your security clearance form (1988)"]]></title><description><![CDATA[
<p>Thank you. I was wondering about that.</p>
]]></description><pubDate>Sat, 21 Feb 2026 21:03:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=47104724</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=47104724</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47104724</guid></item><item><title><![CDATA[New comment by aliceryhl in "Trump's global tariffs struck down by US Supreme Court"]]></title><description><![CDATA[
<p>Hmm, I read some of the decision, and now I'm not sure what to make of all of it.<p>When I came to the opinion from Jackson, J., I found it extremely compelling. He says this:<p><i>... But some of TWEA’s sections delegating this authority had lapsed, and “there [was] doubt as to the effectiveness of other sections.” Accordingly, Congress amended TWEA in 1941, adding the subsection that includes the “regulate ... importation” language on which the President relies today. The Reports explained Congress’s primary purpose for the 1941 amendment: shoring up the President’s ability to control foreign-owned property by maintaining and strengthening the “existing system of foreign property control (commonly known as freezing control).”</i><p><i>When Congress enacted IEEPA in 1977, limiting the circumstances under which the President could exercise his emergency authorities, it kept the “regulate ... importation” language from TWEA. The other two relevant pieces of legislative history—the Senate and House Reports that accompanied IEEPA—demonstrate that Congress’s intent regarding the scope of this statutory language remained the same. As the Senate Report explained, Congress’s sole objective for the “regulate ... importation” subsection was to grant the President the emergency authority “to control or freeze property transactions where a foreign interest is involved.” The House Report likewise described IEEPA as empowering the President to “regulate or freeze any property in which any foreign country or a national thereof has any interest.”</i><p>However, then I read Kavanaugh, J. who writes the following:<p><i>In 1971, President Nixon imposed 10 percent tariffs on almost all foreign imports. He levied the tariffs under IEEPA’s predecessor statute, the Trading with the Enemy Act (TWEA), which similarly authorized the President to “regulate ... importation.” The Nixon tariffs were upheld in court.</i><p><i>When IEEPA was enacted in 1977 in the wake of the Nixon and Ford tariffs and the Algonquin decision, Congress and the public plainly would have understood that the power to “regulate ... importation” included tariffs. If Congress wanted to exclude tariffs from IEEPA, it surely would not have enacted the same broad “regulate ... importation” language that had just been used to justify major American tariffs on foreign imports.</i><p>And I also find this compelling.<p>To add onto this, Roberts, C. J. says: <i>IEEPA’s grant of authority to “regulate ... importation” falls short. IEEPA contains no reference to tariffs or duties. The Government points to no statute in which Congress used the word “regulate” to authorize taxation. And until now no President has read IEEPA to confer such power.</i><p>This seems directly contradictory to Kavanaugh, J.'s dissent! Kavanaugh, J. claims that Nixon used the word “regulate” to impose tarrifs. And apparently the word isn't just in some random other statute — Nixon did so from TWEA, the predecessor of IEEPA: <i>when Congress enacted IEEPA in 1977 it kept the “regulate ... importation” language from TWEA.</i> (from Jackson, J.) So the point that no President has read IEEPA to confer such power seems pretty weak, when Nixon apparently did so from TWEA.<p>I have no conclusion from this, but IMO both Jackson, J. and Kavanaugh, J. have pretty strong points in opposing directions.</p>
]]></description><pubDate>Sat, 21 Feb 2026 08:24:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=47098648</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=47098648</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47098648</guid></item><item><title><![CDATA[New comment by aliceryhl in "Rex is a safe kernel extension framework that allows Rust in the place of eBPF"]]></title><description><![CDATA[
<p>I asked about this when they presented the project at the Linux Plumbers conference. They replied that it's not really intended to be a security boundary, and that you should not let anyone malicious load these programs.<p>Given this thread model, I think their project is entirely reasonable. Safe Rust will prevent accidental mistakes even if you could technically circumvent it if you really try.</p>
]]></description><pubDate>Sun, 28 Dec 2025 09:00:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=46409555</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=46409555</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46409555</guid></item><item><title><![CDATA[New comment by aliceryhl in "Asahi Linux with Sway on the MacBook Air M2 (2024)"]]></title><description><![CDATA[
<p>I have no insight into the Asahi project, but the LKML link goes to an email from James Calligeros containing code written by Hector Martin and Sven Peter. The code may have been written a long time ago.</p>
]]></description><pubDate>Thu, 25 Dec 2025 20:55:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=46386980</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=46386980</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46386980</guid></item><item><title><![CDATA[New comment by aliceryhl in "Asahi Linux with Sway on the MacBook Air M2 (2024)"]]></title><description><![CDATA[
<p>That's an email from James Calligeros. All this patch says is that the author is Hector Martin (and Sven Peter). The code could have been written a long time ago.</p>
]]></description><pubDate>Thu, 25 Dec 2025 20:51:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=46386955</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=46386955</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46386955</guid></item><item><title><![CDATA[New comment by aliceryhl in "Texas is suing all of the big TV makers for spying on what you watch"]]></title><description><![CDATA[
<p>Where I'm from, it probably would not be stolen by anyone.</p>
]]></description><pubDate>Fri, 19 Dec 2025 16:43:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=46327845</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=46327845</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46327845</guid></item><item><title><![CDATA[New comment by aliceryhl in "The healthcare market is taxing reproduction out of existence"]]></title><description><![CDATA[
<p>How?</p>
]]></description><pubDate>Mon, 01 Dec 2025 22:58:40 +0000</pubDate><link>https://news.ycombinator.com/item?id=46114632</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=46114632</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46114632</guid></item><item><title><![CDATA[New comment by aliceryhl in "Upcoming Rust language features for kernel development"]]></title><description><![CDATA[
<p>It never made it into upstream Linux, but there is already a sample implementation that Wedson wrote in 2022:
<a href="https://github.com/Rust-for-Linux/linux/pull/798" rel="nofollow">https://github.com/Rust-for-Linux/linux/pull/798</a></p>
]]></description><pubDate>Fri, 17 Oct 2025 16:40:19 +0000</pubDate><link>https://news.ycombinator.com/item?id=45618792</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=45618792</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45618792</guid></item><item><title><![CDATA[New comment by aliceryhl in "Upcoming Rust language features for kernel development"]]></title><description><![CDATA[
<p>It won't be different from Tokio. When you pass a future to tokio::spawn, that will also eagerly execute the future right away.</p>
]]></description><pubDate>Fri, 17 Oct 2025 16:37:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=45618751</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=45618751</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45618751</guid></item><item><title><![CDATA[New comment by aliceryhl in "Upcoming Rust language features for kernel development"]]></title><description><![CDATA[
<p>It's trivial to implement an async runtime in the kernel. The kernel's workqueue is already essentially a runtime.</p>
]]></description><pubDate>Thu, 16 Oct 2025 12:17:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=45604424</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=45604424</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45604424</guid></item><item><title><![CDATA[New comment by aliceryhl in "Io_uring, kTLS and Rust for zero syscall HTTPS server"]]></title><description><![CDATA[
<p>> IIRC Alice from the tokio team also suggested there hasn't been much interest in pushing through these difficulties more recently, as the current performance is "good enough".<p>Well, I think there is interest, but mostly for file IO.<p>For file IO, the situation is pretty simple. We already have to implement that using spawn_blocking, and spawn_blocking has the exact same buffer challenges as io_uring does, so translating file IO to io_uring is not that tricky.<p>On the other hand, I don't think tokio::net's existing APIs will support io_uring. Or at least they won't support the buffer-based io_uring APIs; there is no reason they can't register for readiness through io_uring.</p>
]]></description><pubDate>Fri, 22 Aug 2025 12:40:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=44983850</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=44983850</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44983850</guid></item><item><title><![CDATA[New comment by aliceryhl in "Rust’s dependencies are starting to worry me"]]></title><description><![CDATA[
<p>I'm quite careful to tightly control the dependencies of Tokio. All dependencies are under control by members of the Tokio team or others that I trust.</p>
]]></description><pubDate>Fri, 09 May 2025 14:04:45 +0000</pubDate><link>https://news.ycombinator.com/item?id=43936910</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=43936910</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43936910</guid></item><item><title><![CDATA[New comment by aliceryhl in "'Mathematically perfect' star system being investigated for potential alien tech"]]></title><description><![CDATA[
<p>The caption for the picture says this:<p>> The six planets orbit their central star HD 110067 in a harmonic rhythm with planets aligning every few orbits.</p>
]]></description><pubDate>Wed, 28 Feb 2024 15:38:49 +0000</pubDate><link>https://news.ycombinator.com/item?id=39539341</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=39539341</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39539341</guid></item><item><title><![CDATA[New comment by aliceryhl in "Git Things"]]></title><description><![CDATA[
<p>Regarding the review process ... one thing that I find challenging and don't know a good solution to is documentation. I've received many PRs where the change itself is fine, but the PR is dragging out because the documentation is lacking, and getting the PR author to improve it sometimes takes a lot of review rounds.<p>What would you do to avoid this?<p>Sometimes the same situation comes up with tests, but it is not as common in my experience.</p>
]]></description><pubDate>Mon, 01 Jan 2024 12:32:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=38831393</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=38831393</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38831393</guid></item><item><title><![CDATA[New comment by aliceryhl in "Rust to stabilize `async fn` and return-position `impl Trait` in traits"]]></title><description><![CDATA[
<p>It's well known that what is being stabilized today is lacking the Send bounds stuff. In fact, there was a lot of discussion about whether they should completely block this feature until the Send bounds stuff was ready. Ultimately I think it is good that they shipped this part of the feature even though the other part isn't ready yet - Tower isn't able to use this yet, but other crates can.</p>
]]></description><pubDate>Thu, 21 Dec 2023 17:42:34 +0000</pubDate><link>https://news.ycombinator.com/item?id=38723773</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=38723773</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38723773</guid></item><item><title><![CDATA[New comment by aliceryhl in "Google OAuth is broken (sort of)"]]></title><description><![CDATA[
<p>If you pay too much in bounties, you risk having your own red-team employees leave so that they can report bugs externally and get paid much more via bounties.</p>
]]></description><pubDate>Thu, 21 Dec 2023 16:45:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=38722872</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=38722872</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38722872</guid></item><item><title><![CDATA[New comment by aliceryhl in "Sudo-rs' first security audit"]]></title><description><![CDATA[
<p>I'm surprised that CLN-003 made the list even as low severity. It's intended to make reverse engineering of the binary harder, but the code is already freely accessible (and CLN-003 also acknowledges this).</p>
]]></description><pubDate>Fri, 03 Nov 2023 22:04:26 +0000</pubDate><link>https://news.ycombinator.com/item?id=38135631</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=38135631</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=38135631</guid></item><item><title><![CDATA[New comment by aliceryhl in "The underground world of credit card network exploitation"]]></title><description><![CDATA[
<p>In Denmark, there's a national system for authentication used for government sites and banks. I have a small device with a single button on it that shows a 6-digit code when you press it. I enter that code along with a password any time I make a purchase online.<p>(There's also an app that most people use. But I like the hardware thingy better.)</p>
]]></description><pubDate>Wed, 02 Aug 2023 21:57:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=36978245</link><dc:creator>aliceryhl</dc:creator><comments>https://news.ycombinator.com/item?id=36978245</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=36978245</guid></item></channel></rss>