SecCodeCheckValidityWithErrors(_:_:_:_:)

Declaration

func SecCodeCheckValidityWithErrors(_ code: SecCode, _ flags: SecCSFlags, _ requirement: SecRequirement?, _ errors: UnsafeMutablePointer<Unmanaged<CFError>?>?) -> OSStatus

Parameters

• code:

  The code object to be validated.

• flags:

  Optional flags; see Seccsflags for possible values. Pass kSecCSDefaultFlags for standard behavior.

• requirement:

  A code requirement specifying additional conditions the code must satisfy to be considered valid. Specify NULL if you don’t want to impose any additional requirements. Use the Secrequirementcreatewithstring(_:_:_:) or Secrequirementcreatewithstringanderrors(_:_:_:_:) function to create a code requirement object. See TP40005929 for a discussion of code requirements.

• errors:

  On return, if the function call fails and returns a result code other than Errsecsuccess, points to an error object further describing the nature and circumstances of the failure. Use the Cferrorcopyuserinfo(_:) function to retrieve the user info dictionary from the error object. See User Info Dictionary Error Keys for possible values. Pass NULL if you do not want this information. In Objective-C, call the Cfrelease function to release this object when you are finished with it.

Return Value

A result code. See Code Signing Services Result Codes.

Discussion

This function obtains and verifies the signature on the code specified by the code object. It checks the validity of only those sealed components required to establish identity. For guest code, first the function checks the code object’s dynamic validity status as reported by its host, then it ensures that the code object’s host is in turn valid. For all code, it validates the code against a code requirement if one is specified. The call succeeds if all these conditions are satisfactory.

This function is secure against attempts to modify the file system source of the code object.