Posts

Post not yet marked as solved
3 Replies
981 Views
Hi,mainly for iOS, is it possible to call SecKeyCreateRandomKey with parameters so that using that private key will- promp the user for touch id- disallow changing touch id sets- falls back to application password (NOT device code)- keep the private key inside the enclaveBasically just likeSecAccessControlCreateWithFlags(kCFAllocatorDefault, kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly, kSecAccessControlTouchIDCurrentSet | kSecAccessControlPrivateKeyUsage | kSecAccessControlApplicationPassword , &error);but not in the way that it first asks for touch and then asks for the password regardless of touch being successful.Cheers,Andreas Pardeike
Posted
by a.p.
Last updated
.
Post not yet marked as solved
5 Replies
1.3k Views
As a large organisation, we have the problem that we cannot put a policy on which devices are being registered as development devices by connection them to Xcode. Basically anyone with a registered account can connect and accept the request from Xcode which makes it hard to enforce a policy that would limit the total number of devices to 100. Is there a way to intercept/prevent either The process in Xcode The overall USB connection of certain devices Our macOS and iOS hardware is MDM managed and we should be able to install custom daemon processes in macOS in case that would help. Any advice appreciated, Andreas Pardeike
Posted
by a.p.
Last updated
.