Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
SSH = a way of running commands remotely on your machine, from another. When you go into terminal, you can do almost anything to your machine with commands. SSH means you can run those commands onto your machine from any location.

Root user = the 'administrator' account in OS X. Administrators in OS X can do almost anything, but not exactly everything. Root user is the hidden user in OS X (same as in Linux, or the Administrator account in Windows).

Root access = the ability to do anything on your machine, usually through SSH.
 
SSH = a way of running commands remotely on your machine, from another. When you go into terminal, you can do almost anything to your machine with commands. SSH means you can run those commands onto your machine from any location.

This topic is moving fast!

How is SSH linked to public WiFi? What is SSH exactly, apart from running remote commands?
 
What inherent security? OS X has some severe vulnerabilities that damage the security of the UNIX system running beneath Aqua.

Yes, and I wholeheartedly agree...but this is *not* one of them. Leaving those services on all the time isn't a security flaw...you're leaving the door open asking for trouble.
 
How is SSH linked to public WiFi? What is SSH exactly, apart from running remote commands?

SSH = Secure SHell.
Do you know Telnet?
It's also a Command Line Interface to remotely use / administer another computer via the "Terminal.app"
Very briefly: SSH is secure form of Telnet.

I don't know why SSH is "linked' to public WiFi, but in any case, if you are connected to the internet via a public WiFi, don't ever switch SSH on!
You don't know how many network packet sniffers are trying to "see" what you are doing on a Wireless connection!
 
Considering the breach, I wonder if you had the firewall enabled and in stealth mode. It may not be impenetrable but it's helpful.
 
my computer has file sharing turned on. I dont especially remember turning it on, but maybe I did. For what reason would that need to be on? Just for sharing files across my home network?
 
What inherent security? OS X has some severe vulnerabilities that damage the security of the UNIX system running beneath Aqua.

Just as many vulnerabilities are in the 'UNIX layer' as there are in the nice shiny OS X-specific bits. Apple has to make sure SSH, Apache/etc remain patched if they want to keep a secure system.

This particular attack looks more like someone did get SSH access. The files have zero data in them, which hints to me that they were created using the touch command. Unfortunately, I don't think we can be any good at armchair forensics with just a single screenshot.

How does one make sure this is "never enabled?"

To not enable root... you don't enable it... OS X doesn't have any 'switch' to turn it on, you have to muck with NetInfo or some obscure terminal commands to activate it.

How does one make sure this is not allowed?

Make sure 'Remote Login' is turned off in System Preferences > Sharing.
 
Just as many vulnerabilities are in the 'UNIX layer' as there are in the nice shiny OS X-specific bits. Apple has to make sure SSH, Apache/etc remain patched if they want to keep a secure system.

Exactly. This is a point that needs to be shouted from the hilltops, because the iPhone hack with everyone swore up and down was a hoax, was able to be done because Apple has an outdated regex library that is many many many versions out of date.

This particular attack looks more like someone did get SSH access. The files have zero data in them, which hints to me that they were created using the touch command. Unfortunately, I don't think we can be any good at armchair forensics with just a single screenshot.

True, but we can make some guesses, based on the fact that SSH was enabled and other factors. But yes we can't be very specific because we don't have the system in front of us.

One more thing:

Security hole? There is no security hole. Looks like you've been clumsy and left the door unlocked.


Hoax or not, this thread has been really useful and interesting. Never knew the serve vulnerabilities of File Sharing and co.

I'd just caution about claiming that there are no security holes with SSH, claiming that this whole thread is a hoax, and then saying that you don't know anything about these things.

SSH has security risks (I clarify this because people talk about trojans vs. worms vs. viruses in other threads) that can be present if the service is not configured in a secure manner.
 
One more thing:

I'd just caution about claiming that there are no security holes with SSH, claiming that this whole thread is a hoax, and then saying that you don't know anything about these things.

I didn't claim that this whole thread was a hoax - I said hoax or not, this thread is useful.

I'll translate that for you since you have trouble understanding. Even if this thread was a hoax which I'm not saying it is, then it is still useful and people can learn from it.

I said there are no security holes that allow someone to hack into OSX easily - I didn't say there was no security holes with SSH. I said he'd left the car door open.

And yes, I don't know very much about SSH, but that hasn't got much to do with my first post.
 
Regardless, let's get to the subject at hand. We need the following details from the OP:

1) Look for other accounts that have been created.
2) Check for open ports
3) Check for newly installed applications
4) Check modification dates of all currently installed applications

5) Did you have any financial information on the computer (bank records, credit card numbers, receipts, etc)
6) Did you have any other volumes connected that could contain this information?
7) Backup your log files and archive them, just in case they didn't clean up after themselves


I'd be willing to look through the log files and give any help that I can. I'd check the secure log as well as the system log and console logs.
 
Hi,
I'm new to the Mac but have used SSH as my primary means of accessing my Linux servers remotely for years and have never been hacked. I have 4 hosts exposed to the public internet 24x7 and by taking a few simple precautions I believe it would take a significant effort to crack my system and wouldn't be worth the effort.

1. Patch the system regularly (esp. openssh, kernel, and network stack)
2. Shift to a non-standard port (ie not 22) for ssh
3. Use a public/private key for access instead of passwords
4. Disable password access
5. Only allow named users to log in and definitely not root
6. Use firewall rules to prevent more than n ssh connections from a given IP address within a given timeframe (eg. 3 attempts per 15 mins)

I've not yet exposed my Mac to the internet but can anyone tell me if any of the above steps can/cannot be applied to the Mac SSH service?

Thanks,
Craig.

ps. Sorry to hear of the hack - one of my servers was hacked a while back using a rogue cgi script which I left lying around on my web server. The b****rds installed a fake Paypal site on my server which I detected within 24 hours and shut down but it still pi$$ed me off big time. Your hack just looks like mischief but you never really know what they may have left behind so best to reinstall and sanitise the system. :(
 
I'm not sure what you mean by "enable root", as far as I can tell it is enabled by default. Anyone with an "administrator" password who is a member of sudoers (I'm not sure if that is all admins by default, or just the first one) can simply run any command with sudo and they have as good as root access. If they are too lazy for that then a simple "sudo su" gets you actual root access. At least thats how it is on my MBP and I know I didn't change anything where that is concerned.



And just so we are clear, SSH is nothing like having an open door. Most servers have SSH enabled, otherwise there would be no practical way to access them. I recommend either using an extremely secure password, or better yet a "key" to access it. If you know where you will be accessing it from then only allow whitelisted IPs, and make sure that is the only one on the whitelist.
 
Security hole? There is no security hole.
That's the funniest thing I've read all week. Yes blame the victim. Save Apple. And one thing's for sure: if there wasn't a security hole yesterday there's a security crater today. You foolish people believe you're invincible. You won't listen when people tell you to be careful. You get hit - and I'd presume you're rooted and owned by now - and then you blame the attackers. Yes it's wrong to leave your car unlocked and blame the thief. But it's also precisely the smug thinking "there is no security hole" which gets you into that situation in the first place.
 
This is a stupid statement.

It has nothing to do with the inherent security of Mac OS X.

Root access with SSH is just asking for problems, Mac, Linux, Windows it makes little difference with an easy password and little or no decent protection makes you a very easy target. You are ensuring you will get some grief from someone who has little or no ethics.

Unless you need specific services keep them turned off if you're not using them, and pick a hard to guess password.

Here's a good article about very very very dumb passwords

And here's some stupid passwords I've seen over the last few years..... Seriously people use these.....
123456789
admin
password
administrator
god
satan
secret
love
sex
qwerty
*Your Name
*Your Username
*Your Birthday
*Your Starsign
*Your favorite thing

:D
 
I'm completely over-reacting, but better safe than sorry IMO...
Yes exactly. And for the record you don't know as you're overreacting. Underreacting got this sucker into this regrettable impasse. No you never use remote login and if you do - you must understand what you do and don't do. And let's hope you don't have the root account enabled because in such case you just gave the intruders a halfway pass to your network.

SSH scans are very, very common on the 'net, and password dictionaries are used to try to attempt a break-in, in combination with "usual" names (root, admin, www, <English names>), and is called a brute-force attack.
This is what scares me. People don't know this stuff and they rig their own computers and they don't know what they're letting themselves into. People are getting hacked all the time through remote login and they don't grasp why this is such a terrible idea if you don't know what you're doing (and even sometimes when you do). The fact you have to explain basic things like brute force attacks - the fact people don't know what this is or worse, that they don't understand the other 99.9% of it - this is what scares me. Cowboys and indians becomes hackers and fanboys and finally Cupertino's Last Stand. Education is a defense. Hats off to those here who are helping.

if ssh is like other tools then Apple probably uses openssh, in which case you should try to see how far out of date the one in OS X is and see if any big vulnerabilities have been patched in the interim
Not again! :D:D

Wait....so your password is 10 digits, as in 10 numbers? And not characters. That would explain it. That's gotta be one of the easiest passwords to brute force
Yes but the hackers wouldn't know that.

I missed where someone claimed that OS X wasn't susceptible to brute-force "let me guess your password" hacks.
And I missed where someone said they knew for a fact this was a brute force attack.

Simple words of advice:
Never enable "root"
Don't allow SSH access
Keep all FileSharing stuff off....
.. until you're very sure of what you are doing.
Second that. Third it too. :D

This is a stupid statement.

It has nothing to do with the inherent security of Mac OS X.
No that is NOT a stupid statement. But your smug attack IS stupid. In addition to being smug and dangerous of course.

Your mention of "inherent security" of course begs the question "what inherent security" - or are you just another one of the inhabitants here who know a lot of buzzwords but have absolutely no experience in the field of security?

The original statement, perhaps poorly formulated, was instead begging the others here to stop thinking "smugly" - which is exactly what you are doing and evidently refuse to stop doing.

Yes, and I wholeheartedly agree...but this is *not* one of them. Leaving those services on all the time isn't a security flaw...you're leaving the door open asking for trouble.
Perhaps you're right - perhaps you're both right - but you don't yet know what happened to the victim's system so it's way too early to start assuming you know the attack vector.

Just as many vulnerabilities are in the 'UNIX layer'
All vulns are ultimately in the Unix layer.

I'll translate that for you since you have trouble understanding.
I don't think that type of hostility is called for in here.

I'm not sure what you mean by "enable root", as far as I can tell it is enabled by default.
No. From the rest of your post it's obvious you're very hazy on all this. I'd take a timeout and study things a bit. :)
And just so we are clear, SSH is nothing like having an open door.
That you do have right! :D
 
I would say this in an oxymoron, but like everyone is admitting, you kinda had a tacky neon welcome sign turned on...

-=|Mgkwho
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.