Loss Prevention

DanTekGeek

MacTechGeek
Im looking for some software to increase the chances of me getting my PB back if it is ever stolen. Im thinking maybe something that will "phone home" with an IP adress or something like that. I dont know, really, so thats why I came to you guys. What reccomendations do you guys have?
 
Get insurance, and a kensington lock. I don't think something like that exists or if it does, I'm quite sure it'll cost a lot.
 
There is some "lojak" type software on VersionTracker, but honestly, I wouldn't bother. Firstly, its not loss prevention, its more like loss recovery. And secondly, I've never heard of it actually aiding in the recovery of a stolen computer.

Honestly, keep your computer secure and insured. A Lojak that calls home and tells you that your computer is enjoying a nice holiday somewhere in Los Angeles is not going to help you much.
 
Your best loss prevention tools are
  1. Good backups that are not stored with your laptop
  2. A good insurance policy
  3. and finally, don't let the sucker out of your control
 
yeah, im most worried about it being stolen at school. i guess ill just do what i do with this one, that is, not ever let it out of my site. i guess i should probably also put a lock on the case. i guess one of my biggest concerns is identity theft. i know osx has a good file vault system, but is that enough?

/me <== paranoid
 
It would be extremely difficult -- if not impossible -- for someone to truly steal your identity just by gaining access to the information on your computer. If you've scanned in images of your driver's license, store credit card numbers, bank account numbers, or other information that really shouldn't be on there anyway, then identity theft is a minute possibility, but still a far-fetched idea.

FileVault will protect everything contained in your home folder, and nothing else. For a system like mine with multiple drives, and data frequently stored outside the home folder, FileVault would do nothing but protect my bookmarks and application settings... for a laptop, though, with a single partition, it may be a viable solution, but I think you need to ask yourself, "Is there information sensitive enough to warrant encryption on my drive?" Term papers, emails to friends, little bits of code you've written -- these things don't need 128-bit AES secure encryption. So what if someone gets their hands on them? If you happened to steal someone's laptop, would you think you hit the motherload when you find last semester's papers or some emails between he and his girlfriend? Naah... people don't want your personal stuff. It's useless to them. Still, if you feel the need for FileVault, I would make sure your drive is in pristine condition (permissions repaired, no disk errors) and I would "clean house" on the home folder, just so FileVault keeps the encrypted disk image size to a minimum.

Instead of FileVault, I would suggest a good, hard-to-guess password, and perhaps setting the open firmware password. That's good enough to keep 99% of the thieves out of your stuff, and the remaining 1% probably wouldn't be interested in your personal stuff anyway. Their only option would be to reformat the drive, granted they knew enough about Macs to open it up and remove/add RAM to get around the open firmware password.

I think you need to worry more about the actual laptop itself rather than what's stored on it. Keep a good backup, as you said, just in case of a theft, but other than that, just keep your eye on your 'book and if you see anyone eyeing it suspiciously, prompty give them a swift kick to the head!
 
I you were to set up an account with dyndns.org, and install a dyndns client, then your computer's external IP address would be reassociated with a constant domain name. This is how I ssh home from work when I (frequently) forget to forward research or files to myself.

Then you could turn on ssh so that you could actually reach the computer when it is turned on.

This wouldn't help you reach the computer if it's behind a NAT router, firewall, or similar gadget. Even in that case, you might be able to get the cooperation of the ISP, and find out what subscriber had the IP address at the time.

You could get arbitrarily complicated with inbound port forwarding over an outbound ssh connection, but that's getting pretty topheavy for something that will hopefully never happen...
 
Back
Top