Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Closed source

Related Topics

In the News (Fri 19 Jul 19)

  Closed source - Wikipedia, the free encyclopedia
Closed source is an antonym for open source software and refers to any program whose license does not meet the definition of open source software.
The phrase "Closed source" is ambiguous because it implies licensing where the source code to a program is unavailable.
Microsoft's Shared source is an example of licensing where the source code is made available but not under an Open source license.
en.wikipedia.org /wiki/Closed_source   (239 words)

 Open vs. Closed Source Software
The reasons for writing open source software range from those who have a passion for computing and who want to contribute to make a difference to those who do not like having to rely on any single company to produce what is needed.
Unlike closed source software, the software is normally provided without warranty and you have no recourse should the software malfunction or not perform, there is also no guarantee of good documentation or support.
In the author's opinion, the abilities and friendliness of open and closed source software are merging, and the real showdown will happen in five to ten years when the only real difference between the two classes will be the cost.
www.scienceinafrica.co.za /2004/january/software.htm   (1529 words)

 Closed Source Is Fertile Ground for Foul Play
Perhaps not today, nor even tomorrow, and not because closed source products are less capable or less efficient than non-commercial products, but because sooner or later, governments that rely on expensive closed source software will put their country's and their citizens' data in harm's way.
Closed source advocates wrongfully maintain that the lack eyes looking at the source tends to prevent problems as well as inefficiencies from being discovered—and that those same lack of eyes would not miss and fail to repair maliciously inserted code as well.
The closed source model does a good job finding and winnowing out malicious code submitted as part of a project when the people in charge of the true project source are both actively looking for potential security problems and also not actively attempting to subvert the model.
www.swoogan.com /Closed_Source.html   (1261 words)

 Why Open Source   (Site not responding. Last check: 2007-10-10)
Since it is open source, and the most recent work is always being published, users or customers will be aware of what the feature is and chances are someone will be interested in paying the developer to finish the project.
An open source software company will be honest and up front about how your problem will be solved: you let us know what your problem is, we give a time and cost estimate, you decide yes or no or change the requirements, and off the solution to the problem goes.
Open source software companies give a big thing to their customers: the customer does not have to continue paying if the service level is too low, they can go elsewhere.
incubator.apache.org /ofbiz/whyopensource.html   (2503 words)

 The security implications of open source software
To the closed source camp, a system can't be truly secure when its source is open for all to read.
According to his article on open source myths (see Resources later in this article), it is common for developers to use cryptography, but misapply it in ways that destroy the security of the system, or to use encryption that is too weak and can easily be broken.
Another complaint with open source software is that most bugs are found after the program has been compiled, tested, and distributed -- not because someone sat down in advance and looked at the code for holes, but because something goes wrong in its use.
www-106.ibm.com /developerworks/linux/library/l-oss.html   (2140 words)

 Open source software is better for society than proprietary closed source software
With open source software, the issue of an undocumented protocol cannot arise--the source code to a program implementing a protocol is a well-defined specification for the part of the protocol that the program implements.
Closed source programmers are less likely to have a personal stake in a program; usually, they write code because they are paid to write it, not because it is software that they want to or need to use.
Proprietary closed source software, with the intermediation between programmers and users that implies (see section Social Impact (Environment)), does not allow for the formation of communities of users and programmers together.
www.stanford.edu /~blp/writings/anp/oss-is-better.html   (5558 words)

 Open source vs. closed source - Wikipedia, the free encyclopedia
Traditionally, source code has been hidden from anyone outside the company that developed the software and the code is treated as a trade secret which companies may attempt to patent.
Closed source software usually is developed and maintained by a relatively small team who produce their "product" in a compiled executable state, which is what the market is allowed access to.
Closed source advocates, including Microsoft corporation, argue that since no one is responsible for open source, there is no way to know whether it has been fixed.
en.wikipedia.org /wiki/Open_source_vs._closed_source   (4207 words)

 Open Source Versus Closed Source Security
Although you can take an open source project, compare it against a closed source project, and say that one is more secure than the other based on some number of observations or measurements, this determination will probably be based on factors other than the nature of the project's open or closed source code.
Secure design, source code auditing, quality developers, design process, and other factors, all play into the security of a project, and none of these are directly related to a project being open or closed source.
On the other hand, I've seen some vulnerabilities in open source software that are so obscure (some of the Sendmail prescan() vulnerabilities come to mind), that you wonder if it would be feasible to discover a similar issue in a closed source project at all.
www.securityfocus.com /columnists/269   (1101 words)

 Ramblings of a Code Monkey: Open Source vs. Closed Source Stories
The author uses this to show that the closed source development model is flawed, because as soon as the company that makes the product goes away, then their customers are, basically, screwed.
The closed source model allowed Microsoft to make a very simple to use operating system and office suite, especially when you consider just how complex and feature rich they really are.
I will admit that I am partial to closed source, not only because that's how I make my living but also because, from my experience, the products produced by the closed source methodology are in general of high quality than those produced by the open source movement.
www.milbertus.com /archives/2003/10/25/open_source_vs.php   (1982 words)

 Closed Source-Open Source
Closed Source software is code that is written and compiled into machine instructions that allow you to do things with your computer like read this.
Open Source software is code that is written and compiled into machine instructions that allow you to do things with your computer as well.
The difference is that the Source Code is available for you to examine, rewrite, change and scratch your head in wonder like me. I use programs, rather than creating them.
www.lemurzone.com /edit/converse39.htm   (778 words)

 The Closed Source Dilemma
Open source applications allow for smaller faster moving companies to provide a new product to customers that are either over served by the current products available or are not in the market for the product at all.
Open source is great at forcing for-profit software companies to quit milking their cash-cow commodity products and start investing more in research and development of new packages.
Open source software is not inherently better than commercial software; it all depends on the problem to be solved and the maturity of the solution being considered.
www.swampfox.ws /index/html-get-innovation   (2842 words)

 ONLamp.com -- Open Source and Open Standards
While he sets up an opposition between standards and source (that little word "versus" in his title), in reality there is no such thing--the two are mostly orthogonal to each other and, as we shall see, both are necessary.
Thus closed formats and protocols are not necessarily the death knell for open source.
If Closed Protocols are allowed to replace them, Open Source is doomed as a legally useful product unless the DMCA and numerous software patents are invalidated and there's very little chance of that.
www.onlamp.com /pub/a/onlamp/2003/04/29/openstandardsopensource.html   (1733 words)

 Why open source security software bests proprietary products   (Site not responding. Last check: 2007-10-10)
On the other hand, open-source developers know that their source code will be examined carefully by potential attackers, and they must, therefore, work much harder to protect against attacks.
Besides the quality issue, open source software is appealing because it is often freely licensed, saving a company the licensing cost.
What's really different about using open source software is that the relationship between the developers and users is usually a close one.
searchopensource.techtarget.com /tip/0,289483,sid39_gci964659,00.html   (1006 words)

 Wikipedia forms partnership with company producing closed-source software | Nerdshift   (Site not responding. Last check: 2007-10-10)
Since the source code (which is human-readable) is not given, users of the software will not be free to "tinker" with it, and the utility is not free/libre open-source software (FLOSS).
The open content and FLOSS (free/libre open-source software) movements are closely interelated and their philosophy is very similar.
Although Answers Corporation has the legal right to not release its source code (given the current laws), one would expect Wikimedia Foundation to show greater support for free software or open source.
portal.wikinerds.org /wikipedia-closed-source   (1060 words)

 Closed Source Hardware
Trust with hardware vendors for open source systems is becoming a one-way street, where in exchange for support they offer a closed source binary solution with no provision to audit security.
This, of course, is great news; I'm happy that the vendor has at least allowed open source operating systems to support their hardware, and even more so, I'm thankful that a developer spent the time to make it happen.
In general, this mean an increase in support for the open source operating systems -- a rapidly growing segment of the market that drives new hardware purchases -- from the various hardware-producing vendors.
www.securityfocus.com /columnists/281   (1056 words)

 Open or Closed Source Code Irrelevant to Security
For starters, the OSS believers feel their software is more secure because the source code is available for public scrutiny and security fixes can be incorporated by any among a large community of users.
What's more, the source code is not available to the general public, so it's not likely that the curious people with way too much free time on their hands will find bugs and flaws in the software.
Whether the source code (and design documentation, for that matter) become open or closed is utterly irrelevant to the security of the software.
www.esecurityplanet.com /views/article.php/3524356   (966 words)

 Microsuck Forums - Closed Source Reverse Engineering   (Site not responding. Last check: 2007-10-10)
December 11th, 2002 12:33 AM I know that reverse engineering closed source software is probably extremely difficult and time consuming.
I know that reverse engineering closed source software is probably extremely difficult and time consuming.
I believe that you are allowed to reverse engineer closed source software that do not document their protocols and interfaces so as to make your software work/communicate with said closed source software.
www.fuckmicrosoft.com /forums/printthread.php?t=7222   (905 words)

 Open & Closed Source   (Site not responding. Last check: 2007-10-10)
The creaters of Free BSD started with the source code to Berkelel Unix, and their kernel is directly descended from that source code.
Closed Source is not open to the public unlike open source.
When a programmer makes a Closed Source program it is more difficult to compete with those who make Open Souce programs.
www.southern.dpsnc.net /~gunterj/opensource.html   (312 words)

 Open Source vs. Closed Source - Snook.ca
A user commented that he thought "it should be an open source effort so [he’s] not going to help." Which was a really intriguing comment because I hadn't said either way whether it would be open source or not.
krang is an open source perl cms framework that you can build modules on top of.
Nevertheless, for the readers of these articles, showing the code you use along the way may be beneficial to the readers but at the same time, it "closes" the "closed-source" door to a certain extent.
www.snook.ca /archives/000247.html   (1458 words)

 Open Source Initiative OSI - FAQ:Advocacy   (Site not responding. Last check: 2007-10-10)
The Open Source Initiative does not have a position on whether ideas can be owned, whether patents are good or bad, or any of the related controversies.
The term "open source" has a technical meaning in the intelligence community; it refers to publicly accessible intelligence sources such as newspapers.
While there is agreement on the broad term "open source" as meaning approximately what is captured in the Open Source Definition the term has, ironically, now become so popular that it has lost some of its precision.
www.opensource.org /advocacy/faq.html   (1357 words)

 Damicon - Open source versus closed source
Let's first define what is meant by open source and closed source and how they differ.
Open-source programs always include source code for those interested in peering into how the program does what it does and possibly contributing to the development effort.
If open source is to have staying power, it must generate new ideas that improve software programs not just copy someone else's work.
www.damicon.com /resources/openvsclosed.html   (1103 words)

 Against the Grain: Getting Projects To Work Together   (Site not responding. Last check: 2007-10-10)
As mentioned in the lead-in, the number one challenge open source interop faces is cultural biases within communities.
The memetic explanation for these effects is that autoimmune responses kick in to defend the culture of a project against threats from the outside.
On the closed source side, you see many interoperability failures in mature products, as well as a vested interest in proprietary file formats or protocols as a way to try to lock in users.
www.advogato.org /article/657.html   (2651 words)

 Is Open Source Really More Secure?   (Site not responding. Last check: 2007-10-10)
This is in contrast to “closed” or proprietary software such as Microsoft Windows, for which the source code is a closely guarded trade secret (except when it’s leaked to the public).
Open source advocates counter that this is merely a form of “security through obscurity,” a concept that’s generally dismissed as ineffective in the IT community.
Of course, the open source people can respond that the very fact that Microsoft has more “enemies” makes their software inherently less secure because so many are trying to bring it down.
www.windowsecurity.com /articles/Open_Source_Secure.html   (1666 words)

 Open Options | Implications of closed source
Open source proponents argue that compatibility is better achieved and preserved with open formats.
Some people believe that open source produces better software because the process and product are open.
Since they control the source code, the company should be able to control risks and close loopholes.
www.netc.org /openoptions/background/closed.html   (743 words)

 Closed Source Is Less Secure   (Site not responding. Last check: 2007-10-10)
It means that your source is closed to peer-review, because it has something to hide.
Contrast this with the Defense Contractor world, where the source is made secret not for technical reasons (so only losers can take a look at it) but purely for political motivations.
If the source code is closed, it does not automatically mean that it is not reviewed.
c2.com /cgi/wiki?ClosedSourceIsLessSecure   (579 words)

 Open Source
Usually in close contact with the coordinator, and in fact these roles can overlap or be rotated.
We have no comparable way of learning closed shops' true rate of 'success' on any conceivable metric; the best proxy would be a sample taken to be representative of the entire population of closed shops, but even then, the ones that refused to participate in such a study might well differ systematically from the norm.
For that matter, nominal open source projects that are failures on commercial and conventional open source criteria alike may well be counted as successful by their primary developers, for instance, student projects.
c2.com /cgi/wiki?OpenSource   (1481 words)

 Slashdot | Mac OS X Kernel Source Now Closed
If the kernel and driver source were available, it would, however, be used for one purpose: to churn out hacks to get OS X to run on non-Apple hardware in a much faster and higher-quality way than has been possible to date.
But they did grasp how to utilize open source to their advantage, but it was always in a way that was really not quite in the spirit of the open source community.
Yes the source code was always available for Darwin and the pieces of OS X. But rarely in patch form and often not buildable without tracking down internal header files.
rss.slashdot.org /Slashdot/slashdotApple?m=307   (6613 words)

 » Can closed source survive? | Open Source | ZDNet.com
What Dargo was saying is that open source is going to become the norm.
Just as we no longer talk about e-commerce, just commerce, we will wonder in five years why anyone assumes their source code should be closed.
While the database space argues between open source advocates such as mySQL and closed source advocates such as Oracle, Dargo said Ingres is trying to evolve a "subscription model," where the money you pay for support and updates really goes into delivering support services and new functionality.
blogs.zdnet.com /open-source/?p=599   (448 words)

Try your search on: Qwika (all wikis)

  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.