Skip to contentSkip to conversation

Mounting a in-ROM filesystem efficiently

DISCUSSION Richard B. Johnson 7 participants 8 messages Dec 17, 2001 – Dec 18, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 7 lines · Dominik Kubla
Quoted 5 lines · Richard B. Johnson

Well RAM is a hell of a lot cheaper than NVRAM. If you don't have the required RAM on your box, the hardware engineers screwed up and have to be "educated" preferably with an axe in the parking-lot.

Quoted 5 lines

What about security issues? I can imagine quite a few scenarios where you would want to insure that you run untampered binaries. (eg. use ROM instead of the usual CD-ROM or read-only FD to run your security critical application.)

I never even implied that you would run CD-ROM or FD in embedded applications. The stuff that runs comes-from ROM, actually NVRAM so in can be written/updated in production. However, EIP software (Execute In Place) has always been a dog and, even Ethernet switches 3COM, Cisco, etc., don't run that way. You need to get the stuff that runs into RAM.

Security isn't a problem with embedded systems because everything that could possibly be done is handled with a "monitor". There is no shell. If there is no way to execute some foreign executable, you don't have a security issue unless some dumb alleged software engineer added some back-doors to the monitor.

Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
Santa Claus is coming to town...
He knows if you've been sleeping,
He knows if you're awake;
He knows if you've been bad or good,
So he must be Attorney General Ashcroft.

#2 lore raw
Quoted 6 lines · Richard B. Johnson

Security isn't a problem with embedded systems because everything that could possibly be done is handled with a "monitor". There is no shell. If there is no way to execute some foreign executable, you don't have a security issue unless some dumb alleged software engineer added some back-doors to the monitor.

A hacker don't need a /bin/sh or any other onboard software to exploit some security flaw. Assume someone discover that your embedded box is vulnerable to a buffer overflow attack of the type usually used to get a root shell. Then they discover that running /bin/sh don't work. What to do? They simply put a simple little shell _in_ the buffer overflow code itself. A hacker don't need to call anything, all he need can be downloaded as part of the exploit code.

If the room for exploit code is thight - use a two-stage approach. The exploit then consists of code that download the rest of the code into some other RAM outside the tiny buffer.

No "dangerous" utilities on board doesn't mean the box is safe at all. The buffer overflow code could contain code for continuing the attack on other boxes, or anything else.

Helge Hafting

#3 lore raw
Quoted 22 lines · Helge Hafting
Quoted 6 lines · Richard B. Johnson

Security isn't a problem with embedded systems because everything that could possibly be done is handled with a "monitor". There is no shell. If there is no way to execute some foreign executable, you don't have a security issue unless some dumb alleged software engineer added some back-doors to the monitor.

A hacker don't need a /bin/sh or any other onboard software to exploit some security flaw. Assume someone discover that your embedded box is vulnerable to a buffer overflow attack of the type usually used to get a root shell. Then they discover that running /bin/sh don't work. What to do? They simply put a simple little shell _in_ the buffer overflow code itself. A hacker don't need to call anything, all he need can be downloaded as part of the exploit code.

If the room for exploit code is thight - use a two-stage approach. The exploit then consists of code that download the rest of the code into some other RAM outside the tiny buffer.

Quoted 5 lines

No "dangerous" utilities on board doesn't mean the box is safe at all. The buffer overflow code could contain code for continuing the attack on other boxes, or anything else.

Helge Hafting

You apparently don't know what an embedded system does. It is a device that uses a processor to perform some designed functions. It cannot do something that it was not designed to do although it can certainly fail to do what it was designed to do.

If you want to break it, it's easier to hit it with a hammer or an axe. There is not any capability to "break in". Even if there was, what could you do? Shut off a motor? Screw up the ignition timing? Put porn pictures into medical images?

Most embedded systems don't have network capabilities. Those that do are like your network printer. It's possible to send it junk. It's possible to send 20,000 form-feeds so it runs out of paper, but basically, you are just creating havoc with something you, or your company, owns.

There is no way that you can teach your Hewlett-Packard printer to become a network rogue and break into the Pentagon --regardless of what you send it.

Embedded systems that perform critical functions such as FMS (Flight Management Systems) have a reset button. If it's screwing up, and they often do, the pilot not flying says some four-letter prayers to be picked up by the cockpit microphone, hits the reset switch, waits for it to re-boot, and enters everything from scratch again --usually the entire day's flight-plan routes, taking nearly 1,000 key-strokes. Now, that's an embedded system.

Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (797.90 BogoMips).
Santa Claus is coming to town...
He knows if you've been sleeping,
He knows if you're awake;
He knows if you've been bad or good,
So he must be Attorney General Ashcroft.

#4 lore raw
Quoted 3 lines

There is no way that you can teach your Hewlett-Packard printer to become a network rogue and break into the Pentagon --regardless of what you send it.

Really. Tell that to the people who already have a full Linux system running on HP laser printers

#5 lore raw

Hello Alan , Got a URL ?-) Verry interested in this . Tia , JimL

Quoted 4 lines · Alan Cox
Quoted 3 lines

There is no way that you can teach your Hewlett-Packard printer to become a network rogue and break into the Pentagon --regardless of what you send it.

Quoted 9 lines

Really. Tell that to the people who already have a full Linux system running on HP laser printers

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | [email protected] | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+
#6 lore raw
In reply to Richard B. Johnson

----- Original Message -----
From: Richard B. Johnson <[email protected]>
To: Helge Hafting <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, December 18, 2001 7:00 AM
Subject: Re: Mounting a in-ROM filesystem efficiently

Quoted 11 lines · Helge Hafting
Quoted 10 lines
Quoted 6 lines · Richard B. Johnson

Security isn't a problem with embedded systems because everything that could possibly be done is handled with a "monitor". There is no shell. If there is no way to execute some foreign executable, you don't have a security issue unless some dumb alleged software engineer added some back-doors to the monitor.

...

Quoted 15 lines

Embedded systems that perform critical functions such as FMS (Flight Management Systems) have a reset button. If it's screwing up, and they often do, the pilot not flying says some four-letter prayers to be picked up by the cockpit microphone, hits the reset switch, waits for it to re-boot, and enters everything from scratch again --usually the entire day's flight-plan routes, taking nearly 1,000 key-strokes. Now, that's an embedded system.

Cheers,
Dick Johnson

Quoted 7 lines

Penguin : Linux version 2.4.1 on an i686 machine (797.90 BogoMips).
Santa Claus is coming to town...
He knows if you've been sleeping,
He knows if you're awake;
He knows if you've been bad or good,
So he must be Attorney General Ashcroft.

....
Hmm, there are lots of embedded things with network capabilities. Think of wireless access points, network routers and switches. Even a network printer can cause network chaos if it would start to chatter on the net. Many of these things run FTP or HTTP servers for management purposes.

However, figuring out how to hack into a non-standard piece of hardware using an unknown processor is a non-trivial problem - it is very difficult even if you designed the thing yourself and has all the info, but could therefore be done by a disgruntled ex-employee.

Exploiting well known network services such as FTP and HTTP for dark purposes certainly should be a serious concern to manufactureres of these devices.
--
Herman Oosthuysen
[email protected]
Suite 300, #3016, 5th Ave NE,
Calgary, Alberta, T2A 6K4, Canada
Phone: (403) 569-5688, Fax: (403) 235-3965

#7 lore raw
In reply to Richard B. Johnson
Followup to:  <[email protected]>
By author:    Alan Cox <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 8 lines
Quoted 4 lines

There is no way that you can teach your Hewlett-Packard printer to become a network rogue and break into the Pentagon --regardless of what you send it.

Really. Tell that to the people who already have a full Linux system running on HP laser printers

My home HP laser printer has a web server running on it -- to save the couple of $$ it would cost to put an alphanumeric display on it.

-hpa

Signature · 3 lines
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<[email protected]>
#8 lore raw
In reply to Helge Hafting
Quoted 3 lines · Richard B. Johnson
Quoted 2 lines · Helge Hafting

A hacker don't need a /bin/sh or any other onboard software to exploit some security flaw.

[...]

Quoted 5 lines

You apparently don't know what an embedded system does. It is a device that uses a processor to perform some designed functions. It cannot do something that it was not designed to do although it can certainly fail to do what it was designed to do.

If it contains a CPU (that is designed to run code) and RAM (that is designed to store code) and you can trick the CPU in running code you tricked it into putting in the RAM, then it can do anything it wants with the other hardware available, anything it is designed to do.

Quoted 5 lines

If you want to break it, it's easier to hit it with a hammer or an axe. There is not any capability to "break in". Even if there was, what could you do? Shut off a motor? Screw up the ignition timing? Put porn pictures into medical images?

Or, be a proxy on the inside of J. Random Paranoid Corporate Network that can relay stuff, snoop, sniff interesting stuff that is being printed, etc. I mean, how about establishing an http connection out to a computer controlled by the Bad Guy, and over that he tunnels whatever he wants? And maybe it gets setup by putting some rogue Postscript in a file he somehow conspires to be printed.

Quoted 1 line

Most embedded systems don't have network capabilities.

Certainly if the embedded system has extremely limited IO (Coke vending machine?) there are limited opportunities for exploiting things like buffer overflows.

But even Coke machines are starting to get IO: to report inventory and apparent function to the vending company, some to even allow payment via a cellphone. Don't think that embedded == isolated, for it is becoming less and less true.

My cellphone has embedded software in it, it can receive e-mail. (There was a recent story of a mal formed e-mail message that would hard-crash some Nokia phones such even a power cycle wouldn't fix it!)

Quoted 3 lines

There is no way that you can teach your Hewlett-Packard printer to become a network rogue and break into the Pentagon --regardless of what you send it.

Boy, are you ever complacent. Just because HP manages to largely obscure the details of its internal CPU and RAM doesn't mean it ain't there and potentially exploitable.

I have a friend who used to be really into desktop publishing, Illustrator, his font collection, etc. He frequently made the distinction between a "hardware RIP" and a "software RIP". His point was actually that the embedded systems were better productized, but I still corrected him and said they were both software, one was simply embedded. He never seemed to get the point, and you don't either.

-kb