Anyone remember this Bloomberg article?US lawmakers are meanwhile considering a Chip Security Act that would require exported chips to be built with "location verification." The bill also calls for an assessment of mechanisms to stop unauthorized use—a proposal that critics say could lead to a "kill switch" like the kind that Nvidia wants to prevent.
https://aws.amazon.com/blogs/securi...on-bloomberg-businessweeks-erroneous-article/
I would imagine the hardware would be designed in such a way that, if it encounters e.g. very specific bytestrings during operation, performance degrades (most likely some very minor memory corruption to keep it subtle; the main goal is to prevent models from training correctly, and a model that seemingly refuses to get better and wastes a year of a team's resources trying to figure out the issue is more effective sabotage than suddenly giving everyone bricks).How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
It would probably be in conjunction with "location verification" where the chip won't operate without signed authorization from the verification server. If it can't contact that server or doesn't get reverification in N hours (or days or weeks), it won't run.How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
Technical challenge to be sure, but not something impossible to achieve. Anyone remember what stuxnet and flame were able to do?How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
Cisco has an extremely complicated procedure for setting the operating region on the first universal wireless access point on a wireless LAN controller. It relies on GPS. Of course, if you're a nation state-sized actor with access to a GPS simulator, you can still set the operating region to any region.
I'd think you could do the same for just about any scheme that attempts to activate/deactivate data center hardware based on physical location as determined from a GNSS.
Edit: assuming you're unwilling to share the P(Y) code keys with a foreign adversary.
He writes using a connected device manufactured in China.Don't buy connected devices manufactured in China. Just don't.
It would probably be in conjunction with "location verification" where the chip won't operate without signed authorization from the verification server. If it can't contact that server or doesn't get reverification in N hours (or days or weeks), it won't run.
https://www.iaps.ai/research/location-verification-for-ai-chips
Hey ... remeber that time when Apple got dragged into a court case that had nothing to do with Apple and the Feds attempted to force Apple to create a backdoor to iOS after a shooting/attempted bombing all because the perpetrator had an iPhone during the situation? Apple then refused due to the same arguments NVidia is now making;Reber Jr. brought up an example from the Clinton administration: The National Security Agency's Clipper Chip initiative, which was abandoned.
They could require active software checkins by the drivers. If the driver can't communicate with NVidia to get a signed authorization key for continued usage, which it then uploads into the hardware, that hardware will shut down.How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
Any time someone says "It would be easy to do this," in a computer security context, you can virtually guarantee they haven't discussed countermeasures with a security consultant.This seems like the way. It doesn't even seem particularly complicated; its just that Nvidia doesn't want to do it, because they like money. Everything else is just smoke and mirrors.
How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
There are multiple potential ways to avoid the driver check-in problem, ranging from generating false approval to using test drivers that don't require the same check, to DLL hacking to disable the check, to DLL hacking that allows non-Chinese drivers to be installed on Chinese products. Don't forget that in order to enforce this sort of thing, Nvidia either has to distribute that driver globally to every user or force Chinese people to download China-specific drivers.They could require active software checkins by the drivers. If the driver can't communicate with NVidia to get a signed authorization key for continued usage, which it then uploads into the hardware, that hardware will shut down.
They could build GPS into the chips, and the location could be part of the signing request. If there's no location, there's no signature.
GPS might be spoofable, but that would not be easy.
On a serious note, how do you all think about your chain of trust? Did you have any recommendations for a securely produced and provisioned TPM that I should consider purchasing? Thanks.He writes using a connected device manufactured in China.
The Cyberspace Administration of China last week said it held a meeting with Nvidia over "serious security issues" in the company's chips and claimed that US AI experts "revealed that Nvidia's computing chips have location tracking and can remotely shut down the technology."
I kinda wonder if the CAC are actually performing entrapment here.Nvidia denied China's accusation last week, telling media outlets that it "does not have 'backdoors' in our chips that would give anyone a remote way to access or control them." The new blog post expanded on the company's denial and argued that governments should not demand backdoors.
You put the GPS into an appliance in the data center rather than in the individual GPUs and use an encrypted / authenticated version of ping / ntp to ensure the appliance is in physical proximity to the GPUs. That appliance is the only device that needs to be connected back to Nvidia HQ.They could require active software checkins by the drivers. If the driver can't communicate with NVidia to get a signed authorization key for continued usage, which it then uploads into the hardware, that hardware will shut down.
They could build GPS into the chips, and the location could be part of the signing request. If there's no location, there's no signature.
GPS might be spoofable, but that would not be easy.
How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
There would need to be some way to require an always on connection that needs to get a signed ping back in >x ms. I'm not sure that's doable in a way that can't be circumvented.How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
Honestly this sounds like a Tuesday for a well funded intelligence agency.How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.
Please please please ! Someone, anyone, give Trump an AI kill switch to play with ASAP !Can you imagine Trump with an AI kill switch? He'd be flicking it on and off every other week just to piss people off.
I don't think anything you said above is wrong, but I think it's relevant to draw a distinction between what nation-states are willing to do if they consider an advantage critical to national security versus what the consumer or commercial markets create in terms of hacks and workarounds.I'm not sure how you'd do it secretly; but the usual mechanism is for the system to demand some kind of license activation and fail closed if it doesn't like the result. That's basically how they handle vGPU features.
Given that the newer cards are all 'hardware root of trust' and have their own onboard processing and firmware it would be viable in principle to move the license verification out of relatively easily tampered drivers and onto the card itself. The main limitation would be what the end user would put up with: Nvidia strongly encourages you to set up a 'cloud' licensing instance with them; but defers to necessity by offering locally hostable images and node-locked license files; which obviously limits the ability to kill something quickly.
You could probably also use the console game/blu-ray trick where updates are forced on offline/uncooperative devices by baking them into new releases, by adding a validation step and kill lists to new CUDA releases; though that would only hit people who actually need to update for some reason.
Tom Cotton is a cynical carnival barker who doesn't care if it's possible so long as it's possible to advance a bill whose name has been tortured into a twee acronym about it; but when you've got cryptographic bootloader lockdown what you can do is mostly limited by your willingness to upset the customer; so it's not totally science fiction.
To be even more specific - it's been proven to be false, yet Bloomberg has never recanted their story. And the damage done is shown by the OP going back to the poisoned well.https://aws.amazon.com/blogs/securi...on-bloomberg-businessweeks-erroneous-article/
"Today, Bloomberg BusinessWeek published a story claiming that AWS was aware of modified hardware or malicious chips in SuperMicro motherboards in Elemental Media’s hardware at the time Amazon acquired Elemental in 2015, and that Amazon was aware of modified hardware or chips in AWS’s China Region.
As we shared with Bloomberg BusinessWeek multiple times over the last couple months, this is untrue. At no time, past or present, have we ever found any issues relating to modified hardware or malicious chips in SuperMicro motherboards in any Elemental or Amazon systems. Nor have we engaged in an investigation with the government."
IOW, total bullshit.
I'm confused: in which jurisdiction does one sue the Chinese Communist Party? Space Court? Dreamland? The UN?I still think the easiest way to shut down the CCP whining and begging is to offer to take back all of the chips. See if they balk, then sue for making false claims against a private company.
You forget that the average Tech IQ of the average politician doesn't get above "imbecile". SLIGHTLY brighter than an idiot, but not as mentally adept as a moron.How would you even operate such a "kill switch"? GPUs are not directly connected to the internet, but rather sit in datacenters, on internal-only networks, running the client's software. How would a kill command make it from the US, through the Great Firewall, the client company's application firewall, hop to an air-gapped server cluster, be correctly received and executed by the client company's in-house software, AND THEN be passed on to the GPU? Same question for the location tracking.