01:25 <jjjaaaccckkk> fanyone have Mathias Lasser's full slide deck from his presentation at 34C3 about reverse engineering the xilinx series 7?

02:18 <az0re> jjjaaaccckkk: https://media.ccc.de/v/34c3-9237-reverse_engineering_fpgas doesn't work for you?

02:18 <tpb> Title: media.ccc.de - Reverse engineering FPGAs (at media.ccc.de)

02:20 <az0re> Ah, just saw your message in #yosys... sorry, can't help

02:27 <jjjaaaccckkk> no worries, yeah I was hoping someone has all the slides from his presentation. In the video he seemed glad to share them with whoever was interested

02:29 <jjjaaaccckkk> Or anyone know Mathias and can ask if he is open to sharing them?

15:43 <ZirconiumX> bunnie[m]: the Intel bitstream is even stranger

15:57 <bunnie[m]> yow.

19:14 <mithro> jjjaaaccckkk: I attended and he didn't have any slides and pretty much no real details

21:05 <jjjaaaccckkk> Thanks, mithro

21:17 <mithro> It is in no way connected to prjxray

21:27 <jjjaaaccckkk> Yep I knew that

21:28 <az0re> What is the difference between prjxray and his work?

21:35 <mithro> az0re: his work doesn't exist as far as I can tell, prjxray is mostly just missing DSP + Serdes

21:44 <az0re> Gotcha, thanks

21:47 <mithro> prjxray is at https://github.com/SymbiFlow/prjxray and prjxray.rtfd.io

21:47 <tpb> Title: GitHub - SymbiFlow/prjxray: Documenting the Xilinx 7-series bit-stream format. (at github.com)

22:24 <jjjaaaccckkk> I am curious, though, do you understand the technique Mathias talked about? It sounds like he was implementing Vivado example projects and reading each pixel in the device view image to see what bits were set?

22:26 <az0re> mithro: Cool work. Thanks for doing it!

22:26 <az0re> I haven't really dug into it yet, but my impression is that the process is roughly like:

22:26 <az0re> 1. Read documentation, get an idea of what resources exist on the FPGA family

22:27 <mithro> jjjaaaccckkk: You generate a lot of bitstreams and then look for cross correlation between bits and features

22:27 <mithro> jjjaaaccckkk: There is some info in the docs above

22:27 <az0re> 2. Write fuzzer generator scripts to instantiate those IP features in uniquely identifiable ways

22:27 <az0re> 3. Do the full design flow in the Xilinx tools, observe changes in the bitstream

22:28 <az0re> 4. Correlate unique identifiers (or uniquely identifying behaviors?) with bits in the bitstream

22:28 <az0re> Is that about right?

23:16 <_whitenotifier-5> [sphinx_materialdesign_theme] mithro opened issue #1: script_files in the theme is deprecated - https://git.io/JvfbR

23:42 <mithro> az0re: pretty much