oh my god i patched the binary to disable the CRC check in transformer mode and it's *different* and *even better*
(here i just XOR a random hunk of the file with 0xAA)
I was doing some micro-benchmarking at the time, needed to quiesce the system to reduce noise. Saw sshd processes were using a surprising amount of CPU, despite immediately failing because of wrong usernames etc. Profiled sshd, showing lots of cpu time in liblzma, with perf unable to attribute it to a symbol. Got suspicious. Recalled that I had seen an odd valgrind complaint in automated testing of postgres, a few weeks earlier, after package updates.
Really required a lot of coincidences.
Marc Stevens came up with a new kind of MD5 collisions:
alphanum, no space, single byte difference (always +4), and not even 2 blocks!
No more high entropy collision blocks!
md5("TEXTCOLLBYfGiJUETHQ4hAcKSMd5zYpgqf1YRDhkmxHkhPWptrkoyz28wnI9V0aHeAuaKnak")
=
md5("TEXTCOLLBYfGiJUETHQ4hEcKSMd5zYpgqf1YRDhkmxHkhPWptrkoyz28wnI9V0aHeAuaKnak")
Use `echo -n` to test otherwise it outputs a newline char, which will get wrong results.
I'm currently in the process of designing an #ExpansionCard for my new #FrameworkLaptop.
I need the #Unifying #dongle (lower latency), but don't want it sticking out and losing a whole slot.
So I'm going to throw a USB hub and the peeled dongle on a PCB and hope it all works out :D
As a further experiment, I routed the USB A SS lines past the hub (USB 2 D+/D- connected to port 1 of the hub).
Not sure if this will play nice with USB drivers, but it's worth a try.