Ssh is no longer working from the commandline

ssh

I was trying to stop ssh from terminating after 10 minutes.

I followed an instruction here saying to modify a config file and restart the service with:

sudo launchctl stop com.openssh.sshd

Now ssh pi@12.34.567.89 just hangs.

I've reverted the config file and rebooted the machine but it still hangs.

How to fix?

PS sudo launchctl start com.openssh.sshd + another reboot also fails.

[pi@pis-iMac] ~ 
> launchctl list | grep ssh
-   0   com.openssh.ssh-agent

Best Answer

You may need to load the service again.

sudo launchctl load -w /System/Library/LaunchDaemons/ssh.plist

Related Solutions

Restarting a airport from the commandline – of a non-mac

You're asking a lot of different stuff here.

Here's the question I am going to try to answer:

"How can I bring my Airport devices into my Nagios monitoring more closely?"

OK so first of all, Nagios supports SNMP and (most?) Airport devices support SNMP. So "all" you have to do is configure the Airport SNMP settings and then set up Nagios to ingest the data.

Unfortunately the current version of the Apple's Airport Utility (6.3.1) removed the interfaces to the SNMP settings in the Airport. You can still download the old version (5.6.1) from Apple but the installer for the old version of the Airport Utility refuses to run on Mountain Lion! However it turns out that it is only the installer that is broken in ML!

Some crazy genius has written and made available an Automator workflow that works around this and allows you to install the old version of Airport Utility. I just tried it and it worked. Was then able to use it to set the SNMP settings of my Airport devices.

If this ends up working for you and you accept my answer, you should consider rewriting the question so that the question and the answer match.

Mac – Need help understanding script running at startup? “osascript -e ‘tell app \”ARDAgent\“ to do shell script \”say quack\“’”

It seems your Mac has been compromised (at the time of your writing) in order to mine bitcoins (./bitcoin-qt.app) probably by using ARDAgent exploit or similar. The posted commands are quite advanced, however plenty of them are copy&paste commands which indicates some pseudo-hacker (with actually little knowledge) who is trying to install trojan on your system.

Find the explanation for history commands below:

1: It removing files from Trash. Maybe clearing some evidence after downloading something.
2-12: Accessing Downloads folder with a bit of trouble. Half of these commands are mis-typed, so maybe the person was in hurry or stressed out.
13-14: Finding all files which belong to an unknown user (for unknown reason).
15-20: Struggling to access your passwords in KeyChains, but most of the commands are mis-typed. This indicates very little knowledge how to use the basic shell commands. It seems he tries to access folders such as /Library/LaunchAgents, /Library/Automator, /Library/Keychains, but fails.
21: There is no command sha.
22-23: Struggling to see your processes.
24-29: Struggling to check all the system users, however present shell prompt in 25-27 indicates that these commands were copy and pasted from some hack tutorial.
34-39: Checking network configuration.
41: Disabling auto updates for Google apps.
40, 45: Log-in to remote host.
47: Checking your non-Apple kernel extensions.
48-49: Checking your non-Apple loaded jobs. Repeating the same command without sudo could indicate that the user didn't have root access.
51: Checking startup items.
57: Disabling remote desktop agent. Why?
71-72: How he managed to install htop using apt-get on OS X? I don't know.
73-164: Checking processes, what's listening on port 80 and the history of last logins.
165-225: Checking your users and files again.
228: Indicates the person is from Windows background, as the parameter /i is invalid.
226-237: Repeating the same things over and over again.
238-480: Clearing DNS caches.
241-259: Running Bitcoin client.
263-264: Pasting code into wrong window. It should be actually:
```
osascript -e 'tell app "ARDAgent" to do shell script "say quack"'
```
Which basically on successful run of ARDAgent would run command say quack which basically say loudly "quack". This suppose to test if ARDAgent is vulnerable to the attacks, but testing by using Speech Synthesis it's the worse what hacker can do, because the user will hear that and figure it out that something is wrong.
265: Testing if check_afp is vulnerable by having SUID flag.

Your action were correct by disabling SUID for ARDAgent. When you run Disk Utility and Repair Permission, it will automatically restore the right permissions (including ARDAgent), unless it has been modified. The other thing it to keep your system up-to-date and monitor logs and history more frequently.

Best Answer

Related Solutions

Restarting a airport from the commandline – of a non-mac

Mac – Need help understanding script running at startup? “osascript -e ‘tell app \”ARDAgent\“ to do shell script \”say quack\“’”

Related Question