@ABasilPlant@lemmy.world

ABasilPlant

@[email protected]

InfoSec Person | Alt-Account#2

This profile is from a federated server and may be incomplete. Browse more on the original instance.

ABasilPlant,

Huge +1 for BobbyBroccoli. Most entertaining & gripping documentaries I’ve watched in a long time. The two part Cloning documentary (Part 1, Part 2) was absolutely spectacular.

Lemmino is great as well.

ABasilPlant,

You’re right, that’s exactly what happened. If you look at the top of the trace, it says __handle_sysrq. Moreover, it’s in the sysrq_handle_crash. That gets called when a sysrq combo is pressed.

How exactly "secure" is a container with all capabilities dropped, distroless, with a custom rootfs directory, a static, single binary with chmod set at 100 and file ownership pointed to non-root u...

ser*, and said non-root user being “nonexistant” (i.e set via ENV)? Can such container -STILL- be exploited/breached through malicious means? Forgot to mention that its a DOCKER container @ title, but there you have it. Just curious....

ABasilPlant,

Absolutely. Check out side channel attacks. The problem here isn’t about software exploits, but hardware issues. en.wikipedia.org/wiki/Side-channel_attack

Some things to get you started: Meltdown and Spectre: en.wikipedia.org/…/Meltdown_(security_vulnerabili…, en.wikipedia.org/…/Spectre_(security_vulnerabilit…

Rowhammer: en.wikipedia.org/wiki/Row_hammer

These are exploited by malicious processes doing something to the hardware which may result in information about your process(es) being leaked. Now, if this is on your computer, then the chances of encountering a malicious process that exploits this hardware bug would be low.

However, when you move this scenario to the cloud, things become more possible. Your vm/container is being scheduled on CPUs that may/may not be shared by other containers. All it would take is for a malicious guest VM to be scheduled on the same core/CPU as you and try exploiting the same hardware you’re sharing.

ABasilPlant,

I’ve been using Hugo since 2017. I recommend it wholeheartedly.

ABasilPlant,

This is such a cool photo - I’m going to use it as my laptop wallpaper (if that’s okay 🤞)!

ABasilPlant,

Hands down, one of the best tools I’ve used in a very long time:

github.com/PJ-Singh-001/Cubic

Download a Debian 12 standard live ISO (or with GNOME or any other iso) and you’re good to go. I’ve compiled custom kernels with it too. If you want persistence, then you use mkusb.

ABasilPlant,

Use the live version (thd try without installing option). You can also remove the installer code if you really want to - I think Ubuntu uses ubiquity/subiquity.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • KamenRider
  • TheResearchGuardian
  • KbinCafe
  • Socialism
  • oklahoma
  • SuperSentai
  • feritale
  • All magazines