Andrew Jeffery

@whitequark@social.treehouse.systems @ConstellationUnion@infosec.exchange @agowa338@chaos.social I collected a Glasgow just this week, so I'll poke around 🙂

@manawyrm@chaos.social @whitequark@social.treehouse.systems @ConstellationUnion@infosec.exchange @agowa338@chaos.social superio driver is here: https://github.com/amboar/culvert/blob/main/src/sio.c

@whitequark@social.treehouse.systems @manawyrm@chaos.social @ConstellationUnion@infosec.exchange @agowa338@chaos.social the block diagram in the board manual suggests so

@whitequark@social.treehouse.systems @ConstellationUnion@infosec.exchange @agowa338@chaos.social depending on your interests, with enough of an LPC requester you can access the BMC's AHB to poke around. That can get you a BMC console with a few more silly tricks, but I don't expect the setup would interact nicely with bringing up the host processors

@whitequark@social.treehouse.systems @ConstellationUnion@infosec.exchange @agowa338@chaos.social the board manual suggests CPU1 has LPC wired to the BMC, and that there's a TPM 1.2 header that you might be able to probe for accesses there. The host SPI flash can be mapped for LPC FW cycles by the BMC, so the LPC cycles may be of interest

@simontatham I've ended up putting together a shell script that maintains markdown checklists and records executions and artefacts in a git repo. It allows me to hone messy processes over time to the point where they can largely be automated, while still documenting the necessary steps where reliable automation hasn't yet been achieved. It gives me a lot of comfort https://github.com/amboar/checklists

@manawyrm@chaos.social @whitequark@social.treehouse.systems @ConstellationUnion@infosec.exchange @agowa338@chaos.social yeah, this bit: https://github.com/amboar/culvert/blob/main/src/bridge/ilpc.c

@me@jaehanley.social maybe they made a logic error

@anon_opin@mastodon.social ircv3 is actually pretty compelling