Bingo. Where I live, having more than four sex toys is an "obscenity" state jail felony as per Texas penal codes. So, they are sold as "teaching devices", "medical mockups", or other items.

This is a fight that doesn't need to be dealt with. Just call it a CNC mill, which is designed for fabricating automotive parts. Hoppes calls their #9 product, "lubricating oil", instead of "gun oil." Might as well not have to deal with a wedge issue when it comes to business if one doesn't have to.

The problem is that this employee data, which would be innocuous in the hands of a company, can easily leave the premises. e-Discovery and fishing expeditions are common, and that info can wind up in the hands of someone completely irrelevant.

Of course, there are always the criminal organizations who would love that info. They find that Joe Ducato is out on a long haul... grab his address, sell the info to a local gang, and they clean his home out. This hasn't been the case yet, but as time progresses and if the economy sours further, it wouldn't be surprising to have your local gangbangers swing deals with overseas organizations to buy dumps of potential victims and when their places will be empty. Right now, crime is relatively low, but that can easily swing up due to economic factors.

My philosophy is to use the least amount of data needed, and if has to be obtained, it be decentralized (for example, the AD servers are separate from the HID badge locks, which are separate from Exchange, which is separate from the CCTV room). If the data isn't present, it can't be slurped off overseas and sold.

I live in Austin. If you can get access to the north/south backbone and the hike/bike trails, it isn't too bad. However, get on roads past that... and things get real dicey, real quick, mainly due to the fact that Austin is at a low boil when it comes to road rage, combined with no significant road improvements (other than toll roads) since 1995.

What type of bike you take is also important. If you are on a bus line to and from UT, don't even bother to assume that there will be a slot free on the bike rack at the front of the bus (people will get into fistfights over these). Grab your Brompton and just pack your two wheels with you.

If you are lucky enough to be able to go on and off the core bicycling corridor, it is wise to use PitLocks for the commute bike so wheels, tires, the fork, the seat, and other items don't disappear. It also is wise (assuming with permission) to leave a security chain at the work rack, and carry a U-lock on the bike. This way at work, the bike is secured by two locks [1]. Of course, an angle grinder will make short work of most sturdy locks... but that is what insurance is for.

[1]: I am partial to Kryptonite's high end locks, but Abus is also good. Both resist even expert picking (not pick-proof, but resistant, which is important.)

Ideally, it should do both. One device would have an extremely large amount of bandwidth to play with if in range of the tower, but as more devices get handed off to the tower, there is less bandwidth per device, but all devices get some level of service until a threshold is reached where the tower cannot accept any more items, where even EDGE or GPRS speed cannot be maintained. This is especially important at sporting events or SXSW where there are tens to hundreds of thousands of people in one space. Assuming the tower has terabits of bandwidth available, it should at least provide 3G coverage, decent enough for people to pop selfies and upload them or tweet about how badly the band on stage sucks.

Usually purchase speed is in this order:

1: Debit card. (user swipes card, enters PIN, done.)
2: Credit card. (user swipes card, signs, done.)
3: Cash.
4: Checks.

From what I've seen at stores, people fumbling for their phones at stores is actually slower than the coupon-clipper with the checkbook.

If Google's mechanism goes via credit cards like Apple Pay, it would be useful, should I lose my wallet, as a backup mechanism. However, if it is ACH based like CurrenC... then I would avoid it at all costs, since all it takes is one bad transaction, and I'm cleaned out with no recourse.

It isn't cheap, but there are ways to use 3D printed parts to make "real" parts. For example, with a dissolvable filament, one can print out an intricate part, put it into sand, plaster, or one's preferred moldmaking substance (making sure you have a hole to pour in, and a vent hole), pour limonene in to get rid of the filament, then pour molten plastic or one's metal alloy of choice. Let cool, then separate (or break apart) the mold pieces. The result is a usable part made out of a material that is up to task.

It might be a part just may need improving. The turbo resonator on Mercedes Sprinter T1N models is one example. The original part was OK, but an aftermarket part would completely fix glitches with the item.

Another item might be RV door handles. There was a batch recalled that had breakage issues. If someone scanned the pieces and made identical items, except of a very tough Iconel, the same door handle would easily outlive the RV.

Right now, 3D printing is plateauing, because there is only so much one can do with plastic. However, if sintering, stereolithography, and other items which work with metal or ceramic become inexpensive, this can mean a lot of useful items.

My worry is that we start seeing DRM mandated for 3D printers. All it would take is having the print controller refuse to print any design unless it was signed with an approval certificate, with a number of parties on the Net that are set up to vet that some item isn't a copy of something.

Of course, DRM ends up an arms race, but ultimately, the victory goes to the deepest pockets. (For example, the PS4 and XBox One have yet to even have a dent made with them.)

I have given up on theaters except for the Alamo Drafthouse here in Austin. Where other theaters have the constant people prattling and tapping on their devices, I have seen the ADH ushers be pretty proactive at tossing the texters and the yakkers out.

Long term, with people's tempers already raw, I wonder how long it will take until brawls start happening because people end up just sick and tired of the phone zombies, be it the cretin with one finger in his ear, screaming into his phone, or the people expecting others to clear a trail for them on the road. It only is a matter of time before this starts rubbing people past their breaking point.

As for lanes... good luck with that as pedestrians, that is great in theory, but once you get the people walking 3-5 abreast, that idea is going to go out the window unless there is a physical barrier preventing people from doing that.

In my experience, the average person buying a system with crapware on this doesn't care about it, provided it doesn't slow their machine down. It is just like the people who spill their lives onto social networks. They don't care who reads it, so likely wouldn't care to be tracked by "marketing browser experience enhancement" software.

The real takeaway from this is for people to pack their own parachute -- image off the drive's original software (just in case), wipe the drive [1], then install the OS from clean media, and from there, install applications. Of course, it doesn't hurt to make a zero-level image after the machine is installed, updated, drivers loaded, and activated, so a complete "bare metal" reinstall is just reloading that image.

[1]: Boot a Linux CD, dd if=/dev/zero of=/dev/hdx if the drive is a HDD, blkdiscard -v /dev/hdx if the drive is a SSD.

My shopping experience is just fine without active MITM attacks.

The ironic thing is that Lenovo has had a good reputation. They inherited the Thinkpad name, and it used to be that it was the go to brand for laptops before Apple jumped in that market. Plus, business-line Thinkpads are pretty secure, be it a decent TPM implementation, fingerprint scanner, and other items.

I just hope they learn their lesson, and this doesn't pop up again, as their products are quite usable.

Ad injection is quite lucrative. This is what entire companies like Phorm which intercepts in-flight connections and inserts ads.

As for ad injection like this, I've seen a number of consumer level PCs route traffic through a local proxy, installing Web browser add-ons to keep the browser switched to the proxy and to inject their own SSL key. The fix was removal, and even then, there were processes that had to be stopped via autoruns, as well as blocked from phoning home via the Windows Firewall (so there wasn't a chance they could do damage even if restarted.)

The exception to this seems to be HP, which might have sample programs on it (Norton, for example), but no crapware that loads in Web browser add-ons. It actually was a shock seeing a new HP consumer laptop actually in a usable state out of the box, without having to go swinging at what starts up with the autoruns pickaxe.

The problem is that companies face zero negative consequences for adding intrusive software like this onto a machine. Joe Sixpack won't know or care that his search engine gets redirected through some no-name third party site so his google search page has flash ads. With the private key out, he won't realize that his banking stuff is compromised until his bank account gets drained.

The fix? As a consumer, either bring your own OS and completely wipe and reinstall the box, or buy a business-line version. Lenovo would not dare to try installing anything like this on the Thinkpad line, just like Dell's Latitude line, and HP's EliteBook line. Of course, there is always Apple, which seems expensive, but if one compares like for like, a MacBook Pro actually has a price advantage to a comparable business line HP or Dell with the same features and chipset.

I personally use a disk image utility to clone the drives before the machine ever boots for the first time, but almost all non-IT people end up losing the recovery disks, or just not making them in the first place. This is why having an OS image in ROM (or technically read-only SSD) would be useful.

The ideal would be both install media, as well as a recovery instance. This way, one could boot the machine, mount the volumes, and save off documents to external media in preparation for a complete format and reinstall. A recovery instance would also be useful for fixing boot issues, or even dealing with malware (although it is best to reinstall if malware is present.)

This is why you use VMs. If malware hits the disk, it is going to find a generic HDD, like a VMWare Virtual drive, and that vector of attack stops for good right there.

We are almost at a point where we should virtualize everything, and what sits at the bare metal is a hypervisor, where there is a definite layer of separation between the OS and devices. This way, a compromise on the OS level won't allow hardware to be tampered with. If there is a firmware update needed, then it should be made available for manual flashing that takes a deliberate set of actions by the user (or via remote, using some administrator certificate) to ensure that a firmware update is authorized.

In fact, virtualization on newer machines is more of a "why not?" item, than a "why?" item. For example, Windows 8 and Windows 8.1 have Hyper-V available with a switch setting and a reboot. With a little bit of work, one can have one instance of Windows just for Web browsing, and the browser would be a seamless application. The advantage of doing this is that if/when something nails the Web browser and gets a user context, rolling back to a snapshot/checkpoint is pretty easy.

A good example of this was when I was browsing in a VM a certain social network without an ad blocking extension in the browser... 10 minutes later, that VM was slammed by malware, likely from an ad server that was serving up exploits. The fix was two clicks and a confirmation dialog away. Of course, if malware isn't detected, that is another story, but for browsing the Web, it is wise to just roll the VM back every so often anyway (at least every month for Patch Tuesday's festivities.)

What would be nice is if PC makers could allow one's choice of hypervisor to be installed on a dedicated SSD that either is physically set read-only and read-write by a DIP switch (with preferences and system info stashed on a separate writable partition), or similar functionality. The advantage of this is that the hypervisor would be pretty much static except for occasional updates (and the update mechanism can be made decently secure), and hardware would be isolated from the VMs.

If a device does need a firmware upgrade, a mechanism at the hypervisor level would address this.

GM cars seem to be relatively rare in my neck of the woods. For college students, Kias, Hyundas, VWs and Mazdas have that market, with the Toyota models after that.

I really don't like GM's ability to disable any vehicle, anywhere. I'm reminded of an Austin dealer which installed devices to disable vehicles if the buyer didn't pay their loan payment... and a disgruntled ex-employee logged on as a valid employee, disabled all vehicles in the system and set them to honk until the batteries went dead. Wasn't a relatively big thing... but if someone did hack GM, the damage they could do with OnStar could be tremendous... for example, if there is a forest fire, hurricane or a disaster causing an evacuation, killing all GM vehicles in that area can turn the disaster into a catastrophe with extreme loss of life, just because the GM cars stalled would prevent movement of everything else.