<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: smlx</title><link>https://news.ycombinator.com/user?id=smlx</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 08 May 2026 16:44:42 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=smlx" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by smlx in "Next.js version 15.2.3 has been released to address a security vulnerability"]]></title><description><![CDATA[
<p>next.js has a history of similar vulnerabilities.<p>I was made aware recently of a vulnerability that was fixed by this patch: <a href="https://github.com/vercel/next.js/pull/73482/files" rel="nofollow">https://github.com/vercel/next.js/pull/73482/files</a><p>In this vulnerability, adding a 'x-middleware-rewrite: <a href="https://www.example.com" rel="nofollow">https://www.example.com</a>' header would cause the server to respond with the contents of example.com. i.e. the worlds dumbest SSRF.<p>Note that there is no CVE for this vulnerability, nor is there any clear information about which versions are affected.<p>Also note that according to the published support policy for nextjs only "stable" (15.2.x) and "canary" (15.3.x) receive patches. But for the vulnerability reported here they are releasing patches for 14.x and 13.x apparently?<p><a href="https://github.com/vercel/next.js/blob/canary/contributing/repository/release-channels-publishing.md" rel="nofollow">https://github.com/vercel/next.js/blob/canary/contributing/r...</a><p>IMO you are playing with fire using nextjs for anything where you care about security and maintenance. Which seems insane for a project with 130k+ Github stars and supported by a major company like vercel.</p>
]]></description><pubDate>Sun, 23 Mar 2025 00:50:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=43449986</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=43449986</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43449986</guid></item><item><title><![CDATA[New comment by smlx in "Kubesafe: Never run Kubernetes commands on the wrong cluster again"]]></title><description><![CDATA[
<p>I came up with a simpler solution that keeps kube contexts separated per terminal.<p><a href="https://smlx.dev/posts/kubectl-global-state/" rel="nofollow">https://smlx.dev/posts/kubectl-global-state/</a></p>
]]></description><pubDate>Sat, 21 Sep 2024 08:07:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=41608394</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=41608394</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41608394</guid></item><item><title><![CDATA[New comment by smlx in "Reverse-engineering an encrypted IoT protocol"]]></title><description><![CDATA[
<p>I have never heard of ImHex before. Thanks, I'll take a look!</p>
]]></description><pubDate>Wed, 14 Feb 2024 17:59:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=39372925</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=39372925</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39372925</guid></item><item><title><![CDATA[Reverse-engineering an encrypted IoT protocol]]></title><description><![CDATA[
<p>Article URL: <a href="https://smlx.dev/posts/goodwe-sems-protocol-teardown/">https://smlx.dev/posts/goodwe-sems-protocol-teardown/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=39371831">https://news.ycombinator.com/item?id=39371831</a></p>
<p>Points: 232</p>
<p># Comments: 40</p>
]]></description><pubDate>Wed, 14 Feb 2024 16:34:22 +0000</pubDate><link>https://smlx.dev/posts/goodwe-sems-protocol-teardown/</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=39371831</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39371831</guid></item><item><title><![CDATA[New comment by smlx in "Blocking Kiwifarms"]]></title><description><![CDATA[
<p>Imagine I own a bunch of billboards around town. A customer comes to me with cash and wants to display someone's personal details and a message encouraging harassment on my billboards.<p>Do I have to wait for law enforcement to stop me from displaying their content? Or can I, as a private company, make a judgement call and decline their business?<p>I think the answer here is pretty obvious and your attempt at passing the buck is pathetically weak.</p>
]]></description><pubDate>Sun, 04 Sep 2022 00:31:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=32708219</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=32708219</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32708219</guid></item><item><title><![CDATA[New comment by smlx in "JiraCLI"]]></title><description><![CDATA[
<p>I wrote a tool that allows me to avoid the terrible Tempo web UI - you might be interested: <a href="https://github.com/smlx/jiratime" rel="nofollow">https://github.com/smlx/jiratime</a></p>
]]></description><pubDate>Fri, 12 Aug 2022 12:26:28 +0000</pubDate><link>https://news.ycombinator.com/item?id=32437465</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=32437465</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=32437465</guid></item><item><title><![CDATA[New comment by smlx in "Gaming on Wayland"]]></title><description><![CDATA[
<p>Not if you use screen scaling.</p>
]]></description><pubDate>Wed, 15 Dec 2021 01:10:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=29560664</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=29560664</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29560664</guid></item><item><title><![CDATA[New comment by smlx in "Gaming on Wayland"]]></title><description><![CDATA[
<p>More accurately, the developers need to a) fix the buggy implementation of the Gnome-specific protocol they currently use, and b) switch to the standard screensharing protocol.<p><a href="https://github.com/flathub/us.zoom.Zoom/pull/182#issuecomment-873409640" rel="nofollow">https://github.com/flathub/us.zoom.Zoom/pull/182#issuecommen...</a></p>
]]></description><pubDate>Wed, 15 Dec 2021 01:10:06 +0000</pubDate><link>https://news.ycombinator.com/item?id=29560653</link><dc:creator>smlx</dc:creator><comments>https://news.ycombinator.com/item?id=29560653</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=29560653</guid></item></channel></rss>