There are only two reasons why you wouldn't be able to edit it:ġ) You are using a standard user who cannot execute sudo, orġ) is the most likely. It is not part of El Capitan's System Integrity Protection (AKA rootless). There are legitimate reasons to edit the hosts file, but that particular Adobe tech you talked to probably assumes the most common reason, like I did.Ī bigger question is why you can't edit that file.

I'm quite sure it would be Adobe's initial assumption too. I'm not necessarily saying that you did that, but that would be my initial assumption in these cases - just the law of averages at work. However, hacking the hosts file to pirate Adobe software is extremely common. I haven't seen the file, so I can't comment on it. (Does Adobe really modify the hosts file? Seriously?) Here's a related discussion over in the Adobe forums. Here's a related description, using TextEdit and the GUI. To gain access - as others have indicated - use the following command, and the nano text editor: # localhost is used to configure the loopback interface

If the hosts file is not at its default configuration, then something (or someone) changed it - and you'll want to determine what happened.Ī typical hosts file looks something like this: If the hosts file is at its default configuration, then there's no need to access it.

While it might be correct, this is also something that some folks use to either break Adobe licensing, or that can be used to gain access to your system. I'm skeptical about the approach that this tech is following, too.

Adobe host file mac