I have two processes that talk to each other using an NSXPCConnection. If I want to pass sensitive data over the connection, should I be worried about it being intercepted or read by other processes? Should I encrypt any sensitive data before sending it over the connection and have the other process have to decrypt it?
I have updated my projects to Swift 5 and as such, we have modified our Applications to require macOS 10.14.4 or newer to avoid having to require our customers to install the "Swift 5 Runtime Support for Command Line Tools". I would also like to take advantage of not including the Swift libraries in our apps as well.
In XCode, it only lets me set the deployment target by the os minor version. (ie. 10.13, 10.14, 10.15). If I select 10.14, it adds the swift libraries. If I select 10.15, it does not. This is a difference of 11.4 MB per target. We still need to support 10.14.4 and newer 10.14.x versions as many of our customers still use them.
Is there a way/setting to select 10.14 as the deployment target and not include the swift libraries during the build/signing/notarization process?
Post not yet marked as solved
Is there any apple recommended steps for a developer to follow when deciding to EOL their app in the app store? Is there an article or documentation somewhere? Do we need to provide refunds for recent purchases?
Post not yet marked as solved
I am attempting to pop up a window or alert on the login screen. If after the user inputs their password incorrectly X amount of times, we want to display a message. All of my attempts to display the window/alert appear behind the loginwindow.
I've tried setting the window.level to Int32.max and some other high values near that. It makes it the top most window behind the loginwindow and on top of everything else. If I go higher than that (somewhere in the Int64 range), it makes it the bottom most window behind everything else on the desktop.
I've also tried running a script to tell loginwindow to display an alert. It pops up, but still not over the loginwindow screen, and keyboard input isn't allowed (just get beeps) until the user hits "enter" to close the non-visible alert. Not to mention that it also requires a privacy approval for my process to access loginwindow by the user beforehand.
I've also tried setting the lock message by writing to the defaults.
sudo defaults write /Library/Preferences/com.apple.loginwindow LoginwindowText "My login window message"
But, haven't been able to get loginwindow to reload/re-read the defaults value once it is already being displayed. Is that even possible?
Any other suggestions?
Is there an API or System Notification we can register for in order to get notified when an invalid login occurs? I want to be able to track the number of times in a row a user has tried to unlock the device but supplied invalid credentials/thumbprint. I've been trying to go through the system logs to see if I can track them there, however I've run into problems with that:1) If I manually lock my computer, then log in correctly, I still see messages by opendirectoryd saying there were authentication failures. 2 usually appear right as I lock the device. And even when logging in cortrectly, another authentication failiure appears as well. 2) I've tried looking at logs from loginwindow, coreauthd, apsd, etc. But, haven't found anything reliable and/or consistent across different versions of OS X.
tagnal.