**** BEGIN LOGGING AT Wed Feb 10 03:04:52 2021
Feb 10 04:22:23 <perdent> SO04:08:45) perdent: https://gofile.io/d/bIRURTHey ! https://gofile.io/d/bIRURT So I  managed to dump this flash memory and extract the  embedded software running on it, and tap its input channel with a  trigger-based capturing device in order to monitor passcode input. How would I retrieve it's secrets though? 
Feb 10 04:22:23 <perdent> (04:08:57) perdent: https://sigrok.org/wiki/File_format:Saleae
Feb 10 04:22:23 <perdent> (04:13:35) perdent: So what is the program doing?
Feb 10 04:25:22 <smurray> perdent: this channel is mostly discussion about the OpenEmbedded build system, suspect no one here can really help you with reverse engineering stuff
Feb 10 04:25:49 <perdent> This is more electronics RE
Feb 10 04:32:59 <smurray> perdent: you'll likely have better luck on #sigrock or ##re
Feb 10 04:57:43 <perdent> I tried sigrok
Feb 10 04:57:45 <perdent> no reply
Feb 10 04:57:56 <perdent> and re
Feb 10 15:15:52 <Crofton|cloud> anyone recall what release branch supports building with python3?
Feb 10 15:25:49 <moto-timo> Crofton|cloud pyro (2.3) is when bitbake changed to python3 http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/bin/bitbake?h=pyro
Feb 10 15:26:08 <Crofton|cloud> hmmm
Feb 10 15:26:51 <Crofton|cloud> I have some stuff based on sump (I think) 
Feb 10 15:26:55 <Crofton|cloud> https://www.irccloud.com/pastebin/WPh7W6xo/
Feb 10 15:26:55 <moto-timo> whoops, morty 2.2
Feb 10 15:27:19 <Crofton|cloud> feels like bitbake might be ok, but some meta-data is angry still
Feb 10 15:32:48 <moto-timo> rocko required python 3.4 http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/sanity.bbclass?h=rocko#n705
Feb 10 15:33:07 <moto-timo> so by sumo it was definitely python3
Feb 10 15:33:19 <moto-timo> I wonder where your pastebin came from...
Feb 10 15:41:30 <Crofton|cloud> hmm
Feb 10 15:46:18 <Crofton|cloud> this is a mystery
Feb 10 15:48:08 <Crofton|cloud> poky/scripts/oe-buildenv-internal:    echo >&2 "OpenEmbedded requires 'python' to be python v2 (>= 2.7.3), not python v3."
Feb 10 15:52:48 <Crofton|cloud> well commenting out the check failed miserably
Feb 10 15:53:43 <moto-timo> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/oe-buildenv-internal?h=rocko#n64
Feb 10 15:53:59 <moto-timo> so even on rocko it was doing a py34 check
Feb 10 15:54:14 <moto-timo> but it needs it to be "python3"
Feb 10 15:54:36 <moto-timo> does the host have an alias from python -> python3 ? what distro and version?
Feb 10 15:55:05 <Crofton|cloud> Fedora 33, no python2
Feb 10 15:55:49 <Crofton|cloud> hmm available though
Feb 10 15:56:19 <Crofton|cloud> I wonder if anything that uses python3 will use /usr/bin/python?
Feb 10 17:02:20 <smurray> Crofton|cloud: that's one of those "it depends" things, only a few distros did python as python3.  It's better to not assume it IMO
Feb 10 17:33:19 <Crofton|cloud> well F33 sets it to python3
Feb 10 17:33:28 <Crofton|cloud> a pox on people shipping ancient crap
Feb 10 17:33:38 <Crofton|cloud> all manner of weird things
Feb 10 17:40:00 <smurray> Crofton|cloud: for rocko, I'd just build in a container with older Debian, probably
Feb 10 17:40:14 <Crofton|cloud> yeah
Feb 10 17:40:21 <Crofton|cloud> I've kind of gotten there
Feb 10 17:40:35 <marex> smurray: you can even use systemd-nspawn as a better chroot for building
Feb 10 17:40:46 <marex> Crofton|cloud: xilinx ?
Feb 10 17:40:53 <smurray> marex: I use schroot most of the time, similar ease of use
Feb 10 17:41:21 <Crofton|cloud> xilinx part are involved, but this isn't their fault
Feb 10 23:40:32 <RP> )
**** ENDING LOGGING AT Thu Feb 11 02:59:56 2021