Re: [cifs-protocol] CAR - ldap display specifiers
Hi Bill, Thanks for the LDIF! Can we assume the license on this is the same as for the schema? For the schema the version we got from MS had the license at the top, which you can see here: For the schema license, see this: http://samba.org/ftp/unpacked/samba_4_0_test/source4/setup/ad-schema/MS-AD_Schema_2K8_Classes.txt I'm pretty sure you intend us to just use the same license, but I thought I should check. Cheers, Tridge ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
You're completely welcome. The notice in the schema is not exactly the same as what is in our current document postings. For the moment, however, the below text is the notice I have been advised should apply. I will ask for additional clarification on this today, since I think it would be *not a good idea* to make any assumptions about, given the textual discrepancies between the below and that provided in the schema. Intellectual Property Rights Notice for Open Specifications Documentation o Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. o Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. o No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. o Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described n the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting i...@microsoft.com. o Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. o Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. Regards, Bill Wesse MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM 8055 Microsoft Way Charlotte, NC 28273 TEL: +1(980) 776-8200 CELL: +1(704) 661-5438 FAX: +1(704) 665-9606 -Original Message- From: tri...@samba.org [mailto:tri...@samba.org] Sent: Friday, July 17, 2009 5:39 AM To: Bill Wesse Cc: cifs-proto...@samba.org; m...@samba.org Subject: RE: CAR - ldap display specifiers Hi Bill, Thanks for the LDIF! Can we assume the license on this is the same as for the schema? For the schema the version we got from MS had the license at the top, which you can see here: For the schema license, see this: http://samba.org/ftp/unpacked/samba_4_0_test/source4/setup/ad-schema/MS-AD_Schema_2K8_Classes.txt I'm pretty sure you intend us to just use the same license, but I thought I should check. Cheers, Tridge ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
[cifs-protocol] Information needed about security token default ACL
Hi, In the course of my work in implementing security descriptor inheritance in Directory service of Samba 4, I came across the following statement in MS-DTYP, 2.5.2 The token also contains an ACL, Token.DefaultDACL, that serves as the DACL assigned by default to any objects created by the user. So, am I right to understand that this DACL is used when no nTSecurityDescriptor is provided by the incoming LDAP add request, and there is no defaultSecurityDescriptor for the objectClass. If so, how is the Token.DefaultDACL constructed and when? Is this based on the user's credentials and how? In addition, I have a question about the security descriptor creation algorithm described in MS-DTYP 2.5.2.3 One of the arguments of CreateSecurityDescriptor is: CreatorDescriptor: Security descriptor for the new object provided by the creator of the object. Caller can pass NULL. Am I right in understanding that this is either the nTSecurityDescriptor attribute provided by the user, or, in the lack thereof, the defaultSecurityDescriptor of the object class? Best Regards, Nadezhda Ivanova ___ cifs-protocol mailing list cifs-protocol@cifs.org https://lists.samba.org/mailman/listinfo/cifs-protocol
Re: [cifs-protocol] CAR - ldap display specifiers
Tridge - every out of band release has a unique Intellectual Property notice. So the notice that was included in the schema is unique, and pertains only to the schema release that we provided (it can be obtained on the 'Microsoft Open Specification Support Team Blog' blog at): Using the Windows Server Protocols documentation set to better understand the Active Directory Schema http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the-windows-server-protocols-documentation-set-to-better-understand-the-active-directory-schema.aspx Once document development has detailed the precise nature of the final data we will be supplying, an IP notice will be attached! Regards, Bill Wesse MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM 8055 Microsoft Way Charlotte, NC 28273 TEL: +1(980) 776-8200 CELL: +1(704) 661-5438 FAX: +1(704) 665-9606 -Original Message- From: Bill Wesse Sent: Friday, July 17, 2009 7:18 AM To: 'tri...@samba.org' Cc: cifs-proto...@samba.org; m...@samba.org Subject: RE: CAR - ldap display specifiers You're completely welcome. The notice in the schema is not exactly the same as what is in our current document postings. For the moment, however, the below text is the notice I have been advised should apply. I will ask for additional clarification on this today, since I think it would be *not a good idea* to make any assumptions about, given the textual discrepancies between the below and that provided in the schema. Intellectual Property Rights Notice for Open Specifications Documentation o Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. o Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. o No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. o Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described n the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting i...@microsoft.com. o Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. o Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. Regards, Bill Wesse MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM 8055 Microsoft Way Charlotte, NC 28273 TEL: +1(980) 776-8200 CELL: +1(704) 661-5438 FAX: +1(704) 665-9606 -Original Message- From: tri...@samba.org [mailto:tri...@samba.org] Sent: Friday, July 17, 2009 5:39 AM To: Bill Wesse Cc: cifs-proto...@samba.org; m...@samba.org Subject: RE: CAR - ldap display specifiers Hi Bill, Thanks for the LDIF! Can we assume the license on this is the same as for the schema? For the schema the version we got from MS had the license at the top, which you can see here: For the schema license, see this:
