eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

209
active users

#loader

0 posts0 participants0 posts today
James_inthe_box<p>An unknown <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/loader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loader</span></a>:</p><p><a href="https://app.any.run/tasks/17232420-9cc7-41f8-937f-16fd654312da" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">app.any.run/tasks/17232420-9cc</span><span class="invisible">7-41f8-937f-16fd654312da</span></a></p><p>c2/drop 185.249.198.213 is suspiciously clean... cc <span class="h-card" translate="no"><a href="https://infosec.exchange/@da_667" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>da_667</span></a></span></p>
James_inthe_box<p><a href="https://infosec.exchange/tags/unknown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unknown</span></a>....but very interesting <a href="https://infosec.exchange/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> <a href="https://infosec.exchange/tags/loader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loader</span></a>:</p><p><a href="https://app.any.run/tasks/db4b4990-c941-4ba2-9d8c-2490e40ea3be" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">app.any.run/tasks/db4b4990-c94</span><span class="invisible">1-4ba2-9d8c-2490e40ea3be</span></a></p><p><span class="h-card" translate="no"><a href="https://infosec.exchange/@da_667" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>da_667</span></a></span> <span class="h-card" translate="no"><a href="https://bird.makeup/users/jane_0sint" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jane_0sint</span></a></span> you're gonna wanna look at this...</p>
TomAoki<p><span class="h-card" translate="no"><a href="https://bsd.network/@dvl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dvl</span></a></span> <span class="h-card" translate="no"><a href="https://bsd.network/@dch" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dch</span></a></span> <br>Not 100% sure about loader.efi, but at least boot1.efi would be affected if any read-incompatible feature(s) is/are enabled and active even on data-only pools.<br>This is because, in boot1.efi, it sniffs the existence of /boot/loader.efi to determine whether the pool is bootable or not.<br>loader.efi should need to sniff at least pool name(s), whether it's bootable or not by somehow reading the pool(s).</p><p>If you're 100% sure there's not at all a plan to have bootable ZFS (means, use UFS for boot throughout the future), and once confirmed it works as wanted, using gptboot.efi would be the way to go.<br>It does not sniff ZFS pools (not linked against ZFS codes) and (in contrast with boot1.efi) not obsoleted.</p><p><a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/loader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loader</span></a> <a href="https://mastodon.bsd.cafe/tags/bootcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bootcode</span></a> <a href="https://mastodon.bsd.cafe/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a> <a href="https://mastodon.bsd.cafe/tags/UFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UFS</span></a></p>