From anay@sun.com Mon Nov 20 09:46:28 2006 Date: Mon, 20 Nov 2006 09:42:56 -0800 From: "Anay S. Panvalkar" User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) To: Gary Winiger CC: craig.payne@sun.com, leo.binchy@sun.com, artem.kachitchkin@sun.com Subject: Re: Contract for Hal/D-Bus use of audit interfaces Content-Transfer-Encoding: 7bit Status: RO X-Lines: 180 Content-Type: text/plain; charset="ISO-8859-1"; format="flowed" Content-Length: 7343 Gary Winiger wrote: > Please reply to me that you accept this contract or offer changes > that would make it acceptable. I approve this contract. -Anay From Leo.Binchy@Sun.COM Mon Nov 20 17:33:01 2006 Date: Tue, 21 Nov 2006 01:29:14 +0000 From: Leontine Binchy Subject: Re: Contract for Hal/D-Bus use of audit interfaces To: Gary Winiger Cc: Craig.Payne@Sun.COM, Anay.Panvalkar@Sun.COM, Artem.Kachitchkin@Sun.COM Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0a1 (X11/20061107) X-Lines: 23 Status: RO Content-Type: text/plain; format="flowed"; charset="ISO-8859-1" Content-Length: 600 accept Gary Winiger wrote: > Leo, > > >> In question 7 you have stated all of the cases are not applicable, I >> assume 7 (c) is applicable >> > > I missed splitting 7c for the two consumers. I'll note 7c for > CONSUMER a is N and vor CONSUMER b is Y. > > Beyond that please reply if you accept. > > Gary.. > > _N_ 7c. Although the stability level doesn't normally allow it, CONSUMER a > will import INTERFACES from a separate consolidation. > > _Y_ 7c. Although the stability level doesn't normally allow it, CONSUMER b > will import INTERFACES from a separate consolidation. > From Craig.Payne@Sun.COM Wed Nov 22 12:02:42 2006 Date: Wed, 22 Nov 2006 11:58:17 -0800 From: Craig Payne Subject: Re: Contract for Hal/D-Bus use of audit interfaces To: Gary Winiger Cc: Anay.Panvalkar@Sun.COM, Leo.Binchy@Sun.COM, Artem.Kachitchkin@Sun.COM Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.5 (X11/20060925) X-Lines: 191 Status: RO Content-Type: text/plain; format="flowed"; charset="ISO-8859-1" Content-Length: 7877 Accepted - with the mods to 7c we see in the history. cap -- Craig Payne Manager, Security Technologies Kerberos & Hardening/Integrity (510) 550-7413 x30176 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES 0. Number: PSARC/2000/517-09 1. This contract is between a SUPPLIER of INTERFACES and a CONSUMER of those INTERFACES, both of whom are entities within Sun Microsystems, Incorporated. 2. The SUPPLIER (definer and/or implementor) is identified by the following: Product or Bundle: Solaris Audit Consolidation: ON Department or Group: Solaris Security Bugster Product/Category/SubCategory: solaris/c2_bsm/other Responsible Manager: Craig Payne 3a. The CONSUMER is identified by the following: Product or Bundle: HAL Consolidation: ON Department or Group: Approchability (KISS) Bugster Product/Category/SubCategory: solaris/utility/hal Responsible Manager: Anay Panvalkar 3b. The CONSUMER is identified by the following: Product or Bundle: Solaris Desktop Consolidation: JDS Department or Group: OPG Desktop Bugster Product/Category/SubCategory: jds/gnome/libraries Responsible Manager: Leo Binchy 4a. The INTERFACES for HAL are: A. The Project Private header files and B. The Project Private adt.h interfaces and symbols: adt_start_session(, , 0); adt_end_session(); adt_alloc_event(); adt_free_event(); adt_put_event(, [ADT_SUCCESS for success | ADT_FAIL for error], [ADT_SUCCESS for success | ADT_FAIL_VALUE_AUTH for error]); C. The Project Private adt_event.h audit events and symbols: ADT_attach, ADT_detach with required char * members auth_used, mount_point, device and optional char * member options ADT_remove with required char * members auth_used, device and optional char * member mount_point ADT_pool_import, ADT_pool_export with required char * members auth_used, pool, device 4b. The INTERFACES for Dbus are: A. The Project Private header files B. The Project Private adt.h interfaces and symbols: adt_start_session(, NULL, 0); adt_set_from_ucred(, , ADT_NEW); adt_export_session_data(); adt_end_session(); 5. The ARC controlling these INTERFACES is: PSARC 6. The CASE describing (Exporting) these INTERFACES is: 2000/517 and 2003/397 7. The following SPECIAL ARRANGEMENTS are made which modify the rules imposed by the stability levels listed in section 4 above: _N_ 7a. Although the stability level doesn't normally restrict it, SUPPLIER promises to only modify INTERFACES in an incompatible way as follows: _N_ 7b. Although the stability level doesn't normally allow it, CONSUMER will expose INTERFACES to a PARTNER, which is external to Sun, namely: Name of Company: Name of Department or Group within Company: Responsible Manager: _N_ 7c. Although the stability level doesn't normally allow it, CONSUMER a will import INTERFACES from a separate consolidation. _Y_ 7c. Although the stability level doesn't normally allow it, CONSUMER b will import INTERFACES from a separate consolidation. _N_ 7d. If SUPPLIER decides to change (including replace or remove) any portion of the INTERFACES, SUPPLIER will notify CONSUMER of the proposed new version, no later than the application for ARC approval of the new version. If SUPPLIER and CONSUMER are contained in the same consolidation, they have the option of arranging for simultaneous conversion to the new interfaces. If this is not possible, or if they are not in the same consolidation, then SUPPLIER will either make best effort to work with CONSUMER so that CONSUMER can detect which version of INTERFACES is being supplied, or else SUPPLIER will make best effort to supply both old and new versions of INTERFACES. If SUPPLIER cannot make both versions of INTERFACES available, and SUPPLIER and CONSUMER cannot devise a method whereby CONSUMER can detect which version of INTERFACES is being supplied, and the old version of CONSUMER will not run with the new version of SUPPLIER, then either the EOL process must be followed by SUPPLIER, or else a major release of SUPPLIER will be required, or the change will not be allowed. 8. If CONSUMER requires changes in INTERFACES, SUPPLIER will make best effort to accommodate such changes, which shall then be treated in accordance with paragraph 7 above. 9. Notwithstanding paragraphs 7 and 8, a change to any portion of the INTERFACES shall be regarded as a completely new set of INTERFACES which require both ARC approval and execution of a new contract. 10. SUPPLIER and CONSUMER agree that evolution of INTERFACES shall be handled as follows: SUPPLIER will notify CONSUMER of changes that may affect the CONSUMER not less than two ON consolidation builds before the changes are integrated. CONSUMER may request changes to the INTERFACES by filing RFEs using the Bugster Product/Category/SubCategory specified in paragraph 2. The SUPPLIER will review the CONSUMER's RFEs based on their priority and severity and either accept them in the normal queue of work or notify the CONSUMER through the normal Bugster process that the request has been rejected and rationale for the rejection. 11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as follows: The CONSUMER may submit bugs against the interfaces using the Bugster Product/Category/SubCategory specified in paragraph 2. The SUPPLIER will fix bugs based on their priority and severity. 12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as follows: In the supplied and header files and in the case directory /net/sac.eng/export/sac/PSARC/2000/517/latest.docs/*3BSM 13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be tested as follows: The SUPPLIER will do initial unit testing. The CONSUMER will create an audit trail or trails with each of the audit events generated. The SUPPLIER will verify the audit records are correctly generated. 14. SUPPLIER and CONSUMER agree that this contract can be terminated as follows: By agreement of both parties. 15. This contract is not valid until "signed" via agreement from the SUPPLIER and CONSUMER, and approved by the ARC CASE referenced by this contract. E-mail agreement to the contract should be archived in the mail archive of CASE; verbal agreement to the contract should be noted in the meeting minutes. This contract remains valid until superseded or invalidated. For SUPPLIER: Craig Payne Date: 22 November, 2006 For CONSUMER a: Anay Panvalkar Date: 20 November, 2006 For CONSUMER b: Leo Binchy Date: 20 November, 2006 For ARC: Gary Winiger Date: 22 November, 2006 A copy of this contract shall be deposited in the CASE directory as "contract-09" or in a "contracts" subdirectory. 16. (Not to be filled in until superseded or invalidated.) This contract was superseded or invalidated by CASE: For ARC: Date: