If you have a MacBook with an infrared receiver, did you know your Mac could be open to other people controlling your computer? By default, Mac OS will recognize the signal of any Apple Remote. Although the effect is relatively harmless (they will probably be able to randomly play some tracks on iTunes), it can range from being annoying if you were studying in the library and your friend happened to prank you, to embarrassing if you happened to be doing a presentation.
Most people do not need to allow any Apple Remote to control their computer. Why would you want other people’s Apple Remotes to control your computer? Here is a tutorial for securing your infrared port so that only your own Apple Remote can control your computer.
If you have an Apple Remote…
You can pair your remote with your computer by pressing and holding the Menu and Next (right) buttons for several seconds, while pointing the remote to the infrared receiver (on the MacBook Pro unibody models, the port is beside the power/sleep light on the front edge of the computer). The pairing logo will show up in the middle of your screen when the pairing is complete.
If you don’t have an Apple Remote…
You can disable the infrared port so that nobody with a random Remote can control your computer.
Open System Preferences → Security & Privacy.
If the preferences are locked, you will need to click on the lock at the bottom left and enter your password.
Click the Advanced… button at the bottom right.
Check “Disable remote control infrared receiver.”
Hopefully this tutorial will help you avoid annoying or embarrassing situations when people try to prank you with their own Apple Remote.
The Heartbleed vulnerability has been all over the news this past week. As usual, the media sometimes twists the facts, sometimes intentionally, other times inadvertently. For example, I’ve heard Heartbleed being called a virus, or being framed as something that was deliberately created to be malicious. Also, from reading people’s comments on the online news articles and blog posts, it seems that many people don’t really understand what Heartbleed is or does. From my point of view as a software developer, I would like to provide some information and resources that I believe are true and report the facts (but as I’m not an expert in the field of encryption/security, you may also want to take these with a grain of salt).
What Heartbleed is simply a software bug. Sure, there are bugs in nearly all, if not all, software out there (obviously we developers try not to introduce bugs, but we humans are unfortunately imperfect 🙁 ), but what makes this particular bug newsworthy?
This particular bug is a vulnerability, which allows a malicious attacker to gain information that should not be accessible.
The bug is in a library (called OpenSSL) that is used in a number of programs that in turn are run on a large number of computers worldwide.
The vulnerability has been out in the wild for two years.
There’s no trace left behind by a malicious attacker exploiting this vulnerability.
I came across this XKCD comic last night. I think it’s a pretty simple way to understand what the Heartbleed vulnerability allows a malicious attacker to do.
The comic illustrates the case where the victim is the “server” and the malicious attacker is the “client.” This is the case that most people are concerned with, as it is likely that servers running the exploitable software are easier to find and will probably have more “interesting” data in the memory. The data could potentially be usernames and passwords, credit card information, or encryption keys, but on the other hand it could also be just bogus data that happened to also be in memory. The data that the attacker could gain really depends on what happens to be in adjacent memory at that time.
However, the vulnerability exists both ways (if the software on the “client” is using a vulnerable version of OpenSSL). You could be owning a device or running a program on your computer that might allow a “server”, which has been maliciously programmed, to read memory off of your device using the same exploit. For example, Android 4.1.1 devices are susceptible to Heartbleed.
Although web servers are the most common targets being mentioned, there are other services that could possibly be affected by Heartbleed including FTP servers and mail servers.
If you are interested in the nitty gritty details behind how the exploit works, CloudFlare has an article on the low-level details (just disregard the fact that they say that private keys aren’t accessible because they were disproved on that point). For higher level information on Heartbleed, the heartbleed.com site has very clear information and a nice FAQ. Troy Hunt also has an informative FAQ about Heartbleed.
What to do about it
For end users
Since there is no trace when an attacker exploits Heartbleed compounded by the fact that Heartbleed has been vulnerable for over two years, it’s not possible to determine exactly what data has been compromised. In addition, if encryption keys were gleaned from Heartbleed, it is possible for even more data to be compromised by decrypting historic logs (if they exist in the hands of the attacker).
So for end users, the precautionary recommendation is to change your passwords after the services that were affected have been patched. Mashable has a running list of the status of popular web services that you can use to determine whether to change your password. In case you use a service that isn’t listed there, you can check it yourself on Filippo Valsorda’s test site. However, keep in mind that not only web services are affected. There are recommendations not to login to services that are still known to be vulnerable because when you login there is a chance that your credentials will be placed in memory, which is susceptible to be read. In addition, ensure that all the software and operating systems you are running are up to date.
For system administrators, developers and service providers
Obviously, ensuring that OpenSSL is up to date or patched is top priority. Troy Hunt provides some additional advice in his blog post.
Heartbleed and the goto fail and GnuTLS bugs
Heartbleed isn’t related to the Apple goto fail or the GnuTLS bug we’ve seen in the past couple months. The goto fail and GnuTLS bugs are susceptible to man-in-the-middle attacks where a malicious intruder can pretend to be the trusted service you’re communicating with and intercept messages between you and the service. Heartbleed on the other hand allows attackers to read parts of the computer’s memory that they should not have access to.
OpenSSL and open source projects
OpenSSL is an open-source project with eleven volunteer developers, maintaining one of if not the most used SSL/TLS libraries, probably on their own time. I think they should be respected for taking on the heavy responsibilities of this project.
Open-source projects allow external developers to read the source code and even submit improvements and contributions. Depending on the project, there are different procedures to getting contributions accepted, usually including a code review process where the core maintainers ensure that the contributions work as intended and meet the standards of the project (kind of like how a newspaper editor goes over the articles of his writers before they get published). Since humans aren’t 100% perfect, bugs and mistakes unfortunately happen, as much as we try not to allow them.
While it is possible to order security audits of software, for open-source projects that usually don’t generate any profit, it is difficult to come up with the money. I remember when we got a security audit for MyBB, it was in the order of thousands of dollars.
There is a lot of information about the Heartbleed vulnerability on the news and media, and from reading the comments on many of the blog posts and news articles I have read, many people don’t really understand what Heartbleed is and its implications. I hope that this article sheds a little bit of light on that, and provides more resources for those who want to dig a little deeper in understanding it.
I bought my MacBook Pro back in 2009. It was a Mid-2009 (2nd generation) version with a Core 2 Duo with the basic 2GB of memory and 250GB hard disk drive. I chose Mac because of many reasons; here are some of them, ordered by what I thought most important first:
Solid construction: The unibody construction was a huge factor. The size was quite slim and easily portable. The aluminum exterior felt solid. Since getting the laptop, I’ve only dropped it once. The hard drive died as a result (expected); was not a big deal to replace it.
Battery Life: The battery life exceeded the average of other laptops of comparable performance and price. I didn’t end up using the advertised 7 hours most of the time but 3-5 hours was good enough for me.
Compatibility with Unix/Linux: The Mac operating system is based on Unix. As a computer science student, being able to easily compile and run *nix programs, navigate around in the Terminal, and connect to remote *nix servers was a definite plus.
Compatibility with Windows: This doesn’t seem to be well known, but Mac easily allows you dual-boot into Windows with its Bootcamp software to run any Windows programs natively. I also used VirtualBox to setup a virtual machine running Windows for the programs that don’t need native performance or external inputs.
Plug and play with projectors/monitors: From using an external monitor at home, to plugging into monitors and projectors at school and places I volunteer, it had to be good to go without much hassle. For the most part, Mac OS X delivered this although I still prefer the more detailed options available back with Snow Leopard and Lion.
The MacBook Pro is an awesome work horse, able to do pretty much do everything I threw at it: homework, programming various things, projecting, editing photos and videos. It has been my primary computer for the past 4.5 years, and having replaced the battery last year I think it could probably last for another couple of years. I’ve slowly upgraded the hardware to max out 8GB of memory and settled with a Seagate 750GB Momentus XT Solid State Hybrid Drive, which fit the bill of having a large storage space while having slightly better performance with the flash cache.
I had hoped that Apple would be producing this line of MacBook Pros for a bit longer so that when my current one dies, I’d be able to replace it with another. However, after surfing the Apple Store recently, I realized that my presumption may not hold true much longer. There’s only one model of the 2nd generation MacBook Pro left and it hasn’t been updated since 2012. The rest of the MacBook Pro lineup consists of retina display models.
MacBook “Pro” with Retina Display
I wouldn’t really call the new MacBooks “Pro”. In my opinion, the current Retina MacBook Pros should just be called “MacBook with Retina Display”.
No network port: How am I supposed to setup a router or debug network issues if I have to have Wi-Fi first? Also, for transfers, a cabled connection is a lot more reliable and, for most access points, faster than Wi-Fi.
No optical disk drive: How am I supposed to read/write CDs and DVDs with installation media to setup older computers? How am I supposed to play DVDs? — a lot of educational media is still on DVDs, if not tape!
No user upgradable parts: There’s no way to replace a stick of memory if one has gone bad. There’s no way to upgrade your memory if you need more. There’s no way to buy a larger hard drive if you run out of space. You have to consider how much memory and space you’ll need up front, and pay Apple’s premium for that specific configuration.
No infrared sensor: I use the infrared sensor with the Apple Remote for a quick remote when giving presentations. The Apple remote is a lot cheaper, smaller and convenient than other remotes out there, for small-scale presentations.
Yes, I realize that down the road (even currently) probably people don’t need a network port, optical disk drive, or upgradable parts, but those people are probably not “Pro” users. That is exactly the reason why I think the current Retina MacBook Pro should be renamed as “MacBook”, and that the MacBook Pro lineup continue to be refreshed.
A real Macbook Pro
What I would consider a real MacBook Pro would be one with the 2nd generation hardware (retaining the ethernet port and optical disk drive) updated with an Intel Haswell processor and retina display. Now that would be something I would find worth buying. Basically, if Apple took the old MacBook Pro line and refreshed it with a new processor and a retina display, that would be the perfect computer for me, and I’m sure I wouldn’t be the only one buying it.
I’m going to briefly explain how to setup a new Raspberry Pi as a basic desktop computer with file sharing and screen sharing so that Macs can connect to it. This will be useful for quickly transferring files over, and taking control of the Pi remotely. I will be assuming that you have basic command line knowledge (running commands, installing packages, editing text files), and some Mac knowledge. I am not going to be too paranoid about security as I only intend on using my Pi on my home network, but if your Pi is going to be Internet-facing, you may want to read up elsewhere on securing your Pi.