Why put ransomeware on a wrench?
For leverage
this post was submitted on 10 Jan 2024
191 points (96.6% liked)
Technology
60081 readers
3446 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
Pay us in 3 days or we'll disable it. This is not a drill.
Ba-dum tss!
LOL.
I think I am less concerned about the ransomware and more confused as to why there is a wrench that can connect to the internet. What use would that provide to the user that would improve it?
Quality assurance on production lines, so there is a record of what happened.
A few ideas off the top of my head
- asset tracking
- location awareness
- ability to send out mass specs to devices
- device assignment
- tracking working hours
I’m not saying all of these are good ideas, or that they couldn’t just have a centralized hub that just pushes and pulls this information. That said, the website for them does list that they also have a camera for scanning barcodes. I could see having barcodes linked with a certain torque spec and that requiring a network connection if the information wasn’t hard coded. website
The wrench is to tighten bolts to spec. You can program it to tighten different bolts to different tightness and that can be programmed online.
So, a torque wrench for someone too lazy to spin the handle to their required ft-lbs/in-lbs?
By that logic, isn't all efficiency really just laziness? When does it become productivity or quality control?
Eeehhh I prefer the OG style of torque wrenches myself, I don't even like the digital ones. They all eventually die but the digital ones seem to die quicker. It ain't efficient if it's broken. And to that effect, if it ain't broke, don't fix it, the clicky ones work fine. Bonus: they go clicky clicky.
I mean, for an automated assembly line sort of deal with not me involved? Hell yeah whatever, robots and shit. If I'm wrenching? Clicky clicky.
OH and yeah, clicky has no wifi, thus to ransom it you need to physically steal it and send me a letter with letters snipped from a magazine and tell me where the hollow tree in the park is to do the drop, whole different animal.
If you wan to put it into simple words… yeah.
That's the neat part, there isn't. There is, however, significant incentive to the tool's manufacturer. Who can, I'm sure, not only demand a subscription for continued use of the tools but also employ lucrative maintenance contracts and other sundry corporate nonsense. I can tell you from a brief stint in the industrial automation industry that the sale of the equipment is not the money maker; it's the ongoing service contract on it.
If these are meant to be used by hand I see no reason they can't just be configured on the tool itself and not need an internet connection. And if the point is plantwide automation, these sit directly in the bottom of the ugly trench between tasks that must be done by a human for whatever reason on one side, and just being done by a damn robot to begin with on the other.
And a further clarification: Even if there is a use case for a hand tool being networked, having it connected to the outside internet is just bonkers.
I see no reason they can’t just be configured on the tool itself and not need a network connection.
Say you've got a couple dozen of these wrenches and during retooling new specs come out. You can either pay a group of people to go around and upload all the new specs to the tool or push it from a central server to all the tools.
Boeing Boeing Boeing Boeing...
-
Hey Joe, is this set up for the correct specs for the plug doors?
-
Bert, don't ask such things, else we'll be here until night. Just fix those darn bolts with it, then let's go for a drink.
You can either pay a group of people
So, like, the guys who are holding the wrenches all day to begin with?
Even so, none of the examples anyone has come up with in this thread have required having the friggin' things connected to the internet. That's our beef here. Not necessarily networking capability.
In fact, back when I was in automation (in the dark ages of ~2008) it was already considered unthinkable not to air-gap all of your mission critical production equipment. A ton of that stuff was networked, sure (and you'd shit a brick if you saw how much of it is still interconnected with RS-485 serial...) but not exposed to the outside world in any capacity. Nor would anyone want it to be, for obvious not-getting-pwned reasons.
I am not a fan of making everything part of 'the internet of things'
Nearly all IoT items are developed for idiots, which is interesting because most of them are also made by idiots.
Iot wrenches are built for blue collar workers to ensure proper tooling of complex parts on production lines
And to then certify it's tightened to spec and send that cert to a logging server, for things like aviation
Why doesn't the wrench then only have the ability to talk to a local server and that server have internet then? If that were the case the wrench would have no reason to download anything from the Internet, just speak to the local server. Probably wont fix every vulnerability but it can't be more vulnerable.
Yup, that would be sensible security practices.
The wrench has a web UI to program it or monitor it. It also talks a few "standardised" car-manufacturer protocols for recieving and sending instructions/measurements/certifications. And it can send also send stuff to a local history server.
The majority of the CVEs seem to exist in its onboard webUI system, with a few in the manufacturing protocols.
But yes, IoT devices should be on an isolated vlan or on pvlans. That should be standard practice.
Access from wrench->server should be via a firewall that logs connections. And access from management->wrench should be via firewall with logging.
There is no reason for unauthorized people to have access to the wrenches network, and there is no need for the wrench to communicate with anything other than the local history server.
except in this case, where it looks like there are more than valid reasons
This feels like one of those things that'll go exactly opposite of what I expect. Ten years from now I'm be explaining to my grandkids how much harder live was before wrenches were Internet connected.
I can't imagine a single valid reason to have an Internet connected wrench. But life is weird, so I'm guessing I'll keep one synced to my fax machine someday.
Do we need this news posted 50 times over the course of a day?
Honestly is the first one I see with s picture showing the ransom request.