4 ms·
It's a standard rock vs hard place situation. But 1) why should nVidia trust the attackers? nVdia might give in, and the files might still be leaked. The a
by hyperman1 5y ago
It's a standard rock vs hard place situation. But
1) why should nVidia trust the attackers? nVdia might give in, and the files might still be leaked. The attackers should be able to guarantee they won't release the files AND nobody steals the files from them. Hard sell for the attackers, especially with a kid profile .
2) These files are legally toxic. You can't look at them and then publicly act on their content. So anything a third party can do has to happen at arm's length, parallel construction style. This also goes for open source devs, who can't permit nouveau gettibg kicked out of the legal repositories.
3)It is well possible the leak is not as damaging as it looks. People in the industry swap jobs all the time, and take knowledge with them. People accidentally do small leaks all the time, being sloppy with data entrusted to them. It seems reasonable for other big organizations to already have some level of knowledge of the content.
On the other side of the coin is the fully legal loss of control of their software. They also open themselves up to future ransomers ('Danegeld').
I'm not saying high level people at nVidia aren't swearing loudly right now, but a 'let the chips fall as they may' response seems most likely to me, especially combined with a 'we'll very publicly sue the attackers in the ground, as an example for all wannabes' response.
- Handytinge 5y ago> These files are legally toxic. You can't look at them and then publicly act on their content I keep reading this, but is this just a US issue? I assume people in other countries can look and clone these? Given close to half the worlds population live in India and China, and the US make up < 5% of the worlds population, this doesn't seem like a big concern.
- feanaro 5y ago> 1) why should nVidia trust the attackers? nVdia might give in, and the files might still be leaked. They might, but they will surely be released if they choose to ignore the attackers. Given the choices between a bad outcome happening potentially and surely, which one would you choose? > 3)It is well possible the leak is not as damaging as it looks. People in the industry swap jobs all the time, and take knowledge with them. People accidentally do small leaks all the time, being sloppy with data entrusted to them. It seems reasonable for other big organizations to already have some level of knowledge of the content. I still fail to see the logic. Assuming the attackers are honest, the choice is between: a) drivers public b) everything (which includes drivers) public Option a) garners significant sympathy. What is the incentive to choose b)? > They also open themselves up to future ransomers ('Danegeld'). This is the only argument that makes a bit of sense to me. > especially combined with a 'we'll very publicly sue the attackers in the ground, as an example for all wannabes' response. That can only happen if they are caught.