Thanks for posting, can confirm that this helps and is certainly the quicker workaround than rebooting. Will try to see if I can move the issue I created with the .NET people to a more appropriate repository.
Even so, the underlying cause is the OS upgrade, since .NET executables didn't change at the time, even though it only seems to appear with .NET. Will be interesting to see if any other access patterns appear through a different set of binaries
FrankQ
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Freiburg im Breisgau, Deutschland
Post
Replies
Boosts
Views
Activity
It asked me to "Allow", "Always Allow" - it seemed to work. Can I maybe revoke that somewhere and then save myself the reboot cycle?
"A problem with the keychain itself" - are there any procedures to mitigate that?
The code is running in the context of a process running under the "dotnet" executable. See also my answer.