I have added the slides to the deck for tomorrow. Praveen will also be doing AJATS training after the regular meeting and before triage. Given there are only handful of issues that need attention I don't think we will need the full hour and expect Praveen to use some of the normally scheduled triage time.
From: Daniel Mihai [mailto:[email protected]] Sent: Wednesday, January 27, 2016 2:05 PM To: Pawel Winogrodzki; [email protected]; [email protected]; Swinson, Ken; Dave Thaler; Lioy, Marcello; Malsbary, Todd Cc: Arvind Padole Subject: RE: New C++ API and C wrappers Hi everyone, We would like to discuss in the Core WG meeting tomorrow, and hopefully get approved, the changes proposed by Pawel. Thanks, Dan From: Pawel Winogrodzki Sent: Wednesday, January 20, 2016 5:44 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; Dave Thaler <[email protected]<mailto:[email protected]>> Cc: Daniel Mihai <[email protected]<mailto:[email protected]>>; Arvind Padole <[email protected]<mailto:[email protected]>> Subject: New C++ API and C wrappers Hi, I'm a new dev at Microsoft working with Daniel Mihai. We would like to introduce wrappers for the C++ APIs responsible for Security 2.0 support plus a few C++ APIs that would allow to set manifest templates and ACLs from XMLs. Please speak up with any questions or feedback. 1. The new C++ APIs would be: a. PermissionPolicy::CreateManifestFromXml - this will create a list of rules that can be passed to the existing API to set the app's manifest template. b. PermissionPolicy::CreateManifestXmlFromRules - the reverse of the above method. c. PermissionConfigurator::SetPermissionManifestFromXml - allows to set the manifest template from an XML. d. PermissionPolicy::CreatePolicyFromXml - will set the PermissionPolicy contents from an XML. 2. C wrappers for the following C++ APIs: a. BusAttachment: i. GetPermissionConfigurator; ii. RegisterApplicationStateListener; iii. UnregisterApplicationStateListener; iv. AddApplicationStateRule; v. RemoveApplicationStateRule; b. PermissionConfigurator: i. GetApplicationState; ii. SetApplicationState; iii. GetClaimCapabilities; iv. SetClaimCapabilities; v. GetClaimCapabilityAdditionalInfo; vi. SetClaimCapabilityAdditionalInfo; vii. SetPermissionManifestFromXml - one of the new APIs from #1; c. ApplicationStateListener: i. State callback - for now will accept key information encoded in PEM format. ii. Constructor and destructor; d. SecurityApplicationProxy: i. Constructor and destructor; ii. Claim - input keys and certs will be encoded in PEM format. iii. GetManifestTemplate (plus a destructor function for the result of this wrapper) - will return the template in the XML format. iv. GetApplicationState; v. GetClaimCapabilities. vi. GetClaimCapabilitiesAdditionalInfo; vii. UpdatePolicy; viii. UpdateIdentity; ix. InstallMembership; x. Reset; xi. ResetPolicy; xii. GetEccPublicKey (plus a destructor function for the result of this wrapper); For all of these I will also write unit tests. Thanks, Pawel Winogrodzki
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
