Security is hard to get right and simple(r) to get wrong....

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

Lob

What could possibly go wrong?
Nov 7, 2020
161
44
sushi.jpg

It all begins with a sushi restaurant that leverages iPads in Guided Access Mode (GAM) for food ordering. The basic idea is to tap, order and then stroke the robot when it delivers the food. What could possibly go wrong, you might ask......

Mistake 1: The waitress tells you the iPad unlock code because, of course, they go to sleep.
Mistake 2: The unlock code is also the code to get out of GAM

Place a teenager at the scene and of course the teen gets the iPad out of GAM and starts taking selfies with a view to replacing the background. Funny - but too much chance of being caught....so said teen AirDrops a fun image to the iPad and replaces the background.

It doesn't end there because the iPads are on a wireless network - one that is not the network being offered to customers.

So...............how can you get another device to join the network? The teen was not sure but a more experienced person was; Apple makes it wonderfully easy to share Wifi passwords! (Caveat: the password can apparently only be shared from a device into which the password was typed, actually good thinking from Apple).

And so there's a new iPhone on the network. Running Fing. Discovery is a wonderful thing......

The barrier to entry in the network is not significant - and on that network you will now find things such as: Sonos speakers for the restaurant and office, the sushi delivery robot (all interesting for the Rickrolling teen) and (for a real attacker) all of the PoS devices plus the office computers.

It's a real shame that the barrier to self-entry and setup for these things is so low because it really could end in tears.

robot_s.jpg
and of course the food delivery robot has a web interface. Do you think the default username/password have been changed?

I am sure they are not alone. The question is whether they need to be told about this and how it can be done.....or if I would want to be the one.
 
Pity that they cannot even be secure when they take the waiter's / waitress' job away and put our credit cards at risk. If you tell them, they'd probably sue you. When systems are sold for a given purpose, like POS, they should be secure by default. When someone who's not an expert integrates a bunch of pieces and parts to do something, it get's a lot harder to cover all the security bases, even if they're concerned enough to try.

May your bits be stable and your interfaces be fast. :cool: Ron