Everything Open 2024 Quick Notes :: Day 2 and 3

Everything Open 2024 Quick Notes :: Day 2 and 3

April 20, 2024
Talks, EverythingOpen, rxlog

I didn’t take as much notes on day 2 and 3, so I merged them into a single article.

Wednesday, 17 Apr 2024 #

Keynote: How Adversaries Use AI #

  • Adversaries:

    • Nation States
    • Ecrime
    • Hactivism
      • Not always clearly separated

  • LLM can help eliminate common language mistakes, perform better social enginerring

  • Many adversaries are trying to integrate LLMs into their workflow, with varying results

  • Time frame from initial foothold to lateral movements is getting shorter, due to better toolings?

GoLang #

  • IDE setup / difference with C and other common language
  • Compile down to single binary for many arch/platforms

Rootless networking: From possible to practical #

  • libslirp is too slow
  • passt & pasta
    • much faster than libslirp
    • same binary, different command
    • translate between layer 2 network interface and native layer 4 sockets on a host
    • unprivileged, no capability needed, good fit for container & VM
    • https://passt.top/passt/about/

Running a Particle Accelerator on Open Source #

Thursday, 18 Apr 2024 #

Keynote: Intelligent Interfaces: Challenges and Opportunities #

  • Another great talk, we don’t get HID talk often unfortunately
  • Sensing: what can we sense more?
    • Eye tracking: figure out when the user is not paying attention and then when the user look back, show a diff/changelog
    • Change Blindness, proximity-based experience: change how detailed the UI is based on proximity
    • RadarCat, Radar and Categorization: better privacy than having camera everywhere
      • obtain infomation via wave reflection and absorption (can this be abused…?)
      • use ML trainning for better accuracy
    • MicroCam and SpeCam: placement based action: detect which surface is under/over the device

FOSS: From Building Websites to Changing Society #

  • Echo chamber: FOSS run on different social/economic structure than commercial proprietary software, it takes effort to convince people

Adventures in fuzzing the kernel on Power #

  • porting syzcaller to run on Power

  • general fuzzinng engines

    • universal eginee: AFL++
    • domain specific fuzzer: syzkaller

  • Unsupervised: no human input required

  • Coveraged-guided: fuzz and measures which codepath is fuzzed

  • Things to fuzz: syscalls/dxrivers/fs/ebpf/kvm/network stacks…

    • KVM: guest-host / host-guest

  • Simple kernel fuzzers existed est. 1991

    • but not coverage based

  • Hosted version on Google Cloud: https://syzkaller.appspot.com/upstream

  • Sanitisers: print errors on memory corruption/UB/concurrency problems etc

  • KMSAN isn’t on Power yet

  • Hardware:

  • New architecture enablement

    • Parse arch-specific details of kernel error
    • Enable kcov (but not everywhere)

  • Stack traces are printed differently across archs

    • use regex, 2.5KLoC ;)

  • instruction fuzzing

    • generate and mutate PPC64 PowerISA machine code
    • More coverage for KVM related pathways
    • Only for x86 and power at the moment

  • QEMU/KVM on bare metal Open Power systems

  • Bug found:

    • KVM guests can crash/hang the host, race conditions?
    • Bugs in KUAP

  • PowerVM

    • Type 1 hypervisor
    • Runs Linux/AIX/IBM I VMs
    • Need a separate machine as management console

  • PowerVC

Lightning Talks #