Slashdot Mirror


Did MS Lobbying Stop NSA Work On SELinux?

inquisitive points to this CNET story on how George Wash Univ. may help Linux gain certification under the Common Criteria, certification required for software to be used in some sensitive government roles. In the same story, though, is an interesting quote from another effort at bringing GPL'd software to the public sector: "'We didn't fully understand the consequences of releasing software under the GPL (General Public License),' said Dick Schafer, deputy director of the NSA. 'We received a lot of loud complaints regarding our efforts with SE Linux.'" Sources familiar with events said that aggressive Microsoft lobbying efforts have contributed to a halt on any further work. 'Microsoft was worried that the NSA's releasing open-source software would compete with American proprietary software,' said a source familiar with the complaints against the NSA who asked not to be identified."

549 comments

  1. NSA by jxs2151 · · Score: 0

    And we are supposed to believe anything remotely associated with the letters N, S and A ??

    1. Re:NSA by Anonymous Coward · · Score: 0

      MOpre importantly, an add for Visual Studio.net on /.???? Never thought I'd see the day!!!

  2. news at 11 by seann · · Score: 1, Insightful

    college and universitys cheating those who already know the job out of jobs because they teach average joes how to do a better job.

    --
    I'm a big retard who forgot to log out of Slashdot on Mike's computer! LOOK AT ME.
    1. Re:news at 11 by Anonymous Coward · · Score: 0

      What are you talking about? I know what each of those words mean individually, but when you put them together in that order....

    2. Re:news at 11 by Anonymous Coward · · Score: 0

      Here's my attempt to translate:

      college and universitys are cheating self taught people out of jobs because they teach average joes how to do the same job better.

      In other words "they know how to do it better because they went to school and learned it. And because of that people hire them instead of me! no fair!"

      Course, this was probably a troll, and as such I reply anonymously to avoid direct ridicule. ;)

  3. It's a new concept... by Demon-Xanth · · Score: 5, Insightful

    ...called competition.
    'Microsoft was worried that the NSA's releasing open- source software would compete with American proprietary software,'

    Apparantly MS is worried that it'll catch on.

    --
    If you think education is expensive, you should try ignorance -- Derek Bok, president of Harvard
    1. Re:It's a new concept... by paladin_tom · · Score: 5, Insightful

      The issue here that made the U.S. government listen is that the "open-source software would compete with American proprietary software." The article states clearly that "Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business."

      This is another example of American government's actions being fuelled by a desire to help American businesses to the detriment of individual freedom, similar to the DCMA.

      --
      #define sig "Every social system runs on the people's belief in it."
    2. Re:It's a new concept... by Slak · · Score: 2

      Yes, but wouldn't it only compete against a *secure* operating system, like those bastard loonies who work on OpenBSD ;)

      Cheers,
      Slak

    3. Re:It's a new concept... by Skyshadow · · Score: 2, Insightful
      This is another example of American government's actions being fuelled by a desire to help American businesses to the detriment of individual freedom, similar to the DCMA.

      Wow, that's wildly inaccurate. I mean, you're astoundingly off-base.

      You're just as free to sit down and work on a patch for the Linux kernal today as you were yesterday; the only difference right now is that the NSA has decided not to work on it with you.

      When you think about it, the government's only real job is to defend the rights and freedoms of its citizens. Among those freedoms, at least here in America, is the right to start a business and engage in free enterprise. Therefore, when the government interferes with free enterprise, it's interfering with the rights of its citizens.

      You can't have it both ways. The same laws that protect Microsoft's ability to sell software protect your right to give it away.

      --
      Every year during my review, I just pray the words "slashdot.org" aren't mentioned.
    4. Re:It's a new concept... by paladin_tom · · Score: 1

      From an economic standpoint, that doesn't matter. The U.S. government is concerned much more with economic competition than with competition among different free software products.

      Having people freely download American SELinux instead of Canadian OpenBSD doesn't equal more money in the American economy.

      --
      #define sig "Every social system runs on the people's belief in it."
    5. Re:It's a new concept... by Anonymous Coward · · Score: 0

      Well said, thank you

    6. Re:It's a new concept... by Anonymous Coward · · Score: 0

      If they give their dicoveries to everyone, how is it unfair to anyone?

    7. Re:It's a new concept... by paladin_tom · · Score: 2, Interesting

      Wow, that's wildly inaccurate. I mean, you're astoundingly off-base.

      You've got a point, there. I just meant that the U.S. gov't is partial to the needs of business, and doesn't really care about free software.

      When you think about it, the government's only real job is to defend the rights and freedoms of its citizens.

      So, you're saying that governments build roads to protect the mobility rights of citizens, for example? I think governments' jobs go much broader than that.

      Among those freedoms, at least here in America, is the right to start a business and engage in free enterprise.

      But rights must be balenced. If I may play the devil's advocate, one of the ideological underpinnings of the Free Software movement is that one's right to make money is less important than everyone's right to improve software, and your responsibility to help others.

      The same laws that protect Microsoft's ability to sell software protect your right to give it away.

      Well, the U.S. government does place restrictions on one's right to give software away (in the case of strong cryptography). Hence OpenBSD is based in Canada.

      --
      #define sig "Every social system runs on the people's belief in it."
    8. Re:It's a new concept... by flacco · · Score: 0, Troll
      NSA has decided not to work on it with you.

      Oh fuck off you toadie apologist scumbag.

      The article pretty clearly says the NSA backed off on its work because of political pressure from Microsoft.

      --
      pr0n - keeping monitor glass spotless since 1981.
    9. Re:It's a new concept... by startled · · Score: 3, Insightful

      He's not as off-base as you think. Why do we want free enterprise? Why do we want people to start businesses? For economic progress, of course. We all want to be richer and better off, to get better health care, to have enough to eat, and so on.

      If the government takes my money and makes something really useful with it, which provides more economic benefit to the country: giving it away so everyone can build on it and be more technologically advanced; or hiding it away so no one else can use it, and someone has to waste time building it a second time?

    10. Re:It's a new concept... by PainKilleR-CE · · Score: 1

      So, you're saying that governments build roads to protect the mobility rights of citizens, for example? I think governments' jobs go much broader than that.



      The government builds roads in order to make other government services (police, fire, military, among others) more efficient, which should, in turn, help protect the rights of citizens.

      --
      -PainKilleR-[CE]
    11. Re:It's a new concept... by Anonymous Coward · · Score: 0

      Go ahead and rationalize theft all you can.

      The government can achieve its ends by violence, something no other entity can legally do.

      So when you speak of what the government does, make sure you add the phrase 'At the point of a gun'.

    12. Re:It's a new concept... by Jeremiah+Cornelius · · Score: 3, Insightful
      These technology issues are not separate from any other social, political or economic threat posed to a democratic society. The issues and subject matter are sometimes daunting in complexity, and obtuse in their argument.
      This means that they are difficult to comprehend and absorb for people not conversant in the technology itself.

      That is a real danger.

      It is dangerous not to understand what is happening here on an international scale.

      In terms of censorship, social control and the relegation of individual populations to a second-class of citizenship, technology issues like this will have a more direct effect than tariffs or export laws.

      What you are allowed read in books and watch on TV will be subject to its profit potential for large corporations. Read that again. Anything else will be Samizdat .

      This will be enforced through agreements and laws like DMCA, UCITA, and the proposed SSSCA and CBDTP. Less is known by even informed people about these laws, than say -NAFTA.

      Why? Because at a cursory glance, the subject matter is dismissed as being too technical, or "just something about TV."

      When second-hand bookshops are being closed - for being unable to meet the minimum payments on 'royalties for redistribution of intellectual property,' everyone will wonder what happened. It started with Internet Audio Broadcasters. You think this is far-fetched, or satirical? Go ask SOMA-FM

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    13. Re:It's a new concept... by mobiGeek · · Score: 2
      like those bastard loonies who work on OpenBSD

      I'm sure its not just Canadians working on OpenBSD...

      --

      ...Beware the IDEs of Microsoft...

    14. Re:It's a new concept... by flacco · · Score: 2

      alas, what's the world coming to when you can't call someone a toadie apologist scumbag during the course of polite conversation.

      --
      pr0n - keeping monitor glass spotless since 1981.
    15. Re:It's a new concept... by mpe · · Score: 2

      If the government takes my money and makes something really useful with it, which provides more economic benefit to the country: giving it away so everyone can build on it and be more technologically advanced; or hiding it away so no one else can use it, and someone has to waste time building it a second time?

      In this case we have someone saying "you can't create something potentially useful and valuable, because it might break our business model". When it isn't the job of government to protect the business models of private commercial entities in the first place.
      Creating "something really useful", like an improved technology frequently bankrupts businesses who cling to old business models. Whilst at the same time improving the profitability of existing business which embraces the new and new business.

    16. Re:It's a new concept... by Anonymous Coward · · Score: 0

      I think the point is that the corps can't take the code, make something with it, and then sell it to you without divulging their IP.

      If the NSA could release their stuff under the BSD license, there'd be no complaint, because the corps could take the code everyone has access to and sell it to suckers.

    17. Re:It's a new concept... by Anonymous Coward · · Score: 0

      More importantly, 99% of Americans use non-GPL systems, so anything produced by the NSA's SELinux would only be available to the 1% or so who do use GPL systems. On top of that, the cyber-criminal element disproportionatly use GPL systems, and helping to secure the criminals' systems of choice at the expense of the law-abiding majority would be detrimental to public security in general.

    18. Re:It's a new concept... by ichimunki · · Score: 1
      It doesn't really mean less either. The amount that people have to spend is a constant. What they spend it on is not. If they can download SELinux for free, or OpenBSD for free, then they can spend that money on something else-- and probably will. The overall economy is probably unaffected as a result, in fact we could argue that the economy is improved since people get more utility overall with less expense. From what I understand that is the whole goal of an economy: to distribute maximum utility as efficiently as possible.

      But I think Microsoft sees it as lost revenue when anyone uses software that does something that MS writes software to do. And to some extent that's correct... that the government should avoid GPL software, however, does not follow logically from this assumption. That they cannot effectively compete with a product that is as free as the air we breathe is a problem with their business model. And, frankly, it's fair play via turnabout-- that's what they did to Netscape, after all.

      --
      I do not have a signature
  4. Government competition by alen · · Score: 3, Insightful

    If the NSA software would compete with MS, then the government has no business releasing it. Government isn't there to compete with private industry. It's unfair, especially considering the fact that the government can subsidize any projects with tax money that comes from it's competitors.

    1. Re:Government competition by jeffy124 · · Score: 1

      well, the government kinda already competes with corporate america. Take the us postal service as an example. It competes with FedEX and UPS.

      --
      The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
    2. Re:Government competition by reaper20 · · Score: 2

      That's just ignorant - do you know how many things the US Goverment currently subsidizes?

      You're right, the government isn't there to compete with industry - it's here to run the country, and it's obvious that SELinux filled a necessary need, otherwise the government wouldn't have needed to subsidize it. Obviously the government felt that there was a need for a more secure operating system.

    3. Re:Government competition by SeanTobin · · Score: 1

      It shouldn't be a problem in Microsoft's case. They don't pay any taxes anyway (directly).

      --
      Karma: SELECT `karma` FROM `users` WHERE `userid`=138474;
    4. Re: Government competition by Black+Parrot · · Score: 2, Insightful


      > It's unfair, especially considering the fact that the government can subsidize any projects with tax money that comes from it's competitors.

      In that case we know Microsoft won't be complaining.

      No taxes; no dividends; sweet deal for Gates and his buddies.

      --
      Sheesh, evil *and* a jerk. -- Jade
    5. Re:Government competition by fatboy · · Score: 2, Interesting

      If the NSA software would compete with MS, then the government has no business releasing it. Government isn't there to compete with private industry. It's unfair, especially considering the fact that the government can subsidize any projects with tax money that comes from it's competitors.

      Mmm, but it's ok to use a Government funded (BSD) TCP/IP stack in the MS Operating Systems right?

      The point is that SE-Linux is free for Microsoft or anyone else to use. It did not compete with Windows, it's a Unix.

      --
      --fatboy
    6. Re:Government competition by obsidian+head · · Score: 1

      Then why not relase the SELinux changes as under BSD license? BSD can be integrated with GPLed code, since BSD is compatible with the GPL. And BSD is not really a competitor to proprietary software.

    7. Re:Government competition by EvilTwinSkippy · · Score: 5, Insightful
      I refute your statement thus:

      First - there is no product from Microsoft that is in direct competition. There will be no product for the forseeable future.

      Second - The NSA would require the source code for whatever system in deploys. It would have to component test all of the subsystems, and ensure that no new bugs are introduced with new features. This flies in the face of the Upgrade Early, Upgrade Often mentalility an M$. (NASA users 486's in the space program, not to be cheap, but because they are a known quantity.)

      Third - What the government produces, all competitors share equally. What microsoft produces, it keeps to itself.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    8. Re:Government competition by Anonymous Coward · · Score: 0

      SELinux directly modified the kernel, which is GPL'd. Under terms of said GPL, they released the sources under the GPL itself. Also under terms of said GPL, they cannot release it under any other license.

      If they wanted to do a SE-BSD, they would have used a BSD-licensed OS.

    9. Re:Government competition by Anonymous Coward · · Score: 0

      -- If the NSA software would compete with MS, then the government has no business releasing it. Government isn't there to compete with private industry. --

      Government isn't there to spend money on software and services that can be obtained more inexpensively elsewhere.

      To force the government to use "private-industry software" amounts to nothing more than welfare to the private-industry.

    10. Re:Government competition by Hammer · · Score: 1

      This was among the worst UltraCapitalist nonsense I have read.
      NSA was trying to create a safe, secure OS, presumably for own, government and public use. It is in the governments own interest to proceed with that. If a government agency can do this cheaper and/or better with tax money than Microsoft can, great that is in the taxpayers interest and to f--king bad for MS. If they cannot then they should not. However, with MS trackrecord I am absolutely certain that NSA can do it both better and cheaper. Remember that it would otherwise be taxpayer money that would subsidize Microsoft without any benefit to the taxpayer...
      GPL states that they would have to release it if it's to be used outside of NSA.

    11. Re:Government competition by windex · · Score: 1

      In theory, the postal service is a goverment managed, but private organization.

      When the renewal agreements between the postal service and the US come up, it's possible for a competitor to take over, but they're under the same rules and regulations that the postal service is, and they don't want to play that way (they want to charge more).

    12. Re:Government competition by Psx29 · · Score: 1
      If the NSA software would compete with MS, then the government has no business releasing it. Government isn't there to compete with private industry. It's unfair, especially considering the fact that the government can subsidize any projects with tax money that comes from it's competitors.

      The government gives money to public schools but you still have private schools, is that competing with private industry? The government has recently enforced tariffs on steel and farm subsidies so US markets can succeed, is that competing with private industry? I am not saying any of these things are good or bad, but creating free software is fairly miniscule compared to the economic impact of the other things the government has done.

    13. Re:Government competition by theNote · · Score: 1, Insightful

      How could this be modded flamebait?
      Just because you don't agree with what the poster is saying?

      The truth is, it is the LAW!

      I write software for the government, and this is something we run into all the time.

      If a government agency wants to provide a new software service, it must ensure it does not compete with exisitng commercial service.

      Guess what, if the post office hadn't existed before FedEX and UPS, THERE WOULD BE NO POST OFFICE. It would not have been given the go ahead to be created.

      Government agencies are not allowed to undercut existing commercial businesses with new services.
      It is one of the oldest rules of government contracting.

    14. Re:Government competition by alen · · Score: 2

      If you haven't realized it, the USPS has been around since the 1800's. Fedex and UPS since the 70's I believe. UPS only went public in 1999. Only trouble with getting rid of the post office is deciding who takes care of residential mail which no one wants because of the cost involved.

      Private schools are another example, but education was basically nationalized in the last century. Only private schools are religious ones and those who cater to the wealthier people in society.

    15. Re:Government competition by jcast · · Score: 1

      If you haven't noticed, the reason the only private schools are religious or exclusive is because nobody else can afford them.

      Which sort of backs up the OP's point.

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    16. Re:Government competition by Anonymous Coward · · Score: 0
      Mmm, but it's ok to use a Government funded (BSD) TCP/IP stack in the MS Operating Systems right?

      Right. Because the BSD license under which the tcp/ip stack was released allows companies to incorporate that code, without requiring they give away derivative works. They're not saying "no free software," they're saying "no restrictive licences".

    17. Re:Government competition by jcast · · Score: 1

      Government agencies are not allowed to undercut existing commercial businesses with new services.
      It is one of the oldest rules of government contracting.

      Then where the hell did public schools come from?
      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    18. Re:Government competition by jcast · · Score: 1

      Actually, real UltraCapitalists agree with you---they treat the government as essentially a private organization, morally.

      What the OP was spouting was corporate socialism disguised as capitalism.

      jcast: In need to get a ``Libertarian Nazi'' nick...

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    19. Re:Government competition by flatrock · · Score: 2

      If SELinux fills a necessary need then the covernment contractors and vendors who are selling systems using it to meet the goverment's needs should pay for it's development and certification. The NSA should not be subsidizing the development of a secure version of Linux. It should be able to compete on it's own merits.

      If the NSA is working with others to improve Linux and get it certified to the extent that they do with other OSs, then I think the NSA is doing their job.

      If they are putting in a significant effort beyond what they would do for other OSs, and actually releasing code they developed under a license that restricts it's use by other american companies for reasons other than security, then they are out of line.

      Vendors for other OSs spend millions of dollars developing secure versions of their OS and getting them certified. Linux shouldn't get a free ride.

    20. Re:Government competition by Anonymous Coward · · Score: 0

      Government isn't there to compete with private industry.

      Not true. If the NSA decides to work with open-source code to improve their own systems, why not? They could make a million-dollar deal with to to the same job. It should be the goal of any government to work as effective (and cheap)
      as possible to save the tax-payers money.

      Currently the german government funds the GnuPG development, because they may use the technolgy
      in the near future.

    21. Re:Government competition by Anonymous Coward · · Score: 0

      So then the government has been doing unfair business practices for a LONG time. Anytime they give out a grant to one company, they are unfairly singling out support for that company.

      So say if MS gets a grant for researching something, they're being unfair toward all other companies that could be reasearching that.

      Since it is open source, MS could take that code and build from it. MS could even make their own version of Linux from it.

    22. Re:Government competition by salimma · · Score: 3, Informative
      Large companies like Microsoft do *not*
      pay much in tax.

      Government projects are paid for by taxpayers, mostly individuals and small-to-medium sized companies, and it would be in their interest to have an alternative to Microsoft.

      Look at it this way, with their monopoly Microsoft is about the only entity that can reliably squeeze money out of large corporations.

      My 2 cents,

      --
      Michel
      Fedora Project Contribut
    23. Re:Government competition by Ian+Bicking · · Score: 2
      If the NSA software would compete with MS, then the government has no business releasing it.
      Quite the contrary -- if the NSA or any government agency is producing software that, at no extra cost to them, could benefit the public, then it has no business keeping it to themselves.

      On your argument, municipalities should not be selling water (at dirt-cheap prices too) when there's private companies selling the same product. Should Danon demand that everyone buy water in bottles, rather than having it subsidized by the state?

      The metaphor continues when you realize that the government actually can give water away for very little, and that bottled water companies are manipulative -- selling the same product for a higher price, and introducing innumberable inefficiencies in the process. So it is with SELinux -- MS wants to sell something inferior, inefficient, and overpriced. That's not the free market, it's just another company that wants to drag down the entire nation so it can make a few bucks. I'm sorry, but the advancement of the People of the United States trumps any corporate, profit-motivated interest.

    24. Re:Government competition by sean23007 · · Score: 2

      # Third - What the government produces, all competitors share equally. What microsoft produces, it keeps to itself.

      If everyone were really allowed to use it equally, the government should be required to use something more along the lines of the BSD license, rather than the GPL, because Microsoft simply can't use code that's under the GPL (they'd have to release all their code), but they can use source that's under the BSD license (TCP/IP...). If the NSA produces a linux distro that's under the GPL, they are not allowing all competitors to share equally. If they released it under the BSD license, they would.

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
    25. Re:Government competition by Amazing+Quantum+Man · · Score: 2

      The USPS has been around since the late 1700s.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    26. Re:Government competition by SJS · · Score: 1
      Government isn't there to compete with private industry.
      That is not its purpose, true. The purpose of Government includes protecting the Public Good. Frequently, this means regulating private industry in an attempt to restrain the typical excesses associated with "Business". Less frequently, it can provide publically-funded alternatives when it is in the interests of the population at large to do so. (Consider fire and police departments.)

      What's unfair is that many corporate executives and financial officers will avoid hanging after what's basically 'Grand Theft Martini'. What's unfair is that the government didn't confiscate the assets of Microsoft for their business practices. What's unfair is that businesses can lobby the government to enact or change policy.

      If you want the world to be fair, then you should strive to make it fair for everyone. That's only fair, isn't it?

      --
      Pick One: http://www-rohan.sdsu.edu/~stremler/sigs/sigs.html (Note - disable Javascript first!)
    27. Re:Government competition by neo · · Score: 2

      And if I wanted to build roads and charge people to ride on them... should the government stop building roads?

      Obviously not. SELinux should be a secure *infrastructure* system and the Government has every right to make secure infrastructures.

    28. Re:Government competition by Anonymous Coward · · Score: 0

      Linux doesn't compete with MS, MS competes with Linux. MS has every right to repackage and sell Linux, they just choose not to.

      I'm sorry if Linux undermines their obsolete business model, but that is just too bad.

    29. Re:Government competition by mpe · · Score: 2

      The NSA would require the source code for whatever system in deploys. It would have to component test all of the subsystems, and ensure that no new bugs are introduced with new features. This flies in the face of the Upgrade Early, Upgrade Often mentalility an M$.

      You missed of the "give us money when you upgrade" bit. Can the US taxpayers really be that happy with their taxes going to a rich corporation which practices extensive tax avoidance?

      (NASA users 486's in the space program, not to be cheap, but because they are a known quantity.)

      They'd probably be happier with 386s, if they could get any.

    30. Re:Government competition by cburley · · Score: 1
      Microsoft simply can't use code that's under the GPL (they'd have to release all their code)

      Sheesh, where do you people pick up such BS?

      Microsoft is both using and releasing GPL'ed code right now, including my own GPL'ed code, GNU Fortran (g77). (I think they call it "Unix for Windows", it comes from Interix, a company they bought?)

      The only issue is whether Microsoft feels comfortable competing with a security-enhanced version of Linux that it can't take and cannibalize to suit the license restrictions they choose to impose.

      The GPL, like BSD, both require copyright as an underlying protection, but they both serve the public interest -- one buy ensuring access to source code for anyone possessing a derived copy of the product, the other by not doing so.

      That there might be legislation requiring "public-domaining" any government-written code is a legal hindrance to the government writing GPL'ed or BSD'ed code, but the spirit is preserved by changing the statutes to permit licenses that assure anyone access to the product, such as the GPL and BSD licenses.

      As long as the "restrictions" placed by the licenses on copying and distribution avoid preventing people from making straight copies and distributing to whomever they please, for example, it hardly makes a difference, in terms of the purposes of government authorship, whether such licenses are used versus simply placing works in the public domain.

      But one advantage the GPL will always have over BSD and PD distributions: when the government, or even a state or local government, ends up with software (e.g binaries) derived from government-written software, that government will be assured access to the complete source code for the product only if the original code was distributed under the terms of the GPL.

      Such assurances go a long way towards protecting the public good in terms of safety, security, openness, and even more mundane things such honesty in procurement (since it's harder to hide the fact that they're buying, from a vendor, 100 lines of vendor-specific code buried in 100,000 lines of "public" source code, when the complete source code is "vended").

      --
      Practice random senselessness and act kind of beautiful.
    31. Re:Government competition by cburley · · Score: 1
      Linux shouldn't get a free ride.

      Oh really? Let's see if you can spot which of these does not belong:

      1. Linux shouldn't get a free ride (due to government improving it on taxpayer monies).

      2. Federal law shouldn't get a free ride (due to government "improving" it on taxpayer monies).

      3. MS Windows shouldn't get a free ride (due to government writing improvements for it on taxpayer monies).

      4. The FORTRAN language shouldn't get a free ride (due to government proposing new extensions for it on taxpayer monies).

      Give up? The answer is #3. Why? Because it's the only one that isn't a free public entity -- the others all are, and that's why there are all legitimate "targets" for improvement by a government (assuming it's going to spend taxpayer monies in such efforts anyway). (In fact, all three have been improved by government -- for FORTRAN, it was MIL-STD 1753, I believe, ages ago.)

      Your use of "Linux", on the other hand, suggests you cannot distinguish a free, public operating system from a single-sourced, proprietary operating system (or, more precisely, from the company that produces it).

      Put another way: what individual or organizations benefits from the taxpayer-funded improvements to the software in question?

      For #s 1, 2, and 4 above, the answer is: the public (in fact, the entire planet); for #3, the answer is: Microsoft only -- everyone else has to pay them to realize the improvements, so they aren't direct beneficiaries of the improvements.

      I realize you aren't necessarily advocating that the government spend $$ to improve Windows for free, but thinking that Linux shouldn't be improved for free is, frankly, seriously misguided.

      (And what people arguing against GPL'ed government software are saying, in essence, is: let's make sure Microsoft can resell taxpayer-funded code at a profit, with severe license restrictions, to people who'll generally have no idea to what extent the software they're buying is made up of their own taxpayer-funded software.)

      --
      Practice random senselessness and act kind of beautiful.
    32. Re:Government competition by Anonymous Coward · · Score: 0

      Sort of.

      If the only way to use the BSD-licensed code is to link it with GPLd code, it could effectively be considered GPLd, until such a time as someone else incorporates it into a different framework.

      I haven't looked at the actual SELinux code, so I'm not sure Linux-specific it is, but I'm pretty sure that reimplementing the functionality based on the same principles would not be significantly harder than porting the actual code.

    33. Re:Government competition by flatrock · · Score: 2

      Your use of "Linux", on the other hand, suggests you cannot distinguish a free, public operating system from a single-sourced, proprietary operating system (or, more precisely, from the company that produces it).

      Until Linux is released into the public domain without the GPL I will never consider it a free, public OS. It is free in that there are no direct costs, and it is public in that you can get the source for free and compile it yourself, but it's not completely free or completely public.

      It's a different way of releasing software, but it still has very strong and significant restrictions on it's use. It definatley provides some advantages to both the general puplic and the govenrment. I don't think the NSA should ignore Linux, but I don't think they should give it significant pereferential treatment either. There are numerous commercial companies that gain significant benefit from using Linux in secure applications. Let those companies put forth the effort and the money to get a certified, secure version of Linux. Let Linux compete on equal terms on it's merits. Commercial companies do receive help form the NSA to get their OSs secure, but the efforts of the NSA are very small compared to the efforts from the companies. The companies also pay the NSA to be certified, which offsets the costs of the NSA working of issues with the OS.

      If a secure Linux requires tax payer money to be developed, then it's hardly free. The costs are just being shifted. If Linux requires significantly more help than commercial OSs to be certified, then those companies have every right to complain because their tax money is being used to subsidise the development of their competition.

    34. Re:Government competition by corey_lawson · · Score: 1

      ...but if the changes in SELinux trump some of the functionality and featureset of Palladium, what is MS to do then? How much of Palladium development has been guided by the work of SELinux? (we'll never know)

      This could be what the percieved competitive threat to Microsoft is about. Microsoft wants to be the "SELinux" to us. Microsoft wants to control it, for itself and its partners (RIAA/MPAA), not the NSA.

    35. Re:Government competition by Anonymous Coward · · Score: 0

      It's not entirely true that MS is not in direct competition with SE Linux,
      at least in a government-applicable sense. I found on the web a while back on some Common Criteria
      related page that MS is attempting to achieve EAL 4 level certification on
      Windows 2K. SE Linux is supposedly attempting to get an EAL2 via CPI at
      GWU. To me, this puts the two in competition for government security-related contracts.

      Clearly SELinux, EAL2 or not is going to be more secure than Win2K... but shown to
      a politi-head with zero tech knowledge and a brief description of the CC ratings, they'd likely pick Win2K:
      they're familiar with it; it's pretty; it "fosters american business" (yeah, right);
      and it has a higher rating. (Assuming they complete the evaluation successfully; and we all know they've enough funds to make anything happen. :)

    36. Re:Government competition by cburley · · Score: 1
      It's a different way of releasing software, but it still has very strong and significant restrictions on it's use.

      Name one such use -- one that does not derive from licensing restrictions placed by someone else on non-GPL'ed code.

      Here is the GPL, point out where it discriminates against corporations, individuals, governments, or anyone else, in terms of their right to use the software, as source code or binaries.

      It definatley provides some advantages to both the general puplic and the govenrment. I don't think the NSA should ignore Linux, but I don't think they should give it significant pereferential treatment either.

      What part of "Linux is not an individual or corporation" do you not understand?

      They aren't giving Linux preferential treatment -- they're giving the public preferential treatment! (Or, they were.)

      If Linux happens to be, for whatever combination of reasons, the best public product for the job they have at hand, then there's nothing wrong with them enhancing it instead of, say, OpenBSD -- and vice versa, should they wish to enhance that.

      Again, Linux is a free public product, like the C language, or the Ada language, or the FORTRAN language -- in some cases, products that, via trademark especially, have some "onerous restrictions" beyond those of the GPL (like, you can't call something X unless your implementation passes a rigorous test suite).

      It's obviously throwing your brain a curve because, unlike standards, it's an actual free implementation, which post-1980s software kiddies generally can't conceive of in a "Free As In GNU" sense.

      But the government has long been in the "business" of freely enhancing free public implementations of software as well -- implementations that have almost always been competitive with proprietary offerings in their day.

      Linux is just another case of this.

      And if it wasn't for Microsoft wetting its pants over Linux as a competitor, we wouldn't be having this discussion -- it'd be assumed a reasonable thing for government to do. (There might be some mumbling resentment over not picking a *BSD, of course, which gets into technical issues I'm not prepared to address.)

      So, the question is this: why are you working as a shill for Microsoft's business interests?

      --
      Practice random senselessness and act kind of beautiful.
    37. Re:Government competition by sean23007 · · Score: 2

      Do you have any evidence that MS is actually using your code (or any other GPL'd code, for that matter)? A lot of people accuse them of it, but there seems to be very little evidence of it. And I mean evidence that they are actually using your code, not just your idea. It is legal for them to reverse engineer your functions, as long as the people actually writing their code have not looked at your code.

      Evidence would be nice.

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
    38. Re:Government competition by cburley · · Score: 1
      From Overview of Services for UNIX 3.0 with Interix:
      SFU includes the Interix subsystem technology with both Korn and C shells, over 350 UNIX utilities and an SDK that supports over 1,900 UNIX APIs, giving programmers and system administrators the tools to easily migrate applications and scripts to Windows. Additionally, the GNU SDK and key GNU compilers and utilities are provided. All running natively on SFU.

      This is even clearer evidence than "Windows Services for UNIX 3.0", which could possibly be interpreted as saying the GNU code isn't, itself, actually included, which is why I double-checked.

      When I pointed this out to my MS-employee sister a month or so ago, her comment was something along the lines of "And you didn't get paid for it! Doh!".

      To me, this is wonderful, because I can't think of a way to more clearly and forcefully illustrate as lies claims like "the GPL is anti-commercial".

      But the pro-MS liars are, and will continue to be, out in full force on this and related issues. (I wonder how many of them actually gain financially from this relationship, which will permanently document them, on forums such as /., as liars?)

      --
      Practice random senselessness and act kind of beautiful.
    39. Re:Government competition by Alsee · · Score: 2

      Do you have any evidence that MS is actually using your code (or any other GPL'd code, for that matter)? A lot of people accuse them of it, but there seems to be very little evidence of it.

      You misunderstand, it wasn't an accusation. Microsoft is including GPL software in some of the packages they sell. All perfectly legal and above-board. There is absolutely do restriction against including both GPL and proprietary programs in one box or on one disk. You just can't put GPL source code in a proprietary executable.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    40. Re:Government competition by flatrock · · Score: 2

      Name one such use -- one that does not derive from licensing restrictions placed by someone else on non-GPL'ed code.

      Here is the GPL [gnu.org], point out where it discriminates against corporations, individuals, governments, or anyone else, in terms of their right to use the software, as source code or binaries.


      The GPL has one major restrictions. It requires that all derivative works also be released under the GPL, and that source code for those derivative works be made freely available.

      That discriminates against against anyone who wants to take a public resource, which has been developed at the taxpayer expense, and add value to it through their own efforts, and then sell the finished product in order to support themselves and their development efforts. If their additions to the software have no value, then no one would have any reason to buy thier software, because the baseline work that the government developed would be freely available to everyone if released in the public domain.

      The government and public could see benefits from the use of such proprietary software. If the benefits are greater than the price the developer is charging for their software, then people will buy it, if not, then people won't. The proprietary software isn't getting anything for free that anyone else didn't get.

      What part of "Linux is not an individual or corporation" do you not understand?

      What does it matter? GPLed software doesn't produce direct profits for it's developers. Some comrporations do contribute to GPLed products so that they can make indirect proffits. Individuals and corporations both can benefit from GPLed software. Individuals and corporations can also benefit from proprietary software. Developers can benetfit from getting direct compensation for developing the software. Corporations that develop software can benefit from getting a return on their investment of the development costs of developing the software. Users of proprietary can benefit from proprietary software if it's benefits out weigh the price they are paying for it.
      Both models have benefits. Both models have projects for which they are better suited. Their are also many applications for which either model will work and they can compete against each other. I don't see any need for the govenment to step in and support one over the other. The government should make ther results of it's efforts equally available to both.

      They aren't giving Linux preferential treatment -- they're giving the public preferential treatment! (Or, they were.)

      If Linux happens to be, for whatever combination of reasons, the best public product for the job they have at hand, then there's nothing wrong with them enhancing it instead of, say, OpenBSD -- and vice versa, should they wish to enhance that.


      Those proprietary developers and corporations are also part of the "public". The users of proprietary software that have no problem paying for the software products they need are part of the "public". If the government should be doing things that can't be effectively done by private individuals. When the govenment developes software as part of it's efforts. It should be released into the public domain so that everyone has equal access to it. GPL is not in the best interest of all members of the public in all cases. If the governemnt allows equall access to everyone, the public can then decide what it wants.

      Again, Linux is a free public product, like the C language, or the Ada language, or the FORTRAN language -- in some cases, products that, via trademark especially, have some "onerous restrictions" beyond those of the GPL (like, you can't call something X unless your implementation passes a rigorous test suite).

      C, Ada, and FORTRAN are industry standards created by standards organizations with input from members of the public. THese languages do not put restrictions on how they can be used or how products that are created with them may be distributed. Linux is also created with input from the public, but the GPL places serious restrictions on derivative works.

      It's obviously throwing your brain a curve because, unlike standards, it's an actual free implementation, which post-1980s software kiddies generally can't conceive of in a "Free As In GNU" sense.

      I'll agree that it's different than a standard, because you can simply fork off a version and still call it Linux. I'm not sure what you mean by standards not being free? They don't cost you anything to implement or use. There may be a cost involved with conformance testing, but in most cases that's to prove to others that you conform to the standard. With Linux there's nothing to conform to. They are different, and free in different ways.

      But the government has long been in the "business" of freely enhancing free public implementations of software as well -- implementations that have almost always been competitive with proprietary offerings in their day.

      Linux is just another case of this.


      The govenment has often funded development of software for the public good. However, they have a responsibility to make sure that the public has resonably equal access to that software. The GPL drasticly limits the use of software by commercial developers, and limits the availability of those benefits to the users of commercial software. The GPL does make sure the source code and source to derivative works remains public in a sense. But if prevents people from freely using that code however they choose.

      And if it wasn't for Microsoft wetting its pants over Linux as a competitor, we wouldn't be having this discussion -- it'd be assumed a reasonable thing for government to do. (There might be some mumbling resentment over not picking a *BSD, of course, which gets into technical issues I'm not prepared to address.)

      If Linux wasn't a competitor this would probably be ignored. Support for government funding of the development of GPLed software has long been justified as an excellent educational tool. GPLed software still is an excellent educational tool, and the GPL gaurentees that extensions to that software will continue to be available for that use. There are situations where there is a distinct public need where supporting the development of GPLed software is in the public's best interest. The development of secure OSs is in the public's best interest. But there are many different OSs, and the govenment shouldn't be supporting one type of OS or License over another. If there is a particular project the government is funding where the development of a secure version of Linux meets the project's needs and is cost effective, then I fully support the government funding it. Linux is a valuble tool in many projects. That's very different than the NSA developing a secure Linux and releasing it under the GPL.

      So, the question is this: why are you working as a shill for Microsoft's business interests?

      I'm looking after my own best interests, and what I beleive to be the public's best interests. I like having choices. I Like being able to choose Windows for my home computer I play games on. It does that pretty well, and is easily worth the $100 to $150 I payed for the OS, it would have been less if I'd have bought a computer rather than built it myself.

      I like being able to choose VXWorks or LynxOS for an embedded real-time project. They both have benefits. VxWorks in particular is very expensive and least for the development tools. However, it's simple, stable, and protable between different processor types. This often makes up for it's high cost. We've also embedded Linux in some of our products where I work. It took longer to get some of the bugs worked out of it, but the $0 licensing fees are definately attractive. For products that are going to sell in high volumes it's great. If you're only going to make a couple, I'd rather use VxWorks. For our hardware development we support drivers for Linux, Windows, VxWorks, and Solaris as our standard OSs. We will also port our software to other OSs if there's significant demand for it or the customer is willing to pay for the development costs. Linux tends to be significantly harder than the other four to support. THe OS just changes too much. Each release fixes some bugs, creates a few others, and the bug fixes often require us to remove our workaround to those bugs and thouroughly retest everything. Changing the software and properly retesting everything takes weeks if everything goes well. Different OSs and different development methods have different benefits. The governemnt isn't in a position to be able to evaluate the benefit of one type over another. They should try to make it so their efforts benefit all of them as equally as possible and let the market decide.

    41. Re:Government competition by mpe · · Score: 2

      You misunderstand, it wasn't an accusation. Microsoft is including GPL software in some of the packages they sell.

      Too many people appear to misuderstand. Maybe it's the result of Microsoft's "viral" FUD, maybe something else.

    42. Re:Government competition by cburley · · Score: 1
      The GPL has one major restrictions. It requires that all derivative works also be released under the GPL, and that source code for those derivative works be made freely available.

      That discriminates against against anyone who wants to take a public resource, which has been developed at the taxpayer expense, and add value to it through their own efforts, and then sell the finished product in order to support themselves and their development efforts.

      How so? It might prevent them choosing a specific model for distribution of the software -- primarily, shrink-wrapped, proprietary, binary-only software under a highly-restrictive EULA -- but that's something they can choose to avoid, and still distribute the software.

      After all, even Microsoft, the Poster Child for the "GPL Is Anti-Capitalist" argument, distributes (presumably MS-modified) GPL'ed software, as I pointed out in another comment.

      In other words, businesses can choose to improve and distribute GPL'ed software. Just not in a way that takes away freedoms compared to the freedoms users would have with the original GPL'ed software.

      That's not discriminatory, except in some sick, twisted mentality that believes there's no distinction between personal choices and individual rights, such that anything someone might choose to do must not only be their right to do, but must be fully funded by society if any other choice they might make is funded by society.

      As an example, you presumably believe that since the government funded the building of roads for driving from point A to point B at moderate speeds, and since some people would rather drive in circles at 200mph, the refusal of the government to fully fund race tracks is discriminatory.

      Now, in the sense that simply making a choice is "discriminatory", it might be, but you're clearly using it in the sense of immorality, or at least negative connoting public decision-making, which is utter nonsense.

      If their additions to the software have no value, then no one would have any reason to buy thier software, because the baseline work that the government developed would be freely available to everyone if released in the public domain.

      Following your line of reasoning, the government must never develop any public-domain code, since corporations like Microsoft, which prefer to distribute code for which it has a monopoly, would be discriminated against!

      The government and public could see benefits from the use of such proprietary software.

      But it'll never see the source, nor have the right to make copies, nor to discuss benchmark results, nor anything else placed in the EULA for the proprietary software, even though it contains code developed for and by the public on the public dime.

      If the benefits are greater than the price the developer is charging for their software, then people will buy it, if not, then people won't. The proprietary software isn't getting anything for free that anyone else didn't get.

      You seem to be confused -- proprietary software is not an individual or organization. So let's recast your argument in terms of actual entities to which governments are responsible:

      The proprietary software developer isn't getting anything for free that anyone else didn't get.

      There, that's better, isn't it?

      And, hey, that statement is 100% true when the publically-developed software is GPL'ed, or BSD'ed, or AL'ed, just like it is when it's PD'ed (public-domain'ed)!

      GPLed software doesn't produce direct profits for it's developers.

      It can, and sometimes it does. There's nothing in the license that prevents it from happening. In fact, the more end users learn to insist on having the source code and other GPL-style freedoms, the more opportunity businesses will have to profit from developing and distributing GPL'ed software. (Certainly, the profits to be had from developing and distributing proprietary software will evaporate!)

      I don't see any need for the govenment to step in and support one over the other. The government should make ther results of it's efforts equally available to both.

      The government's job is not to "balance" between models of distribution of software -- rather, it should seek to balance issues involving the best interests of the public, private interests, and so on. (Unless you're prepared to show me constitutional language specifying that the government must be business-model-neutral in all its transactions?)

      I don't see that the private interests Microsoft has to distribute highly-restricted derivatives of public software for profit weigh enough over the public interest in having all programs containing certain public software come with source and related GPL-style freedoms.

      But let's at least agree to honestly characterize the issue as that, rather than pretend as though the government is supposed to choose between distribution models as if they're all morally equivalent, when they're not.

      It should be released into the public domain so that everyone has equal access to it. GPL is not in the best interest of all members of the public in all cases. If the governemnt allows equall access to everyone, the public can then decide what it wants.

      Software released under the GPL is software to which everyone has equal access, despite your attempts to mischaracterize it. The GPL is in the best interest of all members of the public in many, though differently many, cases that PD is -- but PD distribution is not always in the best interests. (Consider software that performs a very critical life-saving task, which needs frequent checking of source by a wide body of people from various fields, a body that grows, changes, and learns, over time. If the software is PD, it'll find its way into proprietary distributions that will be unfixable when bugs are found in the PD version of the software, unless the single corporation that owns the copyright on the unfixable software agrees to fix it. The result? People will die. So PD isn't always the best option -- in this case, the GPL would be, among the choices being discussed.)

      So, since distributing under the GPL is, as I have shown, non-discriminatory, then it is a valid option, and the public can choose how best to accept it, in what forms, etc. Just as with PD or BSD'ed software -- only the shape of the "freedom envelope" is different.

      C, Ada, and FORTRAN are industry standards created by standards organizations with input from members of the public. THese languages do not put restrictions on how they can be used or how products that are created with them may be distributed. Linux is also created with input from the public, but the GPL places serious restrictions on derivative works.

      This is almost entirely wrong, since those "standards" are, or at least for a time were, not free for the public to improve and copy on their own! And, of course, Linux place even fewer restrictions on itself as an implementation than did any of those language standards on mere copies of their documents! (Not that these are what I would considered "highly-restrictive" standards as a result, just that, if you're going to draw moral equivalences between a restriction such as "you must not prohibit any friends you share this with from sharing it with others" and "you must not discuss, look at, benchmark, or copy this for friends", then a restriction against making extra copies of a standard for friends for free is just as onerous as Linux not "allowing" itself to be cloned as a proprietary product.)

      So, for the most part, Linux is as free and public an implementation of software as C, Ada, and FORTRAN are as standards for computing languages. There are subtle differences in terms of exactly what you are and are not free to do with them, but, again, for the most part, they are public projects which invite (or invited) public input, unlike any proprietary software or developer thereof.

      The development of secure OSs is in the public's best interest. But there are many different OSs, and the govenment shouldn't be supporting one type of OS or License over another.

      But it has to choose, if it is going to do something, unless you're arguing that it must fund identical changes to every single OS/license combination presently deployed on the planet to avoid being "discriminatory".

      This is pure nonsense, <RANT>but seems to be the natural result of the mindless, judgement-free, multicultural elitist crap that's been taught in our schools too long</RANT>. (I feel better now.)

      When government chooses to build roads for cars, it necessarily "discriminates" against other modes of transport, both real and mythical. Some of that can't help but hurt actual businesses.

      But at least those businesses have a valid complaint in that it is incredibly non-trivial to re-engineer their planes and trains to use the new roads, now that there are more of them.

      Software companies like Microsoft have nowhere near that level of hurdle to jump -- they can choose immediately to distribute GPL'ed software in its existing form, for profit, simply stamped with their own corporate logo. To the extent they modify it to coexist and cooperate with their own proprietary software, they will probably be able to sell even more of it.

      Unix for Windows is a telling example of this: MS is selling this, presumably, for profit, chock full of GPL'ed code. For people who want some assurance that MS is standing behind a Unix compatibility layer for Windows, this is worth paying for, even though they might be able to legally snarf the GPL components from other sources.

      Your other explanations and arguments, which I haven't quoted, stand, in my opinion, on their own quite well. They have almost nothing to do with licensing issues, and they don't explain, to me, why you waste a single moment trying to justify a pro-MS, anti-GPL position when it comes to government funding of software.

      All I can suggest is that if the NSA believes producing a secure version of Linux is, from a purely technical perspective, in the best interest of the country, the fact that it's GPL'ed should not matter one whit, since the GPL is a nondiscriminatory license designed specifically for free public software (the "P" stands for "Public", after all).

      You might feel that's a poor technical choice. I'm not prepared to disagree with that!

      ...

      One final question: all governments on the planet, considered in totality, provide a vast source of funding for proprietary software developers, in return for software that they can't examine, can't discuss, can't share with the very people who provide the source for that funding (namely, the taxpayers), depending on the various EULA's and special exemptions.

      Given that fact, and the fact that the comparative expenditures of all governments to fund public software probably amount to less than 1% of the total (but I'm guessing at that)...

      ...is it really fair to discuss the propriety (heh ;-) of NSA's funding of improvements to Linux under the GPL in isolation, as if the government wasn't already massively funding one business model (represented by Microsoft and Oracle) to the exclusion of another (represented by the FSF and GNU) by virtue of its purchases of software?

      I'm just wondering how "holistically" you're willing to apply your own interest in "balancing" the choices between distribution models and OS choices....

      --
      Practice random senselessness and act kind of beautiful.
  5. That's scary by EvilTwinSkippy · · Score: 4, Insightful
    Think about it folks.

    We have Microsoft telling the NSA what to do. Shouldn't it be the other way around?

    Or maybe it's one of Bill's minions I hear breathing over the phone line?

    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
    1. Re:That's scary by TurdFurgeson · · Score: 0

      Quick! Dawn the aluminium foil helmet!

    2. Re:That's scary by slutdot · · Score: 2

      No. The NSA is a government agency. I certainly don't want them telling me what to do.

    3. Re:That's scary by Anonymous Coward · · Score: 0

      Or maybe it's one of Bill's minions I hear breathing over the phone line?

      No, that's me, you sexy mother.

    4. Re:That's scary by guttentag · · Score: 4, Interesting
      Or maybe it's one of Bill's minions I hear breathing over the phone line?
      To quote from Sneakers:

      Agent: National Security Agency.
      Martin: Oh, you're the guys I hear breathing on the other end of my phone.
      Agent: No, that's the FBI. We're not chartered for domestic surveillance.
      Martin: Oh, I see. You just overthrow governments; set up friendly dictators.
      Agent: No, that's the CIA. We protect our government's communications. We try to break the other fella's codes. We're the good guys, Marty.
      Martin: Gee, I can't tell you what a relief that is, Dick... You know, I could have joined the NSA, but they found out my parents were married.

      Bear in mind that just because it's illegal for the NSA to spy on Americans doesn't mean they don't. Also, any technology released to commercial entities or the public in America is going to find its way to the rest of the world. Therefore, it is in the interest of the NSA to prevent Microsoft/Linux users/common people from securing their computers (the only computers the NSA is charged with protecting are the government's). However, it would be in the interest of the NSA to lead those groups to believe their computers are "so secure not even the NSA could get into them" when in fact they have easily-exploitable holes.

      Ask yourself this question: why would the NSA release open source security software to the world?

    5. Re:That's scary by Anonymous Coward · · Score: 0

      Kind of like microsoft promoting paladium without any concerns from the fbi. Makes me wonder about back doors.

  6. Fuck the NSA by Anonymous Coward · · Score: 0

    Do you trust them? How about anyone outside of the US, do you trust them? Didn't think so. This is a case of having the source code to "review" means little as 99.9% of us would not be able to find anything amiss in the NSA contributed code if their were intentional flaws.

    1. Re:Fuck the NSA by millwood · · Score: 1

      You're lost. Millions of people read and re-read the source for major open-source projects every day. So what if 99% of the users can't spot a problem? That still leaves a LOT of people that can and would.

      --

      "Hello, World", 17 errors, 31 warnings
    2. Re:Fuck the NSA by Anonymous Coward · · Score: 0

      No, millions of people do not read and re-read the source for major open-source projects everyday. You are greatly inflating your numbers my friend, and you know it. Apache? OpenSSH? PHP? zlib? Wanna keep going? You are correct that problems are discovered by well meaning, well educated code reviewers and it does help us all. You are incorrect regarding the number of users who are capable of providing any real contribution to code security. My point is, this is the NSA we are dealing with. The whole trust relationship must be re-examined when you are dealing with an organization with that kind of mission and capabilities. Trust who you want I suppose. I trust tons of OSS everyday, but I would not be comfortable running anything from the NSA. I also do not have much faith that my more experienced fellow OSS users and code reviewers could spot the nefarious code before the damage was done.

  7. weak..... by reaper20 · · Score: 1, Flamebait

    If MS keeps saying how much better Windows is in the server room then why are they worried about SELinux?

    Seems like they're having a hard time believing their own hype - maybe if they spent the effort fixing the SSL IE/Windows hole, then SELinux wouldn't have such an 'advantage'.

  8. Most Secure Shops... by Verizon+Guy · · Score: 2

    Use AIX or Solaris... so maybe they were wasting their time?

    --

    Aw, fuck it. Let's go bowling. - The Big Lebowski

    1. Re:Most Secure Shops... by SilverThorn · · Score: 2, Informative

      Or HP-UX 10.20 or 11i trusted version. In fact, there is an article in the Information Week magazine about HP now distributing a secure Linux dist that runs on their Itantium servers for some $600.

      -- M

      --
      Artificial intelligence is no match for natural stupidity.
    2. Re:Most Secure Shops... by Salsaman · · Score: 2

      AIX 5L is the first certified system

    3. Re:Most Secure Shops... by Amazing+Quantum+Man · · Score: 2

      Having written for COE, the link has absolutely nothing to do with security.

      Is the DoD's "software plug-n-play" initiative, for lack of better phrasing. And the OS is only a part of that. AIX just got certified for COE 4. I worked on COE 3 systems.

      Security has absolutely nothing to do with COE. And wasn't VMS (either 5.0 or 4.x) certified years ago to Orange Book B1 or B2?

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    4. Re:Most Secure Shops... by Anonymous Coward · · Score: 0

      If you are VERY serious about security and your a Solaris shop, then you should take a look at Trusted Solaris, which supports MAC (like SELinux), otherwise forget it. But wait you'll need Trusted Solaris workstations to talk to your servers, due to the Trusted Network system, you might as well be is a TS organization, because it is anything but trival.

      SELinux is a lot more appropriate for a corporate environment than Trusted Solaris. Remote administration plus the flexibility are a must. The NSA did good and last time I checked MS didn't produce anything related to Linux security, let alone windows security.

      But it is true that most Linux/BSD distros are more secure than "normal" AIX or Solaris out of the box. Try host based firewalls, and some forms of rudementary intrustion detection, tcp wrappers (or xinetd) ...etc.

      In my eyes Linux and the open BSDs are ahead of the major commercial vendors and SELinux is the future of security. Thank you NSA and open source developers, keep up the good work!

    5. Re:Most Secure Shops... by Verizon+Guy · · Score: 2

      Remote administration plus the flexibility are a must.

      It is of my opinion that remote admin is a no-no in a secure environment.

      --

      Aw, fuck it. Let's go bowling. - The Big Lebowski

  9. Competition Must Be A Bad Thing Or.... by NormAtHome · · Score: 2, Insightful

    maybe Microsoft has such poor faith in their products that they don't think they can compete against anthing else without a hugh advantage.

    or possibly their products are that bad.

    1. Re:Competition Must Be A Bad Thing Or.... by Anonymous Coward · · Score: 0

      No, that's not it.

  10. TrustedBSD by Anonymous Coward · · Score: 0

    Does this mean that TrustedBSD's days are numbered?

    http://www.trustedbsd.org

  11. Billy's Backdoor Fun by Xentor · · Score: 0

    Nah, MS just wants the government to use nothing but THEIR software, so Big Bad Billy can cruise through the DoJ sites with his secret backdoor :)

    --
    "The amount of intelligence on this planet is a constant. The population is growing." -Cole's Axiom
  12. Re:First Post by Anonymous Coward · · Score: 0

    ^_^

    Ah hah! You're another fat anime-loving moron!

  13. Those Bastards! by Anonymous Coward · · Score: 0

    They killed Tux!

    (apologies to SP)

  14. yes.... by teslatug · · Score: 4, Insightful
    'Microsoft was worried that the NSA's releasing open-source software would compete with American proprietary software'
    Wasn't that the whole point? The existing software wasn't secure enough so they had to provide some software that would be.
  15. Yeah, why can't they just make competition illegal by Anonymous Coward · · Score: 0

    You know, take the high road, like the open source community did, and attempt to legally exclude your competition from even being elligible? Oh yeah, spin the story so it's all about "freedom."

  16. Microsoft controlling the NSA? by Kakarat · · Score: 2, Insightful
    Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business.

    Translation...Complaints from Microsoft criticized the agency for providing the fruits of research to everyone, not just Microsoft, and thus hurting Microsoft's control over the world.

    Thus...Bill slaps the NSA and says "Don't do that!", and the government quickly complies.

    --
    "I bet I'll get blamed for this." --Mayor Quimby
    1. Re:Microsoft controlling the NSA? by paladin_tom · · Score: 1

      That's MS's point of view; however, the government's point of view is exacly as the article states.

      If NSA work is released under the GPL, then non-American businesses can benefit equally from the NSA's work, even though the NSA receives no tax money from said businesses. Thus, the NSA would be helping the economies of foreign nations that compete with the U.S. From a business perspective, this seems like a reasonable move, and even though this doesn't benefit me (since I'm not American), I really can't blame the NSA for making this choice.

      --
      #define sig "Every social system runs on the people's belief in it."
    2. Re:Microsoft controlling the NSA? by Anonymous Coward · · Score: 0

      But they had no choice! They *found* Linux licenced under GPL (well, large parts of it) and just added their own stuff. Which thus legally had to be GPLed as well.
      Alternatively they could have written their own OS from scratch, a *huge* job. Or built on BSD. Less likely to become ever useful in American society at large, the way Linux looks set to become.
      Remember, most of the code in SELinux is of non-American origin. And they could freely use it all, an incredible gift.

    3. Re:Microsoft controlling the NSA? by paladin_tom · · Score: 1

      However, the ethic that every government follows is to do what's best for it's country, regardless of what is "fair". Just look at any trade dispute.

      The fact that, with Linux, the US benefits from foreign work, does not mean that the NSA has any obligation to "give back to the community". :-(

      --
      #define sig "Every social system runs on the people's belief in it."
    4. Re:Microsoft controlling the NSA? by mpe · · Score: 2

      If NSA work is released under the GPL, then non-American businesses can benefit equally from the NSA's work,

      This is different from if they used BSD or made it public domain exactly how?

      even though the NSA receives no tax money from said businesses.

      This argument also applies against Microsoft and quite a few other US corporations.

    5. Re:Microsoft controlling the NSA? by mpe · · Score: 2

      But they had no choice! They *found* Linux licenced under GPL (well, large parts of it) and just added their own stuff. Which thus legally had to be GPLed as well. Alternatively they could have written their own OS from scratch, a *huge* job.

      Also a more expensive job.

      Or built on BSD. Less likely to become ever useful in American society at large, the way Linux looks set to become.

      Unless using BSD would have been much less expensive they would still have been failing to provide best value to the people who actually paid for the work.

  17. If I were a rich man..... by bogie · · Score: 5, Insightful

    It wouldn't surprise me and goes in line with their current effort of "advising" the government on how linux is evil. Remember Corel dropping linux? Yes the linux desktop was a tough market, but really there is no doubt it was a quid pro quo transaction.

    Also what's with MS giving its software away for Free to a different government every week? Its a clear pattern designed to make sure noone can possibly compete. How are they even allowed to do this? I mean its not like they are some cash strapped competitor with no market share looking to get an edge. They are a convicted monopolist who somehow continues to walk between the raindrops and "get away with murder" right out in the open!

    --
    If you wanna get rich, you know that payback is a bitch
    1. Re:If I were a rich man..... by EvilTwinSkippy · · Score: 1

      If this were steel or wheet, MS would be under FTC sanctions for dumping.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    2. Re:If I were a rich man..... by symbolic · · Score: 2

      Also what's with MS giving its software away for Free to a different government every week?

      Think "PR". I suspect that this is nothing more than a loss leader - M$ will make all their money back and more when they start demanding outrageous licensing and support fees down the road.

    3. Re:If I were a rich man..... by Anonymous Coward · · Score: 0

      " It wouldn't surprise me and goes in line with their current effort of "advising" the government on how linux is evil."

      What's a bit confusing is how the US gov't has bought the message with regard to Peru, getting the US ambassador to have a chat with them. State Department? Perhaps they will create a new position, US Ambassador to Washington, who could then serve Microsoft's interests there. Might help Colin Powell communicate with the White House as well.

  18. wow by JPriest · · Score: 1

    It seems to have no end. Does anyone have a short list compiled of some monopolistic things MS has done? I'm going to start putting one together for reference.

    --
    Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
  19. No. by Axe · · Score: 2
    Shouldn't it be the other way around?

    No. On who pays the fiddler orders the tune..

    Oh, you are saying its the tax payers who pay NSA, not Microsoft shareholders....

    Bah..

    --
    <^>_<(ô ô)>_<^>
    1. Re:No. by FreeUser · · Score: 5, Interesting

      Shouldn't it be the other way around?

      No.


      Correct. The NSA shouldn't be telling anyone what to do. Their mandate is to collect information and provide security advice to other agencies and, where authorized, the private sector. They are not a governing body. Ditto on the last sentence for the FBI, the CIA, and various other black-op agencies running around grabbing people out of their homes in the middle of the night and confiscating their material wealth without due process in the name of the ongoing War on [insert your favorite cause here].

      On who pays the fiddler orders the tune..

      Only partially correct. If we truly believe in democracy and "one person, one vote", then the amount of influence we wield on our government should be proportional to the number of people we represent, not the amount of taxes we pay or, more commonly, the quantity of bribes, relabelled "campaign contributions" we stuff into the pockets of our so-called representatives.

      But, even if it were 100% correct that the amount of taxes we pay should dictate the amoutn of influence we wield on our government, it should be pointed out that Microsoft almost never declares a profit on their tax returns (last year it was a 19 cent/share loss IIRC, as for tax purposes they do report those stock options which, conviniently, don't appear on the SEC filings), so Microsoft actually doesn't pay any taxes at all.

      Given your reasoning, I should have much more influence on the NSA than Microsoft does. Unfortunately, that is not the case and one of the main reasons, perhaps the main reason, that democracy in the United States is falling to pieces.

      --
      The Future of Human Evolution: Autonomy
    2. Re:No. by Subcarrier · · Score: 2, Funny

      If we truly believe in democracy and "one person, one vote"...

      Apparently, Bill is the one person with the vote.

      --
      "I have opinions of my own, strong opinions, but I don't always agree with them." -- George H. W. Bush
    3. Re:No. by ajp · · Score: 1

      From http://zdnet.com.com/2100-1107-946250.html

      7. Microsoft pays loads in taxes
      According to information found on Yahoo Financials, Microsoft paid $1.288 billion dollars in income taxes for the fiscal quarter ended March 31.

    4. Re:No. by realkiwi · · Score: 1

      > perhaps the main reason, that democracy in the
      > United States is falling to pieces.

      Excuse me. What democracy?

      --
      realkiwi
    5. Re:No. by deveco · · Score: 1

      I must agree with you regarding "campaign contributions" and MS's control of "our" goverment. A quote from a good artile in fortune this spring.

      And Microsoft and its employees gave a whopping 4.6 million to federal candidates and parties, Republican and Democrat alike, in the 2000 election--more money than any other company but AT&T and more than double that of its biggest rival, AOL Time Warner...

      --
      Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery?
    6. Re:No. by Anonymous Coward · · Score: 0

      I, too, was insulted by his use of the word. It is obvious that our country, the grand old United States, is a confederacy, and we kill those black niggers who say otherwise every day!

    7. Re:No. by mpe · · Score: 2

      Microsoft the corporate entity doesnt pay taxes. There are plenty of tax revenues generated by MS though - property, sales, income, luxury, and whatnot.

      Since they also gain tax money through selling software to government where is the net balance?

    8. Re:No. by Anonymous Coward · · Score: 0

      If you consider the income taxation of Microsoft employees, do you think that this should give Microsoft's lobbyists a say in politics or that it should give Microsoft's employees a say?

      If your answer is the former, then do you really think that most people as individuals should have absolutely no say in politics, because all of the money they put in government comes from their employers?

    9. Re:No. by Anonymous Coward · · Score: 0

      you must be a foreigner. "nigger" always refers to someone who is black, even as kikes are Jews, polacks are Poles, pansies are homosexuals, rednecks are southern white cowboy-wannabes, honkeys are whites, gooks are vietnamese, chinks are chinese, etc.

      so anyway, stop being redundant.

  20. Microsoft is half-right. by Anonymous Coward · · Score: 0

    They are also half-wrong.

    Software paid for with tax-money should be fully public domain with no strings attached what so ever.

    In this case the original code that the tax-payers paid for will be free forever and whoever wants to use it for commercial or GPL'd software can.

    1. Re:Microsoft is half-right. by Anonymous Coward · · Score: 0

      It seems to me that ALL software produced with our
      tax dollars would represent a threat to commercial interests
      and should cease and desist immediately.
      -unless the development work is given to US companies.
      -and ONLY to US companies. No open source licensing allowed !
      At least according to Microsofts argument.
      -
      If the development work is released to the public, the work
      would have the potential to benefit foreign commercial
      interests.(they would have access to the work)
      So the way I read this is...
      Publicly funded research is given to US companies that
      attempt to use this research to develop products that
      are later sold to the same taxpayer that funded the
      original research. Now thats a fair system.
      At least according to microsofts argument.
      -
      Please do not babble on about how the BSD license is
      better. If the development work is released under
      the BSD license, any foreign company could benefit from
      our tax dollars and thus put us in the same boat as
      we are now.
      At least according to microsoft argument.
      I say to hell with BILLG. But what do I matter.

    2. Re:Microsoft is half-right. by mpe · · Score: 2

      It seems to me that ALL software produced with our tax dollars would represent a threat to commercial interests and should cease and desist immediately.
      -unless the development work is given to US companies.
      -and ONLY to US companies. No open source licensing allowed !
      At least according to Microsofts argument.


      Even leaving aside the 14th ammendment issues how exactly would you define "US company"? Being incorporated in the US would include plenty of "foreign companies". Attempting to work out comany ownership is not always simple, especially when you have companies able to own parts of each other in complex ways, when all of the companies involved are traded on a public stock exchange.
      Maybe if someone were to come up with a definition Microsoft wouldn't actually qualify as a "US company" anyway.

  21. Individual Commercial Interests by gerf · · Score: 3, Insightful

    "Our interest is in helping to ensure that the government licenses its research in ways that take into account a stated goal of the U.S. government: to promote commercialization of public research."

    As an American, i see the government to

    • serve protect the people
    above and beyond anything else. I include protector from other Americans, and other American Companies in this. The government was NOT made to serve commercial interests. The U.S. Gov't was made to keep individual freedoms, from the dammed British Stamps.

    I'm simply atonished by how a Company now has more power than an Individual. It was this way in the early 1900s and late 1800s, when de facto slavery of immigrants and whole families in factory towns led to the Union movements. Sadly, Unionization will not work in this day and age, not in these circumstances. Instead, sheer humanity must overcome evils like this, lead by initiatives like Open Source, which give the power back to the Individual, and letting him control his own destiny once more. Thank you programmers and hackers for letting OSS live on.

    FSCK the man!

  22. Microsoft: threat to national security by coyote-san · · Score: 4, Insightful

    I'm not surprised Microsoft lobbied the NSA....

    I'm surprised they listened. Didn't Alchin, senior Microsoft executive, recently testify (in the anti-trust case, IIRC) that Microsoft software is so poorly designed and/or implemented that full disclosure of the API would inevitably result in the death of many Americans? (That is, after all, what "national security" ultimately comes down to.)

    Maybe Microsoft has a point that the NSA's work with SELinux hurts the proprietary software manufacturers, but by Microsoft's own testimony it should be out of the running for all future contracts anyway. I don't care about certification, when a senior exec testifies in court that using his product poses a threat to national security I want the procurement officials to pay attention!

    (On a related note, I WILL be asking the Congressional candidates this election cycle what they plan to do about the Federal software procurement cycle in light of senior Microsoft executives admitting that the quality is so poor that it threatens the national security. Microsoft has made it's values clear - $40 billion in the bank is more important than lives - and I want to make sure that my representatives make our values as a country clear. I don't want to force governments to only use OSS software, but I have no patience for excuses from companies sitting on cash reserves larger than the GDP of many nations!)

    --
    For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
    1. Re:Microsoft: threat to national security by msimm · · Score: 1
      Maybe Microsoft has a point that the NSA's work with SELinux hurts the proprietary software manufacturers, but by Microsoft's own testimony it should be out of the running for all future contracts anyway.

      Wouldn't it have made sense for the NSA to have partnered with an American business, like, say Red Hat? Wouldn't that be supporting American business.

      --
      Quack, quack.
    2. Re:Microsoft: threat to national security by Anonymous Coward · · Score: 0

      ---"Running Win98 on my grandmothers desktop isnt a
      threat to national security. "

      Respectfully disagree. A network getting owned is only one possible ramification of unsecured machines-your grannies desktop could be zombied, kept in reserve by "the badguy du jour". Any attcker could gain immensely from shutting down critical infrastructurwe or communications services at a time of attack with a million "grannied" zombies all doing a simultaneous DDoS attack. In fact, I'd bet a years pay there are a million windows boxes out there right now all zombied up, with their owners blissfully unaware they are part of the el bad guys attack network, kept for a dire circumstance. Most of the windows users I know, the 'grannies", joe and josephine web surfers and outlook express users, don't patch squat, run every possible service turned on, have minimal to zero knowledge of security, buy a copy of mcafee once then forget about it for as long as they run their machines, and wouldn't know if they were transmitting pings and part of a flood if the box told them in clear voice. Yes, one tiny individual machine isn't that bad, but it's the reality of the 10,000 mosuqitoes against the elephant syndrome-it still "works" as a successful attack. A pack of lions-uberhackers, can take down the pachyderm, so can the mosquitoes, all those grannies out there. And in any cyberwar, we WILL have both attacking the US, count on it. shutting the net down as a response accomplishes a successful attack, yes?
      o with microsoft dominating both the desktops, and also delibarately enforcing dumbed down computing by abusing their monopoly status, insuring there are those million haxored grannies out there so they can squeeze a few more dollars out of the economy without having to do work for it, ie, making the smart, secure software they should have. Nope, they create a small handful of multi millionaires who think their profits are more important than the country's security, their mercedes and mansions are worth "more" to them then hiring a lot more programmers a long time ago and coding decent stuff.. Your granny is definetly part of the problem, even though she is intellectually innocent of it, as are the bulk of the other windows users. What the percentage of fault is, I can't really say, but it's not zero, that's for sure.

      Tis same reasoning of problems like this can be applied to almost everyone-some examples-we all use federal reserve notes (If a USAian), even though the reality is is that it's funny money, counterfeit, and part of creating a very insecure inflationable (and dishonest) economy that could crash horribly. We all (mostly) cooperate with the heinous IRS. The bulk of the people blissfully yank the republocrat monopoly political party lever every election. yada, yada, yada, lotsa examples. Ignorance can be used as an excuse, but it's the lamest one out there. Granny shouldn't be forced to be a complete security expert, but if she's on the net at all, she's going out of her way to NOT find out how thoroughly rank microsoft OS is, how insecure it is, and is at *some* fault for still using it when she don't have to, especially because she has a smart grandson to help her out..

      %^)

  23. Did MS Lobbying Stop NSA Work On SELinux? by trentfoley · · Score: 1

    Well, duh!

  24. "American"? by Wolfier · · Score: 5, Interesting

    Have anyone noticed this buzzword used by every Microsoft lobbying effort after 9/11 just to trying to give the probably fake impression of Microsoft being "patriotic"?

    Somebody has to wake up.

    1. Re:"American"? by Anonymous Coward · · Score: 0

      Are you suggesting an all-American company is faking patriotism? You're not one of them T-words are you?

    2. Re:"American"? by gearheadsmp · · Score: 0

      Jingoism indeed.

    3. Re: "American"? by Black+Parrot · · Score: 2, Funny


      > Have anyone noticed this buzzword used by every Microsoft lobbying effort after 9/11 just to trying to give the probably fake impression of Microsoft being "patriotic"?

      Yeah, they're supposedly coming out with Red and White screens of death, too.

      BTW, what you observe is hardly limited to Microsoft. Lots of businesses do it, anlong with almost every politician in the country.

      --
      Sheesh, evil *and* a jerk. -- Jade
    4. Re:"American"? by Anonymous Coward · · Score: 0

      I wonder how many H2a or H1b employees Microsoft has. Can they really call it "American" product? Is a made-in-Ohio Honda an "American" car?

    5. Re:"American"? by 10am-bedtime · · Score: 1
      yes, unfortunately neal stephenson was wrong in snow crash (although his language is delightful anyway). america will probably lose the lead in competitive software technologies (read: AI) in the next decade or so if its government (by the people for the people, supposedly) adopts and supports the proprietary software mindset. that just leaves pizza delivery and music, and everyone knows the latter is crap already.

    6. Re:"American"? by marauder404 · · Score: 2, Interesting
      What about this article by RMS on the FSF website: The GNU GPL and the American Way. I know that the article is by RMS, but it reflects the official views of FSF.
      The Free Software Movement was founded in 1984, but its inspiration comes from the ideals of 1776: freedom, community, and voluntary cooperation. This is what leads to free enterprise, to free speech, and to free software.
      Patriotism is something that's been stirred into most Americans lately, and with good reason. An organization frequently reflects the views of the individuals from which it is composed, so don't fault Microsoft for being patriotic unless you're willing to fault the individuals therein.
    7. Re:"American"? by aallan · · Score: 2

      Have anyone noticed this buzzword used by every Microsoft lobbying effort after 9/11 just to trying to give the probably fake impression of Microsoft being "patriotic"?

      Its not exactly going down well in the UK and (the rest of) Europe....

      Have a look at the recent BBC coverage of Microsoft; here, here, here, here and here for instance.

      Compare this with recent Linux coverage; here, here, here, here, here and here.

      Is it just me, or is there a strong pro-Linux, anti-MS bias creeping in there?

      Al.
      --
      The Daily ACK - Eclectic posts by yet another hacker
    8. Re:"American"? by Vegard · · Score: 1

      From a national point of view, it makes good sense to support open source if you're not in the US. Most of money for MS-ware goes directly in MS pockets, out of the country. If you encourage and use open source, you can stimulate a services-based local industry.

      Also, using MS software have been more and more expensive, at least when you compare the relative costs between hardware and software. I'd bet many companies use more than half the IT budget on commercial licences, most of which is basically Microsoft Windows and Office anyways. That's a heck of a lot of money that could go to build good open source solutions!

    9. Re:"American"? by Anonymous Coward · · Score: 0

      It's called propaganda.

      The president has been doing it for an entire year, now.

    10. Re:"American"? by Anonymous Coward · · Score: 0

      Uhhh, all those links are to the BBC. Do you have any links that are NOT to the BBC? I really don't trust the BBC any more than I would trust PBS to accurately report on anything of substance. Publicly funded ventures are often complete crap.. at least PBS is. Now, show me the CNN, MSNBC, or Fox News links and I will listen!

    11. Re:"American"? by sean23007 · · Score: 2

      Everybody tries to use "American" so they'll seem more "patriotic." Since that day, it works, but it shouldn't. Somebody does have to wake up.

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
    12. Re:"American"? by Chris+Burke · · Score: 1

      Why isn't this +5 funny yet? Damn moderators; stop browsing at +1!

      --

      The enemies of Democracy are
    13. Re:"American"? by mpe · · Score: 2

      From a national point of view, it makes good sense to support open source if you're not in the US. Most of money for MS-ware goes directly in MS pockets, out of the country. If you encourage and use open source, you can stimulate a services-based local industry.

      It would make plenty of sense for many US businesses too. Washington State is hardly "local" for most of the US, including the most highly populated parts. Microsoft's ability at tax avoidance dosn't help here.
      Throwing money at a far away entity is much the same, even if they happen to be in the same country as you...

    14. Re:"American"? by Anonymous Coward · · Score: 0

      Ahahahahhahaha
      that's almost as funny as those 'you can depend on CNN' commercials

  25. Licenses aren't compatible by TheConfusedOne · · Score: 1

    BSD and GPL aren't compatible licenses because of the GPL restrictions. Since SELinux is an expansion of current GPL code it has to be GPL licensed as well. If it were a collection of libraries then it might be possible to use BSD for the libraries as long as they access the core Linux in an LGPL compatible manner.

    (IANAOLE - I am not an OSS License Expert)

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    1. Re:Licenses aren't compatible by zavyman · · Score: 2

      Actually, I'm sure the government could still release public domain code as GPL improvements both technically and legally. Legally, they could make the diffs public domain, such that one could use their code improvements however one wanted to. But if someone wanted to distribute the whole work -- the whole SELinux system -- it would have to be under GPL distribution terms.

      I'm not sure about the distribution of the work as a whole, however.

    2. Re:Licenses aren't compatible by Royster · · Score: 2

      There is a lot of code in the Linux kernel which has been released as BSD without the Advertising clause. BSD without the advertising clause is compatible with the GPL.

      The SE Linus extensions could have benn released BSD.

      But the bigger question is are the NSA-funded extensions Public Domain? Since the product of Gevernment Work may not be copyrighted and since the GPL requires copyright to function, I strongly suspect that the GPL can not be enforced on the SE Linux patches.

      --
      I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
    3. Re:Licenses aren't compatible by Znork · · Score: 2

      Nope, the BSD-without-advertizing license is compatible with the GPL. SELinux extensions could be clearly marked as BSD licensed, and anyone could lift those extensions out of the GPL codebase.

      You can combine BSD code with GPL code any way you want. Only as long as you distribute them together do you have to (to distribute the GPL part), apply the GPL license to the work as a whole. Separate the GPL code from the BSD code and you have two separate works again, for which only the applicable license is valid.

      Of course, such code might be so heavily integrated into the GPL code that separation might be pointless since you'd just get a bunch of unusable (altho BSD licensed) code.

  26. What if MS bought patents to SELinux? by hopeless+case · · Score: 1
    I almost hate to say this, but...


    If I were Microsoft, I would attempt to buy the patents to the Mandatory Access Controls as used in SELinux, in order to stop the scenario described here from playing out.


    The scenario is that by further developing the SELinux concept, linux would become such a secure OS for general government use that governments would be forced to use it instead of Windows.

    1. Re:What if MS bought patents to SELinux? by Dr.+Spork · · Score: 2
      Fortunately, it is too late for now for a patent to be issued ("prior art"). However, the article you linked is indeed quite good for a zdnet piece. Sure, the US gov't is a big contract, and MS payola will make sure it's theirs. However, there are hundreds of other governments, like China's, that will surely be running a descenant of SELinux.

      What we need is an international effort of coders to super-secure Linux. That sort of effort, distributed over the non-US world, would definitely justify the costs.

      Maybe this will be the next step after Linux gets officially accepted by some large governments.

    2. Re:What if MS bought patents to SELinux? by mpe · · Score: 2

      If I were Microsoft, I would attempt to buy the patents to the Mandatory Access Controls as used in SELinux,

      Using patents against the government which issued them is kind of a non starter. Especially if the magic words "national security" are involved.

  27. This was already mentioned by tautology · · Score: 1

    In this slashdot article. It is the same article text on zdnet.com and news.com.

  28. i wonder what would happen... by dollargonzo · · Score: 1

    ... if a conglomeration of quotes from /. was sent to some senators, or even better, the judges in the antitrust suit. obviously m$ has far more far-reaching influences than we expected. every now and then we see another story about how m$ tells some company (dell) or some gov't agency (nsa) they are not allowed to do something, or HAVE to do something. that is BS. sure, the agencies and companies can't do anything b/c bill is sleeping w/ the CEOs' wives...but perhaps judges will be better.

    QED

    --
    BSD is for people who love UNIX. Linux is for those who hate Microsoft.
    1. Re:i wonder what would happen... by Anonymous Coward · · Score: 0

      --most judges are appointed political hacks. members of either the crips-democrats, or the bloods-republicans -ongoing mafia like criminal gangs who have conspired to use their monopoly status to transform two private organizations into a pseudo "government". No place in the constitution does it mention these parties, no place does it say we must have these two parties, but over the generations they have seized control, and passed enough "laws" that the ability of any other person or org to devlop any sort of presence in "government" to be mostly doomed to failure..It's as blatant as using the FCC government/public controlled broadcast networks to only have the representatives of these two private organizations in the presidential 'debates", and it goes downhill from there. the gangsters appoint their own gang members to be judges. The law-writing gangsters write laws to pay off their "private" criminal corporate gang memberswo give them bribes called 'campaign contributions" or "speaking and consultation fees". And as such, these political gang member "judges" are exactly the same in their ability to be influenced by bribery and blackmail, same as most senators and legislators and the so called "leaders" in the various states' and federal executive branches are. They are mostly biased and crooked, their collective actions with "judgements" that are blatantly unconstituional, if you speak english as opposed to gangster-black's law speak- prove it, daily, all over the nation.
      Is it any wonder that micromonopoly always skates? It's judicial theater for the sheeples, melodrama for the million mommies, sound bytes for the sycophants. A LOT of cash money has probably changed hands over the years. Who wants to bet against that? The fix is in, money buys political reality. Once in awhile they have to have a sacrafice like enron, to "prove" how honest this one party dictatorship criminal gang government is. It's a scam, man.

    2. Re:i wonder what would happen... by dollargonzo · · Score: 1

      yes, but in a court of law, it is still harder (not impossible, just harder) to bribe judges.

      .

      --
      BSD is for people who love UNIX. Linux is for those who hate Microsoft.
  29. Ahh New America by kenp2002 · · Score: 2, Troll

    It's good to see that we now live in a nation that fears competition, exhaults mediocrity, and rewards the foolish, corrupt, and wicked. Oh what a brave new world! Soma! Soma For All!

    Welcome to hell.. The United Socialist States of America. I had hoped my kids whould have had the opportunity to grow up on the USA, looks like we lost the war for freedom.

    --
    -=[ Who Is John Galt? ]=-
    1. Re:Ahh New America by buzzdecafe · · Score: 1

      The union of corporate power with state power is fascism, not socialism.

    2. Re:Ahh New America by kenp2002 · · Score: 1

      I was shooting more towards the behavior of the population more than the behavior of the corporations (i.e. welfare, entitlement, etc..)

      --
      -=[ Who Is John Galt? ]=-
    3. Re:Ahh New America by ctid · · Score: 2

      How the hell is this "socialist", for God's sake?? This is you, the taxpayer, paying for top quality software to which you would have access indefinitely, because it is GPLed. But now you're going to lose that because a convicted monopolist doesn't want the competition. Wake up and smell the coffee! Microsoft is all over your government like a cheap suit. If you don't do something, they'll be telling you what you can and cannot do instead of just your government.

      --
      Reality is defined by the maddest person in the room
    4. Re:Ahh New America by jcast · · Score: 1

      Give me one actual difference between socialism and fascism (besides who's in charge, that's irrelevant).

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    5. Re:Ahh New America by jcast · · Score: 1

      Um, if M$ can tell you what to do, they are the de facto government (or part of it).

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    6. Re:Ahh New America by mvdwege · · Score: 2

      You are absolutely right: this has nothing to do with Socialism.

      On the other hand, you do know what a government consisting of collusion between the State and the Corporations is called? It was invented in Italy in the 1920s by Benito Mussolini and it is properly called Fascism.

      The news coming out of the USA is scaring me more every day.

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    7. Re:Ahh New America by buzzdecafe · · Score: 1
      Unfortunately, socialism is a term that has become very corrupt. But in theory, the difference is that a socialist economy is one where the means of production are owned collectively; this unfortunately led to a situation of the party replaces the collective, and the dictator replaces the party. Fascism is political organization characterized by dictatorial control of all aspects of society, nationalism, militarism, and racism. It is important to note that economically, fascism is intertwined with corporate power:

      "Fascism should more appropriately be called corporatism because it is a merger of state and corporate power." -- Benito Mussolini
      This is quite a contrast from the foundation of socialism.


      (Of course, Joe Blow on the street doesn't particularly care whose jackboot is kicking in his door--as far as that goes, the two systems have had some ugly parallels in the real world.)


      All that said, the US is much closer to fascism than socialism, and is merrily treading down the garden path in that direction.

    8. Re:Ahh New America by SubtleNuance · · Score: 1

      Just as a point of interest. GNU/Linux *would* (should) be the moral choice by socialists (or Communists). Co-Operation, transparency, collectivism -- all Socialist (Communist) ideals.

    9. Re:Ahh New America by justsomebody · · Score: 2

      That just proves your lack of knowledge.

      Which comunist country was ever promoting open standards. No one, comunism in the boks of Marx and Engels should be like that. Real life ain't. That's proven realm of comunism. Comunist party rules, other suffer and pretend they're happy. Either that or penalty.

      Every comunist country I know has far less freedom of speech than some other non-comunist one. There were always strict (and cruel ones) penalties for even talking something against national politics and regime.

      To take that thinking and compare to United States. I guess you're the ones that are moving towards comunism silently.

      Open standard would be out of question believe me.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    10. Re:Ahh New America by SubtleNuance · · Score: 1

      ...Yes, there have been many (very sever) issues with many implementations of Communism. But its true that the *ideal* should be the goal - a system which implements those goals would be a Socialist or Communist state - the ones you site, exactly because they had those downfalls were *NOT* Communist or Socialist. An apple calling himself and Orange does not become an Apple - Comprende?

      Im obviously making issue w/ a troll, but to say "just proves my lack of knowledge" betrays your own. An honest and Propaganda(TM) Free analysis of Socialism (Communism) does not lead to the ignorant McCarthyism 100% of Americans display.

    11. Re:Ahh New America by justsomebody · · Score: 2

      Not a troll. But one who experienced wanna-be-comunism. And as it seems we do agree about apple and orange.

      Comunism was a goal, result was something completely different. But the result was still called and common known as comunism. So apple became orange.

      "An honest and Propaganda(TM) Free analysis of Socialism (Communism) does not lead to the ignorant McCarthyism 100% of Americans display."

      Good point actualy. But considering that I was reffering "lack of knowledge" as "not living in country that was wanna-be-comunism". Not reffering to your political knowledge but practical (and only in the knowledge of what comunism is, sorry badly pointed out). Real truth is that comunism regime was never clearly represented outside of that state, because all countries I'm reffering were practicaly closed to outside world. Picture shown to outside world was completely different than reality. You might call that a misguided point of view.

      To explain in a different simpler way. US is practicaly bounding it self with DRM, RIAA.... The ones who get worst of it are common people. That's a comunism from insider, but never comunist. Except that a participant in comunist party always had an advantage in every view. Look at that from another point "Cop never betrays cop". Doesn't that mean that cop can break the laws but avoid the punishment. Same was in comunism, comunist were always more protected by laws. On the other hand, having one company that dictates government as MS. Well, that's just a capitalist way of comunism (try to take this sentence not so hard as is, but as a refferal).

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    12. Re:Ahh New America by jcast · · Score: 1

      OK, in theory, ``socialism'' and ``fascism'' are quite different. In theory, BSD and Linux were founded with quite different goals. But the end result is the same, so I say they're identical.

      It's the same with socialism and fascism. In theory, they start from different goals. In practice they always lead to the same thing. So, they're practically identical.

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    13. Re:Ahh New America by Anonymous Coward · · Score: 0

      I will say your logic and 'N Sync are identical because they both give me a headache.

    14. Re:Ahh New America by Anonymous Coward · · Score: 0

      On the other hand, you do know what a government consisting of collusion between the State and the Corporations is called? It was invented in Italy in the 1920s by Benito Mussolini and it is properly called Fascism.

      Fascists are usually quite happy to call themselves "socialist", or anything else, if they think it will improve their popularity...

      The news coming out of the USA is scaring me more every day.

      Take a look into what the current US president's grandfather got up to.

  30. Wait a minute... by Idarubicin · · Score: 3, Insightful
    From the article...

    'Microsoft was worried that the NSA's releasing open- source software would compete with American proprietary software,'

    Indeed. We ought not have the government funding university labs, because releasing medical research to the public domain might interfere with pharmaceutical company profits.

    Not everything that's good for General Motors is good for the country, or its people, or its economy.

    --
    ~Idarubicin
    1. Re:Wait a minute... by alext · · Score: 2

      ...whereas in fact the Government provides a significant source of pharmaceutical companies' profits.

      Oft-repeated quote:

      According to the NIH, U.S. taxpayer-funded scientists conducted at least 55 percent of the research projects that led to the discovery and development of the five top-selling drugs in 1995.

      A corollary for the IT industry would therefore be a company like MS paying for the rights to exploit a publicly produced technology - an arrangement that is not necessarily in conflict with the GPL.

  31. oh shit by Anonymous Coward · · Score: 0

    Soon we'll see Microsoft putting spaceships into space.

    oh wait.. it's NSA, not NASA

    1. Re:oh shit by shades66 · · Score: 1

      It could be worse... The next newsflash could be "Microsoft XP to be use used to control next NASA shuttle"...

      (Hopefully Bill we get a free ticket!)

      --
      ---- There are 10 types of people in the world. Those that understand binary and those that don't
  32. Re:lesser known AutoCAD by Anonymous Coward · · Score: 1, Informative

    AutoCAD used to be available for a number of the proprietary *nixes (Solaris, SGI IRIX, HP/UX, etc) back in the Release 10, 11, 12 (and early R13) days. People I used to know that worked at AutoDesk used to make sort of veiled hints that Microsoft put some kind of pressure on them to quit supporting alternative platforms. More or less what they were saying is that AutoDesk was told if didn't quit supporting non-Microsoft platforms that Microsoft would enter the CAD market (possibly by buying up one of AutoDesk's competitors), or at least announce that they were going to, and that would kill AutoDesk by "giving away" the product. But of course nobody in those days would dare come right out and say something like that.

  33. So much for non-Microsoft desktops for the DoD by Mastos · · Score: 4, Insightful

    In the Department of Defense, desktops and servers have to go through a NSA lockdown of the operating system before they can go into production. If you wanted to run linux on your desktop, the first question they ask is what does the NSA say about it.

    While there are lockdown procedures for Linux from what I understand, having an NSA secure version of linux would have gone a long way to validating the os from the information assurance people. I hate to be forced to use Winx for _security_ reasons. :(

    Don

    1. Re:So much for non-Microsoft desktops for the DoD by Anonymous Coward · · Score: 0

      This doesn't mean that NSA won't still produce a secure Linux version for DoD use, but only that they won't distribute it to the general public.

    2. Re:So much for non-Microsoft desktops for the DoD by Anonymous Coward · · Score: 0

      SELinux is about implementing security policies such as Mandatory Access Control and (IIRC) further privilege separation for more fine-grained access control (relevant to servers), not about making Linux more secure in general.

      I can hardly imagine that desktop machines would require such features, or that Linux (or MSWin) would be a likely candidate for any use where MAC is an issue.

    3. Re:So much for non-Microsoft desktops for the DoD by corey_lawson · · Score: 1

      ...the lockdown is only for computers handling classified information. There are plenty of PCs used by the Government/DoD that do not handle classified information that are not locked down significantly, no more so than any other corporate desktop PC (they have big green stickers with white letters that say, "UNCLASSIFIED" on them). So the NSA had a hand in telling installers that DoD systems must not run Win9x/Millenium, that end-users should not be in the [domain/local] Administrators groups, etc.

    4. Re:So much for non-Microsoft desktops for the DoD by Mastos · · Score: 2, Interesting

      Having previously worked for the computer engineering folks in a branch of the armed forces, I can assure you that any computer on either the NIPRNET (unclass) or SIPRNET (classified) undergoes an NSA security lockdown. True, they are more protective of the class machines, but both still are locked down. Also, the NSA lockdown is a set of procedures involving a ton of reg changes and is quite thorough. In fact, when we were migrating to 2000, I worked with a Microsoft engineer walking through the NSA lockdown and documenting the install procedure for unclass machines.

  34. The end is near and wear a Microsoft logo by Vodak · · Score: 2, Funny

    One day the United States will have a long range rocket or two loaded with WindowsCE and something's going to go wrong. A windows crash will happen.. the rocket will hit the wrong country.. and it'll cause the third world wear.

    And it'll be Bill's fault that only cockroaches and ABIO roam the earth.

    1. Re:The end is near and wear a Microsoft logo by malIgna · · Score: 1

      Did you mean AIBO?

      --
      Nothing to see here, move along.
    2. Re:The end is near and wear a Microsoft logo by Anonymous Coward · · Score: 0
      Too late. Do a Google search for the keywords

      Belgrade
      Chinese
      Embassy

    3. Re:The end is near and wear a Microsoft logo by Vodak · · Score: 2

      My spelling is less then gooder =]

  35. Glass houses? by Spackler · · Score: 2

    Should Microsoft be worried about releasing a secure product before ordering around the government? Next thing you know, Bush will come out and say that CEO's shouldn't take out loans from a company to buy stock. They are all a bunch of flamebaiting hypocritical butt-munchers.

    And with that, I release my excellent karma to the winds of change.

  36. Well then lets push the other way by Anonymous Coward · · Score: 0

    Why don't we at least write our representatives regarding this. If we do not at least let them know about our objections, we cannot expect them to take them into consideration.

  37. Let's Not Forget the Good News... by EvilTwinSkippy · · Score: 1, Insightful
    Hey, don't forget the first part of the story.

    For years the NT folks have never let us live down that their OS is certified and Linux was not.

    This is really positive stuff.

    --
    "Learning is not compulsory... neither is survival."
    --Dr.W.Edwards Deming
  38. analogy by jhampson · · Score: 1

    Let's say you have a fruit stand. This fruit stand is your sole source of income. Now let's say someone plants an apple tree right next to your fruit stand and let everyone take some apples for free(worms and all!). Now let's say you have an axe. Do you mean to tell me that you wouldn't try to chop down that tree? I would.

    1. Re:analogy by EllF · · Score: 2

      Rather than breaking the law and killing something so that you could still continue to sell a product that at least *some* people don't want, perhaps you should find a better way of earning an income - something that doesn't depend on a resource that anybody could, given sufficient time, emulate as well or better (and for Free!) than you?

      --
      We who were living are now dying
      With a little patience
    2. Re:analogy by Anonymous Coward · · Score: 1, Insightful

      I would take the apples and sell them at my fruit stand.

    3. Re:analogy by Anonymous Coward · · Score: 0

      Perhaps someday, you'll truly find out what the "Real World" is, and you won't need to talk to others about it with such a condescending tone.

    4. Re:analogy by Sean+Clifford · · Score: 3, Insightful
      Troll, but I'll bite anyway.

      A better analogy:

      Say you have a chain of lemonade stands and are selling weak, unsweetened lemonade for $199 a glass. The lemonade stand is your only source of income, so you want to protect it. You forbid anyone from sharing the lemonade they drink and if they drink your lemonade you forbid them from drinking anything else to slake their thirst.

      The community deploys water fountains, a few people put down fruit trees and a few start selling different kinds of fruit juices.

      You bribe public officials with "campaign contributions" to pull the water fountains and send hired goons to intimidate, buy out, or otherwise break up your competition.

      That's a better analogy of what Microsoft is doing with regard to Linux.

      And no, I wouldn't hire goons, grab an axe, or bribe officials. I'd start offering what people were asking for rather than crush the life out of them like an asshole.

    5. Re:analogy by jcast · · Score: 1

      No. I would never commit vandalism to further my own interests. And neither should M$.

      --
      There are reasons why democracy does not work nearly as well as capitalism.
      -- David D. Friedman
    6. Re:analogy by Aexia · · Score: 2

      Oh, I fully expect them to *try* to cut down the apple tree.

      I just didn't expect the *owner* of the apple tree, the NSA, to *let* them cut it down.

    7. Re:analogy by Anonymous Coward · · Score: 0

      So what your saying is you should not allow any thing to be given away free if there is a market for that product.
      for example Netscape had a market and Microsoft gave away the Internet Exploder. Hmmm

      Only apply's to some I guess!!!

  39. Re:If I were a rich man.....(redundant) by Martigan80 · · Score: 1

    How right you are-BUT if you_own_ 80% of the desktop market anyway who will stop you? The DoJ uses nothing but MS on their computers so why shut them down? Besides we have all seen from MS's "new" EULAs that they can tailor it to there needs while making the end-user bow down. It's like suing the gas companies for having a monopoly on the gas-turbine engine...99% of the would use it.

    --
    This SIG pulled due to lack of funding. (This damn war is costing too much!)
  40. NSA should continue working on SE Linux by dh003i · · Score: 3, Interesting

    Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business

    Gee, imagine that -- the fruits of the research that the hard working taxpayers of America paid for is also provided to those very same citizens! Outrageous! It may be true that this research also benefits any other government or company in the world which may choose to use it; but more importantly, it can benefit any US citizen who chooses to implement it.

    aggressive Microsoft lobbying efforts have contributed to a halt on any further work. "Microsoft was worried that the NSA's releasing open-source software would compete with American proprietary software," said a source familiar with the complaints against the NSA who asked not to be identified.

    Gee, imagine that -- the taxpayers get can get free access to the fruits of the research which their tax dollars made possible. Lets not forget, MS can also get access to this research and implement it: either the exact implementation, which would need to be separated (at a hands length) from other components of MS' OS, or the idea and make their own implementation, which they could license under any scheme they wanted.

    Microsoft would not comment directly on its lobbying efforts, but did stress that it wanted to ensure the government continued to fund commercial ventures. "The federal government plays an important ro7le in funding basic software research," said a Microsoft representative. "Our interest is in helping to ensure that the government licenses its research in ways that take into account a stated goal of the U.S. government: to promote commercialization of public research."

    That's interesting. According to MS, the government has an obligation to make taxpayers pay twice for the what their tax-dollars funded. Come on. Research is publicly funded because it can help all of the US, not just corporations like MS. Gee, tough concept there -- everyone pays taxes to support research, thus everyone should benefit from it, not just MS. Again, MS can make use of this research internally, thus benefit, or even put it in their OS at a hands length, or develop their own implementation of it.

    In addition, the Common Criteria process, run jointly by the NSA and the National Institute of Standards and Technology under the National Information Assurance Partnership (NIAP), is better suited to certify proprietary software coming from a single company. It's ill suited to deal with the myriad updates that the open-source community produces on a regular basis.

    Then the solution is rather simple. We create a central organization of Linux volunteers to handle the mriad of updates, and they analyze and review those updates (quality-control), and submit them to the NSA and the NIAP.

    Back to the government development of GPL'ed software. I think that whenever possible, the government should develop using the BSD-type license (actually, I think that the public domain should be redefined to be like the BSD-license, so that credit is always given and that the "source" of the originals are always distributed under that "license"). This is because the BSD-license allows all of the US taxpayers to implement the code in exactly the way they choose, even charge for it or make non-free modifications; but it also preserves the commons aspect of what was created by a public effort. In some cases, it may be necessary to develop under the GPL because that which your basing development off of is the GPL; such was the case in SE Linux.

    1. Re:NSA should continue working on SE Linux by Anonymous Coward · · Score: 0

      FYI

      Since the government can not copyright software, there really is no way for it to enforce a license.

    2. Re:NSA should continue working on SE Linux by SubtleNuance · · Score: 1

      redefined to be like the BSD-license NO, it should be released as Public Domain, BSD has the advertising clause, which is incompatible w/ GPL. Therefore a pc of soft could be released into PD and a BSD + GPL + proprietary + ?? projectect could take the code and run with it.

      Just give it away without *ANY* stipulations.

    3. Re:NSA should continue working on SE Linux by Anonymous Coward · · Score: 0

      "Gee, imagine that -- the taxpayers get can get free access to the fruits of the research which their tax dollars made possible."

      How about this? Don't make the tax payers fund it. Problem solved.

    4. Re:NSA should continue working on SE Linux by dh003i · · Score: 2

      There should always be the stipulation that whatever was taken from the public domain be redistributed openly.

    5. Re:NSA should continue working on SE Linux by Anonymous Coward · · Score: 0

      Having worked in a group preparing an OS for evaluation under common criteria rules, let me inject one group's experiences and my own opinions.

      1. SELinux is wonderful and will help the overall security of the net.
      2. Those who have responsibility for the evaluation of SELinux have run up against the reality of the difficulty of getting a general purpose OS evaluated. Assume for a minute that SELinux's code and design is perfect and needs not a single change to meet common criteria requirements. Imagine that multiple levels of documentation are required. Imagine that dozens of people years of writing tests are required. Imagine the managerial difficulty of getting such a task coordinated. And imagine that doing so guarantees that the version that is evaluated doesn't keep up with the latest code base (by years), doesn't lead to increased sales, can't be secure enough to be used in classified environments, and doesn't bring in enough $ to fund any of the documentation and test tasks let alone the lab expenses (NSA doesn't do the evaluation at the lower levels, the "company" that wants the evaluation must pay a NSA certified lab to do that work at multi hundreds of thousands of dollars. Then NSA blesses the results.).
      3. Developers don't want to document, they want to go on to the next neat code wigget. So someone else has to do the grunt work. They will probably want to get paid because, if they are doing it for free, they will want to work on the fun stuff.
      4. If SELinux should ever be evaluated, then changes would have to be handled in a manner different from the way "real" Linux handles them today or their inclusion would make the evaluation invalid. This destroys one of the great strengths of Linux and a prime reason for using it.

      IMHO, it's too big a nut to crack. There is no economic incentive for any outside company to fund it. For NSA to fund it would be a conflict (imagine evaluating your own product).

      There is a company working on getting evaluations of an OS that runs Linux applications, but the underlying OS has no code in common with "real" Linux and is designed for security from the begining, much more architecturaly "pure" in design, less rich in driver support for devices (every driver adds evaluation overhead). Such a company has a commercial incentive to spend the dozens of staff years in doing the documentation and test writing tasks.

      The product can't be cheap because they must recover the millions in investment to write the OS and then prepare for the evaluation, fund the evaluation and then maintain the evaluation.

      There is no such thing as a free lunch.

  41. Enter some stupid rhetoric MS hating crap here by josh+crawley · · Score: 1

    How can we even trust what the NSA was doing? Perhaps there was some weird coding loophole that they could exploit..

    ANyways, wasnt this patch only used to add a level of true user based security and checking (based on certain credientials: IP, time, packet size.. whatnot).

    And If I can remember, I believe Linux made the security model of the Linux kernel to be hot swappable with future new models- like that of VMS. The user/group based security is a pain in the ass. At least with MS, permissions arent a big problem (they have shitloads of other problems).

    All this leads up to what my big point is.. MS has it right with permissions (well, what they ripped off of VMS) and Linux doesnt. The NSA source is GPL and just sitting there. WHo wouldnt stop a kernel hacker to make a good implementation of a UP TO DATE security model? Well, that and an FS for it.

    1. Re:Enter some stupid rhetoric MS hating crap here by Anonymous Coward · · Score: 0

      How can we even trust what the NSA was doing? Perhaps there was some weird coding loophole that they could exploit..

      Nope.

      ANyways, wasnt this patch only used to add a level of true user based security and checking (based on certain credientials: IP, time, packet size.. whatnot).

      Nope.

      And If I can remember, I believe Linux made the security model of the Linux kernel to be hot swappable with future new models- like that of VMS. The user/group based security is a pain in the ass. At least with MS, permissions arent a big problem (they have shitloads of other problems).

      the Linux Security Module won't be in a stable kernel version until 2.6

      All this leads up to what my big point is.. MS has it right with permissions (well, what they ripped off of VMS) and Linux doesnt. The NSA source is GPL and just sitting there. WHo wouldnt stop a kernel hacker to make a good implementation of a UP TO DATE security model? Well, that and an FS for it.

      #1, DAC (aka user/group) is the way unix works, linux isn't trying to spin off into its own incompatible corner of the universe (yet)
      #2, SELinux used a technology that was covered under a patent, the kernel is supposed to be untainted with proprietary crap
      #3, filesystem for it? WINDOWS is the one who had to invent a new filesystem to have a new security model.
      #4, just sitting there? I use it.

    2. Re:Enter some stupid rhetoric MS hating crap here by Anonymous Coward · · Score: 0
      How can we even trust what the NSA was doing? Perhaps there was some weird coding loophole that they could exploit..
      Try:
      diff -u linux-orig/ selinux/
      That will, believe it or not, show you all the changes the NSA made to the code. Now you can go and find your "weird coding loophole."
  42. Comment removed by account_deleted · · Score: 3, Insightful

    Comment removed based on user account deletion

  43. third world wear? by Anonymous Coward · · Score: 0

    so everyone will switch to clothes made overseas? already happened anyway

  44. slightly OT, but... by dmnic · · Score: 1

    the company I work for sells many desktops, workstations and servers to the DOD. NONE of them are Windows machines. their either OSX or Unix....take it how you will...

    1. Re:slightly OT, but... by Anonymous Coward · · Score: 0

      Who do you work for? We are fighting the Windows vs Mac battle where I work and could use as much good security/stability info for OSX as we can get. Thanx.

  45. Implications of GPL dawning by Subcarrier · · Score: 1

    We didn't fully understand the consequences of releasing software under the GPL (General Public License),'

    NSA probably figured out that terrorists have the right to create a derived work without the NSA backdoor as long as they distribute the source code.

    --
    "I have opinions of my own, strong opinions, but I don't always agree with them." -- George H. W. Bush
  46. What I find annoying here by Vicegrip · · Score: 2

    It's particularly annoying that an explanation of exactly what the NSA didn't understand about the GPL wasn't well identified here-- other than "a lot of well-heeled lobbying.... erm complaints ... changed our minds".

    The NSA has a large breadth of expertise to offer that should not benefit solely proprietary software. Has no-one bothered to propose to them the concept of dual-licensing? Surely if Microsoft was interested in a portion of their technology they could obtain that technology under a different license.

    This whole escapade has the feel of ugly politics.

    I know I found the idea of SE Linux extremely refreshing and encouraging.

    --
    Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
  47. The article makes at least one mistake by sheldon · · Score: 1, Troll

    The article makes this statement, "Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business."

    This statement is wrong. If the NSA had wanted to make a secure version of FreeBSD, then the fruits of the research would have been available to everyone. It is because they choose to use Linux, which is licensed under the GPL, that they received complaints because the fruits of the research would be available only to non-commercial entities. [Keep in mind the fruits of the research refers to the source code, not the binaries. A lot of Free Software advocates seem to like to confuse those terms.]

    Towards the end of the article they mention some cooperation with Apple on making a secure version of FreeBSD. There are drastic differences between the BSD and GPL licenses, and it is extremely frustrating to see those issues either not addressed, or purposefully blurred. Commercial software developers are not complaining about Open Source, they are complaining about the GPL.

    1. Re:The article makes at least one mistake by Vicegrip · · Score: 2

      Agreed, there are differences that make GPL (not LGPL) licensed software difficult for being adopted by commercial interests.

      The problem with commercial software however, is that its lifespan is limited by profitability-- a volatile threshold that has seen countless interesting innovations dead on the shelves of corporate dis-interest.

      We saw with PGP what happens when a company decides to cancel a products. It goes on the forget-about-me-shelf until somebody with enough muscle and $$$ can buy it from them-- and maybe resurrect it.

      Some technologies lend themselves rather badly to being closed up into proprietary black boxes and I think the domain of secure software is one of these such areas.

      What happens when it simply isn't profitable to fix a security flaw? I know I've spent countless hours in meetings weighing the pros & cons of fixing flaws in commercial software; meetings where the severity of the flaw is a miniscule factor when wheighed against the perceived return/cost of working on it.

      Some things need to be maintained regularly for long periods of time. Commercial interests often fail far short of doing the job adequately.

      I think there is value in insisting that security technologies remain open-- ensuring that critical security software continue to be properly maintained. To this end, I think the GPL/LGPL (the LGPL moreso) is an excellent vehicule.

      --
      Do not spread "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0" over the internet, thank you.
    2. Re:The article makes at least one mistake by Anonymous Coward · · Score: 0

      Yea, I think BILLs head explodes when anyone within
      earshot mentions the GPL license.
      After years of legally appropriating BSD code, the thought
      of having to spend money on programmers (due to the GPL)
      scare him to death.
      -
      If microsoft does not use BSD code in the manner
      described above, and if microsoft has no plans of ever
      using GPL code in its products, then
      WHAT THE FSCK is the problem??
      If I were king ...

    3. Re:The article makes at least one mistake by sheldon · · Score: 1, Troll

      These are certainly valid concerns. It's just not clear to me why people think the GPL is a solution.

      If the technology created by the government research is of any use, it's going to be of interest by commercial firms. If you use the GPL that simply means that they will recreate the source via a simple reverse-engineering process. i.e. document the APIs and write flow-charts for method calls and then rewrite from scratch. They may contribute back some comments, but it won't be in the form of source patches because their implementations are different.

      Now if the BSD license were used, the commercial companies could integrate the exact source into their product, most likely contributing back updates and suggestions on how to improve it. This insures a certain level of compatibility and similarity between implementations. If they do not contribute back then ohwell, the BSD version is still available and can be maintained by non-commercial entities interested in that. You have not lost anything.

      Either way the consumer will have a choice, the free version or the commercial version. It's just in the GPL case you've created a lot of extra work for someone, and it's not quite clear to me what the purpose of that is. If you say it's because it's not fair that a commercial entity would profit off the work, then charge something for it. Government agencies do that all the time to try to recuperate costs. But if it's not available at all, I think a very valid argument could be made that says it is not the job of the government to invest in such research if it is closed off from commercial usage.

      This debate appears to me to be taking the form of "We have the GPL, now we must find problems to justify using it!" Rather, why don't we first lay out the problems, and then think of ways to solve those problems which provide an adequate solution to all parties involved?

      Most of the arguments seem to revolve around the need to have access to the source code. Understandable, and I think we can find ways to do this with commercial software. Remember, commercial software does not mean closed source, that just happens to be the defense mechanism used today because of abuse. But what if all software were mandated to come with source? Then it'd be pretty easy to look for source code plagarism, and I think it would benefit the entire industry by showing others how to do things. This would also provide some balance with the use of software patents.

      In all of these discussion, what I'm not seeing is a justification for the freely distributable point. Other than a desire for a handful of geeks to get software for free, what valid purpose does this serve above and beyond the availability of source code with the product? If I have the source, I have openness and maintainability. What does forcing freely redistributable gain me other than being anti-commercial?

    4. Re:The article makes at least one mistake by Anonymous Coward · · Score: 0

      The source code is available to non-commercial as well as commercial entities. The GNU GPL just forces the commercial entities to play fair and distribute the source if they also distribute the binaries.

    5. Re:The article makes at least one mistake by cburley · · Score: 1
      Commercial software developers are not complaining about Open Source, they are complaining about the GPL.

      This is, what, the third time I've pointed out that you are lying with this "GPL source code cannot be used by commercial companies" crap?

      Microsoft is a commercial company, yes?

      Microsoft is distributing the source code to GNU Fortran (g77), yes?

      Microsoft is therefore distributing GPL'ed source code for commercial benefit, yes?

      Why then do you keep telling lies about how GPL'ed source code can't be used commercially?

      (Hey, ever hear of Red Hat?)

      --
      Practice random senselessness and act kind of beautiful.
    6. Re:The article makes at least one mistake by mpe · · Score: 2

      If the NSA had wanted to make a secure version of FreeBSD, then the fruits of the research would have been available to everyone.

      The results of would be available, to everyone, regardless of if the code was released BSD, GPL, or public domain. The only difference is that GPL code cannot be mutated into proprietary software. For most people and corporations this isn't any kind of issue at all, since they would never want to do this in the first place.

      It is because they choose to use Linux, which is licensed under the GPL, that they received complaints because the fruits of the research would be available only to non-commercial entities.

      This is completly untrue, it is equally available to all entities.

      There are drastic differences between the BSD and GPL licenses,

      These "drastic" differences mean nothing to most people. Since they involve a set of actions which few people would even consider. It is also highly questionably that any entity should be allowed to perform these actions on publicly funded material in the first place.

      and it is extremely frustrating to see those issues either not addressed, or purposefully blurred. Commercial software developers are not complaining about Open Source, they are complaining about the GPL.

      Proprietary software developers, a very tiny group, are the ones blurring the issue. Demmanding that the interests of the majority be subverted to protect their interests. (N.B. "commercial" is not a synonym for "proprietary".) In this case it isn't even the tiny group it's a minority of one. If a regular person had complained to the NSA, even if they had a more valid complaint, would any notice have been taken of them?

    7. Re:The article makes at least one mistake by mpe · · Score: 2

      Some technologies lend themselves rather badly to being closed up into proprietary black boxes and I think the domain of secure software is one of these such areas.

      It's quite possible that proprietary software is really best suited to highly specific applications and not as "software infrastructure". Though it is probably possible to "make do" with using proprietary software in this way.

      Some things need to be maintained regularly for long periods of time. Commercial interests often fail far short of doing the job adequately.

      There is a lot which falls into this catagory, most commonly in government usage, since government tends to have to keep data secure for a long period of time. However even commercial users of software often have such requirements.

      I think there is value in insisting that security technologies remain open-- ensuring that critical security software continue to be properly maintained.

      Security is an issue more or less fundermentaly incompatable with the ideas behind proprietary software.

  48. Contradictions abound by BigBir3d · · Score: 2
    "Our interest is in helping to ensure that the government licenses its research in ways that take into account a stated goal of the U.S. government: to promote commercialization of public research."


    In essence, we get to decide who makes the money.
  49. Three Words: by Anonymous Coward · · Score: 0

    I hate Microsoft.

    Just like Standard Oil.

    Just like Ma Bell.

    Just like General Elecrtic.

  50. Taxes and Public Ownership by Restil · · Score: 2

    If our tax money goes to pay programmers for a public agency, such as, the NSA for instance, then the fruits of those efforts should be made available to the public that paid for it. Granted, software that deals with national security does not need to be opened to the world, but the NSA recognizes, as do many others in the security business, that having secure systems in the public leads to greater security overall. One insecure system by itself can't cause much damage, but when thousands, millions of them are exploitable, it is not only the owners of those individual systems that suffer, but others on the same network. The world survives if Yahoo and Ebay go down for a day due to the juvinile maliciousness of a 15 year old. But as our lives become ever more intertwined with public networks, there will be those with far less honorable intentions who can cause REAL damage.

    The NSA had chosen to work on a product that will assist in making some of these systems more secure. They even did so in such a way that the conspiracy theorists out there can be satisfied without a doubt that there are no hidden NSA backdoors. And since they probably did so with the aim of using such software in house, at least to some extent, the lack of significant license expenses will result in less budget requirements, or at the very least, more efficient use of the current budget.

    Microsoft may be upset over the double blow. One, because the NSA won't be purchasing as much of their software, and two because they'll be releasing their efforts back into the open source (read PUBLIC) community for no additional cost, therefore offering more competition to Microsoft. Of course, it's the very actions of companies like Microsoft that gave rise to the open source communities in the first place. Its a shame they feel the need to whine about it now.

    -Restil

    --
    Play with my webcams and lights here
    1. Re:Taxes and Public Ownership by Anonymous Coward · · Score: 0

      So you are saying that the govt should do no work under the GPL. I couldnt agree more. Anything the govt does should be done under a BSD type license, or just put into the public domain. The GPL is not a suitable license for govt work (or really any software work) - it pisses me off that my taxes are used for GPL work - I wouldnt mind if it was all BSD style.

  51. did they? by Anonymous Coward · · Score: 0

    well you're the fucking journalist timothy. you tell us, instead of basing an article purely on conjecture

  52. old news by Triumph+The+Insult+C · · Score: 1

    at least to the NSA ... they knew about this 4 weeks before it happened. new for us tho. i wonder if they're still after will smith ... i know the movie is over, but his acting was dreadful. please nsa spooks, find him and do something with him.

    --
    vodka, straight up, thank you!
  53. Why not BSD? by renoX · · Score: 2

    Apparently Microsoft is lobbying specifically against the GPL license for products made with tax dollars.

    BSD or LGPL would be fine as far as I'm concerned.

    Let's not be GPL integrist.

    1. Re:Why not BSD? by SmokeSerpent · · Score: 1

      All Government software releases should be BSD-style or Public Domain. Anything GPLish has the problem of requiring anyone using the source code to play it forward, which is not appropriate for Government and particularly in cases such as this hinders the possible benefits by preventing non-open-source developers from integrating any improvements.

      I mean sure, I like Linux, and it'd be great to see it as the only secure desktop OS, giving Redmond a sock in the eye, but OTOH, we cannot deny that the vast majority of USians are going to be using MS products on their desktop for the forseeable future, and having a secure OS in every PC is a greater good than the furtherance of one particular OS.

      --
      All kings is mostly rapscallions. -Mark Twain, The Adventures of Huckleberry Finn
    2. Re:Why not BSD? by Anonymous Coward · · Score: 0

      All software released under a BSD license would be
      available to foreign companies. (thats the nature of the beast)
      This is what microsoft was complaining about.
      -
      NO tax dollar funded research should be made available to
      any entities other that US corporate interests.
      At least according to Microsoft goonies.

    3. Re:Why not BSD? by Anonymous Coward · · Score: 0

      There's nothing wrong with government funding GPL'd software. It's paid for by the public, therefore the public gets the benefits of it.

      Why should private companies get the benefit of using software paid for by public money, without having to give anything back?

      The GPL is there to protect us all.

  54. Too late, Tim. The process is already politicized. by Ilan+Volow · · Score: 2

    Recently, Tim O'reilly wrote a piece on the growing politicization of open source. The software industry has already been politicized by Microsoft. We already have an IT purchasing system where merit has been passed over for political expediency. Quoteth The Who, Microsoft "decided the shotgun sings the song". With government IT spending already politicized, Open Source is merely playing by the rules of the game.

    --
    Ergonomica Auctorita Illico!
  55. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  56. All your IP are belong to us. by dackroyd · · Score: 2

    Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business.

    Microsoft would not comment directly on its lobbying efforts, but did stress that it wanted to ensure the government continued to fund commercial ventures. "Our interest is in helping to ensure that the government licenses its research in ways that take into account a stated goal of the U.S. government: to promote commercialization of public research."


    Hmm, so let's get this straight, using tax-payers money to do useful research and then giving the results of the research out to the tax-payers, hurts companies, so instead the research should be handed over to a commercial company who will sell the IP at a huge profit ?

    There is something wrong in American society where the needs of a few (or one) companies, outweighs the need of all the citizens, and the other 99.99% of companies, who would all benefit from the research being released into the public domain.

    I suggest for the benefit of your country, you send a message of support to the Open Source now bill, before your government is completely assimilated.

    --
    "Free software as in beer, copy protection as in racket" - Telsa Gwynne
    1. Re:All your IP are belong to us. by mpe · · Score: 2

      Hmm, so let's get this straight, using tax-payers money to do useful research and then giving the results of the research out to the tax-payers, hurts companies, so instead the research should be handed over to a commercial company who will sell the IP at a huge profit ?

      Actually it may hurt a few companies and the one whineing the most dosn't pay much in the way of taxes in the first place.
      Effectivly Microsoft is asking for a subsidy from the US government.

      There is something wrong in American society where the needs of a few (or one) companies, outweighs the need of all the citizens, and the other 99.99% of companies, who would all benefit from the research being released into the public domain.

      To these hundreds of millions of people having the code GPLed has zero negative consequences and some potential positive consequences. Microsoft's objection is that they couldn't take the software then "embrace and extend". Which is something which hurts the majority whilst only benefiting Microsoft.

  57. Re:lesser known AutoCAD by gerf · · Score: 1

    As i look in my AutoCAD 'about' file, i see "Copywright Microsoft 1996." so, basically, they 0\/\/|\| Autocad. yeh, poopy, isn't it? my opinion is that Acad should be a part of their Ori-er, Office package.

  58. ... and thus hurting American business by Anonymous Coward · · Score: 0

    The news article says: "Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business."

    So it is OK for ripping off the work of people living worldwide and use it only for American Corporation, and rip of companies of other countries?

    Yeah .. we all love the american way of thinking ...

  59. It wasn't Microsoft who did it... by Apostata · · Score: 1

    ...it was Mrs. Plum...in the library...with a candlestick.

    --

    This wasn't just plain terrible, this was fancy terrible. This was terrible with raisins in it. - Dorothy Parker
  60. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  61. Re:Individual Commercial Interests by gerf · · Score: 1

    True, but we at least like to think we made some leeway in there somewhere. old man: "remember back in the day, when we could walk down the street, tokin on a doobie, and the cop would just nod his head and say 'have a good day sir'? them were the days, oh yeah." it's what the capitalistic business model is: more restrictive for bigger profits. like sh1t, it happens

  62. Compete with private industry my ass by dh003i · · Score: 2

    SE Linux does not compete with private industry. Any corporation can take the techniques used to enhance linux (hence SE) and implement them in their own software. Any corporation can just grab the code and stick it in, provided they keep it separated from their proprietary code.

    Any corporation can benefit from this by using it within their infrastructure.

    MS' claims are absurd. The US government has the responsibility to do what is best for all of its citizens (while respecting the constitution and the amendments), not just what is best for corporate America. Granted, corporate America is a part of the picture, but its not all of it. SE Linux is a great benefit to the public as a whole.

    The government has no obligation to subsidize obsolete products by buying them when it can make superior ones and use them; this -- subsidizing and using inferior products regarding security -- is dangerous to the security of the nation.

    Futhermore, the results of government research should be available to all to use, whenver possible. In this case, the government based it off of the GPL, so it had to be GPL'ed. Never-the-less, it is available for all to use, with one restriction in that any modifications of it must also be GPL'ed. But MS whine the same complaint if the government did SE BSD: its competing with private industry. Bullshit.

    If MS doesn't like the fact that this is hurting their business, they should make a more secure OS. But don't expect MY tax dollars to go towards buying an INSECURE OBSOLETE operating system, thus subsidizing a private industry (i.e., MS) which can't make it on its own.

    1. Re:Compete with private industry my ass by Anonymous Coward · · Score: 0

      Agree. And let me follow up by saying our government develops products that technically competewith products from private industry all the time. A classic example is agricultural crop varieties. Since the late 1800's, the USDA, in conjunction with state land grant universities, have been developing new varieties of crops with taxpayer money and then releasing those varieties to the public domain (including all the research information, such as the pedigree of the variety, details of the breeding selection process, etc). Thus, even though we as taxpayers did front the money to develop the varieties, any citizen can obtain those varieties through the federal germplasm banks or state crop improvement agencies to plant or to conduct further research. This system competes directly with private seed companies, but for the most part private companies don't seem to mind because they benefit from the research as much (and arguably more so) as everyone else. I think that our government getting involved in open source software can be very positive for everyone, including our goverment agencies, the taxpayers, and commercial software companies. The problem is that Microsoft, like some other industries/companies, like their current business model and will do anything to prevent change. However, change is inevitable. Microsoft is showing their desparation to keep things the way they are, but unless they are willing to change they may one day go the way of many other formerly successful companies that are today out of business.

    2. Re:Compete with private industry my ass by mpe · · Score: 2

      SE Linux does not compete with private industry. Any corporation can take the techniques used to enhance linux (hence SE) and implement them in their own software. Any corporation can just grab the code and stick it in, provided they keep it separated from their proprietary code.

      To the vast majority of corporations this is no issue at all. Since only a minority are in the business of making proprietary software and selling it to third parties. Even quite a few entities supplying software to third parties do so with the software bundled with a product or service and only go proprietary because that's what everyone else does.

      Any corporation can benefit from this by using it within their infrastructure.

      To the vast majority, software is part of their infrastructure. To these these people being able to modify/have modified any part of the software to suit their needs and a lack of a complex licencing model is likely to mean lower costs to them.

      MS' claims are absurd. The US government has the responsibility to do what is best for all of its citizens (while respecting the constitution and the amendments), not just what is best for corporate America.

      Corporate America does not equate to The Microsoft Corporation or even the proprietary software industry

      Granted, corporate America is a part of the picture, but its not all of it. SE Linux is a great benefit to the public as a whole.

      The vast bulk of corporate America is part of the public who stand to benefit in this case anyway...

    3. Re:Compete with private industry my ass by dh003i · · Score: 2

      You make a good point. In most cases, when I said "Corporate America," I should have said Microsoft, since Microsoft's reall the only one with anything to lose.

  63. trust in the govt? by Anonymous Coward · · Score: 1, Interesting

    Hold up. Forget competition for a second.

    A large number of /.ers don't trust the govenment to keep our privacy intact, but you want to run a government built OS?

    Not to mention the govenment doesn't exactly have the best record with any type of security. Hell, they can't even keep track of the acutal computers that contain private information.

    I can't tell you how disappointed I am that I don't get my govenment OS.

    1. Re:trust in the govt? by atarola · · Score: 1

      I would not mind using this government built OS because if i was afraid of any security problems in it, I can look at the source. If the OS was not Open Source however...

      --
      For every complex problem there is an answer that is clear, simple, and wrong. --H L Mencken
  64. They have one point by jasonditz · · Score: 3, Insightful

    IMO Government research, if it is to be done at all, must be placed in the public domain for all to use. Its undesireable and unneccesary to have the government advocating any particular license. Using BSD or X11 license would make more sense for government software projects. Let everyone (even proprietaries) get some use out of it. After all, all that money to pay for it was stolen from them too.

  65. All research competes. by deanpole · · Score: 1
    It is funding research free to the rest of the world which competes with American Corporations

    Yeah, so is all government funded research. Have you heard of The Genome Project vs. Celera?

  66. Should the Government Compete w/ Private Industry? by Skjellifetti · · Score: 4, Insightful

    Years ago the University Ag Campus where I went to school had a meat shop where you could get cheap beef/poultry/pork, etc. These were animals that had been raised on the Ag Campus farms for research and teaching and were no longer of use in whatever project. But they got into hot water with the Krogers supermarket chain because they were a gov't entity competing with private enterprise. NSA's Linux enhancements are no different. It isn't clear to me that MS is in the wrong here. Gov't should not be writing GPLd software that cannot be used in proprietary applications. A BSD style license would be much better. And such software efforts should be relegated to research only and not be attempts to build production ready software.

  67. Libertarian Groupthink by Royster · · Score: 2

    When you think about it, the government's only real job is to defend the rights and freedoms of its citizens.

    Government's role is to promote the welfare of the people. Sometimes that means promoting business. Sometimes that means providing a social safety net. Sometimes that means providing for a common defense.

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
    1. Re:Libertarian Groupthink by Anonymous Coward · · Score: 0

      Microsoft is the only company allowed to tax our government. They are simply protecting that right by not allowing SE Linux to let them get away from paying the MS tax.

    2. Re:Libertarian Groupthink by 1010011010 · · Score: 1


      Government's role is to promote the welfare of the people.

      No, it's not. That's your mother's job.

      Prenventing and punishing use of force and fraud is the legitimate role of government. Not providing "free" money to one group by taking it from another.

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    3. Re:Libertarian Groupthink by 1010011010 · · Score: 2

      Government's role is to promote the welfare of the people.

      No, it's not. That's your mother's job.

      Prenventing and punishing use of force and fraud is the legitimate role of government. Not providing "free" money to one group by taking it from another.

      Sometimes that means providing for a common defense

      That's about all it should mean. Not ptomoting business. Not providing a social "safety net."

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    4. Re:Libertarian Groupthink by Anonymous Coward · · Score: 0
      Is it telling that your idea of the proper role of government is not realized in a single modern or close-to-modern government?

    5. Re:Libertarian Groupthink by 1010011010 · · Score: 2

      Is it telling that your idea of the proper role of government is not realized in a single modern or close-to-modern government?

      I don't think so. It wasn't realized in Medieval governments either, for instance.

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    6. Re:Libertarian Groupthink by Anonymous Coward · · Score: 0
      In the future, people will worship you.

  68. That is MY money they are talking about! by bluGill · · Score: 3, Insightful

    "The federal government plays an important role in funding basic software research," said a Microsoft representative.

    As a US tax payer, that is MY MONEY they are talking about there. I have no objectisons to the federal goverment funding development for things they need, but Microsoft is talking as if it is their right to have the money. It is not a right. Software may not be a significant part of the US budget (though much of it is obscured in other items), but it still amounts to millions or even billions of dollars a YEAR! (I used to work from one company that was getting a couple million a year to develop software, combine that with a few other companies)

    I pay taxes on the money I earn. I expect that money will be used as carefully as I take care of mine. (and I'm known as a frugral guy) That doesn't mean spend no money, but it means think twice before spending it.

    It is NOT the job of the goverment to fund research. Microsoft has a large pile of money, it is their job to invest that money in research. It is the goverment's job to see where the goverment needs something (that may not even be useful to anyone else), and supply money to get the need filled quickly. Any other research is for universities, and should be public domain.

  69. To serve and protect whom? by Dan+Crash · · Score: 5, Insightful

    When you think about it, the government's only real job is to defend the rights and freedoms of its citizens.

    But wasn't that *exactly* what the NSA was doing by working on Security-Enhanced Linux? Defending your rights and freedoms by making sure the computers on which they depend are more secure? Should they be entrusting this job to corporate America, instead?

    Second thing: What should happen to software that the government creates? Should it never be released to the public, left to sit and wallow as a waste of our tax dollars? Aren't we better off by having more choices in the marketplace instead of less?

    (Wow -- every sentence a question.)

    --
    He who refuses to do arithmetic is doomed to talk nonsense.
    1. Re:To serve and protect whom? by Anonymous Coward · · Score: 1, Insightful

      "Defending your rights and freedoms by making sure the computers on which they depend are more secure? Should they be entrusting this job to corporate America, instead?"

      entrust coporate america to develop secure computers?

      coporate america produced windows.

    2. Re:To serve and protect whom? by M.C.+Hampster · · Score: 2, Interesting

      No, that's not at all what they were doing. If you extend the concept of "rights and freedoms" to things like having a more secure OS, you can extend to anything, like "enjoying a good movie".

      Please, show me where in the Consitution or any amendments where we have the "right" you are talking about.

      Ultimately, this comes down to unfair competition. People will say that it's good that Microsoft will have to compete with the NSA. How could that possibly be fair? How is a private corporation that has to make money to continue its existence going to compete with a government organization that has little to no accountability?

      --
      Forget the whales - save the babies.
    3. Re:To serve and protect whom? by Alien+Being · · Score: 1

      the government's only real job is to defend the rights and freedoms of its citizens.

      Uh, what about the postal service? The people realized that such an important part of society could not be trusted to corporations (our founding fathers were communists to a degree). Of course if MS had been in the delivery business back then...

      Unfortunately, citizens don't count anymore. The only thing the politicians care about is favors from rich people.

    4. Re:To serve and protect whom? by EugeneK · · Score: 1

      So Microsoft has to compete with the NSA. Tough. Please, show me where in the Constitution it says that private corporations enjoy the right not to be competed against by government.

    5. Re:To serve and protect whom? by M.C.+Hampster · · Score: 1

      And if the government starts competing with whatever business you may be involved with, you'll be ok with that? Of course, judging by your extremely informative "Tough" response, I'm guessing you are a government employee.

      I don't have to show you where the government is prohibited from doing anything. The Consitition grants power to the government, it doesn't limit it.

      --
      Forget the whales - save the babies.
    6. Re:To serve and protect whom? by IndependentVik · · Score: 1

      How is a private corporation that has to make money to continue its existence going to compete with a government organization that has little to no accountability?

      And MS is oozing accountability? After all, they were found guilty of anti-competitive business practices and were punished with . . . punished with what, exactly?

      --
      I'd suggest you don't use Slashdot as your only news source, or you will suffer permanent brain damage.
    7. Re:To serve and protect whom? by jaaron · · Score: 1

      Should they be entrusting this job to corporate America, instead?

      YES. Look, I don't care if you like M$ or any other corporation, but the US Government (or any government for that matter) shouldn't be doing the job that some other reasonable business could be doing. The government is to provide for those products and services that are NOT viable business ventures, ie- national defense via the military. There's no reason the government should be monopolizing business opportunities that competent individuals and corportations can do.

      That said, what probably should happen is the NSA hire some corporation to do the work and have it stipulated that after the work is done and paid for the code be released to the public under some sort of Open Source License.

      --
      Who said Freedom was Fair?
    8. Re:To serve and protect whom? by IndependentVik · · Score: 1

      There's no reason the government should be monopolizing business opportunities . . .

      Exactly. Private enterprise is performing admirably in this regard already.

      --
      I'd suggest you don't use Slashdot as your only news source, or you will suffer permanent brain damage.
    9. Re:To serve and protect whom? by M.C.+Hampster · · Score: 1
      And MS is oozing accountability? After all, they were found guilty of anti-competitive business practices and were punished with . . . punished with what, exactly?

      Well, if you would take my entire sentence into consideration, you would see the "accountability" I was specifically refering to was making a profit. Microsoft can't continue to exist unless they make money. We've seen, obviously, the government doesn't have to worry about sticky problems like, oh say, a "budget".

      As for the antitrust stuff, I'll leave that to another thread to argue.

      --
      Forget the whales - save the babies.
    10. Re:To serve and protect whom? by Elwood+P+Dowd · · Score: 2

      Second thing: What should happen to software that the government creates? Should it never be released to the public, left to sit and wallow as a waste of our tax dollars?

      It should be released into the public domain. This is pretty intuitively obvious. If the government produces IP, everyone should get a peice. The government should never ever produce IP that's covered by an individual's or corporation's copyright. This is not compatible with the GPL. I really have to go with MS on this argument. If the NSA wants us to have a secure operating system, they should work on stuff with a BSD license.

      --

      There are no trails. There are no trees out here.
    11. Re:To serve and protect whom? by Clubber+Lang · · Score: 1

      (Wow -- every sentence a question.)

      "Do I know what rhetorical means?" - Homer J. Simpson

      --
      Actuaries - making accountants look interesting since 1949
    12. Re:To serve and protect whom? by gricholson75 · · Score: 1

      You realize private corporations do a much better job than the post office, right? I mean really, who uses the USPS to ship packages anymore? Why not? Because compared to UPS and FedEx, they suck. If either of those two were allowed to ship regular mail, they would do a better job, at lower rates, and be profitable. Instead, we are stuck with the USPS.

    13. Re:To serve and protect whom? by Anonymous Coward · · Score: 0

      The US Constitution does limit the power of the federal government. The tenth amendment to the constitution states "The powers not delegated to the United States by the Constitution, nor prohibited by it to the States, are reserved to the States respectively, or to the people."

    14. Re:To serve and protect whom? by M.C.+Hampster · · Score: 1

      Sorry I didn't clarify. The Consutition enumerates the powers of the Federal government. It does not begin with the assumption that the Federal Government weilds unlimited power and is then limited from that point. I think the 10th Amendment makes that clear by saying any power not delegated to the United States (meaning Federal Government) are reserved for the states and people.

      --
      Forget the whales - save the babies.
    15. Re:To serve and protect whom? by DavidTC · · Score: 5, Insightful
      What the hell is the point of that? The NSA employees hundreds of computer security experts. Outsourcing is possibly the stupidist possible suggestion you could make.

      Working on security is half the NSA's job. (The other half being working on encryption.) They chose to work on the security of Linux, because they use it. Because they want to see their changes incorperated into the kernel (So they don't have to keep updating it.), they gave it back to the community. They didn't just decide to start a computer programming business for no reason, they want security in their OSes and they use Linux. (Possibly because that's code they know doesn't have backdoors.)

      This isn't the NSA trying to compete with MS, this is the NSA trying to make things simpler for itself by putting security, as default, in the OS it uses, so it doesn't have to patch the source each time, and more people will look at the code and find mistakes. (The NSA doesn't fall for security though obscurity. They are well aware the best way to make something security is to hand a copy to a million people and ask them to break it.)

      --
      If corporations are people, aren't stockholders guilty of slavery?
    16. Re:To serve and protect whom? by DavidTC · · Score: 1
      Um...you can't release patches to the Linux kernel under the BSD license, and, even if you could, that would be entirely pointless, as you can't use them without Linux anyway.

      Do you people even know what SELinux is? It's a way to partition off linux programs completely from each other. It's not like it's usable in Window, you can't just move stuff between OSes like that.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    17. Re:To serve and protect whom? by Dan+Crash · · Score: 2

      Just curious -- do you think that the government should never integrate any Open Source licensed code to create needed software, even if the cost of re-writing that code is, say, several thousand dollars more than the OS code? Is there any trade-off to you between economic practicality and pure public domain source?

      --
      He who refuses to do arithmetic is doomed to talk nonsense.
    18. Re:To serve and protect whom? by 4of12 · · Score: 2

      So if the Chinese Red Army wants to release Red Flag SE-Linux 2.0 with Wine 2.0 without source code, then we'd be fine with that?

      Personally, I like the "share and share alike" aspects of the GPL because of the higher force of propagation and distribution of intellectually valuable ideas that it promotes. I like when my tax dollars go into GPL code.

      --
      "Provided by the management for your protection."
    19. Re:To serve and protect whom? by Elwood+P+Dowd · · Score: 1, Flamebait

      Exactly. Since the govt can't release patches to the Linux kernel under the BSD license, then the government should not release patches to the Linux kernel.

      I thought I was pretty clear.

      --

      There are no trails. There are no trees out here.
    20. Re:To serve and protect whom? by shawnseat · · Score: 1

      The USPS does something that really does help the economy, though: it equalizes the cost of delivery anywhere in the US. Under a privatized system, mail would be a lot cheaper between Chicago and New York City, but it would be a lot MORE expensive to send from Lower Armpit, Arkansas to Road Hole, Alaska. This dramatically lowers costs for developing areas away from the largest cities.

      --
      Religion is the opiate of the masses. The wealthy smoke the real stuff.
    21. Re:To serve and protect whom? by Elwood+P+Dowd · · Score: 3, Interesting

      I don't understand your question. It doesn't seem to relate to my post at all.

      I like the "share and share alike" aspects of the GPL too, and I wish I could figure out a way to defend the govt producing GPL code.

      But I can't. Just like I'd be pissed if (and I bet they do this anyway) the govt hacked proprietary software and allowed the proprietary vendor to sell the code.

      The government should never produce intellectual property. Since the public owns the government, the public should own the government's source. This means Microsoft should own it and this means you should own it.

      --

      There are no trails. There are no trees out here.
    22. Re:To serve and protect whom? by Amazing+Quantum+Man · · Score: 2

      Please, show me where in the Consitution or any amendments where we have the "right" you are talking about.

      How about the Ninth Amendment or the Tenth Amendment?

      The Ninth says "Just because we didn't explicitly mention it here, doesn't mean you have it."

      The Tenth says, "If it's not listed here, the Feds don't control it, and it's your right."

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    23. Re:To serve and protect whom? by Dan+Crash · · Score: 2

      From what I understand, the Security Enhanced Linux project was developed in-house for NSA servers, and then publicly released. Any competition was incidental.

      Having said that, now it exists. Why should Microsoft's "right" not to be competed against (where's *that* in the Constitution, again?) trump my right as a taxpayer to get the full value of the software my tax dollars have been spent on?

      --
      He who refuses to do arithmetic is doomed to talk nonsense.
    24. Re:To serve and protect whom? by Elwood+P+Dowd · · Score: 2

      The government usually contracts out developement. If there were a proper competitive bidding process (which there isn't, I guess) then the winning bid would come from the company offering the perfect economic practicality. This could be either proprietary, open, or free software.

      However, if someone employed by the government is doing the hacking, then it should *always* fall into the public domain. No trade off.

      I feel like this solution nicely avoids any wasted tax dollars, and any unfairness.

      --

      There are no trails. There are no trees out here.
    25. Re:To serve and protect whom? by Anonymous Coward · · Score: 0
      Ha. You mean charge twice as much (you really think you could send mail anywhere in the country for 38 cents?) and cover half the territory. If we privatized the road system, every road would be a toll road, and you wouldn't be able to drive to anywhere where the people weren't rich.

      We start with the assumption that the mail system needs to cover the entire country, and we realize that the "profit motive" would not guarantee this. Interstate commerce is strongly benefited by this, and also by the fact that mail service is flat rate, that you can forward mail for free, etc. And not a dime of your tax dollars goes to the Post Office. People love to complain about any large institution, but the Post Office's unique requirements make it pretty damn good.

    26. Re:To serve and protect whom? by Anonymous+Coed · · Score: 1

      Yes, but this is so routinely ignored as to be utterly meaningless. (And it makes me wonder; if this part of the Constitution is meaningless, what about the rest of it?)

    27. Re:To serve and protect whom? by NamShubCMX · · Score: 1

      Isnt GPL a bit of that? Everyone owns the code. Microsoft can use it in their own internal programs if they want to. If they sell it, they must release their code too. Like the rest of the general population. I don't see the big deal in that. If they refuse the code because they wanted to steal it from the governmant, tax payers, public domain, whatever and incorportae it in their OS, break compatibility, and use their monopoly (and their EULA which lets them install what they want on your system) to force it down upon everyone, that's their problem.

      --
      We've always been at war with Eurasia.
    28. Re:To serve and protect whom? by byran+lei · · Score: 0

      >You realize private corporations do a much better job than the post
      >office, right? I mean really, who uses the USPS to ship packages
      >anymore? Why not? Because compared to UPS and FedEx, they suck.
      >
      >
      Bullshit. Do UPS and FedEx deliver to remote rual areas like the USPS does? No they pretty much don't. Left to their own devices do you think UPS and FedEx would serve people living in the inner city? Damn right they wouldn't. They would skim off the profitable routes in the suburbs and leave the rest to the USPS. As for UPS and FedEx being better than the USPS, that's a load of BS. My brother-in-law who lives in VA buys RedHat cdroms from CheapBytes which is in CA and gets them *IN ONE OR TWO DAYS* when he tells CheapBytes to mail the cdroms to him using Priority Mail.

    29. Re:To serve and protect whom? by Elwood+P+Dowd · · Score: 2

      Sure, the GPL is a bit of that. But it's different. Different in a way that makes it not ok.

      Mostly: GPLed software is often copyright by someone. Correct? If the govt makes patches, like SE Linux, they have contributed to someone else's copyright. That is Messed Up. Hell, if they contributed to ReiserFS, then Reiser gets to modify that govt code and release it closed source, and no one else does. That is unfairly assisting the copyright owner.

      Why is it strange to suggest that the government cannot have/contribute to intellectual property?

      --

      There are no trails. There are no trees out here.
    30. Re:To serve and protect whom? by mpe · · Score: 2

      So Microsoft has to compete with the NSA. Tough. Please, show me where in the Constitution it says that private corporations enjoy the right not to be competed against by government.

      Probably in the same section which says that business has a right to make a profit and once a business model has proven profitable every effort must be made to ensure that it continues to be just as profitable
      This is probably somewhere in the CSSA (Corporate Socialist States of America) constitution.

    31. Re:To serve and protect whom? by Anonymous Coward · · Score: 0

      Should they be entrusting this job to corporate America, instead?

      Of course. Only people who can afford to pay ridiculous fees should be allowed secure software, and they should NEVER be allowed to verify that it's secure. That would prevent sales of upgrades.

      Let it never be said that the US Government doesn't look after it's (financially capable) corporate citizens!

    32. Re:To serve and protect whom? by lsdino · · Score: 1

      Responding to the uber-parent & parent:

      uber-parent wrote:
      The USPS does something that really does help the economy, though: it equalizes the cost of delivery anywhere in the US. Under a privatized system, mail would be a lot cheaper between Chicago and New York City, but it would be a lot MORE expensive to send from Lower Armpit, Arkansas to Road Hole, Alaska. This dramatically lowers costs for developing areas away from the largest cities.

      parent wrote:
      Bullshit. Do UPS and FedEx deliver to remote rual areas like the USPS does? No they pretty much don't. Left to their own devices do you think UPS and FedEx would serve people living in the inner city? Damn right they wouldn't. They would skim off the profitable routes in the suburbs and leave the rest to the USPS. As for UPS and FedEx being better than the USPS, that's a load of BS. My brother-in-law who lives in VA buys RedHat cdroms from CheapBytes which is in CA and gets them *IN ONE OR TWO DAYS* when he tells CheapBytes to mail the cdroms to him using Priority Mail.


      The government still regulates interstate commerce. Rather than going out of it's way to create a large government controlled bueracracy, the government could have easily set regulations for the mail/package delivery industry. Each company would have to choose a flat rate for US mail, and would have to deliver mail to everyone. That, of course, would include the ability to pick up mail on par with USPS.

      As for the parent's claim that UPS & FedEx don't deliver to remote rural areas, that's not true, at least not for UPS, who does deliver to remote rural areas.

      Of course, this is really a moot point. USPS is generally run as a seperate entity from the government, and they are generally profitable. The government may as well spin them off, but it doesn't really matter if they do or don't because USPS is generally profitable overall. So who really cares...

    33. Re:To serve and protect whom? by cduffy · · Score: 3, Insightful

      But most systems aren't built ground-up.

      If you've got existing infrastructure you can build on that's GPLed, you have one cost for building something new based on that and GPLing the result, and another (generally much higher) cost for rebuilding the whole thing ground-up.

      Forcing folks to always do the latter, even when the former will accomplish the initial goal of providing the necessary component and at lower cost, is unreasonable.

    34. Re:To serve and protect whom? by cduffy · · Score: 3, Informative

      Mostly: GPLed software is often copyright by someone. Correct? If the govt makes patches, like SE Linux, they have contributed to someone else's copyright.

      Not quite right.

      Linux, for instance, is not all copyright Linus. In fact, most of Linux is not copyright Linus, because whenever someone else contributes a substantial portion, they own copyright on that portion (not Linus).

      That's why folks writing GPLed software can't change the license (or offer an alternately-licensed version) if they accept other people's patches, unless they either rewrite all those patches themselves or require contributors to file a copyright assignment.

      So the government can contribute to a GPLed project and still maintain their own, independant copyright. (That said, it makes more sense to release their patches into the public domain -- even if the derivative work, that being the patched product, must be GPLed).

    35. Re:To serve and protect whom? by Alien+Being · · Score: 1

      "You realize private corporations do a much better job than the post office, right?"

      Nope. For letters and small parcels the USPS gives much better service for the dollar.

      Anyway, my point was that, like the creation of the postal service, the creation of a low cost, secure, open OS is a worthwhile infrastructure project for the US government.

      I wouldn't object to Uncle Sam contracting with private companies to develop it, but the government should have rights to the source code and should be obligated to make it available to citizens.

      We (the people) pay companies to build roads, but we don't pay them a royalty everytime a new car drives on it.

      r-o-y-a-l-t-y - the reason we fought for our independence from England

    36. Re:To serve and protect whom? by Anonymous Coward · · Score: 0

      No. Only about 1% of American computer users use a GPL-licensed system, and those people are disproportionatly likely to be engaged in activities (e.g. hacking into credit-card databases) that are harmful to the population in general.

      If the NSA want to make sure systems are more secure, they should use a liberal licence, so that the systems used by the 99% of people providing the virtually all the funding for that research can actually benefit from it.

    37. Re:To serve and protect whom? by Anonymous Coward · · Score: 0

      Actually, you *can* release patches under any licence you like; the only time the GPL comes into play is when you *merge* those patches into a kernel.

      The BSD licence without the advertising clause is GPL-compatible, and so Linux kernel patches *can* be released under the BSD licence.

    38. Re:To serve and protect whom? by Elwood+P+Dowd · · Score: 2

      Yeah, I know. Still, it irks me as unfair. I realize that the Gov't probably wouldn't go the length of assigning their copyright to someone else, so they could probably never have their stuff included in a product like ReiserFS. Since Reiser requires a copyright assignment.

      Thing is, I was under the impression that the government could not legally hold a copyright. Period.

      What's this you say about "it makes more sense to release their patches into the public domain -- even if the derivative work, that being the patched product, must be GPLed"? I like this idea a lot. I just thought that the FSF types had said that patches *are* derivative works, and thus must also be GPLed. Have I misunderstood copyright law? Are the FSF folks out of their minds? Is this a debatable point?

      --

      There are no trails. There are no trees out here.
    39. Re:To serve and protect whom? by cduffy · · Score: 2

      What's this you say about "it makes more sense to release their patches into the public domain -- even if the derivative work, that being the patched product, must be GPLed"? I like this idea a lot. I just thought that the FSF types had said that patches *are* derivative works, and thus must also be GPLed. Have I misunderstood copyright law? Are the FSF folks out of their minds? Is this a debatable point?

      Well... maybe. :)

      By the FSF's definition, a derivative work is "a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language". A context diff could be construed as containing portions of that which it modifies, but a complete new file or subsystem is pretty clearly a separate work. If that file or subsystem is written so as not to be specific to the GPLed larger work it plugs into, its ability to stand alone as an independant work becomes much clearer.

      So, roughly: On something where you're modifying preexisting functions, it's debatable -- but the FSF types would have a good shot at winning. On something where you're adding new files and not copying in code from the rest of the system, on the other hand, they'd have much less of a case. If the internals of your code don't depend on API functions and such specific to the GPLed code you intend to integrate it to, your ability to make your code public domain even if the derived work including your code must be GPLed is exceedingly clear.

      I don't know if the federal government can hold copyright, by the way, and don't particularly care to look it up right now. What they certainly can do (and have done before) is controlled what was done with the rights on software via contract with the companies developing the same. A few extra hoops involved, certainly, but the end effect is the same.

      All that said, though, I'm not a lawyer. Civil law is kind of a hobby of mine, but I'm not as well read on IP law as I should be. So: If you want to actually go do anything based on what I've said here, go talk to a real IP lawyer licensed in your jurisdiction. All that aside, though, I *think* I'm right.

    40. Re:To serve and protect whom? by DavidTC · · Score: 1
      I stand corrected. I don't really know why I said that, I know you can release your own source under any license at all.

      My point was supposed to be that the NSA can't really release it under any license except GPL, because it's so tied to the Linux kernel. Sure, their code can be released under the BSD, but as their code is basically kernel patches, that's a bit silly.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    41. Re:To serve and protect whom? by luphus · · Score: 1

      corporate america produced windows.

      Hey now, don't blame a blame all of corporate america for the actions of M$ and some bad crack.

      nwp

  70. Re:Why Linux sucks by shades66 · · Score: 1

    Is this the transcript of Bill Gates talking to the NSA??

    --
    ---- There are 10 types of people in the world. Those that understand binary and those that don't
  71. You forgot some etc/hosts entries by Anonymous Coward · · Score: 0

    Add these to your list:

    127.0.0.1 images2.slashdot.org
    127.0.0.1 ad.doubleclick.net
    127.0.0.1 ln.doubleclick.net
    127.0.0.1 m.doubleclick.net
    127.0.0.1 m2.doubleclick.net

    1. Re:You forgot some etc/hosts entries by Anonymous Coward · · Score: 0

      Thank you for your cooperation.

  72. Microsoft and Bush, Rubbing a Magic Lantern by Anonymous Coward · · Score: 0

    Call me paranoid, but I think there's more than campaign contributions and fiscal back-scratching going on here.

    I'd say that most of the reason this has come about is a secret agreement between Microsoft and the Bush administration to install backdoors Microsoft Operating systems that the NSA can access.

    Why do you think there was the recent change in the way that Win2K does software updates?

    Just a thought.

  73. neither you or the guy you replied to gets it by YaRness · · Score: 3, Insightful

    in the article, the fear was that american businesses would suffer because, if the nsa produced open-source software, it would be available on a international level, and would offer more competition to american businesses.

    "Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business."

    which is all bullshit: open source stuff would promote more and better research; you have to learn how to do it better/faster/whatever when everyone just got access to the latest greatest way of doing it (whatever "it" happens to be).

    anyway the good news is,

    "Despite the intense battle surrounding the open source, the NSA will still fund research on secure operating systems based on Linux as well as work with U.S. companies to create better security in their own operating systems."

    1. Re:neither you or the guy you replied to gets it by Anonymous Coward · · Score: 0

      If "it" happens to be GPL, rest assured nobody will make any real money on it.

    2. Re:neither you or the guy you replied to gets it by mpe · · Score: 2

      in the article, the fear was that american businesses would suffer because, if the nsa produced open-source software, it would be available on a international level, and would offer more competition to american businesses.

      The false assumption in the argument is that a major part of American businesses are in the software supply business. When in truth the vast majority of businesses, in the US and elsewhere, are consumers of software.
      Increased competition is generally good for customers, since it tends to lead to better quality products at lower price. If US business wasn't giving Microsoft lots of money you might expect that their shareholders, employees and customers would benefit.

    3. Re:neither you or the guy you replied to gets it by YaRness · · Score: 1

      i know that, and you know that, but when the government has that 1 billion dollar producing a month mammoth charging at them yelling something else, they tend to listen. much to our disadvantage.

      and i'm not necessarily knocking microsoft for doing it either, right now i'm more irritated at the government being so open to influence by coporatations.

  74. M$ really has something to fear by Anonymous Coward · · Score: 1, Interesting

    Microsoft is certainly worried about one thing: the increase in noise coming out of governments (Peru, China, the EU, etc) where they are either creating or promoting GPLed software across the board. RedFlagLinux is aptly named, as it throws up a red flag regarding the future of government IT.

    Governments have the resources to push public IT anywhere they choose. And where public IT goes the private sector might follow. In the US, corporate giants are welded to the suger tit of Government contracts. What if they had to start developing financial and defense applications for a GPLed Federal infrastructure? They would, you know. The NSA could have handed out their inhouse Linux brew, even if there was no Peru-style legislation to require it. And given the hysterical terror-hacker meme making the media rounds many US agencies would have snapped up a free governement certified secure OS, if only to cover themselves. It would have been all done under the table, and nobody the wiser unless they noticed a downturn in governement IT RFPs for general purpose operating systems.

    But given that this is the NSA, come on folks, what do you really think? They just shut down and went home? What do you think they do with all that "black budget" funding they get to fight terrorism? The next time you run into SELinux it might reading your email.

  75. WTF? by Platinum+Dragon · · Score: 2

    "The federal government plays an important role in funding basic software research," said a Microsoft representative. "Our interest is in helping to ensure that the government licenses its research in ways that take into account a stated goal of the U.S. government: to promote commercialization of public research."

    Translation: we want the Feds to pay for stuff we can package up and sell. God, mom, and apple pie forbid they release anything for free under a license we don't like.

    Read another way, it sounds as if Microsoft wants to turn public information into private property for its own benefit.

    A lot of people complain that the federal government seems to be bought and owned by numerous corporate interests. Microsoft seems to be saying that's the way it should be, that federally-produced software, made with taxpayer dollars, should be released in such a way that M$ can sell it back to those taxpayers for a healthy profit.

    Perhaps I'm overreacting (I do that quite a bit lately), but this seems to be a very arrogant position for a company to take. Then again, this is the same company that invited Peru's president to its headquarters in an effort to fight a Peruvian free-software-in-government law, while that company's government made nasty noises to Peru through its ambassador.

    Am I the only one creeped out by this?

    --

    Someday, you're going to die. Get over it.
    1. Re:WTF? by Anonymous Coward · · Score: 0
      Ridiculous!

      "The paradoxical notion is that allowing anyone and everyone to see secret data creates greater security. The NSA releasing SE-Linux under the General Public License did not increase cyber-security worldwide. The exact opposite effect has been noted by the NSA regarding SE-Linux. Unwittingly, the NSA has fallen into the same trap that the traitorous American scientists who gave the Soviets nuclear secrets in the late-40s/early-50s fell into. The taxpayer-purchased SE-Linux 'enhancements' by the NSA and released worldwide under the GPL have made everything less secure for everyone in the world."

  76. I'm removing one Windows Server from my network. by SphynxSR · · Score: 1

    This article pisses me off so much I'm going to remove one Windows Server from my corporate network.

    --

    I don't suffer from insanity, I enjoy every minute of it.
  77. MS buys everyone by Dr.+Spork · · Score: 1
    OK, I know this is a bit off topic, but I just can't live with the irony of yet another "Microsoft Payola story" which Slashdot serves up with a huge ad for Microsoft's VisualStudio.net.

    Let me go on record as saying that the next time I see another such ad, I will install an ad-blocker so I won't see any of /.'s sponsors. It is for your guys' own good. I just dread the thought of what would happen if Slashdot got much cozier in Microsoft's money-lined bed.

  78. How's this for a solution? by thrillbert · · Score: 2

    Let the NSA continue it's research into securing the Linux Kernel. Then they can Certify it for Government Use ONLY.

    Now this in my book does not compete with American Companies because as far as I know, there's no one out there who is trying to build a Linux kernel *just* for the government..

    Besides, how many of you are going to trust the NSA enough to have a SE Linux box in your home LAN?

    ---
    To err is human.. and then there was Microsoft...

    1. Re:How's this for a solution? by DavidTC · · Score: 1
      The GPL forbids licenses like that. You can not discriminate against certain people or organizations.

      As SELinux is a kernel patch, and hence a derivative work, it is licensed under the GPL automatically.

      I don't see why the NSA doesn't just release these things into the public domain, it's not like the code is actually usuable without Linux anyway.

      --
      If corporations are people, aren't stockholders guilty of slavery?
  79. That was by 0xdeadbeef · · Score: 3, Insightful

    spin-tastic!

    Now, did you actually say anything to refute the previous poster? I mean, you can't deny the fact that the government already has its hand in quite a lot of things, through academic grants, defense research, etc. etc.

    How the government wields power in this arena is how it premits the fruits of that labor to be releasesd. Refusing to release code under the GPL, but simultaneously allowing vendors to appropriate code developed with public money, smacks of hypocrisy and shows a clear bias in how they approach this issue. It is obvious that they bowed to pressure from a few whiney corporations threatened by Linux.

    So, either the government keeps its hands off industry entirely, or it should plays fair and impartially. You can't have it both ways, using the former argument to attack the latter.

    1. Re:That was by Ben+Edwards · · Score: 0

      Refusing to release code under the GPL, but simultaneously allowing vendors to appropriate code developed with public money, smacks of hypocrisy and shows a clear bias in how they approach this issue. It is obvious that they bowed to pressure from a few whiney corporations threatened by Linux.
      Quite true. When you think about it, anything developed by the NSA or any other government entity is research or product paid for by the U.S. Taxpayer...and hence is public property. Can that public property be given or sold to a private company? I think not, or at least not without a public auction of the technology.
      Actually, the GPL is very closely aligned to the original intent of government research. Such research is to be for the public good. GPL software is freely available to the public, source code and all. Closed-source software, on the other hand, is not available to the public. You can't own it, only license a copy for use under very specific terms and perhaps only for a specific period of time. So government-funded research such as SE Linux should be encouraged...the only real question being "do we release this as open-source, or do we keep it strictly for internal (i.e., governmental) use only?"

    2. Re:That was by tiedyejeremy · · Score: 1

      "So, either the government keeps its hands off industry entirely, or it should plays fair and impartially.
      " do we release this as open-source, or do we keep it strictly for internal (i.e., governmental) use only?"

      It seems to me that virtually all problems with governments in general stem from either an inability or unwillingness to assume responsibility for what it does. Is this any different?

      --
      Anything you say will be held against you. ... "tits"
  80. Re:Too late, Tim. The process is already politiciz by Pfhreakaz0id · · Score: 2

    let me tell ya something, the government contract selection process period (IT or not) is heavily politicized.

  81. US Gov simply cannot release stuff under GPL. by phkamp · · Score: 4, Informative
    It's really very simple:

    To release source code under the GPL, you have to hold the copyright to the code.

    The US Government (in this case represented by NSA) cannot hold a copyright, the law does not allow for it.

    No copyright, no GPL, end of story.

    But I have no doubt that M$ whined too.

    --
    Poul-Henning Kamp -- FreeBSD since before it was called that...
    1. Re:US Gov simply cannot release stuff under GPL. by phkamp · · Score: 4, Informative
      Here is the actual chapter and verse:

      17USC 105. Subject matter of copyright: United States Government works

      Copyright protection under this title is not available for any work of the United States Government, but the United States Government is not precluded from receiving and holding copyrights transferred to it by assignment, bequest, or otherwise.

      --
      Poul-Henning Kamp -- FreeBSD since before it was called that...
    2. Re:US Gov simply cannot release stuff under GPL. by dwheeler · · Score: 3, Informative

      No. It's true that government employees, if they write code, cannot acquire a copyright. But most code is written by contractors (this is true for SELinux), and they CAN have a copyright. And, they can assign their copyrights to the government (the government CAN own copyright).

      --
      - David A. Wheeler (see my Secure Programming HOWTO)
    3. Re:US Gov simply cannot release stuff under GPL. by Error27 · · Score: 2

      >No copyright, no GPL, end of story.

      The government could release the code as public domain and it could be used in a GPL project.

    4. Re:US Gov simply cannot release stuff under GPL. by mpe · · Score: 2

      To release source code under the GPL, you have to hold the copyright to the code.
      The US Government (in this case represented by NSA) cannot hold a copyright, the law does not allow for it.


      IIRC it actually works that they cannot create or destroy copyright. But can have copyright assigned to them and are subject to licencing of copyright works. If the latter didn't hold the US government could simply buy one copy of any Microsoft product they wanted to use and do whatever they liked. Which would really annoy Microsoft.

      No copyright, no GPL, end of story.

      A lot of the things they are likely to have done involved creating a derived work. In the US derived works retain the original copyright holder. Under the current rules the US government can't just take someone elses copyright away. So where is the problem? If there was a problem it would be for one or more of the kernel copyright holders to raise a complaint, rather than some third party.

    5. Re:US Gov simply cannot release stuff under GPL. by mpe · · Score: 2

      The government could release the code as public domain and it could be used in a GPL project.

      If it's original code it would have to be public domain. But if they were to do this with GPL derived code they would effectivly be destroying copyright, which the US Government cannot do, at least not without compensating the copyright holder(s).

    6. Re:US Gov simply cannot release stuff under GPL. by Error27 · · Score: 2

      >>If it's original code it would have to be public domain.

      A program is a collection of original pieces of code. The peices that they authored would be public domain.

  82. Nobody wants the GPL. by Anonymous Coward · · Score: 0

    w000t! What a surprise.

    Nobody wants RMS breathing over his neck (or inside his a$$).

  83. a good threat by briancnorton · · Score: 1

    it seems that all MS has to do is say "We're going to start bundling strong encryption if we have to compete." everybody encrypting email would make the NSA's job impossible.

    --

    People who think they know everything really piss off those of us that actually do.

  84. A 'Statement of Assurance' on SELinux patents by Odinson · · Score: 3, Interesting
    This came just a few weeks ago. It was a top story on LWN the week that LWN said they might go under.

    Apparently, all of a sudden the NSA's partner, Secure Computing Corporation, came out and made a special exception from their Manditory Access Control Patents for SELinux. It may have been a desperate act to keep the NSA on board. It seems this company was deriving exclusive software patents from work partial completed/funded by the NSA. If I were a generally unaware politican told of this situation by a Microsoft birdie, I would see it a fraud/waste as well.

    Although I cannot know for sure, from the basic facts availible to me, this seems to be a case of SCC's software patent greed biting them on their own ass. MSFT probably spun it as, "the govenment partially paid for labor leading to a patent for a competitor of ours, and it's not public domain.

    Disclaimer: I hate software patents, as much as I would hate math patents if they existed. This may bias me against SCC.

  85. Re:lesser known AutoCAD by Anonymous Coward · · Score: 0

    umm, the 'Copywright Microsoft 1996' in AutoCAD is there because ACAD supports .wmf file format, which is copywright microsoft.

  86. Re:Should the Government Compete w/ Private Indust by Anonymous Coward · · Score: 0

    Hi, how are things in Redmond? I guess it is ok for Microsoft to have an unfair advantage in the market, but if someone does it to them they have to stop. Why shouldn't the government write something that is GPL'd? Shouldn't they too be able to make use of any advances in the code base that others may make? After, all they wrote it.

  87. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Which of the listed points are wrong? I will make corrections.

  88. Re:Individual Commercial Interests by L1nUx+h4x0r · · Score: 0

    Instead, sheer humanity must overcome evils like this, lead by initiatives like Open Source, which give the power back to the Individual, and letting him control his own destiny once more. Thank you programmers and hackers for letting OSS live on.

    Thank you, Comrade. You are just the example of the individuals we need to make the Democratic People's United States of America a reality.

    --
    The GPL makes software more like your mom. Free and open to all.
  89. Question by dh003i · · Score: 3, Interesting

    Though I think that there's no basis for MS' complaints, all credability to them would be lost if MS released their additional improvements or modifications into the public domain or under the BSD license.

    But the question is, can the government do that? According to the GPL, no. But, the owner of a copyright can grant exceptions to the license. Thus, Torvalds could grant an exception to the NSA regarding SE Linux, which would be as such: the original source code of the kernel/Linux upon which you based your modifications must still be released under the GPL; however, the modifications or additions you made may be released into the public domain or under the BSD license.

    Furthermore, such would give the GPL license legal credability, as the government would be asking for an exception (though the NSA already gave the GPL license legal credability by releasing their modifications under the GPL).

    That said, perhaps there should be some modifications of the GPL to allow people to release modifications under alternate licenses (which would include the public domain and OSI-certified or OSS licenses), if they can't possibly (due to legal restrictions) release it under the GPL. After all, its better that the modifications be released under a BSD-like license or the public domain (as opposed to the GPL), than not be released at all (which would ocur if the authors of the modifications were prevented from releasing modifications under the GPL).

    1. Re:Question by jpmorgan · · Score: 3, Informative

      Does Torvalds own the copyright to the entire kernel? I wasn't aware that he had had all the contributers in the past send him copyright assignments (which is what the FSF does). I'm fairly sure different parts of the kernel are copyrighted by lots of different people.

      And due to some of the wonderful properties of the GPL, you'd need to get every person who has contributed code into the kernel to agree to the exemption. Good luck.

    2. Re:Question by jsse · · Score: 2

      He does not own the copyright of every part of the kernel, but he's the registered trademark owner of the word 'Linux'. The own of that kernel part may change the license and release their own version of kernel, but it'll not be calling 'Linux'.

      In fact Linus could charge anybody who use the word 'Linux' in their distro, but I'm not sure whether he has exercise his right. (well he does has stocks of RedHat but was given voluntarily, at least that was what his said in his bio)

    3. Re:Question by jpmorgan · · Score: 2

      No, you couldn't, since your code is part of the kernel, which is GPLed, and requires that your code also be GPLed. Hence why you have to get all agreement, or nothing.

    4. Re:Question by rweir · · Score: 1
  90. infrastructure by SethJohnson · · Score: 5, Insightful



    Therefore, when the government interferes with free enterprise, it's interfering with the rights of its citizens.

    By providing a free operating system, the US govt. is NOT 'interfering with the rights of its citizens any more than:

    1. The public libraries interfere with the private bookstores' rights.
    2. Police officers interfere with private security firms' rights.
    3. Public water fountains interfere with bottled water vendors' rights.
    4. Free public skateparks threaten private Van's-owned parks.

    I think it's high-time the US govt. supported an open-source OS project. Though backwards in its perspective on human rights, China is lightyears ahead in its thinking on this subject. If we had a national open-source OS that was used in every government office and available to citizens for free, it would be a dozen times more powerful of a punishment than any wrist-slapping the DOJ is going to give to MS for it's anti-trust crimes.

    Seth

    1. Re:infrastructure by Anonymous Coward · · Score: 0

      china doenst consider "exploitation through capitalism" as a "human right".

      Communism != totalitarianism or fascism.

      Did you know the US houses more people in prisons, and executes more each year than China? What does that say about "human rights"?

    2. Re:infrastructure by Anonymous+DWord · · Score: 2

      While I agree with what you've said, I think if China had a Microsoft, things might be a little different. They have no interest in helping Windows becoming the dominant world-wide system.

      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    3. Re:infrastructure by Anonymous Coward · · Score: 0

      > Did you know the US houses more people in prisons, and executes more each year than China? What does that say about "human rights"?

      First off, that's inaccurate. Quote your source. Even if it were true, it tells me nothing about human rights. What it tells me is that we have lots of violent criminals in the US.

    4. Re:infrastructure by Anonymous Coward · · Score: 0

      Coming soon to you the "Volks-OS!"

      You sound like a Nazi. Seriously.

    5. Re:infrastructure by Anonymous Coward · · Score: 0

      I call Godwin's Law.

    6. Re:infrastructure by EugeneK · · Score: 1
      >First off, that's inaccurate. Quote your source.

      your parent post is correct..

      Prisoners in US : 1,585,401 (number one in the world; USA, USA! woo!)


      Prisoners in China : 1,236,534


      (note that China has about FOUR TIMES as big a population).

      >Even if it were true, it tells me nothing about
      >human rights. What it tells me is that we have
      >lots of violent criminals in the US.

      First off, that's inaccurate. Quote your source. What it tells me is that we have a lot of nonviolent drug offenders in the US.

    7. Re:infrastructure by SN74S181 · · Score: 1

      And I think it would be fine for the US govt. to support an open-source OS project. Released to the public domain, not beholden to some private organization's political agenda.

    8. Re:infrastructure by extrasolar · · Score: 2

      Yes, its a political agenda.

      But its honest politics.

      Thats the difference.

    9. Re:infrastructure by Anonymous Coward · · Score: 0


      While I agree that we have way too many people jailed because of nonviolent drug-related offenses, I don't think that this sheer number of incarcerated people is a black mark on America's human rights record. As a drastic comparison, let's consider Nigeria, where the punishment for adultery is death-by-stoning. I am betting that they have way fewer people in prison (check both total number and per capita for South Africa) than the US, yet I would hardly call Nigeria generous in the human rights department.

      Carl Sagan
  91. Government as a Publicly-owned Company by Slur · · Score: 2

    The government is owned and operated "by the people" for the benefit "of the people." It should go about its appointed tasks in spite of its possible effects on business. There are a million examples of things the government provides every day which could be construed as harming the commercial enterprises that provide those same services.

    This goes to a more fundamental point. If the will and needs of the people must be set aside whenever some commercial interest feels unfairly marginalized then to my mind it satisfies one condition of "anti-competitive" monopoly behavior. i.e., If changes to a product are designed to serve the profit motive of an enterprise at the expense of hurting customers then that action can be seen as anti-competitive.

    It seems to me that the American People should establish themselves as a corporation that can compete on the same level field as Microsoft. The American People - as shareholders in this enterprise - should seek to do what is in their best interest, in service of long-term viability, and to hell with competitors like Microsoft.

    --
    -- thinkyhead software and media
  92. FUD by PineHall · · Score: 2

    Nothing is stopping Microsoft from using SELinux. If they don't like GPL, they can just look at it and use the ideas with their own code. With an open license many "American" companies can make use of it. This is much better than the government working with a single company to develop a commerical product. In that case only that company benefits. Their argument is nothing but FUD.

  93. Re:Why Linux sucks by josh+crawley · · Score: 3, Interesting

    >Linux is slower and less stable than windows

    Which versions? Are you using standard (good) hardware or POS rummage stuffs?

    >My windows box uses about 40 megs of ram to boot, Linux uses about 175 (and
    Linux is a monolithic kernel)

    I'm using 172 MB of memory (with all the nicieties ON). And about that "Monolithic kernel crap"..

    modprobe idiot_slashdot_poster IQ=1

    >Linux crashes much more often than windows, way more

    How so? Windows freezes much more on me. Even hangs during INSTALL. I've never seen Linux hang like that.

    >The few Apache/MySQL vs IIS/MS SQL tests I have seen have been won (sometimes dominated by) Windows

    I dont care about those tests... However, I do remember some test that had really crappy hardware for Linux and a quad proc with Win. Wonder what won that...

    X is a one size fits all poor implementation at a responsive display server (both Apple and MS are moving to hardware accelerated GUI) ...If you're running a 486.

    >KDE is maybe the only thing on earth more intigrated than windows explorer, everything under the sun imbeded into konqueror, it makes it clunky as hell, Nautalus is nearly as bad

    Damn straight. It crashes a lot over stupid stuff, and it does hog memory. Still, after it crashes It works OK.

    >Ease of use for the newbie is not as important as ergonomics for powerusers, but Linux has yet to bring an environment to the table that I can efficiently get work done it.

    If you like Windows interface, go use FVWM95. I'll stick to using KDE and Wmaker.

    >WinXP Pro comes with a 480 meg CD, Mandrake is 3 CD's and SuSE is 7

    That's all apps you can use. Only thing I need to download is a DVD/AVI app. Windows comes with garbage (MSNMessenger vs. Gaim , IE vs. Moz, Paint vs. Gimp, nothing vs GCC suite).

    >NTFS is much more stable than any Linux file system, hard shut down in Linux and watch it fsck your box

    Permissions on WinNT are much nicer to deal with. Still, XFS and Reiser are really good for Linux. Only a second or 2 to "check disk".

    >Installing software on a Linux system is badly broken, often you end up fixing make files, chasing dependencies, or in situations where you can't update a library with out breaking other apps, many libraries are not very backwards compatable and someone still has yet to write an installer for Linux. Nullsofts SperPiMP installer for windows is only 498K but such a simple installer has yet to exist for Linux because it's design is funamentally flawed.
    Even windows 3.11 had an installer and you can install the 32 bit libraries for it and still run binaries that were compiled on XP, lets see Linux do that

    Creators dont care to package a nice installer like the one Loki used in UT install. Still, if you compile static LIBS inside your binaries, thye'll run on nearly any Linux X86 platform (if that's the arch you compiled them for). RPM's are OK, but you have different companies repackaging them and breaking them. Still, the best is AUTOCONF ./configure . It ckecks for everything you need on your system and errors if you dont have it.

    >Developers will often use GPL just so they can avoid having to create and test seperate packages for the last 3 versionsof every major distro, GPL lets someone else do it.

    Yep. Essentially they are lazy in a certain regard. If you'd undertsand, they make the app for themselves alone. If somebody else wants it, try it out. If it doesnt work (and you want it), you fix it and submit patches. That's part of the cost of using Linux stuff. It doesnt cost money... Just time.

    >The exists no development environment more compelling than gcc and emacs, for this reason Linux apps will always be behind

    QTdesigner, INTEL's cc, KDevelop... I'd say they're "nice". Still, that's a simple bitch comment.

    >Would like feedback on this
    >Thanks

  94. What do you find more frightening? by Anonymous Coward · · Score: 0

    Like the subject line says, what do you find more frightening?

    - NSA controlling you

    or

    - MS controlling NSA

  95. Biased article? by jpmorgan · · Score: 3, Insightful

    I have a problem with this statement:

    Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies, and thus hurting American business.

    This is pretty biased. Shouldn't it be more like 'Many complaints criticized the agency for providing the fruits of research to only free software developers, not to all software developers and companies, thus hurting American business.'

    How would developing the security extensions in the public domain, or under a BSDish license keep them from being used by 'everyone'? Putting then in Linux (and consequently having them been covered by the GPL) does a much better job of keeping 'everyone' from using them than a more free license like BSD.

    If the NSA were going to do something like this, they should have based it on one of the BSDs instead. By developing the extensions in Linux, they effectively made them useful only to Linux - putting them beyond reach of countless software companies. Of course, this has been the software industry's complaint to government funded research producing GPLed software from the start.

  96. I remember when there was a USA by gelfling · · Score: 3, Funny

    Yeah back in the early part of the century before Redmond bought the rights to everything that ever had been or ever will be invented, thought of, spoken, typed, glyphed or otherwise ideated or communicated in any living or non living mode. Then they put a EULA on the Declaration of Independence and the Constitution and made people pony up dollars if they wanted to be a legitimate licencee of Freedom and Democracy. Everyone else was sent to the Gulags "to protect them from themselves and to insure that the bona owners were not stolen from."

    Then they added a new ammendment to the Contitution EULA that effectively invalidated the 13, 14, 15 ammendments of the old Constitution and made it legal for software companies (MS because by then there was only one) to literally own people and make them buy software whether they wanted to or not. Debtor's prisons came back online after over 200 years. The shortway around that was to simply become the nation and hire the entire country as cadres of MS employees. Everyone became a 'limited use MS employee licencee'.

    Around 2014 was when DoubleplusXXXP+# was running the food distribution complex in east central Billtania (formerly called the "Midwest") and a major BSOD glitch caused 65 million people to starve to death. In order to make up market share MS tripled the food EULA charges on the survivors and then cut their wages by 30%. Which is when the mass suicides and infanticides began.

    In 2018 Bill proclaimed himself God-Man and licenced the air we breathe now.

  97. And you'd like to replace that... by dave-fu · · Score: 3, Insightful

    ...with a few thousand unpatched Linux boxes? There's no magic bullet that suddenly makes a given server safe for eternity out there, now or ever. As the lifetime of a server unpatched and unmanaged (as all these hypothetical NT4 boxes in your example are) reaches infinity, you can be damned sure that the probability that ANY box gets rooted out reaches 100% as well.
    Or will running SELinux and forgetting about those patches be different from running NT4 and forgetting to run well-publicized best practices checklists?

    --
    Easy does it!
    This comment has been submitted already, 276865 hours , 59 minutes ago. No need to try again.
    1. Re:And you'd like to replace that... by rweir · · Score: 1

      Well, there is one solution:

      while true;do apt-get update && apt-get -fuy upgrade;sleep 24h;done

      Works for me;)

  98. Re: Liberal Groupthink by mi · · Score: 0, Flamebait
    Government's role is to promote the welfare of the people.

    No. Not at all... People themselves are much better at that, governments need not bother. Keep this sort of ideas to your socialist conventions...

    --
    In Soviet Washington the swamp drains you.
  99. Does this mean by outriding9800 · · Score: 1

    that the NSA will also stop helping M$ with securing thier own produts ?? http://nsa1.www.conxion.com/

  100. USA export regulations by yerricde · · Score: 3, Informative

    Well, the U.S. government does place restrictions on one's right to give software away (in the case of strong cryptography). Hence OpenBSD is based in Canada.

    But do these U.S. export restrictions apply to free software? The current crypto export regulations (section 740.13(e)) seem to grant an export License Exception for publicly available source code and object code compiled from publicly available source code provided that the original publisher of such code notifies crypt@bis.doc.gov (cc: enc@ncsc.mil) of the code's public availability. (Notification seems not to be required for mirrors.)

    Hence Mozilla is based in the United States, where the only restriction on exporting OSI Certified(tm) open source encryption software is that it not implement a system primarily designed to restrict the fair use of a copyrighted work.

    --
    Will I retire or break 10K?
    1. Re:USA export regulations by paladin_tom · · Score: 1

      However, these regulations also state the following:

      (4) Country restrictions. You may not knowingly export or reexport source code, corresponding object code or products developed with this source code to Cuba, Iran, Iraq, Libya, North Korea, Sudan or Syria.

      If you post it on the net, then there's nothing stopping these countries from getting the code. Hence, doesn't that put one in murky legal waters?

      --
      #define sig "Every social system runs on the people's belief in it."
  101. We the People by drivers · · Score: 3, Informative
    Funny, I thought that government (established by the people) was the means by which people promoted their welfare.


    We the people of the United States, in order to form a more perfect union, establish justice, insure domestic tranquility, provide for the common defense, promote the general welfare, and secure the blessings of liberty to ourselves and our posterity, do ordain and establish this Constitution for the United States of America.

    1. Re:We the People by smithmc · · Score: 1

      Funny, I thought that government (established by the people) was the means by which people promoted their welfare.

      Which "people"? And at the expense of which other "people"? The government has no business promoting the welfare of some people at the expense of others. This just as true for the consumer as it is for the producer, the rich as well as the poor, the privileged as well as the disadvantaged. The government's job is to promote the welfare of all people, and the services which government can provide that fit that criterion are fairly limited: defense, police, courts, etc. One could conceivably argue for roads, schools, rails, etc. But there's no way it means "protecting big business against competition from free software".

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    2. Re:We the People by drivers · · Score: 2

      You spout your Randroid nonsense as if it were gospel.

    3. Re:We the People by Anonymous Coward · · Score: 0

      You spout your collectivist claptrap as if it were gospel...

    4. Re:We the People by smithmc · · Score: 1

      You spout your Randroid nonsense as if it were gospel.

      You spout your "Randroid nonsense" nonsense as if it were gospel. If I were this "Randroid" of which you speak, would I be saying that big business should not be protected against free software, you 'tard?

      --
      Downmodding is the refuge of the weak. Don't downmod, make a better argument!
    5. Re:We the People by 1010011010 · · Score: 1


      Actually, yeah, I think Rand would have a lot bigger problem with Microsoft than with GNU, as the last thing Microsoft actually wants is a free market. Microsoft's isn't very capitalist (as Rand saw it).

      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    6. Re:We the People by drivers · · Score: 2

      The "Randroid" part was referring to the part where you said government can do x, y, and z, not a, b, and c as if that was the only valid political opinion. Presumably that means that the government shouldn't be using our tax money to develop free software. However you previously stated (as you pointed out) that big business should not be protected against free software. The question is, does this mean you are for or against the NSA writing free software which "competes" with Microsoft?

    7. Re:We the People by mi · · Score: 2

      You answered yourself...

      ... the means by which people promoted their welfare.
      ...

      We the people...

      Damn it!..

      --
      In Soviet Washington the swamp drains you.
  102. A non issue really if you are outside America by miffo.swe · · Score: 2

    If you look at the speed GNU/Linux is picking up in China and other countries in other parts of the world Microsoft can be seeng themselves outpaced by various distributions. Microsoft will find themselves fighting to many wars instead of making their own crappy OS workable.

    Sure they can lobby and buy votes in congress but its harder to do it abroad. SElinux wasnt used that much and wasnt a fullblown ready to go distro but rather a concept. There are plenty of highly secure distros out there but one fact remain. Almost any distro can be secure if it has a good sysadmin. The same cannot be said about Windows where the sysadmin and his server is in the hands of someone else.

    --
    HTTP/1.1 400
  103. Not the whole story.... by giminy · · Score: 5, Interesting

    I sort of work on SE Linux. Our group is unsponsored by the NSA (thus far). Since we are unofficially working on it, though, we hear birds chatter sometimes. The rumor mill around our office has been saying that it is not the case that Microsoft has done anything. What happened? A party, whose name shan't be mentioned, because we have not been told their name (we shall call them the Party), was given an SE Linux contract by the NSA. The NSA it seems didn't understand the GPL so well (or some lawyer of theirs who hammered out the contract didn't). The NSA contract said that the Party working on the contract could have propietary code, and could patent ideas used to achieve goals on the project. Much work was done on SE Linux in the mean time by the Party, but patents/etc are held on certain parts of the code by the Party, and therefore cannot be released under GPL. The quotes you see in this article heading make perfect sense to me in this context. The NSA didn't understand the GPL. And yeah, I would complain too if I couldn't have the complete source to my kernel...

    Yes I hate Microsoft, but this article is kind of ridiculous...it uses some vague quote to make microsoft look bad. This is not the way to win the war.

    --
    The Right Reverend K. Reid Wightman,
    1. Re:Not the whole story.... by ozbird · · Score: 2

      The current version of SE Linux appears quite up to date (2.4.18-based) - has official development stopped now? An official statement from NSA on the status of the project would be useful.

      If work has stopped, or there are serious legal issues over the existing codebase, it sounds like a good reason for a code fork - take the known good GPL code and run with it and stay clear of any "patented" bits.

    2. Re:Not the whole story.... by Malcontent · · Score: 2

      Who moderated this up so high? Where is the evidence? Who is this "party"? DO you really expect everybody here to believe that the NSA is incapable of understanding the GPL? Are you really saying that the NSA employs no lawyers or that their lawyers are insanely stupid?

      Put up or shut up. Spill the evidence if you have any any.

      --

      War is necrophilia.

    3. Re:Not the whole story.... by giminy · · Score: 2

      No, I don't expect everybody to believe it. But by the same token people should not believe that Microsoft coerced the NSA into dropping SE Linux. There's no proof in the main article, just a vague quote attached to an unrelated story. I cannot supply the party's name because we don't know, the NSA never told us. I imagine it is the NSA's nature not to reveal who is working on what so that people don't bother the groups working on a particular contract directly. Ideas should be going to the NSA who will then filter them down to their contracted groups.

      I too used to think the NSA was always up to no good and was corrupt, focusing mainly on spying on US citizens, but reading a little history of what they've done has shown me otherwise (though I still enjoy movies like Conspiracy Theory ;-)). I do truly believe they have the public's best interests in mind vis-a-vis SE Linux. Assuming microsoft tried to leverage them into using windows as their secure OS: well that might work okay for the NSA (of course the NSA would be given the code in this case), but it does little to appease the public. Who would trust NSA-Windows if they couldn't have the source code? I doubt Microsoft will allow the NSA to release the code to any hardened operating system they release. The SE Linux project was started, if you'll recall, to create a publically usable trusted operating system.

      Using GPL (or another "free" as in source license) is really the only thing that makes sense.

      And as for the question about the NSA's lawyers, I am simply saying that it is possible for one of their lawyers to make an error in foresight (a "mistake"). The NSA is interested in securing data, and I would imagine they have lawyers on hand mulling over legal matters with respect to securing data. It's possible one of them drafted the contract for working on SE Linux (see previous statement regarding non-disclosure of who "party" is. The more outside people involved in a contract, the higher the likelihood a mistake will be made and "party" will be revealed).

      Anyway, I admit that I cannot provide said "proof." Neither can this story. If I were reading this article and this particular message thread, I would probably believe neither. But given what I have heard, I definitely do not believe Microsoft had anything to do with stopped development on SE Linux.

      --
      The Right Reverend K. Reid Wightman,
    4. Re:Not the whole story.... by Anonymous Coward · · Score: 0

      "Yes I hate Microsoft, but this article is kind of ridiculous...it uses some vague quote to make microsoft look bad. This is not the way to win the war. "

      Hear hear. Microsoft does not require help to look bad. Fake look bad can be exposed, leading to an impression of implied look good. Doesn't logically follow, but impression over reality. Ugly enough facts on a lot of fronts, things that MS can try to spin but can't explode. Show their spinning tops for what they are, better than a battle of the spinning tops.

    5. Re:Not the whole story.... by Malcontent · · Score: 2

      Three things.

      1) You don't know who this party is and therefore it could very well be Microsoft.

      2) The NSA is like most other govt agencies in that it employs and contracts with an army of lawyers. There is zero percent probability that every single lawyer for the NSA is somehow only knowledgable about security.

      3) The GPL is a very simple document as far as legal documents go. I can read it and understand it and so can millions of laymen all across the world. Not only that there have been countless articles written about it in all kinds of forums. If you spent a half a day searching on google you would know the GPL inside out. Despite this you keep asserting that real life lawyers working for one of the most elite govt agencies in the world are simply unable to read or interpret this simple document. Not only that but they are so ignorant that they are unable to do searches on google and read about other people's analysis of the GPL on the internet. The lawyer(s) assigned to the task of studying this simple document are lazy, incompetent, and illeterate right?

      --

      War is necrophilia.

    6. Re:Not the whole story.... by giminy · · Score: 2

      1) You don't know who this party is and therefore it could very well be Microsoft.

      2) The NSA is like most other govt agencies in that it employs and contracts with an army of lawyers. There is zero percent probability that every single lawyer for the NSA is somehow only knowledgable about security.

      3) The GPL is a very simple document as far as legal documents go. I can read it and understand it and so can millions of laymen all across the world. Not only that there have been countless articles written about it in all kinds of forums. If you spent a half a day searching on google you would know the GPL inside out. Despite this you keep asserting that real life lawyers working for one of the most elite govt agencies in the world are simply unable to read or interpret this simple document. Not only that but they are so ignorant that they are unable to do searches on google and read about other people's analysis of the GPL on the internet. The lawyer(s) assigned to the task of studying this simple document are lazy, incompetent, and illeterate right?


      1) Probably not microsoft. You have no proof of this. See your own comments on subject of proof before throwing out wild accusations. Also, I doubt Microsoft won a contract to develop SE Linux, though I suppose anything is possible.

      2) "'We didn't fully understand the consequences of releasing software under the GPL (General Public License),' said Dick Schafer, deputy director of the NSA.

      3) See point 2.

      --
      The Right Reverend K. Reid Wightman,
    7. Re:Not the whole story.... by Anonymous Coward · · Score: 0

      Hey frickin' moron--
      How about doing a little research before you
      post about the subject? Giminy was right--
      Secure Computing Corporation used some of
      their "Type Enforcement" code in this, which
      is TM/Copyright/Patented/Proprietary/NotToBe
      GivenAw ay...and then NSA released the code.

      Secure Computing was officially Not Happy.
      I don't think that Microsoft was either...but
      Secure Computing are the ones with their panties
      really in a wad.

      --Someone who should know better than to post
      to Slashdot.

  104. Re:Should the Government Compete w/ Private Indust by Skjellifetti · · Score: 1

    No, if the gov't requires the GPLing of proprietary enhancements, that would be theft of the enhancement, something forbidden by the US Constitution which requires that the gov't pay for any private property taken for a public purpose.

    And I live in the Midwest, so I haven't a clue how things are in Redmond. When you grow up you will realize that even the worst villians occasionally have something useful to say.

  105. Mandatory Access Control (MAC) by Josh · · Score: 3, Insightful

    The distinction between MAC (mostly used by the military) and Discretionary Access Control (the common form in most OSs) is classical in the security literature. SELinux was primarily an attempt to produce a MAC system our of a free resource, Linux, that is highly usable, works on cheap hardware, runs lots of applications, and could do many functions for the government. Microsoft, to the best of my knowledge, doesn't even offer an OS with MAC capabilities. That the NSA would be cowed by Microsoft nonsense out of continuing development on a worthwhile project that could save the government hundreds of millions of dollars is absurd and criminally stupid.

  106. They are doing all wrong... by Anonymous Coward · · Score: 1, Interesting

    The NSA goofed from the very beginning by trying to implement SELinux themselves.

    Lets take a look at the main complaint about the NSA working on SE Linux.

    "NSA's releasing open-source software would compete with American proprietary software"

    So put the work in the hands of the American companies! A very simple solution would be to contract the work out to a private company like all other government work that needs to get done. The goverment doesn't design aircraft, they pay boeing and lockheed martin to do it. So why should they program a secure OS? They shouldn't! Pay someone else to. Define a set of requirements (If linux is one of them is irrelevant) and put the contract out for bid. This way, any company, including M$, has a chance to make money of the contract. So how government funds being put in private industry is hurting "American proprietary software" is beyond me.

    1. Re:They are doing all wrong... by mpe · · Score: 2

      The goverment doesn't design aircraft, they pay boeing and lockheed martin to do it. So why should they program a secure OS?

      Not quite the same thing, since an aircraft is a physical machine which requires complex specialist manufacturing facilities

      They shouldn't! Pay someone else to.

      So governments should have a policy of paying private corporations, with tax payers money, even if they could do the work more cleaply themselves? Why not just have a "corporate support tax"?

  107. You are DEEPLY in error by Jeremiah+Cornelius · · Score: 2
    Both the Preamble and Article I, Section 8 of the Constitution call upon the federal government to "promote the general welfare." By extension, "we the people" are urged to promote the general welfare as well.

    We may disagree as to what the general welfare requires, but the framers intended that we accept this principle as being essential to the preservation of freedom.

    --
    "Flyin' in just a sweet place,
    Never been known to fail..."
  108. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    >Which versions? Are you using standard (good) hardware or POS rummage stuffs?

    Yes, but Windows was fast on the bad hardware too

    >I'm using 172 MB of memory (with all the nicieties ON). And about that "Monolithic kernel crap"..

    Even when I am multitasking on windows I don't use 172 MB of RAM, one of the major advantages of Monolithic systems is that they are "faster and use less RAM" so Linux even with that advantage is still lacking. Microkernel designs are much more robust and stable, in windows, close everything out, then go to task manager and kill explorer.exe, then go the apps tab and select a new task and run explorer again. Only on a microkernel can this be done and have the system remain stable.

    >modprobe idiot_slashdot_poster IQ=1

    Drivers are something I forgot to cover, again much easier write and install on a microkernel system, thanks.

    >How so? Windows freezes much more on me. Even hangs during INSTALL. I've never seen Linux hang like that.

    I think this is up for debate only by the people that do not use Linux. I've used multiple versions of multiple distro, 2K and XP crash _much_ less (if ever). I am not making this up.

    >X only sucks if you're running a 486.

    I'm not

    >KDE crashing.. Damn straight. It crashes a lot over stupid stuff, and it does hog memory. Still, after it crashes It works OK.

    Reiteration of my above point on stability.

  109. Don't trust GWU - (MOD ME UP.) by Anonymous Coward · · Score: 0

    I don't think I'd bet anything on GW's ability to create something our country must rely and depend on.

    I mean, c'mon, the head of this "Cyberspace Policy Institute", Director Martin, was part of NASA's successful Apollo 13 mission.

    Plus the school is a money hungry, special interest serving beast.

    What do you expect from a school who's core CompSci curriculum is based on the Ada 95 programming language?


    ChopSuey

  110. It's the applications, stupid by Animats · · Score: 4, Informative
    Most of you miss the point about SELinux. It's not an attempt to build something NSA would consider a secure system. It's a prototype on which apps can be written which might, someday, run on a system with mandatory security policies.

    Writing server-type apps to live within the constraints of a mandatory access policy is tough. (Look at how much crap runs as root because people can't make it live within the UNIX permission structure, which is far less restrictive.) But it's the only approach that works, because the applications aren't trusted.

    If you want to help, make some major application, like a mail program, work under SELinux, with as little trusted code as possible. Somebody was doing this for an FTP server, but those are of limited use. A mail server on SELinux would actually be useful.

  111. US interests by Target+Drone · · Score: 2
    From the article: Many complaints criticized the agency for providing the fruits of research to everyone, not just U.S. companies...

    I know the US government is here to serve US interest and all but whatever happened to doing things for the betterment of mankind.

    Perhaps I'm being too idealistic.

  112. Uhhh -- Conterexample! by Codex+The+Sloth · · Score: 2

    Two words: Post Office.

    Next topic?

    --
    I am not a number! I am a man! And don't you ... oh wait, I'm #93427. Ha ha! In your face #93428!
  113. Doesn't matter by Anonymous Coward · · Score: 0

    It doesn't matter if someone is light-years "ahead"..

    If it's for all the wrong reasons. It will change again, as everything does.

  114. No, the givt should fund "basic" research by Ars-Fartsica · · Score: 2

    There are substantial research projects that consist of basic sciences, social sciences, and the humanities that do play a role in the public good. I don't a problem with the government funding basic research. Product development is another issue.

  115. Re:That's scary - NOT by EQ · · Score: 3, Informative
    because it's illegal for the NSA to spy on Americans doesn't mean they don't...

    Having worked there, I can tell you this: intercepting a US person is a SERIOUS infraction. Its not something you can do without running afoul of a lot of laws. The abuse done by the NSA during the Nixon years caused a lot of severe curbs (both open and classified) to be placed on the NSA, and those laws have serious teeth that will bite anyone violating them. As with the armed forces, there are a lot of very liberty minded folks working there to preserve your freedoms at the cost of their own. One example is that free speech is very limited once you hold certain accesses and clearances.

    IMHO, you're in more danger from those folks at the FBI.

    You really ought to do a seach on "USSID 18". I cant say anything confirming or denying, but there are some very interesting things that have been declassified out of Big Daddy DIRNSA's pockets.

    Secondarily, its NSA/CSS. Ever hear of the CSS side of the house? I suggest you look it up before posting obvious biased off-base stuff thats based on a hokey movie [sneakers].
    --
    Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo! http://goo.gl/J9bkO
  116. Foreign access to SELinux by ericman31 · · Score: 3, Interesting

    I think the line about anyone having access is telling, but not in the way many people seem to be taking it. The NSA isn't concerned with US citizens having access to SELinux, although I'm sure that some people within the NSA are. They are concerned that security technology developed by the NSA will be made available to other countries. The NSA is fighting the tide of knowledge. The Soviet Union used to do this, to an even more dramatic extent than our government does. Anything mailed or published outside the USSR was subject to censorship. Soviet scientists used to get around this in interesting ways. For example, a physics paper was published that started "Imagine the interior of a star .... ". The censor immediately decided that there was nothing of interest militarily and passed the paper through for publishing in Western Europe. The star described could not possibly exist, it was actually describing a third stage thermo-nuclear explosion and gave Western physicists insight into the sophistication of Soviet nuclear weapons technology.

    Information and knowledge cannot be prevented from spreading, as the Catholic Church in the middle ages learned, as the Soviet Union learned, and as the NSA keeps trying to forget.

    --
    In my universe I'm perfectly normal, it's not my fault you don't live in my universe.
  117. Re:Should the Government Compete w/ Private Indust by Anonymous Coward · · Score: 0

    With the GPL there is no such thing has proprietary enhancements. Don't you get it? If the tax payers pay for something a company can't just take it enhance it and make money off it without contributing back.

    I don't want my tax dollars spent to make someone a millionare.

  118. Get a clue about how research is funded by Genus+Marmota · · Score: 2, Insightful

    It is the goverment's job to see where the goverment needs something (that may not even be useful to anyone else), and supply money to get the need filled quickly. Any other research is for universities, and should be public domain.
    Man, you need to get a clue about how research is actually funded at universities in the US and who "owns" the results. At the department where I worked it went something like this:
    • Famous scientist solicits 10s of millions of $$s from a variety of sources including government (NIH, DOE) & industry. This process is incredibly political WRT who the govt does and does not fund, academic dominance struggles, backbiting, etc.
    • University takes half off the top.
    • Scientists in department also get their own grants, frequently from industry, with all sorts of strings attached.
    • Enormous pressure on all involved to come up with "commercial" IP.
    • Stuff is developed.
    • Furious battles among researchers - who owns how much of what - as industry & VC gathers round. University is heavily involved through "Office of Technology Transfer" (from Regan era mandate forcing recipients of public funds to actively seek ways of transferring IP to private sector).
    • Startups are formed and/or patents "transferred" (some might say given away). Everyone who can keeps a percentage (stock, rights) including University, but usually not including postdocs, lab techs, anyone other than principal investigators whether or not they were really important to the work.
    • The public gets the publications (which is to be fair the most important thing)but precious little of the technology (actual HOWTO and rights to do so)
  119. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  120. Microsoft undermines national security by Angst+Badger · · Score: 3, Interesting

    So let me get this right: the National Security Agency develops a port of Linux to augment, unsurprisingly, national security. Microsoft bitches that national security runs counter to their profit interests and manages to get SE Linux terminated.

    Fine.

    But let's be sure to mention this next time Osama bin Ballmer starts foaming at the mouth about how Linux is un-American, and remind him that Linux developers have never undermined the safety of American citizens in order to line their pockets.

    And while we're at it, let's consider what gigantic software monopoly distributes a flight simulator capable of accurately emulating passenger airliners, along with detailed scenery of American airports and major urban centers, complete with individual office towers.

    Of course, having already crippled Naval warships, I shouldn't be surprised that Microsoft is now trying to cripple our chief intelligence agency.

    --
    Proud member of the Weirdo-American community.
    1. Re:Microsoft undermines national security by lunchlady+doris · · Score: 1

      "And while we're at it, let's consider what gigantic software monopoly distributes a flight simulator capable of accurately emulating passenger airliners, along with detailed scenery of American airports and major urban centers, complete with individual office towers."

      Oh come on! You want to imply that Microsoft should shoulder some of the blame for what some zealots did because their game is accurate? That is completely preposterous. I am not a fan of the pigopolists over in Redmod either, but this statement is just a knee-jerk reaction spouted with no logical consideration.

    2. Re:Microsoft undermines national security by mpe · · Score: 2

      So let me get this right: the National Security Agency develops a port of Linux to augment, unsurprisingly, national security. Microsoft bitches that national security runs counter to their profit interests and manages to get SE Linux terminated.

      Whilst the US Constitution defends Microsoft's right to bitch as much as they like it dosn't oblige anyone, including the US government, to take any notice of them at all.

      But let's be sure to mention this next time Osama bin Ballmer starts foaming at the mouth about how Linux is un-American, and remind him that Linux developers have never undermined the safety of American citizens in order to line their pockets.

      If anything the GPL has more in common with the US Constitution than anything Microsoft has ever come up with.

      And while we're at it, let's consider what gigantic software monopoly distributes a flight simulator capable of accurately emulating passenger airliners, along with detailed scenery of American airports and major urban centers, complete with individual office towers.

      At least one news media demonstrated using this software as a means of training people to crash airliners in to specific buildings.

      Of course, having already crippled Naval warships, I shouldn't be surprised that Microsoft is now trying to cripple our chief intelligence agency.

      It appears that the way Microsoft operates makes it difficult for them to produce software well suited for government work. By the time people get to know the software well enough to seriously consider starting using it Microsoft is likely to have stopped making it available. That for the majority of governments they are a foreign corporation is another point against them.

  121. Who is Dick Shafer by Anonymous Coward · · Score: 1, Interesting

    Somebody should call the NSA's Public Affairs Office and ask for Dick Shafer, because I've never heard of the guy, and I wonder if he was made up. And if not, PAO should have cleared him to make that statement - which definitely doesn't sound like bureaucrat-ease.

  122. Is the last one? by Anonymous Coward · · Score: 0

    Is the last one sentence a question or an interjection?
    -James

  123. Don't use this consulting company by mgibbs · · Score: 1, Insightful
    From the article:

    Mark Westerman, managing partner with network consultant Westcam, installed the SE Linux access controls on a critical server for one of his customers after a common security flaw, known as a buffer overflow, allowed a hacker to take control of the company's server. Westerman configured the access rules but left the buffer overflow unpatched on the server as a test.

    When the hacker came back a second time to the server and attempted to gain control of the process, the access controls limited what the attacker could do. Instead of taking control of the computer, the hacker could only crash the service that had the buffer overflow, but did no other damage.

    That's all well and good, but if I were a Westcam customer, I don't think I would want a critical server left unpatched "as a test".

  124. Re:Why Linux sucks by dclifton · · Score: 2, Informative

    I've run Linux since 1993 when there were no distributions. I ran it on a 386 / 16 with 8Megs of memory. I've run almost every version since and I have yet to have any lockups / crashes. Either you have no idea how to install the OS or you are forcing the software to load into improper directories so that the system crashes when it is trying to run. Currently I'm running Mandrake 8.0 on a Pentium 100MHZ PC with 60 Megs memory and it hasn;t crashed in over six months. Personnaly, if I could run it at work, I'd delete every copy of windows I have and only run Linux.

  125. Re:Why Linux sucks by headmonster · · Score: 2, Interesting

    I can't agree with your experiences on stability. In fact, I trust my Linux boxes more than anything with Winx on it. In my experience, the only reason our Winx boxes don't crash once or more per month is that we've adopted a strategy of rebooting them once per week so they don't "eat themselves". (A hard learned lesson. Maybe exagerated _a little_.)

    That only addresses the server side of things though.

    I agree on software installation - there are a lot of problems, mostly stemming from the lack of a strong, unified configuration. That is, everybody seems to have their own version of how a Linux (or unix in general) box should go together - and so the configuration options are too broad for a strong standard to emerge. MHO. Even Red Hat's RPM fails to solve the problem a lot of the time (my experience)...

    I recently launched a RH7.3 server for MySQL & Resin (JSP Application Developmet). Everything from the CD went well - and then I needed to add Java. Got the RPM from Sun, and wouldn't you know it - the install went great.

    (The other shoe drops here)

    ...but the program (java) wouldn't run - let alone the fact that I have to manually hack all of the environment varialbes. I thought that maybe this was ahead of the curve (using 1.4 instead of 1.3 on the CDs). I Turned back to the 1.3 version on the CD's - that failed too in precisely the same way.

    As it turns out Java needed another package installed before it would work - a dependency - precisely what RPM is supposed to solve. After 3 days w/ tech support (sometimes it just doesn't go well) I got the answer on the package that needed to be there - I found it on the CD, installed it manually, and that problem was solved.

    This is an example of something that should have been very simple, but became extraordinarly complex - from cryptic error messages and difficult technical support calls to locating installation packages to manual environment configuration etc... A less technical user would have been in real trouble.

    An executive comparing that to the one-button install on a Winx machine doesn't take long to decide it's a better business decision to "stick with what works".

    On the point of a user environment/desktop. There again, I have to agree. Every couple of months I pull out the latest RH version, wipe a machine, and try to build a user workstation that I could throw at my user base for business, software development, or even webware work... Every time so far it's a disaster - there are too many tools missing and the tools that do exist have steep learning curves.

    On the point of learning curves, there's another core problem here I think - a cultural one. The *nix crowd in general seems to have a built in right of passage. You either know all of the right buzzwords, techniques, tools, and utilities, or it's your own fault that you haven't figured it out yet. (RTFM!)

    It's difficult to describe - but I'll bet anyone who's tried to use *nix has had the experience:

    You find yourself staring at a problem that should be simple to solve, but everything about it is inpenetrable - you don't even know what questions to ask... - or when abruptly reminded RTFM - which FM to F' READ...

    ...then, if you're lucky, you will stumble across some *nix guru who will press a few obscure keys and solve the problem instantly (thus is the power of *nix) - Even if they were nice about it and tried to teach you, and even if you took copious notes - this little tid-bit is probably not much more help than wrote instructions - and if you loose them, or forget them some day, you're just as lost as if you'd never had the help.

    Even the simple things are maddening. Take the vi / emacs debate - then, prompty forget about it because it completely misses the point. For the typical computer user, in a world where every editor you can find works just about like Notepad (even edit on a DOS prompt works this way for the most part) - vi and emacs are useless and inaccessible.

    The newbie can't begin to gain access to a *nix system. What we (people who want Linux to succeed) have to do is realize that in it's most profound terms.

    In most of the companies in the world using computers, the guy that has to make it all work isn't a well trained technician or engineer, or even a hobbiest. He's the poor schmuck who figured out how to modify autoexec.bat with his trusty text editor - the token computer geek in the office - and through his continuing experiences he may eventually become a well trained technician... but today he can get by with a few simple tweaks and keep the wheels moving. This is just not so in the Linux world right now.

    Show of hands: How many of you know why the following expression is a bad idea:

    [ /] rm -rf *

    The short of it is that I think *nix in general, and by extension Linux, is structured so that the learning curve is far too high for casual entry.

    Once you get past the learning curve enough to be somewhat effective, you no longer have the time or energy it would take to bring the next fellow along - and so they will struggle as you have, or they won't "join the club".

    I think it likley that until the Linux community solves this entry problem the barriers to solving usability, installation, and integration problems will remain unsolved.

    What's needed is a workable environment that doesn't require a deep knowlegde, but does not preclude the benefits of that deep knowledge. A way for the novice to get their work done on their way to becoming a whiz...

    Typically those in the open source development community that have the skills to solve these problems are busy with other things - and in any case there's little strong direction as to what the details of such an environment should be...

    The challenge is going to be defining that goal and motivating the developer community to achieve it.

    The first part is hard because the very people who can help to define that goal are kept out of the community by the entry barriers - and therefore don't get into the conversation.

    The second part is hard because it is the nature of the development community (generally) to solve local problems and then share those solutions - rather than coming together to collectively solve a central problem they don't personally have. (Is that where RTFM comes from?!)

    Think of it this way... If I have to make my mail server or database work properly, and I can fix the open source code to solve that problem - then I can do that and keep my job - it's all part of the work I've got to do. When I'm done, that work is now available for everyone. By extension, the most common problems will be solved and overall the open source software will be extremely reliable for the majority of people most of the time.

    Try to apply that to this problem: Basic users need a unified desktop and operating system with integrated applciations and a shallow learning curve. Now tell your boss that you're working on a suite of productivity apps and a one CD linux distribution that will slickly install and interoperate with the majority of the business world running Windows. I'll bet he will ask: "How's that going to get our database up?"

    The boss in this case might be the developer themselves. Best intentions, altruism, and grand visions not withstanding, it is not the open source developer's job to make everyone's desktop work and their installs go without a hitch - This is an advantage that the Microsoft developer has - it is their job and they get paid to do it. Similarly for the ISV/ISD - the potential for conflicts of interest are reduced significantly.

    The short way of saying this might be that the open source community, left to it's own devices, probably can't solve this problem.

    What's needed is an economically viable project that can focus the community on a unified vision, and specifically one that is strong enough, and compelling enough that the majority of the community will wish to participate.

    To work, this project would have to encoumpass a wide range - not only the operating system and it's environment, but also the applications that make that environment powerful - IDEs for all programming languages, Word processing and document publishing, Spreadsheet, Database, Presentation, Mulitimedia, Web & Email access, all of those applications will have to work together in a seamless way - and had better coexist nicely with Microsoft's products which, like it or not, set the standard due to market share.

    To date, I've seen some methodologies get close to supporting this kind of effort (a few good tries) - but nothing seems to have captured the critical mass necessary to generate this kind of focus.

    It's a thorny problem.

    I think we'ev seen some glimpses of what it _might_ be in the likes of MySQL, RedHat, Sun(java)... where there is a blend of open source and commercial licensing - sort of the best of both worlds. None of these seem to be perfected yet.

    Anybody have a solution?

  126. Re: Liberal Groupthink by Royster · · Score: 2

    Oh, so I'm a Socialist for asserting that promoting the welfare of the people is a legitimate role of government?

    I didn't advocate government ownership of industry.

    --
    I have discovered a truly marvelous sig, unfortunately the sig limit is too small to contain i
  127. GOOD by Anonymous Coward · · Score: 0

    The last thing we need is for the US Government to nationalize the software industry..

    Why don't you socialist maggots go read about the communist revolution and look what it leads to before you bash Microsoft.

  128. Bad info? by L0rdV4der · · Score: 3, Interesting

    Did anyone bother to check the info? This quote may be old, misquoted (or misinterpreted), or dead wrong.

    Dick Schafer is not the deputy director of the NSA. Per one of their press releases over two years ago, Bill Black is the Deputy Director:
    http://www.nsa.gov/releases/newddir_071000.html

    Also, SELinux was updated on July 3rd. Sounds like a bit of work for a dead project :-)
    http://www.nsa.gov/selinux/news.html

    --
    I am Me. No one else is Me, but Me. You are You. Get over it.
    1. Re:Bad info? by SwedishChef · · Score: 2

      There are several "Deputy Directors" of CIA and it would not surprise me at all if there were not several at NSA. This is the title given to the equivalent of "Vice-President".

      --
      No one ever had to evacuate a city because the solar panels broke!
  129. I don't think I am in error by 1010011010 · · Score: 2

    The founders intended for the federal government to be essentially what the libertarians say it should be. It enumerates specific powers granted to the federal government. Anything not covered by that enumeration, or one of the amendments, is not in the jurisdiction of the federal government. Please locate the constutitional authority for federal "welfare" programs such as social security and medicare.

    You and I can think "general welfare" means whatever we want for it to mean; but when it comes down to it, the constitution determines what powers the federal government actually, legitimately, has.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    1. Re:I don't think I am in error by 1010011010 · · Score: 2
      --
      Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
    2. Re:I don't think I am in error by gowen · · Score: 1
      But most constitutional scholars do not consider the Bill Of Rights to have been an attempt to provide an exhaustive list of the role and responsibilities of government. Allow me to quote "The West Wing" to you:

      Seaborn:In 1787, there was a sizable block of delegates who were initially opposed to the Bill of Rights. This is what a member of the Georgia delegation had to say by way of opposition; 'If we list a set of rights, some fools in the future are going to claim that people are entitled only to those rights enumerated and no others.'"

      Harrison: "Were you just calling me a fool, Mr. Seaborn?"

      Sam: "I wasn't calling you a fool, sir. The brand new state of Georgia was."
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  130. a sign of the times by merriam · · Score: 1
    "I don't think even United Linux has enough money to get Linux-certified."

    Linux-certified? I know technology and internet companies are short of funds these days, but I didn't know it was that bad.

  131. Re:Why Linux sucks by josh+crawley · · Score: 1

    >>Which versions? Are you using standard (good) hardware or POS rummage stuffs?

    >Yes, but Windows was fast on the bad hardware too

    I'll give you that one. Linux seems to find all those nasty hardware fuckups (on the bad hardware expessially)

    >>I'm using 172 MB of memory (with all the nicieties ON). And about that "Monolithic kernel crap"..

    >Even when I am multitasking on windows I don't use 172 MB of RAM, one of the major advantages of Monolithic systems is that they are "faster and use less RAM" so Linux even with that advantage is still lacking. Microkernel designs are much more robust and stable, in windows, close everything out, then go to task manager and kill explorer.exe, then go the apps tab and select a new task and run explorer again. Only on a microkernel can this be done and have the system remain stable.

    You mentioned something about mono kernals that doesnt quite fit Linux. Well, you can have a monolithic kernel with Linux... however about that ram usage. Linux buffers stuff into ram until it "needs" to write it. As an example (what runs me away from using Linux on public computers) is the floppy example. Take a 1 MB file and a clear floppy (Fat 16, right). Now mount the floppy in Linux and cp the file over to it. It "somehow" got done writing to it in less than a second (expessially when floppy write is about 8 KB/s). Instead the Linux kernnel cached the floppy in memory, so when you umount it, it does the rest of the writing. I see a good and bad points about this system...

    Good: YOU can cp a movie file (given enough ram) and edit iot on the other location. It's actually in memory, so your speed is greatly increased in editing. However, It's sort of a hack doing it that way, as if the computer fcrashes, you've lost your edit.

    Bad: Floppy example in a public setting. Some user makes a document and saves to a disk. They've been taught (by Windows) whgen green light is off, it's ok to remove disk. They now have lost all of the document. I could see a possible project in the floppy, or zip driver to make them more.. well idiot friendly. In the current way, though they work, but suck for regular users.

    >>modprobe idiot_slashdot_poster IQ=1

    >Drivers are something I forgot to cover, again much easier write and install on a microkernel system, thanks.

    True, so are the device lists in /dev . It's much easier to access /dev/dsp rather than to go through some Windows DLL for sound.

    >>How so? Windows freezes much more on me. Even hangs during INSTALL. I've never seen Linux hang like that.

    >I think this is up for debate only by the people that do not use Linux. I've used multiple versions of multiple distro, 2K and XP crash _much_ less (if ever). I am not making this up.

    Well, I've used all common versions of WIndows (3.1 up to Win2k) and many distro's of Linux. Usually the Win9x versions would hang on teh install in about a 1/4 chance. The NT versions are much better at that in about a 1/100 chance of hanging on install. Under standard installs (no apps) WIndows is very stable (both WinNT and Win9X). It's only when you start actually using the system, does it start to degrade. However, I'm guesssing that the half-life of a Windows installation is much less than the half-life of a Linux installation.

    With Linux, I've used Slackware, debian, Redhat, SuSE, and Mandrake. I dont like the way SuSE handles configurations in some sort of config DB. It likes to crap out Autoconf on many source .tar.gz's. RedHat is nice only if you like Gnome (I prefer KDE/WMaker). Debian users are usally too uppity to even glance at you if they're problems. Let alone that most of their packages are either "stable" (old crap) or apt-get doesnt even work (current or whatever). Mandrake hides all the problem solving stuff (or doesnt even have it at all). It prevents you from tamering with the system much. Then there's Slackware. I like it, but it's waaay too hard for the average Linux newbie. I download all my stuff in source and compile it. I've even considered adding to the RPM database with Slack so that you could add all the dependancies (now, all the dependancy lists aren't there - all must be forced). Still under no way, the installer has NEVER crapped out while installing packages. I've had problems with other things (unsupported/badly supported sound cards, graphics cards and modems). Network stuff usually just works.

    >>X only sucks if you're running a 486.

    >I'm not

    I've got quite a bit of modules to increase the quality of XWindows and (window manager). That includes GL, DRI, V4L, and a bunch of other modules. All that adds up, no matter what system you put it in. I'd rather have a video input that would go directly to the video card (through X11) through DGA.

    >>KDE crashing.. Damn straight. It crashes a lot over stupid stuff, and it does hog memory. Still, after it crashes It works OK.

    >Reiteration of my above point on stability.

    I know. ;-) Good points though.

  132. Not unpatriotic by Anonymous Coward · · Score: 0
    Just downright fucking stupid.

    The moron would rather believe Bill Gates.

  133. Your third point is wrong, and that's the problem. by Ungrounded+Lightning · · Score: 2

    Third - What the government produces, all competitors share equally...

    That's what's SUPPOSED to happen.

    But if the government enhances a GPLed product and releases the result, the enhancement comes under the GPL.

    So proprietary software vendors (like Microsoft) DON'T get to use the improvements - at least not verbatim. The improvements carry the Gnu Public Virus and can't be integrated into the vendor's code base without risking a suit from the FSF for GPL violation.

    Of course Microsoft cried "foul". They have a valid point. (How would YOU like it if the CIA spent a lot of YOUR tax money helping Microsoft fix up their software and wouldn't let YOU have the result?)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  134. Alternatives by Anonymous Coward · · Score: 0

    SELinux was based on patented technology and a hardware processor. http://dte.sourceforge.net is the one shown off at defcon, and there are other projects with other styles of access control schemes.

  135. Re:fp - CLAIMED! by Anonymous Coward · · Score: 0

    is CLIT a subgroup of TWAT? (The War Against Terrorism)

  136. Now we've done it... by SoSueMe · · Score: 3, Interesting

    We've /.ed "www.nsa.gov".
    At first I was surprised, but a Netcraft look-up explained it all.
    "The site www.nsa.gov is running Microsoft-IIS/5.0 on Windows 2000."

    That does NOT comfort me at all.

    1. Re:Now we've done it... by Vanguard(DC) · · Score: 0

      wowowowoowowowowowowowow...

      never thought to look... then again, it could be a faked banner...

      --
      "I think, therefore I get paid."
  137. NSA no longer working on linux? Right. by split+horizon · · Score: 1

    Do you guys really think the NSA has stopped working on SELinux? The NSA is one of the most powerful, secretive government agencies in the world; for years its very existence was classified. They operate covertly and answer to virtually no authority. They haven't stopped working on SELinux, they've just stopped giving out their work to the public. Why would they want a super-secure os to be in the hands of people they might want to spy on?

  138. Re:Should the Government Compete w/ Private Indust by Arandir · · Score: 2

    As a longtime BSD advocate, I must partly disagree. SELinux must be under the GPL, because it's based on GPLd software. The NSA can't arbitrarily change the license. As long as the choose to create derivative products from GPLd code, they must use the GPL. Besides which, public domain is incompatible with the GPL.

    p.s. On the other hand, the NSA getting involved in a hardened BSD OS would be awesome.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  139. Unidentifies sources are hardly proof by HiThere · · Score: 2

    I believe that MS is probably guilty, based purely on their past history. I can't consider that attributing "unidentified sources" for this conjecture adds much of anything to its trustworthyness.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  140. Open source, yes. GPL, no. by Courageous · · Score: 3, Insightful


    Having the U.S. government develop open source is just fine. We, the people, are the ones paying for the work, and the results of the work belong to us. However, having the U.S. government develop under the (full) GPL results in software which is restricted, and not available to everyone. The appropriate result of government work is really the PUBLIC DOMAIN.

    C//

    1. Re:Open source, yes. GPL, no. by Dirtside · · Score: 2

      As far as I know, various courts have established that the (United States) government cannot copyright things. Any work produced by goverment employees is in the public domain. However, work done by companies or individuals under contract to the government can be copyrighted.

      --
      "Destroy science and religion. Science would re-emerge exactly the same; but not religion." - Penn Jillette, paraphrased
    2. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      GPL results in software which is restricted, and not available to everyone.

      Please stop spreading lies: GPL results in software which is specifically available to everyone.

      (How else is Microsoft getting away with distributing my own GPL'ed software, g77?)

      --
      Practice random senselessness and act kind of beautiful.
    3. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      It's not a lie. For example, any employee of any corporation cannot legally include a GPL product in any of their own work without explicit permission of a signatory executive officer of the company. Any other behavior is legitimate grounds for termination and would also be civilly actionable by the corporation against the employee. These problems, I'm quite sure, are often overlooked by employees of companies, even middle-to-senior level managers who believe that they actually have yes-saying power in this situation, when in fact they legally and most assuredly do not and would face the same potential censure as would the lowest level employee in the event of an error.

      Your position that GPL software is "specifically available to everyone" applies more to the LGPL, which doesn't have a poison pill clause like the full GPL. This position of yours is really misrepresentative.

      C//

    4. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      You're correct. Which begs the question of why it is that U.S. government workers are surrendering their intellectual property rights and agreeing to create derivative works of intellectual property which belongs either to a private individual or an institution, now doesn't it?

      I don't have anything against government employees doing work for the public trust. I even believe that all U.S. government contractors should be forced to submit (non-secret/sensitive) software developed on the public dole to an open source license, but I'm a much bigger fan of BSD-style licenses.

      C//

    5. Re:Open source, yes. GPL, no. by rweir · · Score: 2, Insightful

      How does the GPL restrict you? Oh, that's right, it says 'here, have this, on one condition: give it to everyone else'. Why exactly is that bad? Because people can't hoard software?

    6. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      It's not a lie. For example, any employee of any corporation cannot legally include a GPL product in any of their own work without explicit permission of a signatory executive officer of the company.

      So a corporation can legally include a GPL product in any of their own work.

      Which means saying that GPL'ed source code cannot be used commercially IS A LIE, your attempts at deflecting the issue notwithstanding.

      Your position that GPL software is "specifically available to everyone" applies more to the LGPL, which doesn't have a poison pill clause like the full GPL. This position of yours is really misrepresentative.

      Here is the GPL. Search it for the text "commerc", and you'll find only one occurrence, in a trivial and unrelated place.

      The GPL has no poison-pill clause against corporations or commerce.

      You, sir, clearly know that, given your detailed and willfully-misdirected rebuttal to my explanation, so you are intentionally lying.

      Therefore you, sir, are a liar.

      --
      Practice random senselessness and act kind of beautiful.
    7. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      Whoops, no, HERE is the GPL. Sigh, forgot to check the link.

      --
      Practice random senselessness and act kind of beautiful.
    8. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      Your characterization of the GPL is incorrect. The GPL is more like "here, have this," and anything you connect to this, you also have to give it to everbody else. You're thinking of the LGPL.

      C//

    9. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      willfully-misdirected rebuttal to my explanation, so you are intentionally lying.

      For someone who claims the high road and a position of reason, you certainly are prone to hyperbolous, inflammatory, and, I might add, highly impolite remarks.

      A corporation cannot, as a matter of reduction to practice, incorporate a (full) GPL product in a release of its own software, because doing so requires them to give up intellectual property rights on their own works (the linking clause, read it yourself). While a few corporations might succeed based on a strict service model, this is the minority of them by a long stretch, and is otherwise inimical to the more normal conduct of commerce.

      "The GPL has no poison-pill clause against corporations or commerce".

      As a matter of reduction to practice, this is quite false.

      C//

    10. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      For someone who claims the high road and a position of reason, you certainly are prone to hyperbolous, inflammatory, and, I might add, highly impolite remarks.

      You previously had the chance to concede that I was, in fact, telling the truth about GPL'ed code vis-a-vis corporate use, yet you chose to obscure the issues further by claiming I was actually misleading the public.

      You could have simply agreed with me that the statement "GPL results in software which is restricted, and not available to everyone" was a lie (one that you told), and then gone on to explain how more-restrictive licenses prevented combining such software with GPL'ed software followed by distribution to others (which would have undercut your argument, I admit, since it'd put the burden of blame on the more-restrictive licenses), and how that inconvenience should be taken into account when considering public policy.

      But, no, you chose to go with the Big Lie that the GPL is somehow inherently anti-commerce, anti-corporate, that GPL'ed software "isn't for everyone", and went on to spin a yarn suggesting that I was the one misleading people.

      That was pathetic, and it will stand as an "eternal testament" to your character here on /..

      So I stand by my previous remarks, which you castigate as "hyperbolous, inflammatory, and highly impolite". If you're going to play with the fire of deceit, expect to get burned.

      A corporation cannot, as a matter of reduction to practice, incorporate a (full) GPL product in a release of its own software, because doing so requires them to give up intellectual property rights on their own works (the linking clause, read it yourself). While a few corporations might succeed based on a strict service model, this is the minority of them by a long stretch, and is otherwise inimical to the more normal conduct of commerce.

      Ah, so now we see how you modify your lies to make them a little more palatable.

      But you're still lying, since "the more normal conduct of commerce", when it comes to software, is not to distribute it as shrink-wrapped, proprietary software. That's a minority model for software, in terms of developed lines of code, probably in terms of deployed lines of code as well. Most software is developed for in-house use only, which is a model with which the GPL is quite compatible.

      And there's no real reason for the government to tiptoe around, as if on eggshells, specific business models employed by a minority of software developers in the commercial sector.

      Further, as you seem to be aware, though you perhaps try to hard to avoid mentioning it, there is a history of corporations choosing to re-license their code specifically so it can coexist with GPL'ed software as a single executable. (Not merely so they can be "connected", as you suggest in another comment.) I believe IBM's Jikes and Next's Objective-C compilers are two such examples; the steady stream of corporate contributions of patches to GPL'ed code bases are less-prominent, but perhaps, on the whole, more substantial and contemporary ones.

      Still, it's nice to see you're getting away from the lie that "corporations cannot use GPL'ed code", finally, though you're having to be dragged kicking and screaming to it. A sad permanent public commentary on your character. What a cowardly display.

      --
      Practice random senselessness and act kind of beautiful.
    11. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      The statement of character is yours, where you illustrate for the general public that the best you can do is become obusive when run out of intellectual ammunition. *sploink*. Omigosh, he's shooting blanks.

      I have quite aptly demonstrated the way that GPL limits commercial organizations. This was my basis for observing that government should not be in the business of preferring or mandating such a license. Public domain is unrestricted, and should be the preferred model for works produced by the public's funds.

      C//

    12. Re:Open source, yes. GPL, no. by J.+Random+Software · · Score: 1

      The corporation holds copyright to my work, but both my manager and I have exactly as much authority as the chief officers have chosen to delegate to us--there is no legal requirement that they make every such decision personally.

      There are no consequences to using GPL'd code in my work unless and until we decide to redistribute and license the work to third parties under incompatible terms.

    13. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      The statement of character is yours, where you illustrate for the general public that the best you can do is become obusive when run out of intellectual ammunition. *sploink*. Omigosh, he's shooting blanks.

      I have quite aptly demonstrated the way that GPL limits commercial organizations. This was my basis for observing that government should not be in the business of preferring or mandating such a license. Public domain is unrestricted, and should be the preferred model for works produced by the public's funds.

      I have neither run out of intellectual ammunition nor have engaged in shooting blanks. I have ceased discussing the issues with a proven liar, who doesn't have the courage to admit that he's been telling lies, thus abdicating, in my view, any responsibility inherently necessary in a thoughtful discussion of the issues.

      See this comment of mine for a more thorough rebuttal to your beliefs as stated by someone else not so insistent on telling lies and then pretending he didn't.

      --
      Practice random senselessness and act kind of beautiful.
    14. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      I have neither run out of intellectual ammunition nor have engaged in shooting blanks. I have...

      What you have done is become increasingly shrill and aggressive, thrown around insults, stooped to name calling, and otherwise fully engaged yourself in the normal tactics of dominance that are usually attempted by individuals who have weakly articulated positions and can't stand to have their opinions openly criticized in a public forum. Those are the facts. Do with them as you will.

      C//

    15. Re:Open source, yes. GPL, no. by mpe · · Score: 2

      A corporation cannot, as a matter of reduction to practice, incorporate a (full) GPL product in a release of its own software, because doing so requires them to give up intellectual property rights on their own works (the linking clause, read it yourself).

      "You cannot do X, because in order to do X you would need to do Y." When nothing stops you doing Y, is an interesting piece of "logic". Also you are making the false assumption that most corporations are in the business of selling proprietary software, which is simply untrue. So the argument is utterly meaningless, since they have none of their "own" software in the first place or if they do it's a set of alterations to GPL code which are utterly useless on their own.
      Indeed there are probably quite a few corporations, for whom owning (not licencing) proprietary software would cost money. Since their business has so little to do with selling software, they'd be like a bookshop which owned pedigree kittens.
      For the vast majority of corporations software is part of their infrastructure. It's not really much different from cables, pipes, even the buildings they use.

    16. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      Since their business has so little

      But this is just my point. The U.S. government shouldn't be in the business of selecting a particular business model to favor. Keeping it all open and public is correct for the U.S. government. Contrary to your (and the other rather rude poster's) seeming impression, I'm not anti-GPL. I've used GPL products in the past, and even have some in development that are planned for release _under_ the GPL. I am, however, quite painfully aware of what it means to me as an intellectual property worker to consider integrating GPL code. It's a big deal.

      While I have nothing at all against a private intellectual property owner releasing their own things under GPL, I'm very much against the government doing so as a matter of preference. It's fully discriminatory in the sense that it discriminates against an entire business model.

      The government should _NOT_ be in the business of doing that.

      C//

    17. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      What you have done is become increasingly shrill and aggressive, thrown around insults, stooped to name calling, and otherwise fully engaged yourself in the normal tactics of dominance

      You haven't seen me "fully engaged".

      Now, how about you come out from behind your cloak of anonymity so we can all learn who you actually are?

      --
      Practice random senselessness and act kind of beautiful.
    18. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      Now, how about you come out from behind your cloak of anonymity so we can all learn who you actually are?

      I note how you are now attempting to use intimidation and harrassment to further your goals. Am I to assume that if you knew who I "really am" that you would do something about it? Interesting implication. Am I supposed to feel frightened? LOL.

      It appears that you can't open your mouth without revealing more and more about your inner nature. By all means, do continue speaking.

      *sneer*

      C//

    19. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      I note how you are now attempting to use intimidation and harrassment to further your goals.

      Hardly. I made no intimidating comments, nor did I "harrass" you in any way.

      My conduct along these lines, of identifying what sort of "entity" you are, has been towards one fundamental purpose strongly related to the discussion at hand: exposing the importance of an open discussion of ideas to a free people.

      This thread has seen its share of claims and counterclaims. I've "accused" you of lying and being a liar, yet all I can possibly be said to have actually done is accuse a spectre, a "/. identity", that is barely distinguishable, except by name and the presumed existence of an actual account, from "Anonymous Coward".

      Now, after writing a long-winded comment assuming you were choosing to remain anonymous (a reasonable conclusion based on the content of your most recent comment), I just noticed that, in fact, you have added a URL to your web page on your /. identity.

      So I'm modifying my comment accordingly, to take into account that fact, and I commend you for finally showing some real courage, if not in this thread per se, in revealing your real identity.

      Prior to this, you'd accused me of all sorts of things, launching your attacks safe from public view, from public assessment of your other "works" outside of /., from even public determination of whether you really believe anything you say, perhaps being paid (by MS, say) just to write nasty, vicious lies about the GPL and about those who, like myself, defend it.

      Yet I am wearing no such mask of anonymity. Yet, the whole time (and for a few years now), my identity has been clear to anyone willing to do even the tiniest bit of research.

      In other words, it's entirely possible that, on my next interview for possible software consulting work, someone will ask me about my (to use your words) "highly impolite" behavior on /..

      I'll have to handle that by looking them straight in the eye and responding.

      Unlike you, I didn't post my comments thinking I could simply go about the rest of my life, secure in the knowledge that nobody knows about my /. identity, allowing me to trash other people's statements and reputations with impunity.

      That's why I make very sure that my accusations are justified, documented, and rational.

      And that's why I believe your counter-accusations are ill-informed, hate-filled, unprovable, and irrational (except probably for the "highly impolite" remark -- I'll grant you that one).

      At least it's nice to see you're willing to take personal credit for them by pointing to your web site, Mr. Kraska, now that I've asked you to come out from behind your anonymous persona.

      Yet, strangely, your answer to my simple challenge, for you to identify yourself, is to spew a few more insults and a few more baseless accusations, without acknowledging that you were revising your /. profile to include your web site.

      No sane person is going to look at my online "profile" and conclude I represent anything approaching a threat to you via intimidation or harrassment.

      Instead, they'll recognize, especially with my help in this comment, that I back up my claims (such as those about your statements and character) with my own personal reputation.

      (It wouldn't be the first time I had to deal with such attacks.)

      And that strongly parallels the differences between GPL'ed software development and proprietary software development.

      With most GPL'ed projects, end users are fairly assured of being able to look at not only the source code, but at a history of just who made which contributions, introduced (or fixed) which bugs, wrote the best documentation, came up with the most wonderfully twisted, yet incisive, test cases, and so on.

      Whereas with proprietary products, end users are usually presented with a monolith that reads "This Came From Proprietary Software Corp". They have no opportunity to view the source code, of course, nor can they make any reasonable attempts at assessing the competence of individual developers who contributed to the proprietary portions of the product.

      A government authoring new software should definitely take this into account: will the proprietary developer, who wishes to cannibalize the public code for his own purposes, and having been found to have produced a buggy product, point the finger of blame at the public code without disclosing the exact interactions -- the source code and, further, the history of changes it made to it -- to back up his claims?

      The answer was shown in this little thread of ours, until you revealed yourself.

      You were given plenty of opportunity to back up your claims, which I consider to include some lies, with a combination of references to actual evidence (say, clauses in the GPL that forbid commercial use) and other factors, such as assurances that you know what you're talking about and are honest, based on your own personal history.

      Until you changed your profile, even looking at your comment, you'd chosen to take the "proprietary" route: "My identity is of no concern. It is cburley [the one who is open and honest about who he is and what he believes] who is the real threat -- he is intimidating and harrassing people who attack his character!".

      That is, in my experience, the proprietary vs. free-software story in a nutshell.

      Sure, I've had some real serious fights with free-software people, especially RMS and Linus Torvalds, but these have been largely in the open, allowing the public to see just what I said and draw their own conclusions about me, my points, and my "opponents'" as well.

      But nothing I've gone through in the free-software arena compares to the kind of cowardly hiding from responsibility that is typical of the proprietary-software world (and I'm not including Microsoft here, since I have no personal experiences working there).

      In the proprietary software world, the whole point is to keep all sorts of stuff secret, supposedly solely for "profit", when, in reality, doing so serves a wider purpose of hiding data about culpability, responsibility, vulnerability, and so on.

      Proprietary developers can pat themselves on the back as much as they like for what they're able to accomplish with the vast funding they're given.

      But they're not even close to being in the same boat with free-software developers, who, at least down to the granularity of each individual's own workstation in most projects, have a fair likelihood of having to work daily under the bright lights of public view, with any random person taking issue with what or how they're doing usually able to email them, or complain to a public mailing list about their work.

      The difference is like that between government beauracrats, who can pretty much write any regulations they want without close public scrutiny, and elected legislators, who have to at least put up with constant public attention to what they're doing on the job.

      In line with my decades-long realization that the proprietary model is to the free-software model what the Soviet Union was to the USA -- closed vs. open; ridigly structured vs. loosely organized; and so on -- I've chosen to conduct myself on /. and other forums as a public figure just as I've done when developing public software, such as g77.

      And, in line with your passionate love for proprietary software and its advantages, such that you feel government should cater to that specific software-distribution model or not develop software at all, instead of backing up your claims with evidence and your own personal reputation, you've chosen to suggest that I was somehow threatening you personally by asking you to reveal yourself after having attacked my character.

      I realize none of this can possibly change your closed-source mind, miracles notwithstanding, but I hope it helps others understand why I'm so passionate -- not so much about the government GPL'ing code, which is not really a concern of mine per se -- but about honesty and integrity in discussions of public policy, which includes not "shading the truth" by making claims such as "GPL'ed software cannot be used for commercial purposes".

      You see, in my view, one of the crucial differences between the American way of life and that of most of the rest of the world is the degree to which we value honesty and integrity in the dealings that we do allow to be in the open (which is a much larger set of dealings than many societies enjoy).

      But if we, collectively, are unwilling to tell the God's honest truth about a matter as comparatively simple and unimportant as the degree to which the GPL is "anti-commerce" or "discriminatory", we show signs of having not much hope for openly and honestly assessing much more serious situations, such as the threat posed by Iraq.

      --
      Practice random senselessness and act kind of beautiful.
    20. Re:Open source, yes. GPL, no. by Courageous · · Score: 2


      realize none of this can possibly change your closed-source mind,...

      You're making stuff up, now. If insults and name-calling don't work, try blowing over straw men, is that right?

      I should have to say? A full page diatribe? I must have really struck a nerve.

      C//

    21. Re:Open source, yes. GPL, no. by cburley · · Score: 1
      realize none of this can possibly change your closed-source mind,...

      You're making stuff up, now.

      That was a joke, son.

      (You have based most of your arguments on the importance of closed-source software, y'see, so it's a pertinent play on "close-minded".)

      I must have really struck a nerve.

      Try reading it and thinking, instead of just typing insults and punching "Submit", for a change.

      --
      Practice random senselessness and act kind of beautiful.
    22. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      Try reading it and thinking, instead of just typing insults and punching "Submit", for a change.

      Your bad behavior began as you entered this thread, as is plain for anyone to see. Review it yourself. You began it with and insult, and proceeded full steam ahead. I made three attempts to converse with you reasonably. You've justifiably earned my contempt. Go away, little man.

      *sneer*

      C//

    23. Re:Open source, yes. GPL, no. by Courageous · · Score: 2

      It's true. If your manager or you have had an executive officer delegate to you the right to unilaterally surrender the intellectual property rights of your company at your discretion, you can do so. I'd advise you to get it in writing, however. Making a mistake here could be a career-busting move.

      Hyperbole aside :), and rhetorically, how many people do you think in major corporations are given the right you describe? Come now. You _know_ the right answer is "miniscule", right?

      The problem here is not with LGPL, BSD, or other licenses. My angst is specifically against the full GPL and its linking clause. It's bad mojo if not handled with the greatest of care, and wildly inconvenient.

      Keep in mind that I've opined previously right here on slashdot that _all_ software developed under contract to the government by open sourced. Outside of security concerns, things paid for by public money should enter the public trust.

      The GPL, however, excludes software sellers from creating interesting derivatives of these works. Derivitive works which are substantially original should be protectable intellectual property.

      Treating intellectual property generating organizations like third class citizens is not the correct thing to do with works made from the public's money.

      C//

    24. Re:Open source, yes. GPL, no. by mpe · · Score: 2

      But this is just my point. The U.S. government shouldn't be in the business of selecting a particular business model to favor.

      Which is exactly what they are doing by letting Microsoft dictate to them.

      Keeping it all open and public is correct for the U.S. government.

      Which is something the GPL does perfectly. So what's the issue.

      I am, however, quite painfully aware of what it means to me as an intellectual property worker to consider integrating GPL code. It's a big deal.

      It's a big deal to the tiny minority in the business of producing proprietary software for sale to third parties. For the vast majority of people, including the vast majority of people who work with software, it is no deal at all.Most software development is done for a specific requirement either in house or by contractors. If the work is done in house there is no distribution to third parties. If it's done by a contractor then the client gets a copy including the source and the contractor can still use what they did for future contracts.
      Is your pain of integrating GPL code really a problem caused by the GPL or is it actually a pain caused by proprietary code?

      While I have nothing at all against a private intellectual property owner releasing their own things under GPL, I'm very much against the government doing so as a matter of preference.

      So you are saying that the US government cannot take and alter GPL code? Even if doing so would cost far less that either writing something from scratch or buying licences to third party proprietary software. Maybe the US government should take a census of the objectors to their using GPL code, so that if they need to spend extra money they know who to send the bill to :)

      It's fully discriminatory in the sense that it discriminates against an entire business model.

      As opposed to discriminating to protect a minority business model. I'm sure in it's history the US Government has trashed lots of business models. Sometimes inadvertantly, as in this case, sometimes very much deliberatly. Should the US allow slavery, stop building public roads, remove all regulation of public utilities, disband all publicly funded law enforcement, etc. Just because these discriminate against someone's business model?

      The government should _NOT_ be in the business of doing that.

      Wrong goverments should not put private profits before fulfiling their mandates. The mandate of the NSA is the protection of the national security of the USA. It is not protecting the profitability the Microsoft Corporation or any other corporation or individual present on US territory.
      It cannot be stated often enough that there is no right to make a profit from commercial enterprise in general. In a free market capitalist economy if you no longer can make a profit from a specific business model (for any reason) they either you change business model or cease trading (if you are smart you do this whilst you still have assets). It's quite possible for your busines to become unviable due to government, indeed some business models are explicitally made illegal.
      WHy should proprietary software have special protection not given to slave traders, ice cutters, buggy whip makers, etc?

  141. I'm upset by syusuf · · Score: 1

    That sux, I was looking forward to playing an GNU version of scrabble from the NSA...

  142. Take it in our hands by Anonymous Coward · · Score: 0

    The projects freely avaliable why doesn't the linux community just dl and continue the work themselves? Someonse gotta be able to make up for the cost of continuing developing it.

  143. Redhat by krmt · · Score: 2

    The article does say that Redhat is working with the NSA on something, although they don't tell you what it is. While they say that Redhat has the money to get certified, I'd be surprised if they really wanted to put forth that money to get it done. Then again, I have no idea what the cost/benefits ratio really is, so maybe that's something they're working on.

    Either way, the SELinux stuff is GPL'ed, so I'd bet Redhat has taken it up and continued to work on it. There will be competition with Windows for the secure government desktops, and I know that the NSA understands the value in having the source GPL'ed. They just want to be able to cast the "guilt" on to Redhat when talking to Microsoft.

    --

    "I may not have morals, but I have standards."

  144. Re: Liberal Groupthink by 1010011010 · · Score: 2

    Nah, you're a "Welfare Statist."

    Welfare Statists advocate forcible (re-)distribution of wealth by the government (can't do it without using force), and government control (at some level) of the means of production. But not outright ownership.

    "Welfare Statists" are generally "Liberals." "Socialists" are generally "Authoritarians" or "Totalitarians."

    I'll take "welfare statists" over "socialists" any day, they're a much more reasonable bunch. Of course, the more capitalism and freedom-oriented the "welfare statist" is, the better I will like him.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  145. Re:That's scary - NOT by Waffle+Iron · · Score: 1
    Secondarily, its NSA/CSS. Ever hear of the CSS [nsa.gov] side of the house? I

    It's bad enough that the NSA is dabbling with OS design. But wasting our tax money on efforts to make prettier HTML formats is even worse. That job clearly should be left to independent standards organizations such as the W3C. Devoting half of a government agency to this effort is totally absurd. Does anybody in Washington have any sense of priorities??

  146. Priority here is.....? by ChrisJones · · Score: 1

    The government/military are quite important to national stability, so it's a fair bet that pretty much everyone is going to say they want their government/military to have computers that work properly, I mean, they invented fiendishly anal languages like Ada precisely to make software less likely to go wrong when someone's butt is on the line.
    I hope that the NSA hires the best of the best of the best (sir! ;) because they will know much better than I do what is secure. I don't even care what they are using, I just want to know that they got some smart people to rubber stamp it as safe.
    What I don't like to see, is anyone telling any important infrastructure that they should run anything other than the technically best solution available to them. I would rather have important data be secure than a monopoly get confirmation from on high what everyone has known for years - rebooting an air craft carrier in the middle of a battle is liable to get you killed ;)
    If Microsoft or anybody else wants to fight their corner, the battle should not be about market forces, it should be about the best solution!

    --
    Chris "Ng" Jones
    cmsj@tenshu.net
    www.tenshu.net
  147. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    I'm not talking about just the kernel. I'm talking X+KDE as well. I don't remember DOS crashing that often either.

  148. This is totally unfair by Anonymous Coward · · Score: 0

    So the NSA can work with microsoft to make it secure? but when they want to help make linux more secure its a bad thing? What a bunch of fscking hypocrates.

  149. Govt needn' t advocate anything Re:infrastructure by Anonymous Coward · · Score: 0

    The status quo is actually fine.

    I don't WANT a government-developed OS. I much prefer the *BSD and Linux alternatives that are available under the most reasonable terms imaginable in a market economy.

    While it was nice of the NSA to provide a blueprint for a more secure linux, it is not REQUIRED to do so unless it starts with GPL'ed code and keeps modifying it.

    I'm not advocating MS lobbying to keep it from being further developed, but neither am I saying we have a guaranteed right to the NSA work product as long as it makes the GPL code it has available on a non-discriminatory basis (free download of source code, no guarantee that working system can be made with it, and NO WARRANTY). If someone else wants to make "Fred's SE Linux", then they can start with what NSA has done, or they can start over with the concepts embodied therein and use OpenBSD and Mac 4 as a base, as those products are available under a less restrictive license than GPL. So go ahead and
    cancel the SE Linux project and let the Open Source advocates take over the project(s)

    Microsoft and anyone else can take the GPL code under GPL terms, but the LAST thing we
    need is a 'government standard, Open-source operating system'? Can you imagine the political football that would come with that?

    Commercial software development is not the government's principal role, and I would much prefer that:
    a) Government sponsored University research project place all their source code in the public domain (with no restrictions)
    That way, anyone can make use as they see fit, and nobody can complain about either:
    a) sweetheart deals for the source code 'licensee'
    b) exclusion (or expensive) citizen's access
    or
    b) government competing with/inhibiting commercial product development. Most technologies with staying power are built on more then free source code, they are built on a unique service concept around that source code.

    Look at the license for NIHCL, the NIH Class Library for C++ programmers. This should give you an idea of possible licensing terms

  150. Re:Your third point is wrong, and that's the probl by Anonymous Coward · · Score: 0

    Just why couldn't M$ release the source to the code they borrow from the NSA?

  151. Intelligence sharing by marm · · Score: 2

    The abuse done by the NSA during the Nixon years caused a lot of severe curbs (both open and classified) to be placed on the NSA, and those laws have serious teeth that will bite anyone violating them.

    Indeed. However, there's absolutely nothing stopping a friendly foreign signals intelligence agency (say, the UK's GCHQ or Canada's CSE) from gathering intelligence on US nationals, and then passing that intelligence back to US agencies through the formalised intelligence sharing agreements that exist. Of course, the NSA isn't allowed to even solicit such information, but how hard do you think it would be for GCHQ to find out who the NSA is interested in, or simply make the judgement call on who to monitor themselves?

    Which means that in reality, those safeguards against spying on your own people mean absolutely nothing. The NSA can enforce those regulations as tightly as they like, and all it does is create warm fuzzies. They'll still be getting all the intelligence they want.

  152. Re:Why Linux sucks by jesco · · Score: 2, Informative

    First, the individuals:

    > Linux is slower and less stable than windows
    A far too generic comment.

    > The few Apache/MySQL vs IIS/MS SQL tests I have
    > seen have been won (sometimes dominated by)
    > Windows

    You can't really compare mySQL and MS-SQL. mySQL is a lightweight database, MS-SQL tries to play in the same league as Oracle, DB2.

    And while I don't have any links at hand to prove you that you're wrong about the speed-comparison, I think that Apache is fast enough for most websites. Let alone the security issues IIS has ;)

    > WinXP Pro comes with a 480 meg CD, Mandrake is 3
    > CD's and SuSE is 7

    This is because MS only gives you the basic OS with some goodies, whereas Mandrake/RedHat/SuSE t al. offer you an OS _and_ applications. In most cases you don't need to download/buy anything else than a Linux distro. It already has everything you need.

    > Installing software on a Linux system is badly
    > broken.

    That'S what RPMs are for. Despite Win32 installation program, RPM keeps track of dependencies. Windows can't do that out of the box.

    > The exists no development environment more
    > compelling than gcc and emacs, for this reason
    > Linux apps will always be behind

    kDevelop, Kylix, only to name the two most professional ones. For Windows there MSVC++, which is actually a neat DevIDE, but it costs quite much and has issues of its own.

    That said, a more general comment by me:

    Linux can be a pain in the ass. Setting up a system is, for a (technical skilled) newbie much more difficult than setting up a Win32 box. Trying to make Linux do something can be quite some (research) work, and during that time you may say 'Oh what a crap system, nothing works.', but once you figured out how to do it right, Linux will rarely fail at its new job.

    WinXP, on the other hand, is the best piece of code that left MS for a few years. It's stable, clearly multimedia-orientated, has a neat UI-design and runs everything you want. But it can be as much as pain in the butt as Linux, when your apps start crashing because you uninstalled a small shareware tool which removed a crucial DLL. Let a newbie figure that out... :o

    But quite frankly, I wouldn't use Linux as my desktop OS if there wasn't this DRM/security stuff.

    Summarized: Both OS'es aren't bad. Each has its use. I happen to favor Linux, you favor WinXP. But try to stay constructive :)

  153. Yes, and we're sure you need Prozac! by Anonymous Coward · · Score: 0

    You're jingoistic ranting indicates your dire need of grin-inducing drugs!

  154. Re:NSA should continue working on SE Linux-BSD by Anonymous Coward · · Score: 0

    I've heard this "run with it" argument time and again. First companies big and small pay taxes as well as citizens. Second even though they may "run with it", so can we. The important thing is that *everyone* is on an equal footing. The GPL doesn't do that, while BSD does, and public domain will break the cycle that generates more research. As far as the advertising clause (which I believe was dropped), that hasn't stopped BSD's use in Linux distributions.

    BTW How are *they* going to run with "BSD + GPL + proprietary + ??"? You might want to rethink your equation?

  155. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Well, that's because you have a crap memory, or you're talking about purely DOS. Sure, DOS sitting at a command prompt doesn't crash... but any app is capable of crashing that OS. I remember having to hit reset thousands of times. Millions once I started writing my own ASM programs.

    Besides which, you are clearly trolling to compare the linux command line system with a DOS 'system'.

  156. And where were our lobbiests during all this? by patbob · · Score: 1
    Oh yeah, I forgot. We don't have our shit together enough to have lobbiests.

    Kinda stupid given that the US government has become a by-the-lobbiests-for-the-special-interests form of government.

    --
    Welcome to the net of 1000 lies. Upgrades are scheduled soon that should bring us to the 10,000 lies mark.
  157. Re:Why not BSD?-Better by Anonymous Coward · · Score: 0

    You are aware that companies pay taxes too, aren't you? Second even if some don't, they do end up paying anyway through licensing fees (read the story). One way or the other it get's paid for.

    Besides the BSD license would be better, because *everyone* would be starting at the *same point*, and anything they *add* on their own would go either proprietary (and can make money) or go GPL ( and further a political goal).

  158. public domain vs. open source vs. proprietary by Dan+Crash · · Score: 2

    It's kinda disingenuous to say, "If the government produces IP, everyone should get a piece," and then turn around and say the government can pay others to produce software for it that everyone won't get a piece of. If you're paying a winning bidder to develop government software that relies upon an Open Source license like the GPL, ultimately, taxpayer dollars are being spent developing non-public domain software.

    I'm not attacking you here; I've been thinking about the same thing myself for a while. Public domain is pretty obviously the best way of developing & releasing government source, since it preserves the ability of the code to be used for either proprietary or Open Source projects in the future. But limiting ourselves to public domain software is likely to be grossly inefficient as Open Source becomes more and more pervasive.

    My own feeling is that guidelines should exist which take different licenses and their cost of development into account. For instance (very roughly):

    All things being equal,

    If the cost of creating public domain software is 150% or more of the cost of coding comparable software which relies on GPL code, the GPL software should be chosen.

    If the cost of creating software which relies on GPL code is 150% or more of the cost of licensing comparable proprietary software, proprietary software should be chosen.

    ____

    The actual percentages could change, obviously, but should still embody the notion that there is an acceptable amount extra we will pay for public domain software, and a smaller amount extra we will pay for Open Source software. Proprietary software is the worst deal, since it leaves us nothing to give back to taxpayers, so we should only choose it if it does everything we want and it's much cheaper than any other solution.

    --
    He who refuses to do arithmetic is doomed to talk nonsense.
    1. Re:public domain vs. open source vs. proprietary by Elwood+P+Dowd · · Score: 2

      It's kinda disingenuous to say, "If the government produces IP, everyone should get a piece," and then turn around and say the government can pay others to produce software for it that everyone won't get a piece of. If you're paying a winning bidder to develop government software that relies upon an Open Source license like the GPL, ultimately, taxpayer dollars are being spent developing non-public domain software.

      Right. Except the reason it's unfair for the gov't to distribute code that is not in the public domain is that they can unfairly compete. They can levy taxes to support their competitive efforts. This is wrong.

      If the government has a fair bidding process that is blind to 3rd party licensing, then there is no way anyone can accuse them of unfairness. A Redhat shop could win the bid, or a MS shop could win the bid.

      I realize that we would all prefer our tax dollars went to GPL software. However, other people would prefer that our tax dollars went to their proprietary software companies. Neither of us can *prove* greater good. I'd rather not have the government deciding which of us is right. Thus, competitive bidding. The government should use software to fulfill it's mission, and it should do it in the most cost effective fashion available. Bar none.

      Of course, for those of us with the long view, it's pretty clear that at some point in the future, most contract solutions would be cheaper/better using free software. We'll keep that long view to ourselves and hope that MS doesn't see.

      I, too, do not mean to attack. Do you see how Gov't produced GPLed software might be objectionable, while contract-produced proprietary/GPL/BSD/whatever software would not? It's about unfair competition, not the type of license that tax dollars contribute to.

      --

      There are no trails. There are no trees out here.
  159. total bull by Anonymous Coward · · Score: 0

    NSA works on free software all the time - it's how they push their agenda. Look for Free ASN.1 compilers. Hell, the whole Public/Private Key stuff is NSA pushed (for obvious reasons to very few apparently) and now available free every where including it's inclusion at no extra cost with Microsoft software. NSA stopped working on Secure Linux because there was no interest. Yeah, I heard that acording to an annonymous source. lol.

  160. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  161. Re:They have one point-enemies by Anonymous Coward · · Score: 0

    "for all to use"? What about our enemies? Should we subsidize them?

  162. Re:Should the Government Compete w/ Private Indust by Anonymous Coward · · Score: 0

    If that's true, then all libraries should be closed, the national army should be privatized, the police forces should be privatized, and the nation's energy should bederegulated such as it was in California. Good idea, let's dissolve our country.

  163. Re:Your third point is wrong, and that's the probl by mpe · · Score: 2

    So proprietary software vendors (like Microsoft) DON'T get to use the improvements - at least not verbatim.

    This is Microsoft's choice.

    The improvements carry the Gnu Public Virus

    No they carry an antibody against the proprietary software virus. The likes of Microsoft can't simply appropriate the code.

  164. Re:Should the Government Compete w/ Private Indust by Anonymous Coward · · Score: 0

    BSD sucks. Why do you guys insist on giving your IP away to rich fuckers like Bill Gates and Steve Jobs. BSD developers are slaves for proprietary software corporations.

  165. Define "knowingly" by yerricde · · Score: 2

    If you post it on the net, then there's nothing stopping [Axis of Evil] countries from getting the code. Hence, doesn't that put one in murky legal waters?

    Not under the definition of "knowingly" used by BIS. Did you read the regulations I linked to? 740.13(e)(6) clearly states (my emphasis):

    Posting of source code or corresponding object code on the Internet (e.g., FTP or World Wide Web site) where it may be downloaded by anyone would not establish "knowledge" of a prohibited export or reexport.

    And if you really want to cover your rectum, you can make a "best effort" by looking up the IPv4 address ranges for the popular ISPs in the Axis of Evil, and just firewall those off.

    --
    Will I retire or break 10K?
    1. Re:Define "knowingly" by paladin_tom · · Score: 1

      From what I know of these countries, it seems extremely unfair to lump Cuba in with Iraq et al as "Axis of Evil". If I were a Cuban, I believe I would be extremely offended.

      So they're in your neck of the woods, and they don't believe in your economic or political system! Deal with it!

      And yes, I read those guidelines. I just got lost in all the legalese. :)

      --
      #define sig "Every social system runs on the people's belief in it."
  166. What _really_ happened by Erwos · · Score: 1

    A little late, but this is all fact:

    MS did in fact come to NSA and lobby the hell out of them to stop because "it helps Linux and not us". What the article _doesn't_ mention was that the group doing SELinux immediately offered to implement security upgrades in Windows _without the GPL_.

    MS said no. Why? Because MS don't really give a crap about security. If it doesn't make them money, MS doesn't care. That's what _really_ happened. It had nothing to do with open vs proprietary. It had to do with MS not wanting to spend money on security that they could get away without, and trying to hide it by doing away with the competition. (like usual)

    -Erwos

    --
    Plausible conjecture should not be misrepresented as proof positive.
  167. Re:Why Windows sucks by Anonymous Coward · · Score: 0

    Cause it crashes all the time.

  168. Re:I'm removing one Windows Server from my network by Anonymous Coward · · Score: 0

    can I have it? I'm getting rid of all GPL software on my network. Trade ya a linux distro that we dont use anymore.

  169. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Ive found linux much more stable then even xp, i have used both slack and mandrake. im running a tricked 8.1 with ext3fs, ext3 blows ntfs and any other m$ based file system clear out of the water and so does gnome 2.0
    Apache vs IIS, apache wins that war hands down, it has over 70% of the market share and growing.

  170. Linux is dying by Anonymous Coward · · Score: 0

    Clearly all this negative press about linux companies dying, linux distributions dying, companies using linux dying, linux publications dying, companies developing linux productst dying, linux distributions numbers getting dwarfed by BSD and MacOS X, and the realization that linux source code just isn't as good as the freely available coherently distributed BSD source code all spell one thing: linux is dying.

  171. Re:Should the Government Compete w/ Private Indust by Arandir · · Score: 1

    We give our code away to everyone, rich or poor, short or tall, stupid or smart. We don't attach strings to it. If you don't like Bill's copy of the code, download your own.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  172. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Yes, DOS does suck hard compared to bash or tcsh, but I really don't think it's crap memory. I am crrently running a beta so that is to be expected, but even on stable releases I get crashes with Konq, Netscape, Mozilla, Galeon kicker, etc. I have 3 computers, 2 of them with good quality hardware. BTW VI on the other hand, has never crashed once, same with Apache.

  173. Doesn't Matter Much by Commykilla · · Score: 1

    Anybody here ever used SE Linux? It wasn't nearly mature enough for serious testing, let alone deployment. I would say it was an academic exercise in extending the Flask architecture to Linux, and leave it at that. The code is still available, and anybody interested can work on making the system useable. It would take a concerted effort among kernel hackers and/or security gurus in the open source community to get the code at any realistic state anyway -- so if you really want it, fire up sourceforge and make it happen!

    --
    Communism was just a red herring.
  174. Re:Your third point is wrong, and that's the probl by cburley · · Score: 1
    So proprietary software vendors (like Microsoft) DON'T get to use the improvements - at least not verbatim. The improvements carry the Gnu Public Virus and can't be integrated into the vendor's code base without risking a suit from the FSF for GPL violation.

    Microsoft already does release GPL'ed code it did not write (nor explicitly ask permission to release -- e.g. of me) and yet does not risk such a suit.

    And, as another comment points out, that they can't simply fold NSA's changes into Windows and distribute it under the licensing MS finds convenient is Microsoft's choice -- a choice they can undo in an instant.

    Here's another thing Microsoft can't do with any government code put out in the public domain: it can't monopolize access to that code the way it does to Windows code it writes itself.

    That means anything the government writes, or modifies, cannot be used by Microsoft to further its monopoly, since the public can always choose to get at the free, PD versions of the enhancements instead of having to buy MS's formulations (involving those enhancements intertwined with proprietary MS code).

    So, just as with the case you complain about, the fact that the government releases code to the public, instead of simply handing it directly over to Microsoft for monopoly control (and I mean this in the copyright/patent, not desktop-PC, sense), means that Microsoft cannot benefit from this expenditure of taxpayer money in the ways to which it has chosen to become accustomed.

    Will you therefore argue that government is to never distribute software except to Microsoft?

    Else, please explain why the US government, or any other people-funded agency, should be expected to avoid public-minded licenses like the GPL and BSD simply to conform to the business models certain corporations happen to find convenient under current market conditions.

    (These licenses are public-minded in the sense that they are specifically authored to ensure long-term free public access to the code -- the source [GPL] or the binaries derived therefrom [BSD], put simply -- and they do not discriminate against any individual or organization, nor do they restrict freedoms such as of speech once any such entity accepts the terms of these licenses. It is precisely this sort of public-minded, freedom-oriented licensing that Microsoft finds frightening, because it cannot conceive of a future in which its business model, of selling closed software under licenses that stifle speech to people who think Software Is Magical And Thus Requires Great Expenditures By Huge Corporations, has been eroded by the public discovering, on its own, that software isn't so magical after all. But MS has specifically targeted the GPL and not BSD license, because with the BSD license it can at least "keep up" with the arms/feature race in theory.)

    Disclaimer: my sister works for Microsoft.

    --
    Practice random senselessness and act kind of beautiful.
  175. This is a good example. by benedict · · Score: 2

    In response to the article about the Tim O'Reilly
    editorial the other day, I said that if the open-
    source community is afraid to lobby, we will only
    ensure that we are not heard in the halls of
    power. This is a lousy situation, but a great
    example of that phenomenon at work. Microsoft is
    not afraid to make government aware of their
    positions. Well, if we believe that open source
    software promotes openness and prevents vendor
    lock-in, and if we believe that those are good
    goals for government -- as many of us do -- then
    we should not hesitate to explain our reasoning
    to our elected representatives and appointed civil
    servants.

    --
    Ben "You have your mind on computers, it seems."
  176. Re:Should the Government Compete w/ Private Indust by Skjellifetti · · Score: 1

    I don't want my tax dollars spent to make someone a millionare.

    Why not? I want the research efforts of government to be open enough that we all have an equal chance of becoming millionaires. All you need do is be smart enough to recognize the commercial potential of any publicly funded research.

    BTW, do you even pay taxes? I sure do! And to be told that I cannot attempt to profit from the research efforts that my tax dollars paid for means that you are stealing from me twice!

  177. Re:Govt needn' t advocate anything Re:infrastructu by the+red+pen · · Score: 2
    • I don't WANT a government-developed OS.
    You're soaking in it! If you are using Linux, then you are probably using networking infrastructure developed by Don Becker on NASA's time. They supported his work, and he felt that as a government employee, he had a "patriotic duty" to develop technology that could be used freely by the citizens who paid his salary.

    If you don't agree with that, go use Microsoft Windows and don't forget to pay the proper per-connection license for your non-government network stack.

  178. open source weakness revealed? by Anonymous Coward · · Score: 0

    So tell me again why we need the government to develop on OS?

    Why can't the open source community develop this on their own?

    BTW...I hear the FBI is developing a secure open source file sharing application. It will be free for download next month, and will also be packaged with every new CD/DVD.

  179. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    I think that's a misunderstanding... I didn't say you have crap RAM, I said you had A crap memory...

    DOS crashed all the goddamn time, it's just that it was due to apps, not DOS itself, because DOS doesn't DO anything past booting up.

    Re: the GUI stuff, I agree with you... I find nearly ALL gui stuff buggy beyond belief with constant crashes, whether it be Linux, BSD, Win32, OS/2 or whatever. I'm starting to question the validity of GUI interfaces as a useful mechanism.

  180. GPL and choice by commodoresloat · · Score: 3, Insightful
    Gov't should not be writing GPLd software that cannot be used in proprietary applications.

    This is absurd. GPL'd software can be used by anyone willing to abide by the terms of the license. If a company chooses to make proprietary software and not release the source, they are voluntarily choosing not to use GPL'd software. It is ridiculous to say that they "cannot" use the software; that is a choice they made based on their own business model.

  181. Damn national parks by Sabalon · · Score: 2

    No wonder disney and six flags can't provide such good service anymore, you have all these national parks competing for business at a much lower price.

    Tonight at 11: Kraft and Velveeta to sue US for government cheese cutting into their business.

  182. Re:Why Linux sucks by Anonymous Coward · · Score: 0
    >This is because MS only gives you the basic OS with some goodies, whereas Mandrake/RedHat/SuSE t al. offer you an OS _and_ applications. In most cases you don't need to download/buy anything else than a Linux distro. It already has everything you need.

    This is true, but I would rather have small, fast, solid base system that can be easily added to. Something like Gentoo with an installer.

    >That'S what RPMs are for. Despite Win32 installation program, RPM keeps track of dependencies. Windows can't do that out of the box

    RPM's have problems too. I think Linux would gain by moving away from package systems and moving to using an installer. There are plenty of Linux apps out there that do come with installers like Netscape, OOo, SO, Kylix, Loki. All of these installed beautify on my system. I don't know how well any of those installers would work for other applications, but maybe some sort of functional universal installer would go a long way. IMHO, this is one of the two largest problems facing Linux. The other major problem is that the RH limbo beta 2 C++ binaries will not run on the beta 3 system. I do realize there has been major changes to GCC recently, but I think this sets a new record for lack of backwards compatibility. These two things are playing the biggest part in holding Linux back from the desktop space. I had many of my windows apps replaced, but many of the apps I used are broken after I updated to QT3 and GCC 3. This is an important issue as major Linux releases usually come more frequent than windows and it hinders commercial support.

    I think if Linux does hit desktop space there will have to be LSB support for an /apps directory or similar. LSB does not really address desktop needs to the extent that it should, I have 20 or so text editors and word processors, most of them in separate locations, /apps/textedit would be nice.

    >kDevelop, Kylix, only to name the two most professional ones. For Windows there MSVC++, which is actually a neat DevIDE, but it costs quite much and has issues of its own.

    I have used Kylix a few times but mostly for little stuff. It is probably the closest thing Linux has to VS.NET, too bad more people don't use it. Delphi has never really gotten the credit it deserves, and Borland only recently added C++ support, maybe it will pick up in popularity soon.

    >Linux can be a pain in the ass. Setting up a system is, for a (technical skilled) newbie much more difficult than setting up a Win32 box. Trying to make Linux do something can be quite some (research) work, and during that time you may say 'Oh what a crap system, nothing works.', but once you figured out how to do it right, Linux will rarely fail at its new job.

    I think the initial install is something Linux has improved on, I actually like Mandrake's DrakeX more than Windows' installer.

    >WinXP, on the other hand, is the best piece of code that left MS for a few years. It's stable, clearly multimedia-orientated, has a neat UI-design and runs everything you want. But it can be as much as pain in the butt as Linux, when your apps start crashing because you uninstalled a small shareware tool which removed a crucial DLL. Let a newbie figure that out... :o

    I find when I am in Windows I miss many of the command Line functions of Linux, and when I am in Linux I miss many of the multimedia apps and GUI of Windows. I liked 2K more than XP, and don't get crashes because I am picky about the code I run on my system. I have had 2 crashes on my XP system; the first was when I killed some services the system needed to boot, the second was when I was using tweakXP with WindowBlinds. My stratagy for keeping windows stable is to run as little code as possible when it boots. It leaves a much smaller footprint in memory and is much less likely to crash. I also usually gut windows pretty thoroughly and make extensive changes to the default install before building on it. A few of the changes I make to my system can be found here and here.

  183. Why should the NSA listen by Anonymous Coward · · Score: 1, Insightful
    "I'm not surprised Microsoft lobbied the NSA...

    I'm surprised they listened."

    The NSA needs Microsoft's cooperation in the future if they want security holes fixed in Microsoft operating systems. Goodness knows the free market economy has not reacted to convince Microsoft of a need for security.

  184. GPLed code and Microsoft - sauce for the goose by Ungrounded+Lightning · · Score: 2

    Microsoft already does release GPL'ed code it did not write ...

    Not relevant.

    Here's another thing Microsoft can't do with any government code put out in the public domain: it can't monopolize access to that code the way it does to Windows code it writes itself

    But we're not talking about code in the public domain. We're talking about code under the GPL. Such code is "monopolized" by the Open Source Community.

    If the code were in the public domain (or under some other licenses, such as BSD), Microsoft could integrate it, or its features, with the core of its own systems, and distribute them without revealing the source. They couldn't stop OTHER people from doing the same. But other people count't stop them, either.

    But the code is under the GPL. The GPL is a RESTRICTIVE LICENSE, based on copyright. If Microsoft integrates such code into one of its OSes, that puts the whole OS under the GPL and requires Microsoft to release the source.

    And the NSA's changes aren't ADDITIONS to Linux, but MODIFICATIONS to it. So they're a derived work, and if the NSA releases it it MUST release it under GPL. They don't have the option to release their enhancements into the public domain or under any other license.

    Linux is under the GPL, a restirictive license that makes its internals useful to the Open Source Community but not Microsoft. Microsoft's OSes are under the Microsoft ELUA, a restrictive license that makes them useful to Microsoft (and to some extent to its customers) but not to the Open Source community. The NSA is just as much in the wrong when it uses taxpayer funds to enhance Linux and give the enhancements to the Open Source Community but not Microsoft as it would be if it used the same funds to enhance Windows 2000 and give the enhancements to Microsoft but not to the Open Source Community.

    So Microsoft was right to squalk. And the NSA was right, once it was pointed out, to stop working on Security Enhanced Linux.

    I don't like it either. And I understand that the viral terms of the GPL exist explicitly to prevent a variation of "Embrace, Extend, Extinguish", to wit: "Embrace, Enhance, Exclude".

    But if the Open Source Community licenses its work in a way that excludes the closed-source community from using the result, it must expect to work without government subsidies. (Or at least without more subsidies that Microsoft, and Sun, and Apple, and SGI, and HP, and IBM, and Amdahl, and SCO, and any other closed-source OS company receive.)

    The cost to a closed-source company for using GPLed code has been characterized as "more expensive than money". Seems that catchphrase applies to the cost to the Open Source Community as well.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:GPLed code and Microsoft - sauce for the goose by cburley · · Score: 1
      Microsoft already does release GPL'ed code it did not write ...

      Not relevant.

      It became relevant when you lied thusly:

      So proprietary software vendors (like Microsoft) DON'T get to use the improvements - at least not verbatim. The improvements carry the Gnu Public Virus and can't be integrated into the vendor's code base without risking a suit from the FSF for GPL violation.

      The counterfact is, Microsoft has been using GPL'ed improvements to GPL'ed software, integrated into its own "code base", whatever you mean by that, and yet does not risk a suit, because they're following the simple rules of the GPL, I assume.

      Here's another thing Microsoft can't do with any government code put out in the public domain: it can't monopolize access to that code the way it does to Windows code it writes itself

      But we're not talking about code in the public domain. We're talking about code under the GPL.

      Excuse me, apparently the concept of "analogy" is foreign to you.

      Once I remove the lies from your case, all it boils down to is "Microsoft can't use the code in the context of the business model it chooses to employ with some of its software".

      My point is that the same thing can be said of the government authoring and distributing public-domain code -- Microsoft can't use the business model of being the sole supplier of that code, and any of its derivatives, to the public.

      I'm simply trying to get you -- or, since you appear to be willfully lying to protect Microsoft's business interests, others reading your "arguments" -- to see that it is Microsoft's, not the government's, Linus Torvalds, RMS's, or my, choice whether to integrate GPL'ed code into its "code base" and distribute the derived results.

      Such code is "monopolized" by the Open Source Community.

      Since that equals "the public", including all public and private corporations, businesses, institutions, charities, governments, as well as individuals, I fail to see how your use of the word "monopolized" is anything other than a Terrible Lie.

      I guess you think the alphabet is "monopolized" by the "Open Source community" as well, since nobody else is allowed to copyright it?

      If the code were in the public domain (or under some other licenses, such as BSD), Microsoft could integrate it, or its features, with the core of its own systems, and distribute them without revealing the source.

      But not revealing the source is entirely their agenda -- it is not the public agenda by any means. (At best, the public might be said to be neutral on the issue. But when it comes to publically funded code, I think it's fair to say the public has more of an interest in ensuring that all programs distributed containing that code come with source, so the public can continue to benefit from improvements made thereto; can continue to help by fixing bugs found in it; can verify claims made about enhancements made to it by private parties; and so on.)

      But the code is under the GPL. The GPL is a RESTRICTIVE LICENSE, based on copyright.

      Yes, and the prohibitions against slavery are restrictive since they assure freedom.

      Really, the only "restrictions" in the GPL are to ensure that freedom to use the code as you see fit is never taken away by a third party.

      You seem to have a problem with that.

      If Microsoft integrates such code into one of its OSes, that puts the whole OS under the GPL and requires Microsoft to release the source.

      Then it shouldn't integrate such code into one of its OSes, or it should pick a different distribution model that allows source-code distribution -- clearly a feature that distinguishes Linux, which many claim is feature-poor, insecure, poorly written, etc. -- from competitors.

      Surely Microsoft can be grown-up enough to deal with the choices life throws at it -- choices between contributing further to the public weal and simply continuing to distribute secret, proprietary code for profit, code that does not get to contain certain publically-funded improvements to free, public projects like Linux?

      And the NSA's changes aren't ADDITIONS to Linux, but MODIFICATIONS to it. So they're a derived work, and if the NSA releases it it MUST release it under GPL. They don't have the option to release their enhancements into the public domain or under any other license.

      False. They can certainly refrain from copyrighting their code, simply make it public domain. All they are required to do is distribute it as source, which allows anyone to use the combination of their enhancements plus the original GPL'ed product.

      Linux is under the GPL, a restirictive license that makes its internals useful to the Open Source Community but not Microsoft.

      You've already implicitly acknowledged that this is a lie, yet you restate it here. Microsoft can certainly use the internals of Linux in ways that are useful to it, just not all the ways that are convenient to its current business practices -- as is the case with BSD'd code, as is the case with PD'd code, and so on.

      Microsoft's OSes are under the Microsoft ELUA, a restrictive license that makes them useful to Microsoft (and to some extent to its customers) but not to the Open Source community.

      Ah, I just love your attempt at "moral equivalence" here. "GPL is a restrictive license which excludes Microsoft in favor of a small community; MS's EULA is a restrictive license which excludes the small community in favor of Microsoft; therefore they are morally equivalent, and the government, by choosing one, disfavors the other."

      Of course, your arguments are based on lies, which you've apparently carefully constructed after studying the issues deeply, given how much verbeage and arrogance you're expressing in your "opinions" -- which might as well be fully funded by Microsoft.

      Here's the truth: GPL's license restricts only, for all intents and purposes, private parties from adding other restrictions to software, so it favors everyone, and disfavors those who would take away freedoms from the public.

      MS's EULA restricts people from viewing, talking about, benchmarking, copying, reverse-engineering, etc., etc., their code, so it favors only Microsoft (by easing their business-model issues) and disfavors everyone else.

      Once a person understands the truth, it no longer seems difficult to understand why NSA choosing to enhance Linux is not morally equivalent to NSA choosing to enhance MS Windows with code available, subsequently, only to Microsoft, despite your claims to the contrary.

      The NSA is just as much in the wrong when it uses taxpayer funds to enhance Linux and give the enhancements to the Open Source Community but not Microsoft as it would be if it used the same funds to enhance Windows 2000 and give the enhancements to Microsoft but not to the Open Source Community.

      Another attempt at equivalencing that, thankfully, marginally intelligent children would see through: Linux not being a corporation, but a free, public body of code, just like federal law, the FORTRAN, Ada, and C languages, and tons of other free-with-source software implementations the government has chosen, over single-vendor proprietary competition, to improve on the public dime.

      I don't like it either. And I understand that the viral terms of the GPL exist explicitly to prevent a variation of "Embrace, Extend, Extinguish", to wit: "Embrace, Enhance, Exclude".

      For someone who doesn't "like it", you seem to be engaging in plenty of pro-Microsoft deceptive advocacy.

      But if the Open Source Community licenses its work in a way that excludes the closed-source community from using the result, it must expect to work without government subsidies.

      No, again, you have it exactly backwards: if the closed-source community licenses its work in a way that excludes Free Software from using the result, it must expect to work without government subsidies.

      The cost to a closed-source company for using GPLed code has been characterized as "more expensive than money".

      Yet Microsoft continues to do it. As do Red Hat, IBM, and so on.

      Let me ask you this: if the public comes to decide that it won't, without rare exception, except software without accompanying source code, exactly what would that mean in terms of this discussion?

      --
      Practice random senselessness and act kind of beautiful.
    2. Re:GPLed code and Microsoft - sauce for the goose by cburley · · Score: 1
      Sigh...that should read: Let me ask you this: if the public comes to decide that it won't, with rare exception, accept software without accompanying source code, exactly what would that mean in terms of this discussion?

      --
      Practice random senselessness and act kind of beautiful.
    3. Re:GPLed code and Microsoft - sauce for the goose by mpe · · Score: 2

      Here's the truth: GPL's license restricts only, for all intents and purposes, private parties from adding other restrictions to software, so it favors everyone, and disfavors those who would take away freedoms from the public.

      Very few entities have any interest in slapping restrictions on pieces of software in the first place. The only ones who do are those who sell proprietary software as their main or only line of business.

      MS's EULA restricts people from viewing, talking about, benchmarking, copying, reverse-engineering, etc., etc., their code, so it favors only Microsoft (by easing their business-model issues) and disfavors everyone else.

      A sizable proportion of people would want to do one or more of these things.

  185. Important? Freaks! by J4tentacles · · Score: 1

    Better off checking news at ipkonfig.com with this type of crap. who really cares, Microsoft is a needle in the hay-stack, with a bunch of queers wondering around the art show.

    1. Re:Important? Freaks! by Anonymous Coward · · Score: 0

      We're all freaks in some way, feels good at times though.....................

  186. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    At the end of this post I state some of the changes I make to windows so its stable. A stable GUI is not hard to do if you scale back on useless features and focus on maintainable code. Fluxbox is an example of this, but could use a few things to make it more ergonomic.

  187. Can you say by IQ · · Score: 1

    Echelon?

    --
    Adults are obsolete children. - Dr. Seuss
  188. BS by Anonymous Coward · · Score: 0

    NSA doesn't leak. Some faggot LOONIX zelot said some fucking shit. Who cares.

  189. America!? by Anonymous Coward · · Score: 0

    Can people understand for once and for all that the US is not America?! I mean Cristobal Colon (which is the real name for the guy that Anglos called Christopher Columbus) didn't even found the US directly. He actually found the Caribean Islands of Cuba, Haiti/Dominican Republic and Puerto Rico. Indirectly, it found the US, only because of Puerto Rico. Still, it is far from the concept that most people in the US have. As if he went directly to Washington, DC and he declared that that was America. Oh boy, and some people actually belief things like this. No buddy, if there is anything that's really America is one of the three Islands just mentioned. European sailors were the ones that discovered the rest of the continent. Yes, the continent of America. Only in the US can people have such big heads to say they constitute the whole continent, regardless if it's only part of the northern side. I wonder if someone could explain that one. We are America, and we are part of North America. Now even songs and little by little encyclopedias are conceived to change history for the interest of a few. Wow! I bet that if Cristobal Colon was here, he would have quite a laugh.

  190. What will happen by Anonymous Coward · · Score: 0

    If this story is true then the US has trouble in the horizon.

    Well NSA may be forced to drop off its efforts on Linux and close everything "open source". Will America be safer? Absolutely not. What will happen will be the same as USSR dropping its efforts to reach the Moon when things are just two steps away. This will only boost the efforts in other countries on developing "security enhanced" linuces. And the US will just loose foot on it.

    Let's note that before NSA took the step there were already a few flavours of such systems. Some are produced in the US, others in Israel, Russia and in the European Union. Porbably India and China have also their projects on the move. Most flavours concern in one way or the other specific parts of computer security. Only two or three projects try to "generalize" the concept of security on the whole. One of them is exactly SELinux.

    Frankly SELinux is not the first but also not the last of these projects. In fact it is a marvelous sprint made by NSA to get a place on leadership. They came late and came with things and ideas that wouldn't fit many wishes and requirements. In fact they came in a way that everyone started to cry wolf as their system first looked as the "only security standard" for Linux. However, with the years, they didn't only managed to cool down the mood but also to gain great respect among the community for their effort. One must say that NSA's reputation changed a lot with this. Before many looked at it as the Agency in Black, now they look a lot more sympathetical and familiar.

    Well SELinux is not a supersystem. It has good things but also a lot of bad things. For a corporate, militar or highly-profiled governmental environment it is quite interesting and manageable. However it is quite unflexible, clumsy and resource hungry to be universally used. It is not unique, in Europe (including Russia) its concurrents don't sleep. One should note that no matter the efforts SELinux still has not won a position in production environments in a market that has already two years of life. Most experts consider it still in a Alfa-Beta status and prefer less complex and more flexible systems for use in critical environments. Besides SELinux is great on its ideology of processes and management, but as with common ideologies, there are those who disagree and this reflects on systems that have nothing familiar with SELinux. The only thing that SELinux may influence on them is to boost the ideological dissidence of the algorithms.

    If SELinux is stopped then the only thing that will happen is that someone will took the podium and drop out the NSA. SELinux will be developed by a corporation, another government or a community. Besides this will not stop all those other systems that are being developed and used in many places in the world. If those who force NSA to close doors to open development claim being American patriots, then I'm sure that they should shut up their mouths before speaking about "America's leadership". In the way things go the US, in the future, may see its once superb security machine trying to find a place in the end of the queue.

    I'm not American and don't well sympathize with the US. But I know the field and know what NSA is doing, and their work is quite interesting. In an academical point of view, because I highly prefer another way to secure the penguin and most of my friends think the same. Not everything "made in America" is taken for granted. Frequently it is taken the other way...

    To NSA: It is a pitty to see you dropping the ship. Hope to see you some day again...

  191. Re:Open source, yes. GPL, no. Public domain, no. by Robb · · Score: 1

    I agree with you that the GPL may not be the best license under which to make government sponsored software available. However I think that just making it public domain is an even worse idea.

    Software is functional so I think that the interests of the people would be best served by including a condition that requires any information needed for interoperability to be published if the software is extended. The specific case I have in mind is Kerberos.

    There may be some other conditions that should be added in order to better serve the interests of the people but I think that it is important that properietary software vendors don't have to jump through a bunch of hoops in order to use the results of government sponsored software research.

  192. Isn't it Share and Share Alike? by Tsujigiri · · Score: 2

    I'm not trying to start any arguments here, but I do think a couple of things are quite ammusing.

    Firstly, the complaints are that a US government agency is providing security patches internationally for a product that was designed and built internationally. If they want a Kernel using the NSA security code only for use by US companies, I think that it should only be allowed to use the kernel code developed in the US. Pretty non functional I'd think. It's pretty poor of them to say, "we'll take all the code developed by foreign private companies and foreign governments thanks, but you lot arn't alowed to touch US Gov funded stuff!". If they (private or government) want to build on shared code, they should provide it.

    Also I think it's ammusing that MS is kinda fighting on behalf of RedHat. :)

    --

    "I'll take the red pill. No! Blue! AAAaaaahhhhhhhhh"
    - Monty Python meets the Matrix

  193. speculating into the unknown by nadaou · · Score: 1

    The bit of your story that doesn't sit well with me is if it was a problem with one contractor- well rip out that code. If it's too deep to make that practicable, start from scrach. The NSA has the budget and enough smart people working for them that if the political will for this thing to happen was there, it would happen. Buy off the friggin patent. Buy the company. Make them pray the deal doesn't get changed further.

    No project goes through without hickups. If there was a 'party' who weaseled a patent in, I don't really see this as a show stopper. A convenient excuse for gracefully canceling something that was causing friction from the higher-ups? A combination of all these things?

    So what are the political reasons for stopping (or closing) public crypto projects?

    The whole question of how bomb-proof do you make something that your adversaries will have free access to may figure. Don't want to give the enemy the tools they don't already have so as to keep you out when you really want in. But-

    The US stands to lose way more than any other country in the world from a massive digital attack. It is much more important to the economic well being of the country (and thus tax money for proxy bombs) that Wall Street's (and main street's, taken in a cumulative sense) main computer systems can be trusted, than taking out an foreign intelligence server. We're way to dependent to go take that on the chin.

    The other thing to remember, is that MS, and others who stand lose from Open Source work have cash and access. Microsoft has lobbyists who can make noise in Washington and put the seeds of semi-reasonable sounding ideas into lawmaker's heads. Open source has slashdot where there's a lot of loud (but nonetheless silent) arguing and self-righteousness and preaching to the choir. -which maybe gets through to one or a few of the hipper congress-peoples, but not much further.

    So get out there and write to John McCain explaining the good that a secure private national computer grid will do for the greater national security! He's our man!

    One thing's for sure, sitting around evangelizing on slashdot won't do shit for any of the good ideas that pop up here from out of the muck from time to time. No more than yelling at the TV or newspaper every day would.

    It's all about political will, and it's all about controlling and feeding ideas to lawmakers. And I don't think the slashdot/stallman digest is delivered to all the guests at the fundrasing weekend each morning.

    food for thought I hope.
    go team!

    --
    ~.~
    I'm a peripheral visionary.
  194. Re:If I were a rich man.....(redundant) by Anonymous Coward · · Score: 0
    BUT if you_own_ 80% of the desktop market anyway who will stop you?

    The European Union maybe?

  195. hehehe by Anonymous Coward · · Score: 0

    you said it right!

  196. Re:Why Windows sucks by Anonymous Coward · · Score: 0

    You do know windows 98 is now 4 going on 5 years old. If you are going to use windows 98 as a comparison, compare it to Linux of nearly 5 years ago.

  197. Re: hacking funded by government by hany · · Score: 1
    So based on what you wrote, Linux patches (which makes SE Linux) should be release under dual licence: GPL (to not to conflict with Linux licence) and public domain (to protect investments made with tax dolars).

    Now under which licence should be released patches to Windows created using tax dolars? Looks like under two licences too: some Microsoftish and again public domain. (question is: How will Microsoft like that? IMO they wont give permission for such hacking in the first place).

    And also what about intelectual property? I make some hacking for say NSA, patches are release as public domain (so the results of the research paid by tax dolars is available) but I can (at least try to) defend my IP and stop everybody from using that public domain code, so I'm defeating the reason for which public domain licence has been used in the first place.

    --
    hany
  198. Re: Liberal Groupthink by gowen · · Score: 1
    can't do it without using force
    Course you can. Its called taxation. If you can raise money for the common defense, you can raise it for welfare.

    Americans are strange people. They'll vote for local taxation to build a group of already-wealthy businessmen a new baseball stadium, but suggest the same thing to pay for the healthcare of the poorest sections of society and they'll call you a socialist.
    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  199. Of course they did. by Anonymous Coward · · Score: 0

    It's all a symptom of extreme emphasis on free market, free trade and free capital. Any company (with the capital to do so) would not do it's job (making even more money for their stock-holders) without lobbying and using other methods of applying pressure to their own and any other goverment to do whatever is in their own (capitalistic) intrest.

    As to whether Microsoft lobbys against NSA and every other goverment agancy to make them stop using free software, developing such themself or giving away research to the public domain: They wouldn't be doing their job if they didn't. The fact that they get caugth doing this kind of activity from time to time just means that they are not very good at it.

    wether or not anybody want's to listen to Microsoft and it's like is up to them.

    On the more paranoyd note, microsoft may have been payd by USA's goverment in a devious plan to make software that's completly insecure and have every other goverment and military to use it. The only problem was: If someone else made a secure OS (like SELinux) their efforts would be completely in vain.

  200. Re: Liberal Groupthink by 1010011010 · · Score: 1

    Course you can. Its called taxation
    Try collecting taxes without the use of force. I know that a lot of people pay "their share" just because they think it's the right thing to do. But what do you suppose would happen to the "compliance rate" if there was no force to back up the tax laws?

    They'll vote for local taxation to build a group of already-wealthy businessmen a new baseball stadium

    I won't. I think that's a scam of outrageous proportions.

    --
    Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
  201. Re: Liberal Groupthink by gowen · · Score: 1
    But what do you suppose would happen to the "compliance rate" if there was no force to back up the tax laws?
    Oh I see. Thats a fair point, but its equally true about taxation for (say) the armed forces, whereas I (mis)read your post as implying that force was necessary because it was for social welfare expenditure. You're right, some people just don't like paying taxes.

    I won't. I think that [publicly funded sports arenas are] scam of outrageous proportions.
    I think you're right.
    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  202. State sponsors of terrorism by yerricde · · Score: 1

    From what I know of these countries, it seems extremely unfair to lump Cuba in with Iraq et al as "Axis of Evil".

    Don't blame me. Blame the people who write the export regulations. Blame USA Government. Blame PoizonBOx. The USA Government has considered Cuba a state sponsor of terrorism long before September 2001.

    Imagine a system where the government is so intrusive that it even controls the amount of food which one is entitled to live off.

    --
    Will I retire or break 10K?
  203. Re:Why Linux sucks by corey_lawson · · Score: 1

    Office 2000 Premium comes on 4 CDs...

  204. The FSF would probably take it by bill_mcgonigle · · Score: 2

    I'm sure they could work out an arrangement whereby the FSF would add final spit and polish (say, a README) and accept copyright of the final work.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
  205. here again by Anonymous Coward · · Score: 0

    your grand politicians and thier deep pocketed lobbiers. I bet millions are dumped daily into the coffers of the democratic and repulsican parties. Micro$ has yet proved again, if you cant break the law and get away with it, campaign contributions work too

  206. Re: hacking funded by government by Elwood+P+Dowd · · Score: 2

    Based on what I wrote, the government would not be able to produce something like SELinux and release it to the public, because it would require a massive licensing violation to put someone else's GPLed work in the public domain.

    Similarly with Windows. The Gov't should not hack windows. That would be unfairly assisting MS.

    --

    There are no trails. There are no trees out here.
  207. Don't know GPL?! by d2002xx · · Score: 0

    We didn't fully understand the consequences of releasing software under the GPL (General Public License)

    Funny! They don't know GPL but M$, did they try to express that it's just a "commerical" goverment?

  208. Re:Should the Government Compete w/ Private Indust by botik32 · · Score: 1
    BTW, do you even pay taxes? I sure do! And to be told that I cannot attempt to profit from the research efforts that my tax dollars paid for means that you are stealing from me twice!

    But you can profit! You can use linux and save the money you pay to M$. And help the rest by reducing the virus rampage.

    I want the research efforts of government to be open enough that we all have an equal chance of becoming millionaires.

    Ah! getting rich off selling someone else's work! What a marvellous and novel idea...

    I have a suggestion for you: go to LasVegas, you might just WIN BIG without much effort. : ))

    sigh
  209. Re:Why Linux [if that is what you call win.] sucks by Anonymous Coward · · Score: 0

    >Linux is slower and less stable than windows

    YEAH RIGHT! In many cases, Linux is FASTER. It is getting faster all the time. PLUS, Linux is REALLY just another UNIX, which provides FAR more platform support!

    >My windows box uses about 40 megs of ram to boot, Linux uses about 175 (and
    Linux is a monolithic kernel)

    YEAH RIGHT! I have 1GB(RAM) on my windows system, and it is STILL not enough! Linux has run on 4MB systems just FINE!(I have an 8MB system that is running just fine with it) Last I heard, people were working on making it run in LESS than 1MB! Try running Windows 95 in 16MB, and it is like a DOG! Will Windows 2000 even BOOT with less than 32MB?

    MONOLITHIC KERNEL? How about M/S with ONE FAULTY message queue? How about the fact that it loads almost ALL DLLS into limited memory, and they STAY there! Windows ends up being quite monolithic!

    Besides, the arguements against monolithic are:

    1. Not able to be updated through modules:
    Linux CAN be, and windows is very limited in this regard.
    2. Not being able to allocate memory dynamically as needs arise for parts of the system.
    Linux CAN. Windows is limited here, and a HOG!
    3. Not well organized.
    Linux is well organized. From what I have heard and seen, windows ISN'T
    4. Not running in as little memory as possible.
    They are trying to get linux down, but it runs well in 1/4 the memory that windows systems require just to boot!

    >Linux crashes much more often than windows, way more

    I have had windows crash MANY times each day on me! Others have the SAME problems! I LAUGHED when it happened to Bill Gates on the BEST system at the WORST time! Yet MANY people had a linux error cause their systems to crash! OH you say, Linux CRASHES! Want to hear the punch line?

    1. This error was fixed OVER 7 years ago!
    2. It ONLY occured if you had your system up for over a year(As I recall it took several years) with NO reboots.
    3. It happened because a counter wasn't reset, and would cause a fault when it overflowed.

    >The few Apache/MySQL vs IIS/MS SQL tests I have seen have been won (sometimes dominated by) Windows

    IIS ISN'T STABLE, and has LOTS of problems.! Most of the tests have been rigged. And they ALL show strengths/weeknesses of each platform. NONE shows Windows is best in all cases.

    X is a one size fits all poor implementation at a responsive display server (both Apple and MS are moving to hardware accelerated GUI) ...If you're running a 486.

    Windows is WORSE! X doesn't look quite as nice, and isn't quite as integrated, BUT.... Problems with X DON'T crash the system. It is multiplatform. It is networkable.(windows requires all CLIENT processing, specialized software, or a buggy and clunky "terminal server").

    >KDE is maybe the only thing on earth more intigrated than windows explorer, everything under the sun imbeded into konqueror, it makes it clunky as hell, Nautalus is nearly as bad

    Damn straight. It crashes a lot over stupid stuff, and it does hog memory. Still, after it crashes It works OK.

    >Ease of use for the newbie is not as important as ergonomics for powerusers, but Linux has yet to bring an environment to the table that I can efficiently get work done it.

    Unix, and the Linux implementation, have been getting work done for OVER 30 YEARS! Microsoft isn't even 27 years old.

    Do you REALLY think that, 10 years after the fact, people would have spent THOUSANDS for UNIX(the O/S, with NO computer), if it was bad? Sure, NOW you have cheap or free variants, but THEN you DIDN'T! SCO for the full system cost over $5000! Yet it competed against M/S Windows/DOS!

    BTW, I made a prediction in the early eighties. I was laughed at. NOW, it is true! Nearly every Computer company has standardized on UNIX!

    IBM, DEC(now gone, I know), DELL, APPLE, HP,SUN, etc.... For their bigger systems, and proprietary ones, as well as many PC workalikes, they use a variant of UNIX!

    IBM =AIX/LINUX
    DEC =ULTRIX
    DELL=LINUX
    APPLE=BSD (as a kernel to their new MAC OS)
    HP=HP/UX
    SUN=SOLARIS(sunos)

    >WinXP Pro comes with a 480 meg CD, Mandrake is 3 CD's and SuSE is 7

    WINXP pro does NOT come with 1 CD! You need MANY to match Linux! You need exchange(disks?), MSDN(1 DVD), SQL SERVER(1+ CD), etc..... NO comparison!

    For the basic O/S? Linux needs 1 DISK(a FLOPPY!)!
    And Windows needs HOW many?

    >NTFS is much more stable than any Linux file system, hard shut down in Linux and watch it fsck your box

    Hard shut down with windows, and watch IT take a while!

    >Installing software on a Linux system is badly broken, often you end up fixing make files, chasing dependencies, or in situations where you can't update a library with out breaking other apps, many libraries are not very backwards compatable and someone still has yet to write an installer for Linux. Nullsofts SperPiMP installer for windows is only 498K but such a simple installer has yet to exist for Linux because it's design is funamentally flawed.
    Even windows 3.11 had an installer and you can install the 32 bit libraries for it and still run binaries that were compiled on XP, lets see Linux do that

    Don't get me started! I had a problem REinstalling VB4 on Windows! When I called Microsoft, they said "It sounds like you installed Office 97." They made changes to OS files, and caused problems! SO, you claim windows 3.11windows XP compatibility? I'm telling you windows doesn't even have Windows 98 windows 98 (SAME installation, and SAME computer) compatibility!

    As for the dependency problem? I call microsoft, and they say "reinstall windows in another directory." This means a weeks downtime, and possibly accomplishes NOTHING. With Linux, you will likely get your problem solved quickly.

    BTW, even MSnbc said that Linux is better supported than Windows! And THEY are part owned by microsoft!

    Fundamental flaws? Microsoft has a GREAT methodology that they encourage everyone to use, but it will NEVER work! WHY? Because M/S doesn't use it! What good is it if your C program handles all dependencies, but the C library(from M/S) DOESN'T? Linux, on the other hand, has distributions that are supported, and has standards that are being followed more and more!

    >Developers will often use GPL just so they can avoid having to create and test seperate packages for the last 3 versionsof every major distro, GPL lets someone else do it.

    Linux supports more platforms DIRECTLY than any other O/S on the planet. Do YOU have the money for vaxes, alphas, mainframes, suns, IBM PCs, Macs, etc.... Not to MENTION the OTHER hardware! GPL reduces the cost from BILLIONS or trillions, to peanuts!

    >The exists no development environment more compelling than gcc and emacs, for this reason Linux apps will always be behind

    There are actually quite a few. KYLIX, FORTE, ETC... Still, I'm betting you're NOT a programmer!

    >Would like feedback on this
    >Thanks

  210. Re:Why Linux sucks by walt-sjc · · Score: 2

    For any horror story on software installation on Linux, I could come up with one for Windows too. For all the "reasons" someone comes up with for why linux sucks, I could come up with Windows couterparts. It's pointless.

    I've got a major newsflash for all you OS bigots. Learning a new OS requires learning new skills, terminology, etc. It takes time. OS's are also different. Yessiree, folks. Setting an IP address on Windows is different than Linux, the Mac, VMS, AS/400, Mainframe, etc. Each OS has it's strengths and weaknesses, but YOUR lack of skill is NOT a weakness in the OS. The poster who claims that his linux kernel took 175M is a good example of someone who does not have the skill or knowledge to understand what he is doing / seeing (which in this case it's probably the fact that Linux uses most of the available memory for buffers / cache, and free's it as needed for other uses. One of those "performance enhancing" features.)

    Understanding a feature and understanding the CONCEPTS behind the feature are two different things. Someone with conceptual / theoritical knowledge is going to be able to pick up a new OS easier than someone who doesn't. Someone without the conceptual knowledge moving from one OS to another is going to try apply the old OS's features and behaviors to the new one and therefore will have LOTS of problems. Stick a Windows user in front of a Mac for the first time and watch them squirm.

    Yeah, a newbie installing Linux for the first time is going to be JUST AS CONFUSED as a newbie installing Windows. So what's a newbie to do?

    First, any novice should buy a book on linux and READ THE DAMN THING. There are several modern distros that are well geared towards the novice. Most install MUCH easier than windows. As long as your hardware is listed as being supported on the compatablility matrix for the distro, things just work. Once installed, the system is fairly self-maintaining, and virtually anything can be done via GUI tools. Users don't need to use vi or emacs, they can use one of the bajillion other editors out there for either the command line or GUI. The solution to virtually any problem a newbie may face is easily solvable by typing a few keywords into google (since ALL linux documentation is online) or browsing the online manuals that come with the distro to find the solution. Next, get the damn book out again and try some of the examples. Learn the system. It's NOT that hard - if my 65 year old non-computer literate mother can do it, and my 9 year old nephew can do it, so can you.

    Enough of the tired old whiney claim that Linux is hard. It's 100% FUD at this point. You just make yourself look incompetent.

  211. Re:Why Linux sucks by headmonster · · Score: 1

    I think that comment is shortsighted and unfair. I also think I would be hard pressed to come up with a better example of the barrier I'm talking about.

    From my personal experience - a Winx user sat in front of a Mac will generally be productive within a day. Same user in front of a Linux desktop will typically give up.

    What's needed here and apparently absent from your comment is an ability to listen to the problems I raised and address them constructively. All too often what I find are comments like yours which belittle the user and serve to squelch the kind of insights that are necessary before Linux will succeed on the desktop.

    This is precisely the barrier I was talking about. A glowing example in fact.

    To address your first point on horror stories, and hopefully leave out the un-needed emotional heat, the point is not a numerical comparison of how many Winx horror stories there are compared with how many *nix horror stories there are. That is immaterial.

    What is important is that there are any Linux horror stories and what to do about reducing that number.

    I for one am not content to have Linux be "just as good" or "better than" Winx in any case by case comparison. I feel that Linux is far too powerful to settle for that.

    Rather, my goal would be to have Linux serve as the basis for a near revolution in computing - one that finally makes reliable, scalable, and powerful computing capabilities accessible in a way that computing has never been. As simple as a toaster for the novice, yet as powerful as the largest super-computer ever concieved for the expert, with no large bumps in-between on the learning curve. An environment that encourages wide and constant innovation while preserving reliability and stability. If a goal must be picked, that would be mine. No FUD here. Linux is good. But, it's not good enough yet. With open eyes - let's solve that issue.

  212. Re:Why Linux [if that is what you call win.] sucks by Anonymous Coward · · Score: 0
    >YEAH RIGHT! I have 1GB(RAM) on my windows system, and it is STILL not enough! Linux has run on 4MB systems just FINE!(I have an 8MB system that is running just fine with it) Last I heard, people were working on making it run in LESS than 1MB! Try running Windows 95 in 16MB, and it is like a DOG! Will Windows 2000 even BOOT with less than 32MB?

    I am talking about desktop Linux, not just the kernel itself; you knew that but chose not to see past it. My windows system has 512 megs of DDR, my Program Files directory is 8.9 Gig, I go through the folders and open every single program, although some stuff is stored in virtual memory, the system still runs smooth using about 380 of primary memory. Mandrake 9.0 beta 2 used 240 Megs of RAM on default install (no servers) just to boot. As previously stated, I can get windows to boot using 40 Megs of RAM, default install is something like 58. Anyone reading this can right click on task bar and Task manager > performance and see that even with the system in use it will usually stay under 100 Megs of RAM.

    1 Gig is not enough for your windows box but Linux runs fine on 4 Megs of RAM...

    Yeah right, I think we are both trolling at this point but least I am being honest. You argue my point on stability but saying UNIX is stable, it is. Linux is stable too when used as a server and not a desktop, it also uses much less RAM when you don't load X and a DE. But you're sidestepping the fact that Linux is still huge, slow, and unstable as a desktop, which BTW, is an important fact when considering its potential on the desktop. The rest of your post continues to go on comparing apples and oranges, and for good reason.

  213. Re:My tax dollars and the GPL by mpe · · Score: 2

    Simply put, I do not want MY tax dollars going towards development of software licensed under the GPL. If my tax dollars fund development that goes into the public domain, fine. If my tax dollars fund development that gets licensed under the GPL, NOT FINE.

    So you'd be happy to pay more taxes to compensate for the inability of government to modify GPL software in any way. You'd prefer if instead they either wrote from scratch (and released as public domain) or paid for proprietary software, either of which are likely to cost a lot more tax dollers than taking some GPL code, modifying it a bit then complying with both the rules requiring the publically funded work be made public and the GPL...
    When it comes to spending public money there are usually rules about not squandering the money. Not allowing government departments to modify GPL software (which is effectivly what a "government may not release GPL software" type rule does, since, unlike private individuals and corporations, they are obliged to publish any modifications made) means that they can have to spend considerably more money, with no apparent benefit to anyone, except possibly a few corporations who didn't contribute their fair share of tax dollers in the first place.

  214. Re:Your third point is wrong, and that's the probl by mpe · · Score: 2

    These licenses are public-minded in the sense that they are specifically authored to ensure long-term free public access to the code -- the source [GPL] or the binaries derived therefrom [BSD], put simply -- and they do not discriminate against any individual or organization, nor do they restrict freedoms such as of speech once any such entity accepts the terms of these licenses. It is precisely this sort of public-minded, freedom-oriented licensing that Microsoft finds frightening,

    When did "to further progress of science and the useful arts" become "to further the profits of big business" anyway?

    because it cannot conceive of a future in which its business model, of selling closed software under licenses that stifle speech to people who think Software Is Magical And Thus Requires Great Expenditures By Huge Corporations,

    To the vast majority of companies software is infrastructure. Even people who may think having clean water piped through out a building, electricity, high speed LANs, telephones, etc are "magical" generally understand that to get these sort of things sorted you can either employ people who know about them or get an external contractor in. No-one in their right mind would chase half way across a continent (or even the planet) to get a magic plumbing kit or a magic cabling kit or even a magic building kit. But somehow Microsoft has managed to sell the idea of a magic software kit, an off the shelf product which will cover all your companies needs without needing to employ an expert to set it up. Maybe because software is newer than buildings, plumbing, etc and there is no real material cost involved in deploying it.

  215. Re:Why Linux sucks by Anonymous Coward · · Score: 0
    I've got a major newsflash for all you OS bigots. Learning a new OS requires learning new skills, terminology, etc. It takes time.

    I have been using Linux as long as I have been using windows, learning the OS is not the problem, it's using it.

    Yeah, a newbie installing Linux for the first time is going to be JUST AS CONFUSED as a newbie installing Windows

    I remember the first time I installed windwos, I don't remember it being a problem. The fist time I installed Linux I didn't have trouble aside form not knowing the mount point for the primary Linux partition.

    Enough of the tired old whiney claim that Linux is hard. It's 100% FUD at this point.

    I don't really think Linux is hard and don't have a problem sifting through google or man pages (apropos :), but even with that in mind, Linux has a long way to go before it is able to replace Windwos on the desktop. FUD is hearing how Linux (desktop) is so much faster and windows crashes all the time, the other way IMHO. Windows never seems to crash for me, I don't really mind Galeon or Mozilla crashing on me either, but it makes BSOD jokes get old fast. I find myself running xkill and kill -9 often.

  216. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    But a stable GUI does not equal stable GUI apps, which is more part of the problem. I am complaining about the general state of GUI interfaces and applications, and I see tens to hundreds of crashes and bizarrities every day.

    Hell, at least once a week Win2k decides to completely remap my keyboard in a random app. Sometimes a command prompt, sometimes Outlook Express.

  217. Re:Your third point is wrong, and that's the probl by cburley · · Score: 1
    When did "to further progress of science and the useful arts" become "to further the profits of big business" anyway?

    Thank you -- an excellent point.

    Personally, I don't mind if the NSA or any other government agency chooses to use PD, or BSD, or GPL for distribution. If it's difficult to make a decision based solely on technical merit, but there happen to be substantial economic benefits to choosing, say, PD over GPL (say, if it might speed acceptance of a new protocol by making the implementation more attractive to software proprietors), I doubt I'd spend hours on /. screaming how that's "discriminatory" against GNU and the GPL.

    So your point is well taken -- the government is not to be accused of "discrimination" simply because the public license under which it might choose to distribute software it writes happens to be inconvenient for a few existing businesses, thanks to distribution models to which they've grown accustomed.

    The interesting thing, to me, about this whole discussion is how intent pro-MS types are on propagating lies and distortions about the GPL being "anti-business", "anti-corporate", "anti-commerce", and "discriminatory", rather than more calmly and rationally discussing the real issues, such as whether Linux is technically the best platform upon which to build a secure OS. (I'd have guessed OpenBSD, based purely on my impressions from reading stuff on the web, for what that's worth....)

    Seeing the stack of cards upon which MS has built its anti-GPL efforts makes me wonder what they're really scared of, and what might be about to happen to their profitability, their stock price, etc. I mean, if they have nothing to fear due to having vastly more funding and all that other stuff, why propagate lies about the GPL?

    --
    Practice random senselessness and act kind of beautiful.
  218. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    I have almost 9 gig of installed programs on my windows box, all of them stable. I don't have any spyware installed on the system though, and nothing non-MS runs in the backround. I am not sure what programs on your system are buggy, but there are probably better more stable replacements for most of them.

  219. Re:Open source, yes. GPL, no. Public domain, no. by mpe · · Score: 2

    but I think that it is important that properietary software vendors don't have to jump through a bunch of hoops in order to use the results of government sponsored software research.

    It isn't the job of government to ensure any business models work and never break. Why shoudl proprietary software vendors get special treatment?

  220. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Yes, but the Office XP has only one install disk (the other disk is a media disk), and GobeProductive for windows is only about 11 meg.

  221. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    You're full of shit dude. The experience of thousands of others denies your unprovable statement.

    Incidentally, I looked at your links, and you must think all windows users are just below "severely retarded" to think either of those articles told me anything I didn't already know, or find out in my first week of running XP. Holy shit.

    Incomplete list of applications that crash frequently (order of at least once a week):
    Outlook Express
    Internet Explorer
    Mozilla
    Opera
    Explorer
    Delphi
    Visual Studio

    To be fair, Opera doesn't usually crash a second time after restarting it, even viewing the same pages.

  222. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Most of the people I know that run 2K and XP claim it's fairly stable. I don't seem to have any problems with the apps you listed (accept outlook which I don't use). Any crashes in Delphi or VS were usually attributed to my inability to code. Maybe the fact that my system does not seem to crash is attributed to pure luck.

  223. Re:Why Linux sucks by Anonymous Coward · · Score: 0

    Perhaps you're talking about the entire system overall. I am not claiming Win2k falls down forty times a day - it certainly doesn't. But the software running on it DOES. Frequently.

    And it's the same on all GUIs too... Mozilla crashes everywhere I've tried it (Note: not every five minutes or anything). This isn't necessarily an attack on Windows, I'm just countering your claim that everything is fine in the land of Win32.

    And sure, some of Delphi's crashes are due to my own imperfect state, but most certainly not all.

  224. Re:Why Linux sucks by jesco · · Score: 1

    > This is true, but I would rather have small, fast,
    > solid base system that can be easily added to.
    > Something like Gentoo with an installer.

    I agree that I don't use of the apps on my RedHat distro. But unlike Gentoo et al. all I don't need to download each new app I may need. apt-get/emerge might be a neat idea, if you have either a flat or broadband. For me per-minute modem user they're unavailable :(

    Still, RPM's ability to watch the dependencies is a good idea. They can save you a lot of hassle when you're about to deinstall a package on which other packages rely. This is the main advantage over vanilla windows.

    Unfortunately, this only works for the RPMS and not user compiled apps/libs. But I read about checkinstall, which creates RPMS out of ./configure;make;make install software.

    > I think the initial install is something Linux
    > has improved on, I actually like Mandrake's
    > DrakeX more than Windows' installer.

    Getting Linux on your harddisk is pretty easy nowadays. And I think vanilla Linux is already far better configured than out-of-the-box Windows (i.e. I don't need to install drivers for half of my hardware).

    It's getting Linux to do all the small things you like it to do. That's the pain in the ass. For example, you want to view encrypted DVDs under Linux. Ok, you got Xine already installed, but nada, that'S not enough. For menu support you need Xine-DVDnav. Oh wait, DVDnav requires libdvd and libdvdcss. Each library needs to be d/l'ed seperately, you need to compile/install the libraries, you need to take care that the version of Xine-DVDnav and Xine are compatible... sheesh, I only want to watch the occasional DVD. Got my point? ;)

    > I liked 2K more than XP, and don't get crashes
    > because I am picky about the code I run on my
    > system. I have had 2 crashes on my XP system;

    I had a few more, but I could always trace back the source of the error. Most times it was my fault (wrong driver etc); only Mozilla made my XP box crash totally on certain webpages, and even then not the whole OS crashed, only the GUI did (which may have the same effect, but Winamp, for example, still played my MP3 collection).

  225. Re:Should the Government Compete w/ Private Indust by Skjellifetti · · Score: 1

    But you can profit! You can use linux and save the money you pay to M$

    That isn't profit, it is cost reduction.

    Ah! getting rich off selling someone else's work!

    It isn't someone else's work. It is MINE! I paid their bills!

  226. Re:Open source, yes. GPL, no. Public domain, no. by Courageous · · Score: 2

    Your point is germaine. It's not the job of government to select business models. Picking GPL is a selection; one that specifically excludes certain models. Hence my original comment that public domain is more appropriate; or more open licenses (like the essentially unrestricted BSD, Apache, and similar licenses).

    C//

  227. Re: patches by hany · · Score: 1
    ... a massive licensing violation to put someone else's GPLed work in the public domain.

    Well, they can maintain and distribute patches. And while patch is theirs as a whole, they can licence it under whatever licences they like: GPL, public domain, some commercial licenses. All at the same time.

    Sure it is less practical, but so is rewritting whole Linux or Windows.

    IIRC lame used such tactic to avoid problems with licence of code they used as building base - they distributed patch licensed under GPL used to patch software under some "free to use but restricted" license.

    (Btw, lame managed to rewrite whole base so now it is fully functional and all under GPL. But "Lame Aint Mp3 Encoder" is not "Linux" :)

    --
    hany
  228. Re:Open source, yes. GPL, no. Public domain, no. by Robb · · Score: 1

    It isn't the job of government to ensure any business models work and never break. Why should proprietary software vendors get special treatment?

    That is exactly my point as well as that of the original poster. Proprietary software vendors should not get special treatment and neither should open source projects. In my opinion the GPL would amount to special treatment of open source efforts.

    The point I wanted to make was that I think that the welfare system for proprietary vendors that would result from everything being put in the public domain is going to far in the other direction. The GPL and public domain are, in my opinion, at opposite ends of the spectrum and I feel that a more balanced license would better serve the public.

    Given that you have some software that was funded by the government what should be done with it? In my opinion you want to maximize that value of the software to the people who paid for it, i.e. the people of the country. It is generally not of much direct use to the majority of people so you are left with choices like license it to a company, put it in the public domain, license it under the GPL or choose some other license.

    My opinion is that the best way to maximize the benefits for the people is to choose a license that maximizes use while also ensuring interoperability and thus competition. The GPL does not maximize use while the public domain does nothing to ensure interoperability.

  229. Re:Why Linux sucks by BakedBeans · · Score: 1

    > Linux is slower and less stable than windows

    You don't actually know this do you? You've never run Linux, hence can't appreciate the fact that the only time it crashes is... dunno. I've only locked it up when playing with accelerated X drivers (closed source NVidia drivers at that.. ha!)

    > My windows box uses about 40 megs of ram

    Mate, you're confusing Windows with Office.. Office takes 40Mb to boot, Windows 2000 and XP both take approx 100 - 170Mb after logging in. I know, I run the both.
    For those who care, OpenBSD/FreeBSD uses about 30Mb.. cool, eh?

    > Installing software on a Linux system is badly broken

    I agree with installs being a pain in the arse..

    I've used Slackware, RH and Mandrake (and stints on Turbolinux and SuSe).. but Gentoo Linux gets my nod due to its excellent portage tree.

    Portage is basically a rip of what BSD has had for ages.. if the app u want is in the ports area, cd into the dir, type make and let your machine handle dependency checks, downloading all relevant apps/libs, building dependant programs, installing etc.
    And guess what.. it works.

    I've cd'd into the 'gnome' dir and typed 'make'. Come back an hour or two later and you've got a complete gnome system, optimised for your machine - the dependancy checks ensured the X was downloaded, built and installed.. tip of the hat to the Gentoo team.

    You can't get any easier than that.. 'make install' .. coffee time. Don't even have to reboot afterwards (or every day..hehe).

  230. And Solaris.... by jotaeleemeese · · Score: 1

    ... and AIX... ... and HP-UX .... ... and SCO ... ... and IRIX ...

    --
    IANAL but write like a drunk one.
  231. Re:Open source, yes. GPL, no. Public domain, no. by mpe · · Score: 2

    Picking GPL is a selection; one that specifically excludes certain models.

    It's an implicit choice, since they started with GPL material and obeyed the licence. N.B. none of the actual copyright holders are complaining about this.

  232. Re:Open source, yes. GPL, no. Public domain, no. by mpe · · Score: 2

    That is exactly my point as well as that of the original poster. Proprietary software vendors should not get special treatment and neither should open source projects. In my opinion the GPL would amount to special treatment of open source efforts.

    Proprietary software vendors are PSVs out of their own choice. No third party went to them and said "you are a PSV, you will always and forever be a PSV". Should corporations be protected form possible negative consequences of their own actions?

    Given that you have some software that was funded by the government what should be done with it? In my opinion you want to maximize that value of the software to the people who paid for it, i.e. the people of the country.

    By this criteria Microsoft probably shouldn't be considered part of the people who paid for it in the first place.

    My opinion is that the best way to maximize the benefits for the people is to choose a license that maximizes use while also ensuring interoperability and thus competition.

    If the US government cannot release GPL code then the only way they could make use of GPL code is to use the programs unmodified. This potentially places a huge and expensive restriction on the US government. Where they could have taken a GPL program and modified it a bit they now have to either develop from scratch or buy from a PSV.

    The GPL does not maximize use while the public domain does nothing to ensure interoperability.

    So maybe you;d need something else for software originated by the US government. The thing is that the issue is more about the US government creating derived works under licence. You'd also need to ensure that they are not restrained from modifying someone elses code, where the copyright holder is perfectly happy for them to do so. Otherwise this would be restricting the interests of the directly involved parties, the US Government and the GPL copyright holder, in order to satisfy some third party PSV.

  233. Re:Open source, yes. GPL, no. Public domain, no. by Courageous · · Score: 2

    But this is the thing. Government employees should not be in the business of giving up their intellectual property rights to private organizations. Why? "Their" intellectual property rights are actually _ours_.

    C//

  234. Rumor has it that... by strat · · Score: 1

    ...Secure Computing actually did a fair amount of the hardening of the kernel, and that NSA wasn't really in a position to release Secure's work, but figured that out after the cow was out of the barn.

    If that's true, it's a wonder that Secure hasn't dragged them into court.

  235. large misunderstanding of our rights by No-op · · Score: 2

    the constitution and the bill of rights do not delineate the only specific rights that you have- they are merely a list of rights that the founders felt needed to be enumerated for clarity. you are given the right to more or less EVERYTHING barring items that conflict with existing laws (and even that is arguable- you can claim, for example, that the DMCA and other 'corporate laws' violate many rights.)

    don't assume you are only given what is listed- that's not how it was intended, and now how you should perceive it.

    --
    EOM
  236. Re:First Post by DrVonDrake · · Score: 0

    Yep, another one of the MANY here on slashdot ^_^