Felix Dreissig
F30@chaos.social
<p>Computer scientist at the intersection of software development, IT operations, and security.</p><p>Currently: Information security at codecentric (but views my own etc.), CTF infra for FAUST CTF, event orga at <span class="h-card" translate="no"><a href="https://chaos.social/@c3speakersdesk" class="u-url mention">@<span>c3speakersdesk</span></a></span>, hiking and skiing in the mountains.</p><p>Previously: DevSecOps for noris network, student at <span class="h-card" translate="no"><a href="https://mastodon.social/@FAU" class="u-url mention">@<span>FAU</span></a></span>, CTF player with FAUST.</p>
Posts
-
Post #679469
1. Tell everybody that your API keys aren‘t secret and it’s safe to publish them on your website. 2. Protect sensitive AI assistant content with the same kind of API keys. 3. Retroactively allow active API keys to access the sensitive content. 4. What could possibly be going wrong?! 🔥 Probably the worst vulnerability Google has ever deployed to prod: https://trufflesecurity.com/blog/google-api-keys-werent-secrets-but-then-gemini-changed-the-rules
-
Post #574717
Schei?encoding fährt heute mit im Bus 420 (Die Ort heißen Völs und Kühtai) #oeffitour