yeah... but how many stories are advertisement, and not news? Personally, and this is just personal, so don't read into this too much, this
was advertisement
Is that enough html for you? Because you seem to have lost the copy/paste functionality within your operating system in order to copy/paste a link with...
But at the same time, if AOL were concerned about spam, why do you have to dig deep into the softwares settings to stop recieving AOL sponsored e-mail advertisements, and pop-ups, and then have to mail them via the postal office to stop any other advertisement?
Hmm.. this could be changed up though, think about it for a second.. sed and awk are on macs by default right? and if not, it could be included in the packager (ok, so I am reinstalling OSX on my iBook as we speak, I was.. disatisfied with how I partitioned everything)
You could ls -al the passwd file, and see what the current users shell is, and say it's bash, grep for the config files, if they are present, then add the line to it, and export the file. Wouldn't be all that (yeah, like I could do this, yeesh! but I know some people could do it..)
You could specify if you want the current user, a user with administrative rights, or the root user to do this. After that, you're pretty much done, it changes those files, then updates itself if you say yes, go ahead and check for updates. Then it asks if you would like a gui for this, and gives you a link to finkcommander.sourceforge.net if you do.
First off, they finished this yesterday, actually got it yesterday in the irc chan on irc://irc.openprojects.net in #fink. It's really a cool installer, even detects if you have an old install and what not.
Second, there is a gui for this, http://finkcommander.sourceforge.net/
It has buttons to e-mail a developer if a package is working for you, and also shows columns for if this package is out of date, or up to date, etc. It's searchable, and really cool. It doesn't require X11, it's a native apple app!
Other than that, I would like to congratulate all the people involved, for the hard work they have put into this. It's a very awesome thing.
Disclosure for the most part, is a good thing. Even with things such as smb, whereas the samba team found a way to shut down a server remotely with it, aren't disclosed, unless there is a threat of disclosure, in which you need to go ahead and patch your hole or you will be seen as, well, uncaring by those who care.
This also allows for faster knowledge, i.e., if there is an active mailing list on it, but I am not on that list, then iss will inform me of the problem, this is in the mailing list, or whatever form of communication said project uses.
The Cons
As mentioned in comments already, I am assuming, people will be able to blackmail one another in order to keep said hack/hole/easter bunny out of the lime light. A little bit of cash can go a long way sometimes. Be wary of what is, and what isn't, reported.
Why this is important to you:
It gives you a more defined description of how things are going to go, and how much salt grain you should take with each hack. You should know that each hack/hole out there has already been out there for a month, and that it could have been out there for a lot longer. Joe blackhat just doesn't give up his tools, unless they are not useful.
Why this is not important:
ISS is not the only security site, and it should not be your only site to get updates from, either. Do a google...
Dude, not to be off topic, but robert jordan is awesome! When is his new book supposed to come out, every time I go by bn or anything like that, they say it's not out.
Re:Great, except I don't want to make a Mac QWZX
on
Review: EyeTV
·
· Score: 1
Actually, a keyboard from apple costs 59 dollars usd. You can get it in black or white, from here: http://store.apple.com/1-800-MY-APPLE/WebObjects/A ppleStore.woa/144/wo/WZetV0ZSyQSIhPLKsI/0.3.0.3.27.7.0.CoverPageLeftAccessoriesPromo.1.1.0.3.1.5.17. 3.1.1.0
Also, you can use any usb keyboard, mouse with your apple. I use a microsoft mouse with my iBook, the wireless intellimouse explorer. It's very nice, except for the battery consumption.
Why not split the platforms, and hire a few more people? I know, I know, this doesn't seem feasible, right? But if you were able to split the code into what it would actually work on, say you have yourself and joe working windows, you guys just work on windows, and have all the code that works within that ide. Jan and Sue, with help from the janitor Steve, are all working on the irix side, etc, etc, etc. It would seem more feasible than actually working all these different platforms together at once? And what about mac, is there a demand for that as well? Would be a good time to look into it...
UNITED STATES OF AMERICA, Plaintiff, v. MICROSOFT CORPORATION, Defendant. UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA Civil Action No. 98-1232 (CKK) ORDER Presently pending before the Court is a proposed consent decree submitted by the parties in the above-captioned case. Following application of the Tunney Act, 15 U.S.C. 16(b)-(h), and upon a finding pursuant 15 U.S.C. 16(e) that, with the exception of VII of the proposed final judgment ("SRPFJ"), entry of the SRPFJ as the final judgment in this action is in the public interest, as set forth in the accompanying Memorandum Opinion, it is this 1st day of November, 2002, hereby ORDERED that the SRPFJ is conditionally approved as the final judgment in this case; and it is further ORDERED that, in order to obtain final approval of the SRPFJ, Plaintiff and Microsoft shall submit to the Court a proposed amendment to VII addressing the concerns described in the accompanying Memorandum Opinion; and it is further ORDERED that such proposed amendment shall be submitted to the Court not later than November 8, 2002. SO ORDERED. _____________________________ COLLEEN KOLLAR-KOTELLY United States District Judge
STATE OF NEW YORK, et al., Plaintiffs v. MICROSOFT CORPORATION, Defendant. UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA Civil Action No. 98-1233 (CKK) FINAL JUDGMENT The Plaintiff States of California, Connecticut, Florida, Iowa, Kansas, Minnesota, Utah, and West Virginia, the Commonwealth of Massachusetts, and the District of Columbia, having filed their complaints in this action on May 18, 1998; Defendant Microsoft Corporation ("Microsoft") having appeared and filed its answer; The Court having entered Findings of Fact on November 5, 1999 and Conclusions of Law on April 3, 2000; The United States Court of Appeals for the District of Columbia Circuit having affirmed the District Court's finding of liability against Microsoft for violation of 2 of the Sherman Act and the state law counterparts to 2 of the Sherman Act in the states of California, Connecticut, Florida, Iowa, Kansas, Minnesota, Utah, and West Virginia, the Commonwealth of Massachusetts, and the District of Columbia, and having remanded to this Court for an order of remedy; and Upon the record of trial and all prior and subsequent proceedings herein, it is this 1st day of November, 2002, hereby ORDERED, ADJUDGED AND DECREED as follows: I. Jurisdiction This Court has jurisdiction of the subject matter of this action and of the person of Microsoft. 2 II. Applicability This Final Judgment applies to Microsoft and to each of its officers, directors, agents, employees, subsidiaries, successors and assigns; and to all other persons in active concert or participation with any of them who shall have received actual notice of this Final Judgment by personal service or otherwise. III. Prohibited Conduct A. Microsoft shall not retaliate against or threaten retaliation against an OEM by altering Microsoft's commercial relations with that OEM, or by withholding newly introduced forms of non-monetary Consideration (including but not limited to new versions of existing forms of non-monetary Consideration) from that OEM, because it is known to Microsoft that the OEM is or is contemplating: 1. developing, distributing, promoting, using, selling, or licensing any software that competes with Microsoft Platform Software or any product or service that distributes or promotes any Non-Microsoft Middleware; 2. shipping a Personal Computer that (a) includes both a Windows Operating System Product and a non-Microsoft Operating System, or (b) will boot with more than one Operating System; or 3. exercising any of the options or alternatives provided for under this Final Judgment. Nothing in this provision shall prohibit Microsoft from enforcing any provision of any license with any OEM or any intellectual property right that is not inconsistent with this Final Judgment. Microsoft shall not terminate a Covered OEM's license for a Windows Operating System Product without having first given the Covered OEM written notice of the reasons for the proposed termination and not less than thirty days' opportunity to cure. Notwithstanding the foregoing, Microsoft shall have no obligation to provide such a termination notice and opportunity to cure to any Covered OEM that has received two or more such notices during the term of its Windows Operating System Product license. Nothing in this provision shall prohibit Microsoft from providing Consideration to any OEM with respect to any Microsoft product or service where that Consideration is commensurate with the absolute level or amount of that OEM's development, distribution, promotion, or licensing of that Microsoft product or service. B. Microsoft's provision of Windows Operating System Products to Covered OEMs shall be pursuant to uniform license agreements with uniform terms and conditions. Without limiting the foregoing, Microsoft shall charge each Covered OEM the applicable royalty for Windows Operating System Products as set forth on a schedule, to be established by Microsoft and published on a web site accessible to the Plaintiffs and all Covered OEMs, that provides for uniform royalties for Windows Operating System Products, except that: 1. the schedule may specify different royalties for different language versions; 3 2. the schedule may specify reasonable volume discounts based upon the actual volume of licenses of any Windows Operating System Product or any group of such products; and 3. the schedule may include market development allowances, programs, or other discounts in connection with Windows Operating System Products, provided that: a. such discounts are offered and available uniformly to all Covered OEMs, except that Microsoft may establish one uniform discount schedule for the ten largest Covered OEMs and a second uniform discount schedule for the eleventh through twentieth largest Covered OEMs, where the size of the OEM is measured by volume of licenses; b. such discounts are based on objective, verifiable criteria that shall be applied and enforced on a uniform basis for all Covered OEMs; and c. such discounts or their award shall not be based on or impose any criterion or requirement that is otherwise inconsistent with any portion of this Final Judgment. C. Microsoft shall not restrict by agreement any OEM licensee from exercising any of the following options or alternatives: 1. Installing, and displaying icons, shortcuts, or menu entries for, any Non-Microsoft Middleware or any product or service (including but not limited to IAP products or services) that distributes, uses, promotes, or supports any Non-Microsoft Middleware, on the desktop or Start menu, or anywhere else in a Windows Operating System Product where a list of icons, shortcuts, or menu entries for applications are generally displayed, except that Microsoft may restrict an OEM from displaying icons, shortcuts and menu entries for any product in any list of such icons, shortcuts, or menu entries specified in the Windows documentation as being limited to products that provide particular types of functionality, provided that the restrictions are non-discriminatory with respect to non-Microsoft and Microsoft products. 2. Distributing or promoting Non-Microsoft Middleware by installing and displaying on the desktop shortcuts of any size or shape so long as such shortcuts do not impair the functionality of the user interface. 3. Launching automatically, at the conclusion of the initial boot sequence or subsequent boot sequences, or upon connections to or disconnections from the Internet, any Non-Microsoft Middleware, except that Microsoft may restrict the launching of Non-Microsoft Middleware which replaces or drastically alters the Windows Operating System Product user interface. 4. Offering users the option of launching other Operating Systems from the Basic Input/Output System or a non-Microsoft boot-loader or similar program that launches prior to the start of the Windows Operating System Product. 5. Presenting during the initial boot sequence its own IAP offer. 6. Exercising any of the options provided in Section III.H of this Final Judgment. 4 D. Starting at the earlier of the release of Service Pack 1 for Windows XP or three months after the entry of this Final Judgment, Microsoft shall disclose to ISVs, IHVs, IAPs, ICPs, and OEMs, for the sole purpose of interoperating with a Windows Operating System Product, via the Microsoft Developer Network ("MSDN") or similar mechanisms, the APIs and related Documentation that are used by Microsoft Middleware to interoperate with a Windows Operating System Product. For purposes of this Section III.D, the term APIs means the interfaces, including any associated callback interfaces, that Microsoft Middleware running on a Windows Operating System Product uses to call upon that Windows Operating System Product in order to obtain any services from that Windows Operating System Product. In the case of a new major version of Microsoft Middleware, the disclosures required by this Section III.D shall occur no later than the last major beta test release of that Microsoft Middleware. In the case of a new version of a Windows Operating System Product, the obligations imposed by this Section III.D shall occur in a Timely Manner. E. Starting three months after the entry of this Final Judgment to the Court, Microsoft shall make available for use by third parties, for the sole purpose of interoperating or communicating with a Windows Operating System Product, on reasonable and non-discriminatory terms (consistent with Section III.I), any Communications Protocol that is, on or after the date this Final Judgment is submitted to the Court, (i) implemented in a Windows Operating System Product installed on a client computer, and (ii) used to interoperate, or communicate, natively (i.e., without the addition of software code to the client operating system product) with a Microsoft server operating system product. F. 1. Microsoft shall not retaliate against or threaten retaliation against any ISV or IHV because of that ISV's or IHV's: a. developing, using, distributing, promoting or supporting any software that competes with Microsoft Platform Software or any software that runs on any software that competes with Microsoft Platform Software, or b. exercising any of the options or alternatives provided for under this Final Judgment. 2. Microsoft shall not enter into any agreement relating to a Windows Operating System Product that conditions the grant of any Consideration on an ISV's refraining from developing, using, distributing, or promoting any software that competes with Microsoft Platform Software or any software that runs on any software that competes with Microsoft Platform Software, except that Microsoft may enter into agreements that place limitations on an ISV's development, use, distribution or promotion of any such software if those limitations are reasonably necessary to and of reasonable scope and duration in relation to a bona fide contractual obligation of the ISV to use, distribute or promote any Microsoft software or to develop software for, or in conjunction with, Microsoft. 3. Nothing in this section shall prohibit Microsoft from enforcing any provision of any agreement with any ISV or IHV, or any intellectual property right, that is not 5 inconsistent with this Final Judgment. G. Microsoft shall not enter into any agreement with: 1. any IAP, ICP, ISV, IHV or OEM that grants Consideration on the condition that such entity distributes, promotes, uses, or supports, exclusively or in a fixed percentage, any Microsoft Platform Software, except that Microsoft may enter into agreements in which such an entity agrees to distribute, promote, use or support Microsoft Platform Software in a fixed percentage whenever Microsoft in good faith obtains a representation that it is commercially practicable for the entity to provide equal or greater distribution, promotion, use or support for software that competes with Microsoft Platform Software, or 2. any IAP or ICP that grants placement on the desktop or elsewhere in any Windows Operating System Product to that IAP or ICP on the condition that the IAP or ICP refrain from distributing, promoting or using any software that competes with Microsoft Middleware. Nothing in this section shall prohibit Microsoft from entering into (a) any bona fide joint venture or (b) any joint development or joint services arrangement with any ISV, IHV, IAP, ICP, or OEM for a new product, technology or service, or any material value-add to an existing product, technology or service, in which both Microsoft and the ISV, IHV, IAP, ICP, or OEM contribute significant developer or other resources, that prohibits such entity from competing with the object of the joint venture or other arrangement for a reasonable period of time. This Section does not apply to any agreements in which Microsoft licenses intellectual property from a third party and such intellectual property license is the principal purpose of the agreement. H. Starting at the earlier of the release of Service Pack 1 for Windows XP or three months after the entry of this Final Judgment, Microsoft shall: 1. Allow end users (via a mechanism readily accessible from the desktop or Start menu such as an Add/Remove icon) and OEMs (via standard preinstallation kits) to enable or remove access to each Microsoft Middleware Product or Non-Microsoft Middleware Product by (a) displaying or removing icons, shortcuts, or menu entries on the desktop or Start menu, or anywhere else in a Windows Operating System Product where a list of icons, shortcuts, or menu entries for applications are generally displayed, except that Microsoft may restrict the display of icons, shortcuts, or menu entries for any product in any list of such icons, shortcuts, or menu entries specified in the Windows documentation as being limited to products that provide particular types of functionality, provided that the restrictions are non-discriminatory with respect to non-Microsoft and Microsoft products; and (b) enabling or disabling automatic invocations pursuant to Section III.C.3 of this Final Judgment that are used to launch Non-Microsoft Middleware Products or Microsoft Middleware Products. The mechanism shall offer the end user a separate and unbiased choice with respect to enabling or 6 removing access (as described in this subsection III.H.1) and altering default invocations (as described in the following subsection III.H.2) with regard to each such Microsoft Middleware Product or Non-Microsoft Middleware Product and may offer the end-user a separate and unbiased choice of enabling or removing access and altering default configurations as to all Microsoft Middleware Products as a group or all Non-Microsoft Middleware Products as a group. 2. Allow end users (via an unbiased mechanism readily available from the desktop or Start menu), OEMs (via standard OEM preinstallation kits), and Non-Microsoft Middleware Products (via a mechanism which may, at Microsoft's option, require confirmation from the end user in an unbiased manner) to designate a Non-Microsoft Middleware Product to be invoked in place of that Microsoft Middleware Product (or vice versa) in any case where the Windows Operating System Product would otherwise launch the Microsoft Middleware Product in a separate Top-Level Window and display either (i) all of the user interface elements or (ii) the Trademark of the Microsoft Middleware Product. Notwithstanding the foregoing Section III.H.2, the Windows Operating System Product may invoke a Microsoft Middleware Product in any instance in which: (a) that Microsoft Middleware Product would be invoked solely for use in interoperating with a server maintained by Microsoft (outside the context of general Web browsing), or (b) that designated Non-Microsoft Middleware Product fails to implement a reasonable technical requirement (e.g., a requirement to be able to host a particular ActiveX control) that is necessary for valid technical reasons to supply the end user with functionality consistent with a Windows Operating System Product, provided that the technical reasons are described in writing in a reasonably prompt manner to any ISV that requests them. 3. Ensure that a Windows Operating System Product does not (a) automatically alter an OEM's configuration of icons, shortcuts or menu entries installed or displayed by the OEM pursuant to Section III.C of this Final Judgment without first seeking confirmation from the user and (b) seek such confirmation from the end user for an automatic (as opposed to user-initiated) alteration of the OEM's configuration until 14 days after the initial boot up of a new Personal Computer. Any such automatic alteration and confirmation shall be unbiased with respect to Microsoft Middleware Products and Non-Microsoft Middleware. Microsoft shall not alter the manner in which a Windows Operating System Product automatically alters an OEM's configuration of icons, shortcuts or menu entries other than in a new version of a Windows Operating System Product. Microsoft's obligations under this Section III.H as to any new Windows Operating System Product shall be determined based on the Microsoft Middleware Products which exist seven 7 months prior to the last beta test version (i.e., the one immediately preceding the first release candidate) of that Windows Operating System Product. I. Microsoft shall offer to license to ISVs, IHVs, IAPs, ICPs, and OEMs any intellectual property rights owned or licensable by Microsoft that are required to exercise any of the options or alternatives expressly provided to them under this Final Judgment, provided that 1. all terms, including royalties or other payment of monetary consideration, are reasonable and non-discriminatory; 2. the scope of any such license (and the intellectual property rights licensed thereunder) need be no broader than is necessary to ensure that an ISV, IHV, IAP, ICP or OEM is able to exercise the options or alternatives expressly provided under this Final Judgment (e.g., an ISV's, IHV's, IAP's, ICP's and OEM's option to promote Non-Microsoft Middleware shall not confer any rights to any Microsoft intellectual property rights infringed by that Non-Microsoft Middleware); 3. an ISV's, IHV's, IAP's, ICP's, or OEM's rights may be conditioned on its not assigning, transferring or sublicensing its rights under any license granted under this provision; and 4. the terms of any license granted under this section are in all respects consistent with the express terms of this Final Judgment. Beyond the express terms of any license granted by Microsoft pursuant to this section, this Final Judgment does not, directly or by implication, estoppel or otherwise, confer any rights, licenses, covenants or immunities with regard to any Microsoft intellectual property to anyone. J. No provision of this Final Judgment shall: 1. Require Microsoft to document, disclose or license to third parties: (a) portions of APIs or Documentation or portions or layers of Communications Protocols the disclosure of which would compromise the security of a particular installation or group of installations of anti-piracy, anti-virus, software licensing, digital rights management, encryption or authentication systems, including without limitation, keys, authorization tokens or enforcement criteria; or (b) any API, interface or other information related to any Microsoft product if lawfully directed not to do so by a governmental agency of competent jurisdiction. 2. Prevent Microsoft from conditioning any license of any API, Documentation or Communications Protocol related to anti-piracy systems, anti-virus technologies, license enforcement mechanisms, authentication/authorization security, or third party intellectual property protection mechanisms of any Microsoft product to any person or entity on the requirement that the licensee: (a) has no history of software counterfeiting or piracy or willful violation of intellectual property rights, (b) has a reasonable business need for the API, Documentation or Communications Protocol for a planned or shipping product, (c) meets reasonable, objective standards established by Microsoft for certifying the 8 authenticity and viability of its business, (d) agrees to submit, at its own expense, any computer program using such APIs, Documentation or Communication Protocols to third-party verification, approved by Microsoft, to test for and ensure verification and compliance with Microsoft specifications for use of the API or interface, which specifications shall be related to proper operation and integrity of the systems and mechanisms identified in this paragraph. IV. Compliance and Enforcement Procedures A. Enforcement Authority 1. The Plaintiffs shall have exclusive responsibility for enforcing this Final Judgment. Without in any way limiting the sovereign enforcement authority of each of the plaintiff States, the plaintiff States shall form a committee to coordinate their enforcement of this Final Judgment. A plaintiff State shall take no action to enforce this Final Judgment without first consulting the plaintiff States' enforcement committee. 2. To determine and enforce compliance with this Final Judgment, duly authorized representatives of the plaintiff States, on reasonable notice to Microsoft and subject to any lawful privilege, shall be permitted the following: a. Access during normal office hours to inspect any and all source code, books, ledgers, accounts, correspondence, memoranda and other documents and records in the possession, custody, or control of Microsoft, which may have counsel present, regarding any matters contained in this Final Judgment. b. Subject to the reasonable convenience of Microsoft and without restraint or interference from it, to interview, informally or on the record, officers, employees, or agents of Microsoft, who may have counsel present, regarding any matters contained in this Final Judgment. c. Upon written request of a duly designated representative of a plaintiff State, on reasonable notice given to Microsoft, Microsoft shall submit such written reports under oath as requested regarding any matters contained in this Final Judgment. Individual plaintiff States will consult with the plaintiff States' enforcement committee to minimize the duplication and burden of the exercise of the foregoing powers, where practicable. 3. The Plaintiffs shall not disclose any information or documents obtained from Microsoft under this Final Judgment except for the purpose of securing compliance with this Final Judgment, in a legal proceeding to which one or more of the Plaintiffs is a party, or as otherwise required by law; provided that the relevant Plaintiff(s) must provide ten days' advance notice to Microsoft before disclosing in any legal proceeding (other than a grand jury proceeding) to which Microsoft is not a party any information or documents provided by Microsoft pursuant to this Final Judgment which Microsoft has identified in writing as 9 material as to which a claim of protection may be asserted under Rule 26(c)(7) of the Federal Rules of Civil Procedure. 4. The Plaintiffs shall have the authority to seek such orders as are necessary from the Court to enforce this Final Judgment, provided, however, that the Plaintiffs shall afford Microsoft a reasonable opportunity to cure alleged violations of Sections III.C, III.D, III.E and III.H, provided further that any action by Microsoft to cure any such violation shall not be a defense to enforcement with respect to any knowing, willful or systematic violations. B. 1. Compliance Committee. Within 30 days of entry of this Final Judgment, Microsoft shall establish a compliance committee (the "Compliance Committee") of its Board of Directors, consisting of at least three members of the Board of Directors who are not present or former employees of Microsoft. 2. Compliance Officer. The Compliance Committee shall hire a Compliance Officer, who shall report directly to the Compliance Committee and to the Chief Executive Officer of Microsoft. The Compliance Officer shall be responsible for development and supervision of Microsoft's internal programs to ensure compliance with the antitrust laws and this Final Judgment. Microsoft shall give the Compliance Officer all necessary authority and resources to discharge the responsibilities listed herein. 3. Duties of Compliance Officer. The Compliance Officer shall: a. within 60 days after entry of this Final Judgment, arrange for delivery to all officers and directors of Microsoft a copy of this Final Judgment together with additional informational materials describing the conduct prohibited and required by this Final Judgment; b. arrange for delivery in a timely manner of a copy of this Final Judgment and such additional informational materials to any person who succeeds to a position described in Section IV.B.3.a above; c. ensure that those persons described in subsection c.i above are annually briefed on the meaning and requirements of this Final Judgment and the United States antitrust laws and advising them that Microsoft's legal advisors are available to confer with them regarding any question concerning compliance with this Final Judgment or under the United States antitrust laws; d. obtain from each person described in Section IV.B.3.a within 60 days of entry of this Final Judgment and annually thereafter, and for each person thereafter succeeding to such a position within 10 days of such succession and annually thereafter, a written certification that he or she: (i) has read, understands, and agrees to abide by the terms of, and has to their knowledge not violated, this Final Judgment; and (ii) has been advised and understands that his or her failure to comply with this Final Judgment may result in a finding of contempt of court; e. maintain a record of persons to whom this Final Judgment has been distributed and from whom, pursuant to Section V.B.3.d above has been 10 obtained; f. on an annual basis, certify to the Plaintiffs that Microsoft is fully compliant with this Final Judgment; g. maintain a record of all complaints received and action taken by Microsoft with respect to each such complaint; and g. report promptly to the Plaintiffs any credible evidence of violation of this Final Judgment. 4. The Compliance Officer may be removed only by the Chief Executive Officer with the concurrence of the Compliance Committee. V. Termination A. Unless this Court grants an extension, this Final Judgment will expire on the fifth anniversary of the date on which it takes effect. B. In any enforcement proceeding in which the Court has found that Microsoft has engaged in a pattern of willful and systematic violations, the Plaintiffs may apply to the Court for a one-time extension of this Final Judgment of up to two years, together with such other relief as the Court may deem appropriate. VI. Definitions A. "API" means application programming interface, including any interface that Microsoft is obligated to disclose pursuant to III.D. B. "Communications Protocol" means the set of rules for information exchange to accomplish predefined tasks between a Windows Operating System Product and a server operating system product connected via a network, including, but not limited to, a local area network, a wide area network or the Internet. These rules govern the format, semantics, timing, sequencing, and error control of messages exchanged over a network. C. "Consideration" means any monetary payment or the provision of preferential licensing terms; technical, marketing, and sales support; enabling programs; product information; information about future plans; developer support; hardware or software certification or approval; or permission to display trademarks, icons or logos. D. "Covered OEMs" means the 20 OEMs with the highest worldwide volume of licenses of Windows Operating System Products reported to Microsoft in Microsoft's fiscal year preceding the effective date of the Final Judgment. The OEMs that fall within this definition of Covered OEMs shall be recomputed by Microsoft as soon as practicable after the close of each of Microsoft's fiscal years. E. "Documentation" means all information regarding the identification and means of using APIs that a person of ordinary skill in the art requires to make effective use of those 11 APIs. Such information shall be of the sort and to the level of specificity, precision and detail that Microsoft customarily provides for APIs it documents in the Microsoft Developer Network ("MSDN"). F. "IAP" means an Internet access provider that provides consumers with a connection to the Internet, with or without its own proprietary content. G. "ICP" means an Internet content provider that provides content to users of the Internet by maintaining Web sites. H. "IHV" means an independent hardware vendor that develops hardware to be included in or used with a Personal Computer running a Windows Operating System Product. I. "ISV" means an entity other than Microsoft that is engaged in the development or marketing of software products. J. "Microsoft Middleware" means software code that 1. Microsoft distributes separately from a Windows Operating System Product to update that Windows Operating System Product; 2. is Trademarked or is marketed by Microsoft as a major version of any Microsoft Middleware Product defined in section VI.K.1; and 3. provides the same or substantially similar functionality as a Microsoft Middleware Product. Microsoft Middleware shall include at least the software code that controls most or all of the user interface elements of that Microsoft Middleware. Software code described as part of, and distributed separately to update, a Microsoft Middleware Product shall not be deemed Microsoft Middleware unless identified as a new major version of that Microsoft Middleware Product. A major version shall be identified by a whole number or by a number with just a single digit to the right of the decimal point. K. "Microsoft Middleware Product" means 1. the functionality provided by Internet Explorer, Microsoft's Java Virtual Machine, Windows Media Player, Windows Messenger, Outlook Express and their successors in a Windows Operating System Product, and 2. for any functionality that is first licensed, distributed or sold by Microsoft after the entry of this Final Judgment and that is part of any Windows Operating System Product a. Internet browsers, email client software, networked audio/video client software, instant messaging software or b. functionality provided by Microsoft software that -- i. is, or in the year preceding the commercial release of any new Windows Operating System Product was, distributed separately by Microsoft (or by an entity acquired by Microsoft) from a Windows Operating System Product; 12 ii. is similar to the functionality provided by a Non-Microsoft Middleware Product; and iii. is Trademarked. Functionality that Microsoft describes or markets as being part of a Microsoft Middleware Product (such as a service pack, upgrade, or bug fix for Internet Explorer), or that is a version of a Microsoft Middleware Product (such as Internet Explorer 5.5), shall be considered to be part of that Microsoft Middleware Product. L. "Microsoft Platform Software" means (i) a Windows Operating System Product and/or (ii) a Microsoft Middleware Product. M. "Non-Microsoft Middleware" means a non-Microsoft software product running on a Windows Operating System Product that exposes a range of functionality to ISVs through published APIs, and that could, if ported to or made interoperable with, a non- Microsoft Operating System, thereby make it easier for applications that rely in whole or in part on the functionality supplied by that software product to be ported to or run on that non-Microsoft Operating System. N. "Non-Microsoft Middleware Product" means a non-Microsoft software product running on a Windows Operating System Product (i) that exposes a range of functionality to ISVs through published APIs, and that could, if ported to or made interoperable with, a non-Microsoft Operating System, thereby make it easier for applications that rely in whole or in part on the functionality supplied by that software product to be ported to or run on that non-Microsoft Operating System, and (ii) of which at least one million copies were distributed in the United States within the previous year. O. "OEM" means an original equipment manufacturer of Personal Computers that is a licensee of a Windows Operating System Product. P. "Operating System" means the software code that, inter alia, (i) controls the allocation and usage of hardware resources (such as the microprocessor and various peripheral devices) of a Personal Computer, (ii) provides a platform for developing applications by exposing functionality to ISVs through APIs, and (iii) supplies a user interface that enables users to access functionality of the operating system and in which they can run applications. Q. "Personal Computer" means any computer configured so that its primary purpose is for use by one person at a time, that uses a video display and keyboard (whether or not that video display and keyboard is included) and that contains an Intel x86 compatible (or successor) microprocessor. Servers, television set top boxes, handheld computers, game consoles, telephones, pagers, and personal digital assistants are examples of products that are not Personal Computers within the meaning of this definition. R. "Timely Manner" means at the time Microsoft first releases a beta test version of a Windows Operating System Product that is made available via an MSDN subscription 13 offering or of which 150,000 or more beta copies are distributed. S. "Top-Level Window" means a window displayed by a Windows Operating System Product that (a) has its own window controls, such as move, resize, close, minimize, and maximize, (b) can contain sub-windows, and (c) contains user interface elements under the control of at least one independent process. T. "Trademarked" means distributed in commerce and identified as distributed by a name other than Microsoft® or Windows® that Microsoft has claimed as a trademark or service mark by (i) marking the name with trademark notices, such as ® or (TM), in connection with a product distributed in the United States; (ii) filing an application for trademark protection for the name in the United States Patent and Trademark Office; or (iii) asserting the name as a trademark in the United States in a demand letter or lawsuit. Any product distributed under descriptive or generic terms or a name comprised of the Microsoft® or Windows® trademarks together with descriptive or generic terms shall not be Trademarked as that term is used in this Final Judgment. Microsoft hereby disclaims any trademark rights in such descriptive or generic terms apart from the Microsoft® or Windows® trademarks, and hereby abandons any such rights that it may acquire in the future. U. "Windows Operating System Product" means the software code (as opposed to source code) distributed commercially by Microsoft for use with Personal Computers as Windows 2000 Professional, Windows XP Home, Windows XP Professional, and successors to the foregoing, including the Personal Computer versions of the products currently code named "Longhorn" and "Blackcomb" and their successors, including upgrades, bug fixes, service packs, etc. The software code that comprises a Windows Operating System Product shall be determined by Microsoft in its sole discretion. VII. Further Elements Jurisdiction is retained by this Court over this action such that the Court may act sua sponte to issue further orders or directions, including but not limited to orders or directions relating to the construction or carrying out of this Final Judgment, the enforcement of compliance therewith, the modification thereof, and the punishment of any violation thereof. Jurisdiction is retained by this Court over this action and the parties thereto for the purpose of enabling the parties to this action to apply to this Court at any time for further orders and directions as may be necessary or appropriate to carry out or construe this Final Judgment, to modify or terminate any of its provisions, to enforce compliance, and to punish violations of its provisions. Unless otherwise indicated, the provisions of this Final Judgment shall take effect 30 days after the date on which it is entered. In accordance with the imposition and affirmance of liability, the Plaintiff States shall submit a 14 motion for the award of costs and fees, with supporting documents as necessary, not later than 45 days after the entry of this Final Judgment. VIII. Third Party Rights Nothing in this Final Judgment is intended to confer upon any other persons any rights or remedies of any nature whatsoever hereunder or by reason of this Final Judgment. SO ORDERED. _____________________________ COLLEEN KOLLAR-KOTELLY United States District Judge
Slashdot Mirror
yeah... but how many stories are advertisement,
and not news? Personally, and this
is just personal, so don't read into this
too much, this was advertisement
Is that enough html for you? Because you seem to have lost the copy/paste functionality within your operating system in order to copy/paste a link with...
well, look at the second question, and answer, on the previous story:
3 /0 2/20/1544245&mode=flat&tid=117&tid=123
http://interviews.slashdot.org/article.pl?sid=0
from what he says, it looks as though, if they modify one program, or include anything gpl, although not lgpl, then they must open source it all..
blatently posted here a few months back:
6 25 3&mode=flat
http://slashdot.org/article.pl?sid=02/04/22/125
have a nice, slash-ad-reading day!
where's the source? as in source code. Isn't lindows based on the linux kernel? Or do they give it to you once you purchase the product?
But at the same time, if AOL were concerned about spam, why do you have to dig deep into the softwares settings to stop recieving AOL sponsored e-mail advertisements, and pop-ups, and then have to mail them via the postal office to stop any other advertisement?
AOL sponsored spam?
You can change the variables for your terminal to produce the green you desire.
Sweet, I didn't realize photos had meta data too. I'll download this onto my iBook tonight and check it out, appreciate it.
Hey Hemos?
I've been looking for a digi cam.. that one looks decent, which is it, and about how much did you get it for?
do you have the developer tools installed?
Hmm.. this could be changed up though, think about it for a second.. sed and awk are on macs by default right? and if not, it could be included in the packager (ok, so I am reinstalling OSX on my iBook as we speak, I was.. disatisfied with how I partitioned everything)
You could ls -al the passwd file, and see what the current users shell is, and say it's bash, grep for the config files, if they are present, then add the line to it, and export the file. Wouldn't be all that (yeah, like I could do this, yeesh! but I know some people could do it..)
You could specify if you want the current user, a user with administrative rights, or the root user to do this. After that, you're pretty much done, it changes those files, then updates itself if you say yes, go ahead and check for updates. Then it asks if you would like a gui for this, and gives you a link to finkcommander.sourceforge.net if you do.
Might be worth something.
Well, two things
First off, they finished this yesterday, actually got it yesterday in the irc chan on irc://irc.openprojects.net in #fink. It's really a cool installer, even detects if you have an old install and what not.
Second, there is a gui for this, http://finkcommander.sourceforge.net/
It has buttons to e-mail a developer if a package is working for you, and also shows columns for if this package is out of date, or up to date, etc. It's searchable, and really cool. It doesn't require X11, it's a native apple app!
Other than that, I would like to congratulate all the people involved, for the hard work they have put into this. It's a very awesome thing.
or give them a remote shell, no install needed...
anyone got a mirror, this seems to be appledotted... :)
Actually, this is a good thing, I can finally convince my employer that maybe it's not such a good idea, as anyone with a mac can login.
Really good:
Disclosure for the most part, is a good thing. Even with things such as smb, whereas the samba team found a way to shut down a server remotely with it, aren't disclosed, unless there is a threat of disclosure, in which you need to go ahead and patch your hole or you will be seen as, well, uncaring by those who care.
This also allows for faster knowledge, i.e., if there is an active mailing list on it, but I am not on that list, then iss will inform me of the problem, this is in the mailing list, or whatever form of communication said project uses.
The Cons
As mentioned in comments already, I am assuming, people will be able to blackmail one another in order to keep said hack/hole/easter bunny out of the lime light. A little bit of cash can go a long way sometimes. Be wary of what is, and what isn't, reported.
Why this is important to you:
It gives you a more defined description of how things are going to go, and how much salt grain you should take with each hack. You should know that each hack/hole out there has already been out there for a month, and that it could have been out there for a lot longer. Joe blackhat just doesn't give up his tools, unless they are not useful.
Why this is not important:
ISS is not the only security site, and it should not be your only site to get updates from, either. Do a google...
Slashdot poll idea!
.Mac
How do you secure your data:
1: Remote offsite backups
2: CD/DVD/Floppy
3: I don't, I live on the wild side
4:
5: Cowboyneal is my remote backup system of choice
Dude, not to be off topic, but robert jordan is awesome! When is his new book supposed to come out, every time I go by bn or anything like that, they say it's not out.
Actually, a keyboard from apple costs 59 dollars usd. You can get it in black or white, from here: http://store.apple.com/1-800-MY-APPLE/WebObjects/A ppleStore.woa/144/wo/WZetV0ZSyQSIhPLKsI/0.3.0.3.27 .7.0.CoverPageLeftAccessoriesPromo.1.1.0.3.1.5.17. 3.1.1.0
Also, you can use any usb keyboard, mouse with your apple. I use a microsoft mouse with my iBook, the wireless intellimouse explorer. It's very nice, except for the battery consumption.
Why not split the platforms, and hire a few more people? I know, I know, this doesn't seem feasible, right? But if you were able to split the code into what it would actually work on, say you have yourself and joe working windows, you guys just work on windows, and have all the code that works within that ide. Jan and Sue, with help from the janitor Steve, are all working on the irix side, etc, etc, etc. It would seem more feasible than actually working all these different platforms together at once? And what about mac, is there a demand for that as well? Would be a good time to look into it...
I thought it was port 5192.. but the last time I checked was 2 years ago...
At least he was able to live his life to the fullest.. or as full as any human can
That being said, the paint job on that iBook is really nice, and I am thinking of getting mine done with something similar, but completely different.
UNITED STATES OF AMERICA,
Plaintiff,
v.
MICROSOFT CORPORATION,
Defendant.
UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF COLUMBIA
Civil Action No. 98-1232 (CKK)
ORDER
Presently pending before the Court is a proposed consent decree submitted by the parties
in the above-captioned case. Following application of the Tunney Act, 15 U.S.C. 16(b)-(h), and
upon a finding pursuant 15 U.S.C. 16(e) that, with the exception of VII of the proposed final
judgment ("SRPFJ"), entry of the SRPFJ as the final judgment in this action is in the public
interest, as set forth in the accompanying Memorandum Opinion, it is this 1st day of November,
2002, hereby
ORDERED that the SRPFJ is conditionally approved as the final judgment in this case;
and it is further
ORDERED that, in order to obtain final approval of the SRPFJ, Plaintiff and Microsoft
shall submit to the Court a proposed amendment to VII addressing the concerns described in the
accompanying Memorandum Opinion; and it is further
ORDERED that such proposed amendment shall be submitted to the Court not later than
November 8, 2002.
SO ORDERED.
_____________________________
COLLEEN KOLLAR-KOTELLY
United States District Judge
STATE OF NEW YORK, et al.,
Plaintiffs
v.
MICROSOFT CORPORATION,
Defendant.
UNITED STATES DISTRICT COURT
FOR THE DISTRICT OF COLUMBIA
Civil Action No. 98-1233 (CKK)
FINAL JUDGMENT
The Plaintiff States of California, Connecticut, Florida, Iowa, Kansas, Minnesota, Utah,
and West Virginia, the Commonwealth of Massachusetts, and the District of Columbia, having
filed their complaints in this action on May 18, 1998;
Defendant Microsoft Corporation ("Microsoft") having appeared and filed its answer;
The Court having entered Findings of Fact on November 5, 1999 and Conclusions of
Law on April 3, 2000;
The United States Court of Appeals for the District of Columbia Circuit having affirmed
the District Court's finding of liability against Microsoft for violation of 2 of the Sherman Act
and the state law counterparts to 2 of the Sherman Act in the states of California, Connecticut,
Florida, Iowa, Kansas, Minnesota, Utah, and West Virginia, the Commonwealth of
Massachusetts, and the District of Columbia, and having remanded to this Court for an order of
remedy; and
Upon the record of trial and all prior and subsequent proceedings herein, it is this 1st day
of November, 2002, hereby
ORDERED, ADJUDGED AND DECREED as follows:
I. Jurisdiction
This Court has jurisdiction of the subject matter of this action and of the person of
Microsoft.
2
II. Applicability
This Final Judgment applies to Microsoft and to each of its officers, directors, agents,
employees, subsidiaries, successors and assigns; and to all other persons in active concert or
participation with any of them who shall have received actual notice of this Final Judgment by
personal service or otherwise.
III. Prohibited Conduct
A. Microsoft shall not retaliate against or threaten retaliation against an OEM by altering
Microsoft's commercial relations with that OEM, or by withholding newly introduced
forms of non-monetary Consideration (including but not limited to new versions of
existing forms of non-monetary Consideration) from that OEM, because it is known to
Microsoft that the OEM is or is contemplating:
1. developing, distributing, promoting, using, selling, or licensing any software that
competes with Microsoft Platform Software or any product or service that
distributes or promotes any Non-Microsoft Middleware;
2. shipping a Personal Computer that (a) includes both a Windows Operating
System Product and a non-Microsoft Operating System, or (b) will boot with
more than one Operating System; or
3. exercising any of the options or alternatives provided for under this Final
Judgment.
Nothing in this provision shall prohibit Microsoft from enforcing any provision of any license
with any OEM or any intellectual property right that is not inconsistent with this Final Judgment.
Microsoft shall not terminate a Covered OEM's license for a Windows Operating System
Product without having first given the Covered OEM written notice of the reasons for the
proposed termination and not less than thirty days' opportunity to cure. Notwithstanding the
foregoing, Microsoft shall have no obligation to provide such a termination notice and
opportunity to cure to any Covered OEM that has received two or more such notices during the
term of its Windows Operating System Product license.
Nothing in this provision shall prohibit Microsoft from providing Consideration to any OEM
with respect to any Microsoft product or service where that Consideration is commensurate with
the absolute level or amount of that OEM's development, distribution, promotion, or licensing of
that Microsoft product or service.
B. Microsoft's provision of Windows Operating System Products to Covered OEMs shall be
pursuant to uniform license agreements with uniform terms and conditions. Without
limiting the foregoing, Microsoft shall charge each Covered OEM the applicable royalty
for Windows Operating System Products as set forth on a schedule, to be established by
Microsoft and published on a web site accessible to the Plaintiffs and all Covered OEMs,
that provides for uniform royalties for Windows Operating System Products, except that:
1. the schedule may specify different royalties for different language versions;
3
2. the schedule may specify reasonable volume discounts based upon the actual
volume of licenses of any Windows Operating System Product or any group of
such products; and
3. the schedule may include market development allowances, programs, or other
discounts in connection with Windows Operating System Products, provided
that:
a. such discounts are offered and available uniformly to all Covered OEMs,
except that Microsoft may establish one uniform discount schedule for the
ten largest Covered OEMs and a second uniform discount schedule for the
eleventh through twentieth largest Covered OEMs, where the size of the
OEM is measured by volume of licenses;
b. such discounts are based on objective, verifiable criteria that shall be
applied and enforced on a uniform basis for all Covered OEMs; and
c. such discounts or their award shall not be based on or impose any criterion
or requirement that is otherwise inconsistent with any portion of this Final
Judgment.
C. Microsoft shall not restrict by agreement any OEM licensee from exercising any of the
following options or alternatives:
1. Installing, and displaying icons, shortcuts, or menu entries for, any Non-Microsoft
Middleware or any product or service (including but not limited to IAP products
or services) that distributes, uses, promotes, or supports any Non-Microsoft
Middleware, on the desktop or Start menu, or anywhere else in a Windows
Operating System Product where a list of icons, shortcuts, or menu entries for
applications are generally displayed, except that Microsoft may restrict an OEM
from displaying icons, shortcuts and menu entries for any product in any list of
such icons, shortcuts, or menu entries specified in the Windows documentation as
being limited to products that provide particular types of functionality, provided
that the restrictions are non-discriminatory with respect to non-Microsoft and
Microsoft products.
2. Distributing or promoting Non-Microsoft Middleware by installing and
displaying
on the desktop shortcuts of any size or shape so long as such shortcuts do not
impair the functionality of the user interface.
3. Launching automatically, at the conclusion of the initial boot sequence or
subsequent boot sequences, or upon connections to or disconnections from the
Internet, any Non-Microsoft Middleware, except that Microsoft may restrict the
launching of Non-Microsoft Middleware which replaces or drastically alters the
Windows Operating System Product user interface.
4. Offering users the option of launching other Operating Systems from the Basic
Input/Output System or a non-Microsoft boot-loader or similar program that
launches prior to the start of the Windows Operating System Product.
5. Presenting during the initial boot sequence its own IAP offer.
6. Exercising any of the options provided in Section III.H of this Final Judgment.
4
D. Starting at the earlier of the release of Service Pack 1 for Windows XP or three months
after the entry of this Final Judgment, Microsoft shall disclose to ISVs, IHVs, IAPs,
ICPs, and OEMs, for the sole purpose of interoperating with a Windows Operating
System Product, via the Microsoft Developer Network ("MSDN") or similar
mechanisms, the APIs and related Documentation that are used by Microsoft Middleware
to interoperate with a Windows Operating System Product. For purposes of this Section
III.D, the term APIs means the interfaces, including any associated callback interfaces,
that Microsoft Middleware running on a Windows Operating System Product uses to call
upon that Windows Operating System Product in order to obtain any services from that
Windows Operating System Product. In the case of a new major version of Microsoft
Middleware, the disclosures required by this Section III.D shall occur no later than the
last major beta test release of that Microsoft Middleware. In the case of a new version of
a Windows Operating System Product, the obligations imposed by this Section III.D shall
occur in a Timely Manner.
E. Starting three months after the entry of this Final Judgment to the Court, Microsoft shall
make available for use by third parties, for the sole purpose of interoperating or
communicating with a Windows Operating System Product, on reasonable and
non-discriminatory terms (consistent with Section III.I), any Communications Protocol
that is, on or after the date this Final Judgment is submitted to the Court, (i) implemented
in a Windows Operating System Product installed on a client computer, and (ii) used to
interoperate, or communicate, natively (i.e., without the addition of software code to the
client operating system product) with a Microsoft server operating system product.
F. 1. Microsoft shall not retaliate against or threaten retaliation against any ISV or IHV
because of that ISV's or
IHV's:
a. developing, using, distributing, promoting or supporting any software that
competes with Microsoft Platform Software or any software that runs on
any software that competes with Microsoft Platform Software, or
b. exercising any of the options or alternatives provided for under this Final
Judgment.
2. Microsoft shall not enter into any agreement relating to a Windows Operating
System Product that conditions the grant of any Consideration on an ISV's
refraining from developing, using, distributing, or promoting any software that
competes with Microsoft Platform Software or any software that runs on any
software that competes with Microsoft Platform Software, except that Microsoft
may enter into agreements that place limitations on an ISV's development, use,
distribution or promotion of any such software if those limitations are reasonably
necessary to and of reasonable scope and duration in relation to a bona fide
contractual obligation of the ISV to use, distribute or promote any Microsoft
software or to develop software for, or in conjunction with, Microsoft.
3. Nothing in this section shall prohibit Microsoft from enforcing any provision of
any agreement with any ISV or IHV, or any intellectual property right, that is not
5
inconsistent with this Final Judgment.
G. Microsoft shall not enter into any agreement with:
1. any IAP, ICP, ISV, IHV or OEM that grants Consideration on the condition that
such entity distributes, promotes, uses, or supports, exclusively or in a fixed
percentage, any Microsoft Platform Software, except that Microsoft may enter
into agreements in which such an entity agrees to distribute, promote, use or
support Microsoft Platform Software in a fixed percentage whenever Microsoft in
good faith obtains a representation that it is commercially practicable for the
entity to provide equal or greater distribution, promotion, use or support for
software that competes with Microsoft Platform Software, or
2. any IAP or ICP that grants placement on the desktop or elsewhere in any
Windows Operating System Product to that IAP or ICP on the condition that the
IAP or ICP refrain from distributing, promoting or using any software that
competes with Microsoft Middleware.
Nothing in this section shall prohibit Microsoft from entering into (a) any bona fide joint venture
or (b) any joint development or joint services arrangement with any ISV, IHV, IAP, ICP, or
OEM for a new product, technology or service, or any material value-add to an existing product,
technology or service, in which both Microsoft and the ISV, IHV, IAP, ICP, or OEM contribute
significant developer or other resources, that prohibits such entity from competing with the
object of the joint venture or other arrangement for a reasonable period of time.
This Section does not apply to any agreements in which Microsoft licenses intellectual property
from a third party and such intellectual property license is the principal purpose of the
agreement.
H. Starting at the earlier of the release of Service Pack 1 for Windows XP or three months
after the entry of this Final Judgment, Microsoft shall:
1. Allow end users (via a mechanism readily accessible from the desktop or Start
menu such as an Add/Remove icon) and OEMs (via standard preinstallation kits)
to enable or remove access to each Microsoft Middleware Product or
Non-Microsoft Middleware Product by (a) displaying or removing icons,
shortcuts, or menu entries on the desktop or Start menu, or anywhere else in a
Windows Operating System Product where a list of icons, shortcuts, or menu
entries for applications are generally displayed, except that Microsoft may restrict
the display of icons, shortcuts, or menu entries for any product in any list of such
icons, shortcuts, or menu entries specified in the Windows documentation as
being limited to products that provide particular types of functionality, provided
that the restrictions are non-discriminatory with respect to non-Microsoft and
Microsoft products; and (b) enabling or disabling automatic invocations pursuant
to Section III.C.3 of this Final Judgment that are used to launch Non-Microsoft
Middleware Products or Microsoft Middleware Products. The mechanism shall
offer the end user a separate and unbiased choice with respect to enabling or
6
removing access (as described in this subsection III.H.1) and altering default
invocations (as described in the following subsection III.H.2) with regard to each
such Microsoft Middleware Product or Non-Microsoft Middleware Product and
may offer the end-user a separate and unbiased choice of enabling or removing
access and altering default configurations as to all Microsoft Middleware
Products as a group or all Non-Microsoft Middleware Products as a group.
2. Allow end users (via an unbiased mechanism readily available from the desktop
or Start menu), OEMs (via standard OEM preinstallation kits), and
Non-Microsoft Middleware Products (via a mechanism which may, at Microsoft's
option, require confirmation from the end user in an unbiased manner) to
designate a Non-Microsoft Middleware Product to be invoked in place of that
Microsoft Middleware Product (or vice versa) in any case where the Windows
Operating System Product would otherwise launch the Microsoft Middleware
Product in a separate Top-Level Window and display either (i) all of the user
interface elements or (ii) the Trademark of the Microsoft Middleware Product.
Notwithstanding the foregoing Section III.H.2, the Windows Operating System Product may
invoke a Microsoft Middleware Product in any instance in which:
(a) that Microsoft Middleware Product would be invoked solely for use in
interoperating with a server maintained by Microsoft (outside the context
of general Web browsing), or
(b) that designated Non-Microsoft Middleware Product fails to implement a
reasonable technical requirement (e.g., a requirement to be able to host a
particular ActiveX control) that is necessary for valid technical reasons to
supply the end user with functionality consistent with a Windows
Operating System Product, provided that the technical reasons are
described in writing in a reasonably prompt manner to any ISV that
requests them.
3. Ensure that a Windows Operating System Product does not (a) automatically alter
an OEM's configuration of icons, shortcuts or menu entries installed or displayed
by the OEM pursuant to Section III.C of this Final Judgment without first seeking
confirmation from the user and (b) seek such confirmation from the end user for
an automatic (as opposed to user-initiated) alteration of the OEM's configuration
until 14 days after the initial boot up of a new Personal Computer. Any such
automatic alteration and confirmation shall be unbiased with respect to Microsoft
Middleware Products and Non-Microsoft Middleware. Microsoft shall not alter
the manner in which a Windows Operating System Product automatically alters
an OEM's configuration of icons, shortcuts or menu entries other than in a new
version of a Windows Operating System Product.
Microsoft's obligations under this Section III.H as to any new Windows Operating System
Product shall be determined based on the Microsoft Middleware Products which exist seven
7
months prior to the last beta test version (i.e., the one immediately preceding the first release
candidate) of that Windows Operating System Product.
I. Microsoft shall offer to license to ISVs, IHVs, IAPs, ICPs, and OEMs any intellectual
property rights owned or licensable by Microsoft that are required to exercise any of the
options or alternatives expressly provided to them under this Final Judgment, provided
that
1. all terms, including royalties or other payment of monetary consideration, are
reasonable and non-discriminatory;
2. the scope of any such license (and the intellectual property rights licensed
thereunder) need be no broader than is necessary to ensure that an ISV, IHV, IAP,
ICP or OEM is able to exercise the options or alternatives expressly provided
under this Final Judgment (e.g., an ISV's, IHV's, IAP's, ICP's and OEM's option
to promote Non-Microsoft Middleware shall not confer any rights to any
Microsoft intellectual property rights infringed by that Non-Microsoft
Middleware);
3. an ISV's, IHV's, IAP's, ICP's, or OEM's rights may be conditioned on its not
assigning, transferring or sublicensing its rights under any license granted under
this provision; and
4. the terms of any license granted under this section are in all respects consistent
with the express terms of this Final Judgment.
Beyond the express terms of any license granted by Microsoft pursuant to this section, this Final
Judgment does not, directly or by implication, estoppel or otherwise, confer any rights, licenses,
covenants or immunities with regard to any Microsoft intellectual property to anyone.
J. No provision of this Final Judgment shall:
1. Require Microsoft to document, disclose or license to third parties: (a) portions of
APIs or Documentation or portions or layers of Communications Protocols the
disclosure of which would compromise the security of a particular installation or
group of installations of anti-piracy, anti-virus, software licensing, digital rights
management, encryption or authentication systems, including without limitation,
keys, authorization tokens or enforcement criteria; or (b) any API, interface or
other information related to any Microsoft product if lawfully directed not to do
so by a governmental agency of competent jurisdiction.
2. Prevent Microsoft from conditioning any license of any API, Documentation or
Communications Protocol related to anti-piracy systems, anti-virus technologies,
license enforcement mechanisms, authentication/authorization security, or third
party intellectual property protection mechanisms of any Microsoft product to any
person or entity on the requirement that the licensee: (a) has no history of
software counterfeiting or piracy or willful violation of intellectual property
rights, (b) has a reasonable business need for the API, Documentation or
Communications Protocol for a planned or shipping product, (c) meets
reasonable, objective standards established by Microsoft for certifying the
8
authenticity and viability of its business, (d) agrees to submit, at its own expense,
any computer program using such APIs, Documentation or Communication
Protocols to third-party verification, approved by Microsoft, to test for and ensure
verification and compliance with Microsoft specifications for use of the API or
interface, which specifications shall be related to proper operation and integrity of
the systems and mechanisms identified in this paragraph.
IV. Compliance and Enforcement Procedures
A. Enforcement Authority
1. The Plaintiffs shall have exclusive responsibility for enforcing this Final
Judgment. Without in any way limiting the sovereign enforcement authority of
each of the plaintiff States, the plaintiff States shall form a committee to
coordinate their enforcement of this Final Judgment. A plaintiff State shall take
no action to enforce this Final Judgment without first consulting the plaintiff
States' enforcement committee.
2. To determine and enforce compliance with this Final Judgment, duly authorized
representatives of the plaintiff States, on reasonable notice to Microsoft and
subject to any lawful privilege, shall be permitted the following:
a. Access during normal office hours to inspect any and all source code,
books, ledgers, accounts, correspondence, memoranda and other
documents and records in the possession, custody, or control of Microsoft,
which may have counsel present, regarding any matters contained in this
Final Judgment.
b. Subject to the reasonable convenience of Microsoft and without restraint
or interference from it, to interview, informally or on the record, officers,
employees, or agents of Microsoft, who may have counsel present,
regarding any matters contained in this Final Judgment.
c. Upon written request of a duly designated representative of a plaintiff
State, on reasonable notice given to Microsoft, Microsoft shall submit
such written reports under oath as requested regarding any matters
contained in this Final Judgment.
Individual plaintiff States will consult with the plaintiff States' enforcement committee to
minimize the duplication and burden of the exercise of the foregoing powers, where practicable.
3. The Plaintiffs shall not disclose any information or documents obtained from
Microsoft under this Final Judgment except for the purpose of securing
compliance with this Final Judgment, in a legal proceeding to which one or more
of the Plaintiffs is a party, or as otherwise required by law; provided that the
relevant Plaintiff(s) must provide ten days' advance notice to Microsoft before
disclosing in any legal proceeding (other than a grand jury proceeding) to which
Microsoft is not a party any information or documents provided by Microsoft
pursuant to this Final Judgment which Microsoft has identified in writing as
9
material as to which a claim of protection may be asserted under Rule 26(c)(7) of
the Federal Rules of Civil Procedure.
4. The Plaintiffs shall have the authority to seek such orders as are necessary from
the Court to enforce this Final Judgment, provided, however, that the Plaintiffs
shall afford Microsoft a reasonable opportunity to cure alleged violations of
Sections III.C, III.D, III.E and III.H, provided further that any action by Microsoft
to cure any such violation shall not be a defense to enforcement with respect to
any knowing, willful or systematic violations.
B. 1. Compliance Committee. Within 30 days of entry of this Final Judgment,
Microsoft shall establish a compliance committee (the "Compliance Committee")
of its Board of Directors, consisting of at least three members of the Board of
Directors who are not present or former employees of Microsoft.
2. Compliance Officer. The Compliance Committee shall hire a Compliance Officer,
who shall report directly to the Compliance Committee and to the Chief
Executive Officer of Microsoft. The Compliance Officer shall be responsible for
development and supervision of Microsoft's internal programs to ensure
compliance with the antitrust laws and this Final Judgment. Microsoft shall give
the Compliance Officer all necessary authority and resources to discharge the
responsibilities listed herein.
3. Duties of Compliance Officer. The Compliance Officer shall:
a. within 60 days after entry of this Final Judgment, arrange for delivery to
all officers and directors of Microsoft a copy of this Final Judgment
together with additional informational materials describing the conduct
prohibited and required by this Final Judgment;
b. arrange for delivery in a timely manner of a copy of this Final Judgment
and such additional informational materials to any person who succeeds to
a position described in Section IV.B.3.a above;
c. ensure that those persons described in subsection c.i above are annually
briefed on the meaning and requirements of this Final Judgment and the
United States antitrust laws and advising them that Microsoft's legal
advisors are available to confer with them regarding any question
concerning compliance with this Final Judgment or under the United
States antitrust laws;
d. obtain from each person described in Section IV.B.3.a within 60 days of
entry of this Final Judgment and annually thereafter, and for each person
thereafter succeeding to such a position within 10 days of such succession
and annually thereafter, a written certification that he or she: (i) has read,
understands, and agrees to abide by the terms of, and has to their
knowledge not violated, this Final Judgment; and (ii) has been advised and
understands that his or her failure to comply with this Final Judgment may
result in a finding of contempt of court;
e. maintain a record of persons to whom this Final Judgment has been
distributed and from whom, pursuant to Section V.B.3.d above has been
10
obtained;
f. on an annual basis, certify to the Plaintiffs that Microsoft is fully
compliant with this Final Judgment;
g. maintain a record of all complaints received and action taken by Microsoft
with respect to each such complaint; and
g. report promptly to the Plaintiffs any credible evidence of violation of this
Final Judgment.
4. The Compliance Officer may be removed only by the Chief Executive Officer
with the concurrence of the Compliance Committee.
V. Termination
A. Unless this Court grants an extension, this Final Judgment will expire on the fifth
anniversary of the date on which it takes effect.
B. In any enforcement proceeding in which the Court has found that Microsoft has engaged
in a pattern of willful and systematic violations, the Plaintiffs may apply to the Court for
a one-time extension of this Final Judgment of up to two years, together with such other
relief as the Court may deem appropriate.
VI. Definitions
A. "API" means application programming interface, including any interface that Microsoft
is obligated to disclose pursuant to III.D.
B. "Communications Protocol" means the set of rules for information exchange to
accomplish predefined tasks between a Windows Operating System Product and a server
operating system product connected via a network, including, but not limited to, a local
area network, a wide area network or the Internet. These rules govern the format,
semantics, timing, sequencing, and error control of messages exchanged over a network.
C. "Consideration" means any monetary payment or the provision of preferential licensing
terms; technical, marketing, and sales support; enabling programs; product information;
information about future plans; developer support; hardware or software certification or
approval; or permission to display trademarks, icons or logos.
D. "Covered OEMs" means the 20 OEMs with the highest worldwide volume of licenses of
Windows Operating System Products reported to Microsoft in Microsoft's fiscal year
preceding the effective date of the Final Judgment. The OEMs that fall within this
definition of Covered OEMs shall be recomputed by Microsoft as soon as practicable
after the close of each of Microsoft's fiscal years.
E. "Documentation" means all information regarding the identification and means of using
APIs that a person of ordinary skill in the art requires to make effective use of those
11
APIs. Such information shall be of the sort and to the level of specificity, precision and
detail that Microsoft customarily provides for APIs it documents in the Microsoft
Developer Network ("MSDN").
F. "IAP" means an Internet access provider that provides consumers with a connection to
the Internet, with or without its own proprietary content.
G. "ICP" means an Internet content provider that provides content to users of the Internet by
maintaining Web sites.
H. "IHV" means an independent hardware vendor that develops hardware to be included in
or used with a Personal Computer running a Windows Operating System Product.
I. "ISV" means an entity other than Microsoft that is engaged in the development or
marketing of software products.
J. "Microsoft Middleware" means software code that
1. Microsoft distributes separately from a Windows Operating System Product to
update that Windows Operating System Product;
2. is Trademarked or is marketed by Microsoft as a major version of any Microsoft
Middleware Product defined in section VI.K.1; and
3. provides the same or substantially similar functionality as a Microsoft
Middleware Product.
Microsoft Middleware shall include at least the software code that controls most or all
of the user interface elements of that Microsoft Middleware. Software code described as part of,
and distributed separately to update, a Microsoft Middleware Product shall not be deemed
Microsoft Middleware unless identified as a new major version of that Microsoft Middleware
Product. A major version shall be identified by a whole number or by a number with just a single
digit to the right of the decimal point.
K. "Microsoft Middleware Product" means
1. the functionality provided by Internet Explorer, Microsoft's Java Virtual
Machine, Windows Media Player, Windows Messenger, Outlook Express and
their successors in a Windows Operating System Product, and
2. for any functionality that is first licensed, distributed or sold by Microsoft after
the entry of this Final Judgment and that is part of any Windows Operating
System Product
a. Internet browsers, email client software, networked audio/video client
software, instant messaging software or
b. functionality provided by Microsoft software that --
i. is, or in the year preceding the commercial release of any new
Windows Operating System Product was, distributed separately by
Microsoft (or by an entity acquired by Microsoft) from a Windows
Operating System Product;
12
ii. is similar to the functionality provided by a Non-Microsoft
Middleware Product; and
iii. is Trademarked.
Functionality that Microsoft describes or markets as being part of a Microsoft Middleware
Product (such as a service pack, upgrade, or bug fix for Internet Explorer), or that is a version of
a Microsoft Middleware Product (such as Internet Explorer 5.5), shall be considered to be part of
that Microsoft Middleware Product.
L. "Microsoft Platform Software" means (i) a Windows Operating System Product and/or
(ii) a Microsoft Middleware Product.
M. "Non-Microsoft Middleware" means a non-Microsoft software product running on a
Windows Operating System Product that exposes a range of functionality to ISVs
through published APIs, and that could, if ported to or made interoperable with, a non-
Microsoft Operating System, thereby make it easier for applications that rely in whole or
in part on the functionality supplied by that software product to be ported to or run on
that non-Microsoft Operating System.
N. "Non-Microsoft Middleware Product" means a non-Microsoft software product running
on a Windows Operating System Product (i) that exposes a range of functionality to ISVs
through published APIs, and that could, if ported to or made interoperable with, a
non-Microsoft Operating System, thereby make it easier for applications that rely in
whole or in part on the functionality supplied by that software product to be ported to or
run on that non-Microsoft Operating System, and (ii) of which at least one million copies
were distributed in the United States within the previous year.
O. "OEM" means an original equipment manufacturer of Personal Computers that is a
licensee of a Windows Operating System Product.
P. "Operating System" means the software code that, inter alia, (i) controls the allocation
and usage of hardware resources (such as the microprocessor and various peripheral
devices) of a Personal Computer, (ii) provides a platform for developing applications by
exposing functionality to ISVs through APIs, and (iii) supplies a user interface that
enables users to access functionality of the operating system and in which they can run
applications.
Q. "Personal Computer" means any computer configured so that its primary purpose is for
use by one person at a time, that uses a video display and keyboard (whether or not that
video display and keyboard is included) and that contains an Intel x86 compatible (or
successor) microprocessor. Servers, television set top boxes, handheld computers, game
consoles, telephones, pagers, and personal digital assistants are examples of products that
are not Personal Computers within the meaning of this definition.
R. "Timely Manner" means at the time Microsoft first releases a beta test version of a
Windows Operating System Product that is made available via an MSDN subscription
13
offering or of which 150,000 or more beta copies are distributed.
S. "Top-Level Window" means a window displayed by a Windows Operating System
Product that (a) has its own window controls, such as move, resize, close, minimize, and
maximize, (b) can contain sub-windows, and (c) contains user interface elements under
the control of at least one independent process.
T. "Trademarked" means distributed in commerce and identified as distributed by a name
other than Microsoft® or Windows® that Microsoft has claimed as a trademark or
service mark by (i) marking the name with trademark notices, such as ® or (TM), in
connection with a product distributed in the United States; (ii) filing an application for
trademark protection for the name in the United States Patent and Trademark Office; or
(iii) asserting the name as a trademark in the United States in a demand letter or lawsuit.
Any product distributed under descriptive or generic terms or a name comprised of the
Microsoft® or Windows® trademarks together with descriptive or generic terms shall not
be Trademarked as that term is used in this Final Judgment. Microsoft hereby disclaims
any trademark rights in such descriptive or generic terms apart from the Microsoft® or
Windows® trademarks, and hereby abandons any such rights that it may acquire in the
future.
U. "Windows Operating System Product" means the software code (as opposed to source
code) distributed commercially by Microsoft for use with Personal Computers as
Windows 2000 Professional, Windows XP Home, Windows XP Professional, and
successors to the foregoing, including the Personal Computer versions of the products
currently code named "Longhorn" and "Blackcomb" and their successors, including
upgrades, bug fixes, service packs, etc. The software code that comprises a Windows
Operating System Product shall be determined by Microsoft in its sole discretion.
VII. Further Elements
Jurisdiction is retained by this Court over this action such that the Court may act sua sponte to
issue further orders or directions, including but not limited to orders or directions relating to the
construction or carrying out of this Final Judgment, the enforcement of compliance therewith,
the modification thereof, and the punishment of any violation thereof.
Jurisdiction is retained by this Court over this action and the parties thereto for the purpose of
enabling the parties to this action to apply to this Court at any time for further orders and
directions as may be necessary or appropriate to carry out or construe this Final Judgment, to
modify or terminate any of its provisions, to enforce compliance, and to punish violations of its
provisions.
Unless otherwise indicated, the provisions of this Final Judgment shall take effect 30 days after
the date on which it is entered.
In accordance with the imposition and affirmance of liability, the Plaintiff States shall submit a
14
motion for the award of costs and fees, with supporting documents as necessary, not later than 45
days after the entry of this Final Judgment.
VIII. Third Party Rights
Nothing in this Final Judgment is intended to confer upon any other persons any rights or
remedies of any nature whatsoever hereunder or by reason of this Final Judgment.
SO ORDERED.
_____________________________
COLLEEN KOLLAR-KOTELLY
United States District Judge
Silly, I use screen within my shell.. Oh yeah, the thing that would interpret my actions.
Oh, and if I were new to this area, I would man map. Silly bumpkin