Pro free for a week: code NETMUTE
NetMute

Two ways to get NetMute

Both are free to download and contain the same features. They differ in how you buy Pro.

Mac App Store

The simple route

  • Pro is bought in the app with your Apple Account
  • No licence key to keep
  • Apple handles payment and refunds
Open the App Store

Direct download

Version 2.3.10 · 13 MB

  • Invoice with VAT ID, ready for expenses
  • 5- and 10-seat licences for teams
  • Unlocked with a licence key
Download the .dmg

The direct build is signed with a Developer ID, notarised by Apple and updates itself. Pro does not carry over between the two: a licence key works only in the direct build, an App Store purchase only in the App Store version.

What Is sshd-keygen-wrapper on Mac? Why It Has Full Disk Access

sshd-keygen-wrapper is a genuine part of macOS: it is the small Apple program that starts the SSH server when someone connects to your Mac through Remote Login. It appears in Full Disk Access because Remote Login has an option that gives remote users full disk access, and if you do not log in to your Mac over SSH you can switch Remote Login off and the entry loses its purpose.

8 min readUpdated

What sshd-keygen-wrapper is

macOS includes OpenSSH, the same SSH client and server used on almost every Linux and Unix system. The client is the ssh command you use to connect to other machines. The server side is sshd, which lets other machines connect to yours. On the macOS 26.6 Mac used for this article, ssh -V reports OpenSSH 10.3p1.

Apple does not start sshd directly. It starts a wrapper first, and that wrapper is sshd-keygen-wrapper. The file lives at /usr/libexec/sshd-keygen-wrapper, is owned by root and is a universal binary for Intel and Apple silicon. Its embedded version string names the project as Apple's OpenSSH build.

The name describes the job. Before an SSH server can accept connections it needs host keys: the cryptographic identity your Mac presents to every client, so that the client can recognise the same machine next time. On a fresh Mac those keys do not exist yet. The wrapper checks for them, generates any that are missing (its own log messages read "Generated %s host key" and "Failed to generate %s host key"), and then hands the connection to sshd. On current macOS it also copies host keys for the pre-boot environment, which its messages refer to as the base system.

The wiring is visible in /System/Library/LaunchDaemons/ssh.plist. That file defines a launchd job with the label com.openssh.sshd, sets its program to /usr/libexec/sshd-keygen-wrapper, listens on the standard ssh port (22) and advertises the services ssh and sftp-ssh over Bonjour. Most importantly, it ships with Disabled set to true. Out of the box, nothing listens and the wrapper never runs.

Why it appears in Full Disk Access

The switch that turns the job on is Remote Login, found in System Settings under General, then Sharing. Apple's own description in that pane reads: "Remote Login lets users of other computers access this computer using SSH and SFTP." Click the info button next to Remote Login and you find a second option: Allow full disk access for remote users.

That option is the reason for the entry you found. Since macOS Mojave, folders such as Mail, Messages, Safari data and other protected locations require Full Disk Access, and that permission is granted per program. An SSH session has no app icon to grant it to. Every remote session starts with the program launchd runs for the connection, which is sshd-keygen-wrapper, and the shell and commands you run inside the session inherit from it. So when you allow full disk access for remote users, the system grants the permission to the wrapper, and the wrapper shows up in the list under Privacy & Security, then Full Disk Access. The Sharing settings component in macOS contains the path /usr/libexec/sshd-keygen-wrapper for exactly this purpose.

In practical terms: with the switch on, anyone who logs in over SSH with a valid account can read the protected parts of that account's data from the command line. With it off, they can still log in and work with ordinary files, but macOS privacy protections stay in force and protected folders return permission errors.

You may also have met the name somewhere else, such as a prompt or a list of background items. The cause is the same in every case: at some point Remote Login was switched on, by you, by an administrator, by a management profile on a work Mac, or by a setup guide you followed for remote access or a developer tool.

Is sshd-keygen-wrapper malware? How to check

The program itself is Apple's. Checking is still a good habit, because borrowing the name of a system process is a familiar trick. Three checks settle it.

Location. The genuine file sits in /usr/libexec, on the read-only system volume protected by System Integrity Protection. Third-party software cannot replace it there. A file with this name anywhere in your home folder, in /Library, in /tmp or inside an app bundle is not Apple's.

Signature. In Terminal, run codesign -dvv /usr/libexec/sshd-keygen-wrapper. On a genuine copy the output includes Identifier=com.apple.sshd-keygen-wrapper, a line starting with Platform identifier, and an authority chain of macOS Software Signing, Apple Code Signing Certification Authority and Apple Root CA. TeamIdentifier=not set is normal for system binaries. Then run codesign --verify --verbose /usr/libexec/sshd-keygen-wrapper. It should answer "valid on disk" and "satisfies its Designated Requirement".

Configuration. The real job is started from /System/Library/LaunchDaemons/ssh.plist. If a launch daemon or agent in /Library/LaunchDaemons, /Library/LaunchAgents or ~/Library/LaunchAgents points to a program called sshd-keygen-wrapper, that is not Apple's setup and deserves a close look.

One point needs to be kept apart. A genuine wrapper does not mean every SSH login is welcome. If Remote Login is on and you did not turn it on, the question to ask is who can connect, and the next section covers that. To see whether anyone actually has, run last in Terminal. It lists recent logins in reverse order, and sessions that came in over the network show the address they came from in the third column. Local Terminal windows appear without one.

Should you leave it, remove it or turn Remote Login off?

Start by finding out whether Remote Login is on. Open System Settings, go to General, then Sharing, and look at the Remote Login switch. In Terminal, launchctl print system/com.openssh.sshd answers "Could not find service" when the job is not loaded, which is the normal state for a Mac that does not accept SSH. (The older command systemsetup -getremotelogin needs administrator rights.)

Then decide based on how you use your Mac.

You never log in to this Mac over SSH. Turn Remote Login off. That disables the launchd job, port 22 stops listening, and sshd-keygen-wrapper has nothing to do. If the entry stays in the Full Disk Access list, switch it off there or remove it with the minus button. This is the cleanest outcome, because a closed service needs no further protection.

You use SSH, but only for shell work, file copies or Git. Keep Remote Login on and turn Allow full disk access for remote users off. Ordinary files in your home folder stay reachable over SSH and SFTP. Only the folders macOS protects for privacy reasons stay closed. In the same info panel, limit access to specific users instead of all users, and prefer key-based logins over passwords.

You need remote tools to reach protected data, for example a backup job that runs over SSH and must copy Mail or Photos libraries. Then the full disk access option is doing what you asked of it. Keep it, and treat SSH access to this Mac as equal to sitting at its keyboard.

Removing the wrapper's entry from Full Disk Access while leaving the option enabled in Sharing only makes the two settings disagree. Change the option in Sharing, and the list follows.

Remote Login is also a network service

Full Disk Access decides what a remote session can read. It says nothing about who is trying to connect. With Remote Login on, your Mac listens on port 22 and announces itself on the local network through Bonjour as an ssh and sftp-ssh service. On a home network that is usually harmless. On hotel, café or office Wi-Fi it means every device on the same network can see that your Mac offers SSH and can try passwords against it.

The built-in macOS firewall handles part of this. It filters incoming connections, and System Settings can show the state "Remote Login: Blocked by Firewall" when the two settings clash. What it does not show is outbound traffic: which apps and system processes on your Mac are contacting servers, and where.

That is where NetMute fits. It lists every app and system process with live network traffic, including Apple's own services, together with the domains each one contacted. If a remote-access or developer tool turned Remote Login on, you can see what that tool itself talks to, and one switch per app blocks it from the network. NetMute does not change Remote Login or Full Disk Access. Those stay in System Settings, where this article sends you.

Frequently asked questions about sshd-keygen-wrapper

See which processes on your Mac go online

NetMute shows live traffic for every app and system process, lists the domains each one contacted and blocks any app with one switch. Free on the Mac App Store. Pro is a one-time purchase, no subscription.

Free on the Mac App Store

Free with no time limit · Pro $12.99 one-time

Download free