Live data from Hacker News

Compromising OpenWrt Supply Chain

flatt.tech

11–20 of 105 posts

Re: Compromising OpenWrt Supply Chain

#11
First of all, nice writeup. I am a bit surprised that so much GPU power was needed to find such short collision but it was nice to see his implementation nevertheless.

Regarding the last section, is 40k a reasonable price for one month of security analysis? Does this mean that a good security researcher make about 500k/yr?

Re: Compromising OpenWrt Supply Chain

#12
post #4

That's why open source can never compete with business grade closed source stuff: - they fixed the in 3 hours instead of making customers wait 6 months for a patch (if any) - they did not try to sue the reporter of the issue - they did not even tell the users to throw away the "outdated" but perfectly working devices, offering a small discount to buy new

Just why I love OpenWrt. They even ask the people that use screen readers like me to test the web interface to make sure that all is working as it should.

Re: Compromising OpenWrt Supply Chain

#13
post #11

First of all, nice writeup. I am a bit surprised that so much GPU power was needed to find such short collision but it was nice to see his implementation nevertheless. Regarding the last section, is 40k a reasonable price for one month of security analysis? Does this mean that a good security researcher make about 500k/yr?

It means a good security research company might make $500k for a good researcher, if they could bring in enough work to keep them 100% utilised. Less actually, given paid time off.

Re: Compromising OpenWrt Supply Chain

#15
post #11

First of all, nice writeup. I am a bit surprised that so much GPU power was needed to find such short collision but it was nice to see his implementation nevertheless. Regarding the last section, is 40k a reasonable price for one month of security analysis? Does this mean that a good security researcher make about 500k/yr?

2^(12*4) is 281,474,976,710,656 possible 12 character strings so seriously impressive that it can look through that many in an hour.

Re: Compromising OpenWrt Supply Chain

#17
post #8

Loving this. I wonder how people even come up with an idea of truncating hashes. For what purpose or benefit?

Truncated hash functions are not vulnerable to length-extension attacks. But you usually take SHA512 and truncate to 256 bits. Anything shorter than this isn't really considered safe these days.

Re: Compromising OpenWrt Supply Chain

#18
post #16
post #8

Loving this. I wonder how people even come up with an idea of truncating hashes. For what purpose or benefit?

when you upgrade from sha1 to sha256 but you don't want to change your data format for storing the integrity checks / keys.

A SHA-1 is not 12 characters (either in digest bytes or hex nibbles)

Re: Compromising OpenWrt Supply Chain

#19
First - open source tool adjusted to the task it wasn’t made for in short time, only because it is open source and written without BuilderFactoryProvider. (already mentioned so I’m sorry, but it’s killing me every day) Big company would take probably -1 years to fix this, because it would just sue the guy, try to arrest him ASAP and never release patch. OpenWrt after getting information just took the insecure service offline, checked the report (while clients were already safe, because of the shutdown), made patch and released in 3 hours. Wow!

Re: Compromising OpenWrt Supply Chain

#20
post #11

First of all, nice writeup. I am a bit surprised that so much GPU power was needed to find such short collision but it was nice to see his implementation nevertheless. Regarding the last section, is 40k a reasonable price for one month of security analysis? Does this mean that a good security researcher make about 500k/yr?

That seems very reasonable to me. It seems like the pentest companies I have worked with in the past charge that much and just do a lazy nmap/metasploit scan and wrap it into a nice PDF.
Post reply on HN