Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.derg.nz/users/anthropy/statuses/115844474489729674">Anthropy (anthropy@mastodon.derg.nz)'s status on Tuesday, 06-Jan-2026 06:00:53 JST</a><a href="https://mastodon.derg.nz/@anthropy" title="anthropy@mastodon.derg.nz"><img src="https://gnusocial.jp/avatar/160721-48-20260318195618.webp" width="48" height="48" alt="Anthropy" style="position: absolute; left: 0; top: 0;">Anthropy</a><div><a href="https://hachyderm.io/@dalias/115844425748050854" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://hachyderm.io/@dalias">@dalias</a> <a href="https://social.treehouse.systems/@astraleureka">@astraleureka</a> I mean, I do agree it feels dirty, but, if you don't trust the hypervisor you're running under that has a whole host (pun intended) of other implications</p><p>like they could just:<br>- extract keys from your RAM (volatility tool, <a href="https://github.com/ZarKyo/awesome-volatility/blob/main/README.md" rel="nofollow">https://github.com/ZarKyo/awesome-volatility/blob/main/README.md</a> )<br>- reboot your VM and inject malicious boot params into your grub/whatever<br>- technically even alter instructions on the fly<br>- etc</p><p>while it does make me feel dirtier to run systemd, hypervisors are always kind of a problem tbh.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/6027488#notice-11866071">In conversation</a><time datetime="2026-01-06T06:00:53+09:00" title="Tuesday, 06-Jan-2026 06:00:53 JST">about 3 months ago</time> <span>from <span><a href="https://mastodon.derg.nz/@anthropy/115844474489729674" rel="external" title="Sent from mastodon.derg.nz via ActivityPub">mastodon.derg.nz</a></span></span><a href="https://mastodon.derg.nz/@anthropy/115844474489729674">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/ZarKyo/awesome-volatility/blob/main/README.md">awesome-volatility/README.md at main · ZarKyo/awesome-volatility</a></h5><div></div></header><div>A curated list of ressources for Volatility 2 &amp; 3. Contribute to ZarKyo/awesome-volatility development by creating an account on GitHub.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Anthropy (anthropy@mastodon.derg.nz)'s status on Tuesday, 06-Jan-2026 06:00:53 JSTAnthropy
in reply to
- Rich Felker
@dalias @astraleureka I mean, I do agree it feels dirty, but, if you don't trust the hypervisor you're running under that has a whole host (pun intended) of other implications
like they could just:
- extract keys from your RAM (volatility tool, https://github.com/ZarKyo/awesome-volatility/blob/main/README.md )
- reboot your VM and inject malicious boot params into your grub/whatever
- technically even alter instructions on the fly
- etc
while it does make me feel dirtier to run systemd, hypervisors are always kind of a problem tbh.
In conversationabout 3 months ago from mastodon.derg.nzpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  awesome-volatility/README.md at main · ZarKyo/awesome-volatility
  A curated list of ressources for Volatility 2 & 3. Contribute to ZarKyo/awesome-volatility development by creating an account on GitHub.

Public

Embed Notice

HTML Code

Corresponding Notice