Hacker News new | past | comments | ask | show | jobs | submit | ibmthrowaway218's comments login

The new CEO will not tolerate new unethical behaviour.

Hopefully he will also slowly eradicate the existing unethical behaviour.


The new CEO will fix everything just like the last 3 GM CEO's changed their corporate culture and stopped them from making cars that kill teenagers...

... crap. My kids won't be buying a GM car.


The downvotes are likely because you're taking an Uber thread veering it off to GM's management and your children, neither of which have any relevance here.


Except for the CEO being changed and having a toxic corporate culture that didn't change and produced the same deadly car across CEO's after promising change but did nothing different--including not stopping production of a deadly vehicle.

I probably should have spoonfed the readers more. They grew up in a world that doesn't need critical thinking anymore so it's probably too much to ask for their brains to activate while reading on a website and have them put distinct ideas together to form a grander one.

Must. Downvote. Comments full of facts but from people I dislike. Must.... errooorrrrroooorrrrrr. 505.

It's okay. Every time I see downvotes here, I know I said something great but I just pissed someone in power off. I'm used to being a minority oppressed by a majority in power. It's no big deal. The system just builds people like that these days.


Still not making the connection from Uber to GM that you are trying to make. Because the GM CEO could not prevent teens across America from joyriding, the new CEO is going to be unable to reign in the behavior of his own supports?

Either make a valid point or let your comments stand. Leave the /r/iamverysmart tandems at the door


https://www.amazon.co.uk/Faster-Obsession-Science-Fastest-Cy... is an interesting read related to this.

(Cycling obviously, but the genetics behind VO2max apply across different types of physical activity.)


I think there's some obfuscation in the tests:-

As you say, the first few test numbers correspond just to simple divisor checks:-

Prime 3 paired with check number 6 (binary 110). So 1 << (n % 3) will only ever be 'safe' if n % 3 == 0, which is 'super bad' as you put it.

(2^3)-2 = 6

(2^5)-2 = 30 so this is a similar division check

(2^7)-2 = 126 ditto

I think these are just here as distractions as it starts to sometimes do different things at p=11

11 is paired with check number 1026, which is (2^10)+2 not (2^11)-2). So under what conditions does:-

( 1 << (n % 11) ) & 1026 != 0

Given 1026 only has two bits set (1024 and 2) it's a rather specific test for (n%11) = 1 or 10. All other residues would be safe.

Don't have time to investigate further for the other primes and check numbers but I can only think of some kind of p-1 or p+1 smoothness they can detect this way.


> Also, I'm having a bit of a hard time understanding the attack.

He forces them to connect to his own AP and forwards all traffic to the destination so that the client is unaware it has been redirected.

He then forces the client to re-install the key which (on anything that is derived from wpa_supplicant e.g. Linux, Android, etc) the client has blanked out after first use, so the key it reinstalls is now all zero bytes.

He can continue to forward the traffic to the destination so that the client gets responses, but now he can decrypt all of the traffic too.

For clients that re-install the correct key (which the account does not recover in any way) the attacker has to rely on snooping enough encrypted data in order to perform a birthday attack as the key re-installation also resets the frame counters which leads to nonce-reuse which is a problem in ciphers like AES-GCM.


> The client is forcibly disconnected from the WiFi network and reconnects to the attackers network instead.

The client is tricked into moving to what it thinks is the same WiFI network running on a different channel, but is actually the attackers network instead.

> The attacker doesn't need to know the WPA2 password but it accepts the connection setting the encryption to zeros.

The attacked doesn't need to know the WPA2 password and (for Android and Linux clients) the client then defaults to an encryption key of all zero bytes.

> The client thinks it is connected to the original wifi network and continues as normal.

Yes.

> Wifi traffic is intercepted and unencrypted.

Wifi traffic is intercepted and can be decrypted (since the encryption key - all zero bytes - is now known).


Just the traffic between the impacted client and the network, right? Because each client is using a different key (has to be, if we're able to reset just one client's key to all zeros)


Except the attack doesn't get you access to their wireless network. It allows you to redirect someone from their wireless network to your own (spoofed) wireless network and then you can snoop the traffic.


If it works in one way what reason is there to think it won't work the opposite direction? This flaw is in the protocol itself.


Both were influenced by _We_ by Yevgeny Zamyatin.


An incredible book if I may add. Zamyatin was one of few dystopian writers to actually be involved in the going-ons in the Russian revolution at the time.


Um, yes, that's exactly what this article is about.


It also hosted a Eastern European military camp in the MacGyver movie _The Lost Treasure Of Atlantis_

Lots more: https://en.wikipedia.org/wiki/Battersea_Power_Station_in_pop...


Depends, for a first time buying couple it's a 10% deposit (plus £45k for stamp duty) and then a combined salary of £225k (assuming 4x multiplier on combined income). Sure ~£110k/year is firmly in the top quartile of dev salaries, but not out of the question.

More than likely a couple who are already earning ~£70k/year each probably already have some equity in a current home, so a £1m home might not be much of a step up for them.


Thats like the 0.1% of people.


It seems like quite a stretch considering people tend to accumulate financial responsibilities over time (kids, aging parents, etc.).


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: