Remote Booting Using a Wireless Network Card? 28
Eboneye asks: "I have been assigned to a project to figure out how to make a diskless portable workstation (laptop) boot through a wireless connection. The idea is to have a stateless client that stores no local data (for security purposes).
The only totally network boot stuff I have found uses PXE extensions. I have seen nothing like this in a PCMCIA card, much less a -wireless- PCMCIA card. For the proof of concept, we'll boot from a read only device, but of course during the setup phase use media to create a boot image on a boot server. I am currently looking at a couple different products that will provide a booting service. Ultimately, the goal is a to have a wireless tablet that can use different PCMCIA wireless adapters to connect to different LANs. Because of the specialized concerns of tablet PCs the solution has to be Windows compatible (sorry, Linux). Has anyone seen or worked on remote boot through wireless? Any experiences, gotchas, or suggestions for ways to solve this are welcome."
For security. (Score:1)
You should maybe think of 802.11a . Which is a wireless standard that is more buisness oriented (High bandwidth) hell of a lot better encription.
WiFi uses WEP (wired equivilant protocol(?)) to encrypt every packet that is send out. WEP, is know to have many weaknesses. There haev been many document exploits (airsnort is one of them). And any script kiddy can use it without using the keyboard.
Hence. I would recomend 802.11a and not WiFi
Re:For security. (Score:1)
802.11a also doesn't have the greatest range, especially indoors. 802.11b and 802.11g have much better range (and 802.11g has the same throughput as 802.11a).
Re:For security. (Score:1)
That's both 802.11a and 802.11b...BOTH can use WEP. To my knowledge 802.11a does not have any additional security measures over 802.11b in the spec. However, many cards being released implement an additional standard called 802.1x, which is better than WEP, but has also been criticised as being insecure. Also some cards (actually many cards these days) have been released with vendor-specific additions to WEP, such as longer keys...any card that claims 128- or 156-bit encryption is one of these. This doesn't really help though, since the flaw in WEP that causes it to be insecure means that doubling the encryption key length only DOUBLES the time that it takes to crack. So if it takes 1 hr to crack WEP at 64 bits, it only takes 2 hrs. to crack WEP at 128 bits.
This is in contrast to secure encrytion where a brute force attack doubles with every additional bit in the key, i.e. 1 hr at 64 bits -> 18446744073709551616 hrs. at 128 bits.
Also users should note that in WEP the first 24 bits of the key ARE NOT SECRET. So a 64-bit WEP key is really only 40 bit encrytion (but they wont tell you that on the box of your network card!)
Don't bother (Score:5, Insightful)
A scheme like this, where you have to wait for a boot image to traverse a network, kinda defeats the purpose of tablet pcs.
If you are doing this for security, use applications that utilize strong encyrption. Playing games like this at the OS level is not the appropriate place to do this.
Other read-only options (Score:2)
encrypt the drive (Score:2)
if the unit goes missing, all the person who finds it can do is replace the drive, cause they woint get squat off the secured one.
I beleive 1 or 2 of these products are fips 140 certified
Re:encrypt the drive (Score:1)
It's available at www.jetico.com and you can make a file that it will load that will make a "virtual drive" *and* it is available for linux and windows. They also have server options too.
One of the things I found which was handy is that you can have your regular password on the encryption file and then a "secret password" too.
This is handy lets say for some reason you got ordered at gun point to reveal the password. Great, reveal it. Give them the original password and then can see all the data put in that bit. But you got the secret password and it can have lots of other data in it...
Infact the goodthing is you cannot tell if there is a secret container held in the file.
Encryption such as blowfish, twofish, gost and more equal some very good encryption levels. Also, the encryption code is "open" so you can do your own security audit if you need
Hope that helps, I don't work for them. But I use their products, Check it out.
let me get this straight... (Score:4, Offtopic)
well, i suppose you didn't say you wanted good/high security. "security reasons" could mean "we want crap, swiss cheese-like insecurity."
not sure of an answer there, but good luck with that.
Re:let me get this straight... (Score:3, Funny)
could you honestly call a system secure that contains wireless network nodes running windows? and you have to answer that question without hallucinagenic drugs or resorting to philosophic ponderings on what words/time/reality mean.
Why make it bootable? (Score:3, Interesting)
First: security. Any authentication to get the boot image would, natrually, have to happen before the image was downloaded, so the Client would have to be able to haddle any encryption protocols before anything useful even happened. Unless you have a powerful system operating pre-boot, that is gonna be really insecure, especially over wireless, comprende? Imagine if the boot image was intercepted? I can't think of how that would be good.
Also, the simple fact that consolidation is typically more economic. One Big Server (could be running linux with crossover[whoring]) is typically easier to maintain than a remo.te, full-fledged laptop. So, read the story on Largo (about the thin clients, rather than the Linux bit) and think about it--decide if you really, really have to make it bootable--be sure you can't or are unwilling to go thin.
Serious security issues with 802.11b (Score:5, Insightful)
Let's assume you set up your wireless network PROPERLY; it has a gateway machine which restricts communications within your internal network, with that gateway being the only machine accessible to your wireless network. Your intent would be for your wireless machines to have nothing accessible, except to that gateway. Your remote machines would use an encrypted tunnel to log onto that gateway.
By remote-booting, you've destroyed that paradigm. A remotely-booting client would have no resources able to establish that encrypted tunnel, so you would not be able to boot through that gateway. Okay, fine, so let's say you put the boot image on the gateway machine outside the tunnel, or on a second server provided just for that purpose.
Now you have a brand new security hole... First off, an attacker doesn't need any security codes to grab a copy of your boot image; and that boot image, in order to establish your encrypted tunnels, would give the attacker, if not direct access to the gateway, at least valuable information narrowing down your security window. Having individual passwords users have to enter to log on might help things, but doesn't close the hole...
Since the link the booting PC would by definition be unencrypted, an attacker could spoof the wireless gateway for the period of time during when a wireless machine was booting, substituting a modified copy of the boot image. The result would be an insecure client, in which, if a password is entered, it could be forwarded to the attacker; or that machine might act as its own gateway, from the attacker through the insecure machine onto your network.
Re:Serious security issues with 802.11b (Score:5, Interesting)
The next step up in complexity, as well as power, is to again use a usbkey to boot, but boot into linux. Have it boot from the read-only keychain, use the (unique) information on each key to establish the connection, etc, and then start X-Windows and rdesktop (linux remote desktop client), connecting to a remote windows server. It would be quite easy to secure the tablet so that the linux distribution is secure, and again you have a unique key to secure the connection. From the users point of view, they're working on a local windows machine, although from your point of view they're remotely logged on to another box.
These are just the first two ideas that came to mind. As the parent said, though, you need some kind of local storage for encrypted booting. I highly recommend a usbkey from one brand or another, as they're relatively cheap, absurdly robust, and quite convenient. And once you're allowing even a bit of storage, make it a useful amount, and boot locally off a secured disk, rather than trying to get the hardware to do something it's not supposed to do. Remote booting, keep in mind, just uses some ROM code to boot the computer and then moves control elsewhere. I'm pretty sure you won't find a system ROM or an 802.11 ROM that does what you need; instead, you're going to have to attach a boot ROM of some kind, and a usb key is about as good as it gets.
Oh, one final point, to make this make sense. Most of the usb keys have a read-only switch that can be latched, which makes them appear as read-only mass storage devices to the OS. Once you write the key, you can physically remove the switch (I've done this to several usb keys) to make it quite inconvenient to write to them again. It is possible to write to them either by opening them up and reconnecting the switch, or by writing a custom driver which ignores that the device is read-only (it turns out that, even in read-only mode, the keys I've worked with do honor writes), but neither of these methods is very convenient. It depends just how much security you need.
Re:Serious security issues with 802.11b (Score:2)
But you say it yourself -- a higher level crypto protocol wouldn't be supported in hardware. It also can't be supported in software, because during boot there IS no software loaded. (Unless your system's BIOS supports such things, which I doubt.) So therefore, at boot time, this operation would be unacceptably insecure.
Consider your security model (Score:4, Informative)
What's the model here? Does somebody walk into a secure facility, pick one up, use it to do some eyes-only investigation, and return it when they leave? What are you trying to secure against? Tampering, or somebody walking off with the data? The solution often depends on the threat model.
If your threat model is to prevent against tampering, then you may be better off exploring other options. For example, have you considered read-only media? How about having the tablets re-ghosted when they're returned, before they're re-issued? That can be done in an automated fashion without a whole lot of hassle-- primarily through the PXE extensions you've already investigated, combined with hardware at the docking stations.
If you're trying to keep people from walking off with data, then diskless isn't going to be the way to go. A lot of data gets left in RAM after power is removed. (See Gutman, P., "Secure Deletion of Data from Magnetic and Solid-State Memory," Proceedings of the Sixth USENIX Security Symposium, July 1996, or do a Google search for "RAM remanence".) You may have seen some computers-- notably the old Macs-- that would power up with their last display still on the screen!
Also, if you have a totally stateless box driven by a wireless LAN, then some shmuck can easily sit in a van a half-mile away with his laptop and find out everything you're wanting to keep private. Stateless booting means that your encryption has to be bootstrapped! A lot of naive ways of doing this exist, such as sending a root filesystem with encryption keys already on it. Some of these open themselves up to passive attacks. Even more sophisticated techniques, such as DH, still are totally vulnerable to active attacks (like the guy in the van pretending to be one of your tablets asking to be bootstrapped).
I seriously suggest you rethink your security model. The Windows compatibility is a big problem. It keeps some of the latest crypto filesystems, etc. from becoming part of the solution. Something based on VNC, Citrix, Windows Terminal Server, etc. may be helpful: make sure the computer doesn't know more than it's telling the visitor. Also, these small programs will tend to re-use the same part of memory repeatedly, making RAM remanence slightly less of an issue.
Remote boot & Windows don't mix (Score:2)
Good news is that linux does support a vast array of windows applications and "Work alike" alternatives.
You need a CardBus card, not PCCard/PCMCIA (Score:4, Informative)
In terms of PXE hardware, you probably want a CardBus card, not a PCCard (which is what PCMCIA was renamed to). PCCard is 16 bit data path and cards are identified by a 64-character text string or something usly like that...PCCard is 32 bit data path and devices appear like PCI devices and are identified like PCI devices (I forget the details, but it's something like a 16-bit manufacturer ID and a 16-bit ID for that particular type of card).
Back in early 2000 or so, we had a PXE-compliant CardBus network adapter (not wireless, but that shouldn't matter to the software level) in our lab that would do remote install of Windows 2000. In fact we had to make zero changes to the code, it worked like any PXE-compliant PCI network card. So if you could find a PXE-compliant CardBus wireless network adapter, you should be able to do a remote install of Windows 2000/XP on it today. Of course this requires setting up a Windows server to hand out the images, etc. which there is undoubtedly a Microsoft white paper on somewhere.
- adam
Try linux bios... (Score:2)
Perhaps you should consider rdesktop / citrix ... (Score:1)
citrix connections can be encrypted, prevent the user from storing local data, are vaguely efficient, come up really fast, and have the facility for proper user authentication that you couldn't really do with network booting.
However, I presume you have a reason not to use citrix/termserv, most likely since you'll need "tablet pc" OS features or similar that won't work over citrix.
This being the case, I'd put a preliminary comment at "no can do" with the basic OS and tools. Microsoft might well have the "XP remote boot tools" hidden away somewhere - good luck finding them though. I'd be budgeting for tens/hundreds of thousands of dollars in customization by MS or a big sol'n provider with an inside channel to MS.
LTSP already support wireless remote bootinging (Score:1)
I have had a Linux tablet PC for two years. (Score:2)
Considering how much space winshit takes up, and the innability for specialised projects to modify it you are faced with a serious challenge.
If I had to do it, I would install Linux on the tablet pc with an svgalib client for VNC [tightvnc.com] or terminal server [rdesktop.org]. It will enforce "on premisis" use. VNC supports SSL if you need security.
Make sure to use every available security option and see if you can get modified 802.11a cards "shifted" to another frequency. It won't be perfect, but it will be more effective than WEP.
Diskless Boot for Windows 2K/XP/XPEmbedded (Score:1)