I'll take the moment to speak like a pyromaniac (electromaniac?) and say that the safety and durability issues just maen it's easier to visualize this being weaponized.
Since I've got my setup to show 50 results per page, I do get tired of searching after three pages.
Is that a self-regulating thing? Power serachers will get a lot of search results per page and go through three pages. Less discriminating people doing a search will be satisfied with Google's default of 10 results per page and go through three pages too.
So, what is the number of search results people stop at? Is it all over the map depending on how many results per page people have, or is it 30?
The easiest thing would be to have a separate power bus for the devices.
Have a klaxon wired to each so that you'd know if it's powered up and also have a communications bus wired in too.
Power up the bus briefly, hear klaxons going off, send unlock commands to specific locks... erm "fasteners", power off the bus.
Any attack to open the fasteners would set off the alarms. Another way to attack would be to tap into the power and set off the klaxons and start to annoy people until they start to ignore it. But the simple way around that would be to short both sides of the power bus. While you're at it, short the communications lines too. That will help prevent something like an ESD event/attack from destroying the fasteners.
The next piece of vandalism would be to tap into the bus and short everything to prevent use of the fasteners, but tif it were a daisy chain, it would be a simple binary search at other tap/break points to track down the short.
Maybe it would be easy enough to just have a lower impedance route to ground when shorting the wires together, that way you can have a constant wiring integrity test running....
Erm, other attacks- split the bus and ESD the downstream wires to destroy the fastener's microcontroller.
A separate power bus with RFID might be the solution- the power bus would only be for actuating the fasteners, but the RFID is still needed to get the fasteners started. The RFID might be hacked, but unless there's power on the bus, how would you know if you've hit on the right code? Power up bus, hear klaxon, test unlock code, power down bus?
Yeah, adding a wiring bus is a pain and pretty expensive, but for things like airline seats and airbags, there's already a wiring harness there.
But I'd personally want a backup method of unfastening them anyway....
It's not their computer, but by lobbying in congress they can attempt to mandate what hardware must be sold integrated with the computer (V-chip on TVs, macrovision on VCRs, etc.).
Look for an increased push for legislation requiring any computer sold to have built in broadcast flag- and now DRM- support. Actually, expect to see such broad language that it will require support in any kind of digital or analog transmission, conversion or storage device or component.
Slashdot Mirror
I'll take the moment to speak like a pyromaniac (electromaniac?) and say that the safety and durability issues just maen it's easier to visualize this being weaponized.
Since I've got my setup to show 50 results per page, I do get tired of searching after three pages.
Is that a self-regulating thing? Power serachers will get a lot of search results per page and go through three pages. Less discriminating people doing a search will be satisfied with Google's default of 10 results per page and go through three pages too.
So, what is the number of search results people stop at? Is it all over the map depending on how many results per page people have, or is it 30?
The easiest thing would be to have a separate power bus for the devices.
Have a klaxon wired to each so that you'd know if it's powered up and also have a communications bus wired in too.
Power up the bus briefly, hear klaxons going off, send unlock commands to specific locks... erm "fasteners", power off the bus.
Any attack to open the fasteners would set off the alarms. Another way to attack would be to tap into the power and set off the klaxons and start to annoy people until they start to ignore it. But the simple way around that would be to short both sides of the power bus. While you're at it, short the communications lines too. That will help prevent something like an ESD event/attack from destroying the fasteners.
The next piece of vandalism would be to tap into the bus and short everything to prevent use of the fasteners, but tif it were a daisy chain, it would be a simple binary search at other tap/break points to track down the short.
Maybe it would be easy enough to just have a lower impedance route to ground when shorting the wires together, that way you can have a constant wiring integrity test running....
Erm, other attacks- split the bus and ESD the downstream wires to destroy the fastener's microcontroller.
A separate power bus with RFID might be the solution- the power bus would only be for actuating the fasteners, but the RFID is still needed to get the fasteners started. The RFID might be hacked, but unless there's power on the bus, how would you know if you've hit on the right code? Power up bus, hear klaxon, test unlock code, power down bus?
Yeah, adding a wiring bus is a pain and pretty expensive, but for things like airline seats and airbags, there's already a wiring harness there.
But I'd personally want a backup method of unfastening them anyway....
This is late, but let me push the Right to Repair movement.
Also, I can't find the company (Yi Tien Electronics) on the web.
It's not their computer, but by lobbying in congress they can attempt to mandate what hardware must be sold integrated with the computer (V-chip on TVs, macrovision on VCRs, etc.).
Look for an increased push for legislation requiring any computer sold to have built in broadcast flag- and now DRM- support. Actually, expect to see such broad language that it will require support in any kind of digital or analog transmission, conversion or storage device or component.