Veganism Social

Vasileios Kemerlis📢 Honored to return to Yale University last week to speak at the Department of Computer Science colloquium on Operating Systems security -- exactly 10 years after my first talk there on the same topic!In this "tin anniversary" edition, I reflected on how OS kernel exploitation and defense have evolved over the past decade, and shared highlights from some of our recent work in the field over the last five years:✳️ xMP (IEEE S&P 2020: 📄 <a href="https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf" rel="nofollow noopener" translate="no" target="_blank">https://cs.brown.edu/~vpk/papers/xmp.sp20.pdf</a>, 💾 <a href="https://github.com/virtsec/xmp" rel="nofollow noopener" translate="no" target="_blank">https://github.com/virtsec/xmp</a>) — Selective intra-kernel memory isolation using hardware-assisted virtualization.✳️ SafeSLAB (ACM CCS 2024: 📄 <a href="https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf" rel="nofollow noopener" translate="no" target="_blank">https://cs.brown.edu/~vpk/papers/safeslab.ccs24.pdf</a>, 💾 <a href="https://github.com/tum-itsec/safeslab" rel="nofollow noopener" translate="no" target="_blank">https://github.com/tum-itsec/safeslab</a>) — Kernel heap hardening through memory tagging.✳️ EPF (USENIX ATC 2023: 📄 <a href="https://cs.brown.edu/~vpk/papers/epf.atc23.pdf" rel="nofollow noopener" translate="no" target="_blank">https://cs.brown.edu/~vpk/papers/epf.atc23.pdf</a>, 💾 <a href="https://gitlab.com/brown-ssl/epf" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/brown-ssl/epf</a>) — Exploiting the (e)BPF sub-system for bypassing modern protections and ways to fix this.(Joint work with <a href="https://infosec.exchange/@mikepo" class="u-url mention" rel="nofollow noopener" target="_blank">@mikepo</a>, Marius Momeu, Vaggelis Atlidakis, <a href="https://mastodon.social/@dijin" class="u-url mention" rel="nofollow noopener" target="_blank">@dijin</a>, and Sergej Proskurin.)If this area of research interests you, you might also find our recent work on BeeBox (strengthening eBPF against transient execution attacks, USENIX Security 2024: 📄 <a href="https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf" rel="nofollow noopener" translate="no" target="_blank">https://cs.brown.edu/~vpk/papers/beebox.sec24.pdf</a>, 💾 <a href="https://gitlab.com/brown-ssl/beebox" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/brown-ssl/beebox</a>) and IUBIK (leveraging memory tagging and pointer authentication to isolate attacker-controlled data in kernel space, to appear in IEEE S&P 2025) worth a look.It was a real pleasure catching up with friends, colleagues, and students. And with the spring weather fully cooperating, I couldn't resist snapping a few photos of Yale's beautiful campus in the early morning light.Thank you to my host Charalampos Papamanthou and the Yale CS department for the warm welcome and thoughtful discussion!<a href="https://infosec.exchange/tags/xmp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xmp</a> <a href="https://infosec.exchange/tags/safeslab" class="mention hashtag" rel="nofollow noopener" target="_blank">#safeslab</a> <a href="https://infosec.exchange/tags/epf" class="mention hashtag" rel="nofollow noopener" target="_blank">#epf</a> <a href="https://infosec.exchange/tags/brownssl" class="mention hashtag" rel="nofollow noopener" target="_blank">#brownssl</a>

utzer [Pleroma]Ich bin überzeugt: Fotoverwaltungssoftware sollte Metadaten immer direkt in den Bilddateien speichern – plattform- und softwareübergreifend nutzbar. Ob Gesichterkennung, Beschreibungstext, Kategorien oder manuelle Tags – all diese Infos gehören nicht nur in eine Datenbank, sondern auch als Metadaten direkt ins <a class="hashtag" href="https://soc.utzer.de/tag/bild" rel="nofollow noopener" target="_blank">#Bild</a> (EXIF/XMP/IPTC etc.). Ich habe im Laufe der Jahre zwei Programme intensiver genutzt: Damals unter Windows: <a class="hashtag" href="https://soc.utzer.de/tag/picasa" rel="nofollow noopener" target="_blank">#Picasa</a> (RIP). Heute unter Linux: <a class="hashtag" href="https://soc.utzer.de/tag/digikam" rel="nofollow noopener" target="_blank">#Digikam</a>. Jetzt überlege ich, auf eine serverbasierte Lösung umzusteigen – aber immer bleibt dieselbe Frage: Wie <a class="hashtag" href="https://soc.utzer.de/tag/portabel" rel="nofollow noopener" target="_blank">#portabel</a> sind meine Daten, wenn die Software ausfällt oder ich wechseln will? Eine Metadatenstrategie, die auf offene Standards setzt, erleichtert Backups, Migration, parallele Nutzung und langfristige Verfügbarkeit. Wie seht ihr das? <a class="hashtag" href="https://soc.utzer.de/tag/fotomanagement" rel="nofollow noopener" target="_blank">#Fotomanagement</a> <a class="hashtag" href="https://soc.utzer.de/tag/exif" rel="nofollow noopener" target="_blank">#EXIF</a> <a class="hashtag" href="https://soc.utzer.de/tag/xmp" rel="nofollow noopener" target="_blank">#XMP</a> <a class="hashtag" href="https://soc.utzer.de/tag/linux" rel="nofollow noopener" target="_blank">#Linux</a> <a class="hashtag" href="https://soc.utzer.de/tag/selfhosted" rel="nofollow noopener" target="_blank">#Selfhosted</a> <a class="hashtag" href="https://soc.utzer.de/tag/fotosammlung" rel="nofollow noopener" target="_blank">#Fotosammlung</a> <a class="hashtag" href="https://soc.utzer.de/tag/foto" rel="nofollow noopener" target="_blank">#Foto</a>

Orion77176 ✅ ⏚ ᓚᘏᗢ ☢️ :lfin:<a href="https://piaille.fr/@quiou" class="u-url mention" rel="nofollow noopener" target="_blank">@quiou</a> <a href="https://mamot.fr/@Chtixof" class="u-url mention" rel="nofollow noopener" target="_blank">@Chtixof</a> bonjour, j'utilise <a href="https://orion.isintu.fr/tags/YunoHost" class="mention hashtag" rel="nofollow noopener" target="_blank">#YunoHost</a> qui est un serveur <a href="https://orion.isintu.fr/tags/xmp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xmp</a> sous debian 12. L'instance est une application de <a href="https://orion.isintu.fr/tags/yunohost" class="mention hashtag" rel="nofollow noopener" target="_blank">#yunohost</a> <a href="https://orion.isintu.fr/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#mastodon</a> tout est assez automatique. Aucun souci pour l'interconnexion avec le fediverse... Le serveur possède son firewall, tous les outils sont intégrés.<a href="https://yunohost.org/index.fr.html" rel="nofollow noopener" translate="no" target="_blank">https://yunohost.org/index.fr.html</a>

ℒӱḏɩę :blahaj:About time <a href="https://tech.lgbt/tags/Gigabyte" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gigabyte</a> fixed <a href="https://tech.lgbt/tags/XMP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMP</a> working on their <a href="https://tech.lgbt/tags/Aorus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Aorus</a> Master <a href="https://tech.lgbt/tags/x670e" class="mention hashtag" rel="nofollow noopener" target="_blank">#x670e</a> board. When I first built this rig in Sept 2022 (release day), my RAM ran at 5200, the entire system was perfect. Then every BIOS update after that busted it, I had to run stock until now with f33b when XMP started working again (I don't have EXPO RAM). Needless to say, never touching this <a href="https://tech.lgbt/tags/BIOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#BIOS</a> again! If it ain't broke.... <a href="https://tech.lgbt/tags/amd" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd</a>

Recent searches

Search options

Administered by:

Server stats:

#xmp