https://www.evernote.com/shard/s2/sh/ae94f399-207a-4d89-bdf6-7700fe1efb8a/bb9a7e8e35564ababf8f232184bbffea

When I try to "Always trust" the certificate from my computer at work and click continue, I cannot enter my administrator password and it freezes other apps on my computer.  I am not able to even restart the machine without forcing it with the power button.

Hi,

Do you mean that your Mac freezes when you trust the certificate? If so, it seems that your Mac cannot add the certificate to the system roots and I would like to suggest you contact Apple support for help.

Thanks.

The same thing is happening to me. When I attempt to trust the certificate the OS privilege escalation dialog appears to enter my password and I lose the ability to type and get to other dialogs below it and have to hard reboot. No other apps suffer from this problem, so I would wager that it is something specific to Remote Desktop.

I too get this issue. 

I am using  MS Remote Desktop Version 8.0.7 (Build 24875) on OSX 10.9.3. This has happened to previous versions MSRD. 

This is the logs at the time of the freeze. 

[2014-Jun-05 09:21:14] RDP (0): --- BEGIN INTERFACE LIST ---

[2014-Jun-05 09:21:14] RDP (0): lo0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): lo0 af=30 (AF_INET6)  addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

[2014-Jun-05 09:21:14] RDP (0): lo0 af=2 (AF_INET)  addr=127.0.0.1 netmask=255.0.0.0

[2014-Jun-05 09:21:14] RDP (0): lo0 af=30 (AF_INET6)  addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::

[2014-Jun-05 09:21:14] RDP (0): gif0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): stf0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): en1 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): fw0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): en2 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): en0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): en0 af=30 (AF_INET6)  addr=fe80::aa20:66ff:fe43:f95d%en0 netmask=ffff:ffff:ffff:ffff::

[2014-Jun-05 09:21:14] RDP (0): en0 af=2 (AF_INET)  addr=10.10.1.25 netmask=255.255.255.0

[2014-Jun-05 09:21:14] RDP (0): bridge0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): p2p0 af=18  addr= netmask=

[2014-Jun-05 09:21:14] RDP (0): --- END INTERFACE LIST ---

[2014-Jun-05 09:21:14] RDP (0): ----- BEGIN ACTIVE CONNECTION -----

[2014-Jun-05 09:21:14] RDP (0): client version: 8.0.24875

[2014-Jun-05 09:21:14] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)

[2014-Jun-05 09:21:14] RDP (0): correlation id: 474ced09-8d6c-9a47-8e3f-54b44bc90000

[2014-Jun-05 09:21:14] RDP (0): Resolved '10.10.0.166' to '10.10.0.166' using NameResolveMethod_DNS(1)

[2014-Jun-05 09:21:14] RDP (0): Protocol state changed to: ProtocolNegotiatingCredentials(2)

[2014-Jun-05 09:30:16] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)

[2014-Jun-05 09:30:16] RDP (0): Protocol state changed to: ProtocolDisconnected(8)

[2014-Jun-05 09:30:16] RDP (0): ------ END ACTIVE CONNECTION ------

[2014-Jun-05 09:30:23] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)

[2014-Jun-05 09:30:29] RDP (0): Protocol state changed to: ProtocolDisconnected(8)

[2014-Jun-05 09:30:29] RDP (0): *** Application terminated ***

Should add the only way I get it to terminate is to physically restart. 

• Edited by awsawyer Thursday, June 05, 2014 1:43 PM

I experience the exact problem as the above users. My MacBook will freeze occasionally when accepting certificates via Microsoft Remote Desktop. It does not always happen. The only solution is to power off the macbook with the power button and restarting. I am running OS 10.9.3 with Microsoft Remote Desktop 8.0.7.

Same exact errors as above. Happened in the last two versions of Remote Desktop. I am running 8.0.7 build 24875, and OS X 10.9.3. I have used the program from my desktop Mac Pro, and my laptop, an MBP 17, and the problem exists in both. (Same level of RDP and OS X).

This hang requires a "hard power off" to clear. I get the spinning beach ball. I note that in the certificate manager, it is definitely the RDP program since it is the RDP icon in the top left corner of the security certificate acceptance screen.

Another way out of the loop is to quit the Remote Desktop app and "kill -9" the pid to SecurityAgent

I too am having this problem. I only experience it with Microsoft Remote Desktop, so I'm inclined to think that it may be a bug with Microsoft's app.

I'm able to kill the hung process with:

sudo pkill SecurityAgent

...but it's still annoying. 

My OS version is OS X 10.9.4 and the Microsoft Remote Desktop verison is 8.0.9 (Build 25073)

• Edited by bmsdfqz Tuesday, September 16, 2014 9:08 PM

I have just had the exact same issue - RDP 8.0.9 on Mavericks 10.9.5.

It started happening after I deleted some certificate from my KeyChain. Clever idea, I know, but a bunch were expired and I kept getting certificate confirmations in Remote Desktop so I wanted a clean slate to reset everything and then accept the certificates I needed. This failed miserably.

(As a side note, the reasons for the certificate warnings where things like we have a wildcard cert for *.ourcompany.co.uk, but within our LAN we connect to the servers via their local //computername/ DNS entry, or connecting to our webserver via ourcompany.co.uk, but the certificate being for it's LAN computer name. This meant the certs didn't match and I'd have to okay each time.)

What (I think!) I did to fix it was:

- Open up KeyChain, on the left select the 'login' Keychain then the 'Certificates' category.
- In the list on the right, find the certificates you use for Remote Desktop (e.g. mine are like server.company.local, *.company.co.uk, id678263).
- Double click each one, open up the '> Trust' section near the top, and ensure 'X.509 Basic Policy' is set to 'Always Trust'.

Now if I open up Remote Desktop I don't get any warning, nor does it freeze.

I did reinstall Remote Desktop before the above to try and get it working, and chuck in a couple restarts. I don't think that's necessary (and remember to export your connections unless you want to enter them all again!) but it doesn't hurt to try.

Thanks for the tip on killing the securityagent process.  Saves me from rebooting the entire computer as simply killing remote desktop app was not doing it.

Seems like there is definitely a bug here.  

I have OS X 10.9.5 and Remote desktop version 8.0.9 (Build 25073).  

I have been having same thing happen but I'm not so sure it is specifically a remote desktop problem as I had the same issue yesterday when I tried to add a certificate for Charles. http://raptureinvenice.com/getting-the-charles-debugging-proxy-to-work-with-ios-and-genymotion/ so I'm thinking it must be happening with adding / changing any certificates.

This seems to be fixed for me. I followed the last answer on http://apple.stackexchange.com/questions/94722/mac-os-x-10-7-5-keychain-hangs-forever and deleted all my expired certificates and I no longer have the issue.

This is happening to me too, several times a week

@ bmsdfq Thanks thanks for the Terminal tip, I tried Activity Monitor but that locked up too. Have been having to force reboot. I'll try the other suggestions here and report back.

• Edited by GregMills Tuesday, October 07, 2014 10:20 PM

This happens to me. It appears to happen even on 10.10.3 only if iCloud keychain is enabled for the current logged in user. Without iCloud keychain this is a non issue. Also, it usually works the first time, but the second or third kills the system. It seems to make it so that currently running apps seem to work fine for a while, but new processes don't launch correctly or work. If you happen to get terminal running quickly enough, you can do a sudo shutdown -r now and this will reboot, but not always. I'm reporting it here and to Apple but I suspect it is this app which needs an API update or something to account for iCloud keychain.