curl command failure on MacOS Monterey iOS 12.3

Question

Jeff Lu OP

Created Jan ’23

Replies 2

Boosts 0

Views 2.3k

Participants 3

Hi There,

I am trying to execute curl command on my new MacOS Monterey with M1 chips, however, it always return operation time out, after looking console.

it always return deny error, what exact issue here? please advise.

Thanks,

 33903  default	09:09:22.396852-0500	mDNSResponder	[Q32359] InitDNSConfig: Setting StopTime on the uDNS question 0x12d052ee8 <mask.hash: 'wSjsuyOuBULV+n0q4hvt6g=='> (Addr)
 33904  default	09:09:22.396939-0500	mDNSResponder	[R783->Q32359] Question for <mask.hash: 'wSjsuyOuBULV+n0q4hvt6g=='> (Addr) assigned DNS service 10
 .....
 33908  default	09:09:22.397845-0500	mDNSResponder	[R783->Q41400] DNSServiceQueryRecord(<mask.hash: 'Zt0Dfjkfx+hqh/cHBsrRZA=='>, Addr) RESULT ADD interface 0: (mortal)<mask.hash: 'FZFu42G57UktPrvr3UXg+w=='>
 33909  default	09:09:22.398360-0500	mDNSResponder	NEHelperTrackerAddIPForAllFlows: completed for app <3204 : c503c325-b8b3-3347-a7d9-a23f985c05ae> <app approved 0> <is_tracker 0>
 33910: default	09:09:22.398627-0500	mDNSResponder	[R784] DNSServiceQueryRecord(1D000, 0, <mask.hash: 'CoyLiMJQSrpXFOpv0J8zIA=='>, AAAA) START PID[3204](curl)
 33911  default	09:09:22.400837-0500	mDNSResponder	[Q38525] InitDNSConfig: Setting StopTime on the uDNS question 0x12d8670e8 <mask.hash: 'wSjsuyOuBULV+n0q4hvt6g=='> (AAAA)
 33912  default	09:09:22.400906-0500	mDNSResponder	[R784->Q38525] Question for <mask.hash: 'wSjsuyOuBULV+n0q4hvt6g=='> (AAAA) assigned DNS service 10
 .....
 33915  default	09:09:22.402347-0500	mDNSResponder	[R784->Q38525] DNSServiceQueryRecord(<mask.hash: 'wSjsuyOuBULV+n0q4hvt6g=='>, AAAA) RESULT ADD interface 0: (mortal)<mask.hash: 'OO9mkVDVIpCZBZePhqX+rg=='>
 33916  error	09:09:22.403017-0500	kernel	129 duplicate reports for Sandbox: com.apple.WebKit(942) deny(1) mach-lookup com.apple.diagnosticd
 33917: error	09:09:22.403042-0500	kernel	System Policy: curl(3204) deny(1) system-privilege 10006
 33918: default	09:09:22.406055-0500	mDNSResponder	[R783] DNSServiceQueryRecord(1D000, 0, <mask.hash: 'Zt0Dfjkfx+hqh/cHBsrRZA=='>, Addr) STOP PID[3204](curl)
 33919: default	09:09:22.406183-0500	mDNSResponder	[R784] DNSServiceQueryRecord(1D000, 0, <mask.hash: 'wSjsuyOuBULV+n0q4hvt6g=='>, AAAA) STOP PID[3204](curl)
 33920  default	09:09:22.680341-0500	Safari	[0x140830a00] CVDisplayLinkStart
 33921  default	09:09:22.680449-0500	Safari	[0x140830a20] CVDisplayLink::start
 .....
 33931  default	09:09:23.188817-0500	Safari	0x1090048d0 - [PID=0, throttler=0x10906d8d8] ProcessThrottler::Activity::Activity: Starting background activity / 'RemoteObjectRegistry invocation'
 33932  default	09:09:23.190171-0500	Safari	0x1090048d0 - [PID=0, throttler=0x10906d8d8] ProcessThrottler::Activity::invalidate: Ending background activity / 'RemoteObjectRegistry invocation'
 33933: error	09:09:23.227658-0500	kernel	1 duplicate report for System Policy: curl(3204) deny(1) system-privilege 10006

Answered by Hoffman in 741505022

Update your Mac from macOS 12.3 to macOS 12.6.2; to the current version of macOS.

Then check whether Terminal.app and probably also sh (if that's offered in your case) are enabled for Full Disk Access in System Preferences.

System Preferences > Security & Privacy > Unlock the Lock > Privacy > Full Disk Access > check some boxes

Boost

Answer 1

simplysecuriti OP

Jan ’23

Is curl trying to write to a write-protected sandboxed location?

curl(3204) deny(1) system-privilege 10006

This clearly shows that the sandbox is killing curl. The error code when matched to the XNU source here

#define PRIV_NET_PRIVILEGED_NECP_MATCH          10006   /* Privilege verified by Network Extension policies */

There is also a related thread with someone facing the same error code as you, perhaps this may help: List of system privileges

0

Answer 2

Hoffman OP

Jan ’23

Accepted Answer

Update your Mac from macOS 12.3 to macOS 12.6.2; to the current version of macOS.

Then check whether Terminal.app and probably also sh (if that's offered in your case) are enabled for Full Disk Access in System Preferences.

System Preferences > Security & Privacy > Unlock the Lock > Privacy > Full Disk Access > check some boxes

0