Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://hachyderm.io/users/joeyh/statuses/112481280910482851">see shy jo (joeyh@hachyderm.io)'s status on Wednesday, 22-May-2024 17:07:20 JST</a><a href="https://hachyderm.io/@joeyh" title="joeyh@hachyderm.io"><img src="https://gnusocial.jp/avatar/158711-48-20230808185707.webp" width="48" height="48" alt="see shy jo" style="position: absolute; left: 0; top: 0;">see shy jo</a><div><a href="https://hachyderm.io/@joeyh/112480942837373784" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/168938" title="nobodyinperson@fosstodon.org">Yann Büchau :nixos:</a></li><li><a href="https://gnusocial.jp/user/261406" title="mih@mas.to">Michael Hanke</a></li></ul></div></section><article><p><a href="https://fosstodon.org/@nobodyinperson">@nobodyinperson</a> <a href="https://mas.to/@mih">@mih</a> <a href="https://chaos.social/@chrysn">@chrysn</a> <br>While it's understandable that someone encountering a symlink related security hole may want to throw out the baby with the bathwater, what the git devs have actually done here is to only throw out the baby. This change will not prevent the class of security hole that motivated it.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3126767#notice-6192388">In conversation</a><time datetime="2024-05-22T17:07:20+09:00" title="Wednesday, 22-May-2024 17:07:20 JST">about 6 months ago</time> <span>from <span><a href="https://hachyderm.io/@joeyh/112481280910482851" rel="external" title="Sent from hachyderm.io via ActivityPub">hachyderm.io</a></span></span><a href="https://hachyderm.io/@joeyh/112481280910482851">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
see shy jo (joeyh@hachyderm.io)'s status on Wednesday, 22-May-2024 17:07:20 JSTsee shy jo
in reply to
@nobodyinperson @mih @chrysn
While it's understandable that someone encountering a symlink related security hole may want to throw out the baby with the bathwater, what the git devs have actually done here is to only throw out the baby. This change will not prevent the class of security hole that motivated it.
In conversationabout 6 months ago from hachyderm.iopermalink

Public

Embed Notice

HTML Code

Corresponding Notice