What happens when Richard Reid Jr., blows up a bomb in his shoe? What happens to a blended body in this case? There have been examples of survivable aircraft terrorist attacks where a hole was blown in the fuselage but the aircraft was able to land...now what happens when the entire aircraft IS the wing?
Although many people believe they HAVE to use Gamespy Arcade to play their favorite game online, and some games bundle it on the CD and suggest you install it, most games also include their own in-game browsers and there are also alternatives available which don't try to force you into a chat room when ever you want to look for a game or shove banners in your face, although some (pingtool) are dead.
Perhaps the government can install readers for these in public places, you can identify people carrying "problem" books, i.e. those promoting political discord, and track their movements.
Anyone from the UK here? You guys are saps for government intrusion. You don't even live in a democracy, but you think you do.
There are a lot of other uses for this UK chip plan--install readers for them in public places, and you can identify people carrying "problem" books, i.e. those promoting political discord, and track their movements.
I think that as more spyware programs take tactics like that bundled with Radlight, a boot-disk image version of Ad-Aware is going to be needed for it to run properly, just like Virus scanners allow you to create a rescue disk. Eventually spyware programs are going to kill the ad-aware process as it starts. A boot disk version would allow you to run Ad-Aware (or similar) without interference from the spyware.
Re:MOD IT DOWN!!!
on
GPL's Strength
·
· Score: -1, Offtopic
mirror modded down
on
GPL's Strength
·
· Score: -1, Redundant
what the hell is that modded down for? the article will be unreachable when everyone on the east coast starts getting to work.
-----------
This essay was originally published in LinuxUser.
Free Software Matters: Enforcing the GPL, I Eben Moglen* [slashdot.org]
August 12, 2001
Microsoft's anti-GPL offensive this summer has sparked renewed speculation about whether the GPL is ``enforceable.'' This particular example of ``FUD'' (fear, uncertainty and doubt) is always a little amusing to me. I'm the only lawyer on earth who can say this, I suppose, but it makes me wonder what everyone's wondering about: Enforcing the GPL is something that I do all the time.
Because free software is an unorthodox concept in contemporary society, people tend to assume that such an atypical goal must be pursued using unusually ingenious, and therefore fragile, legal machinery. But the assumption is faulty. The goal of the Free Software Foundation in designing and publishing the GPL, is unfortunately unusual: we're reshaping how programs are made in order to give everyone the right to understand, repair, improve, and redistribute the best-quality software on earth. This is a transformative enterprise; it shows how in the new, networked society traditional ways of doing business can be displaced by completely different models of production and distribution. But the GPL, the legal device that makes everything else possible, is a very robust machine precisely because it is made of the simplest working parts.
The essence of copyright law, like other systems of property rules, is the power to exclude. The copyright holder is legally empowered to exclude all others from copying, distributing, and making derivative works.
This right to exclude implies an equally large power to license--that is, to grant permission to do what would otherwise be forbidden. Licenses are not contracts: the work's user is obliged to remain within the bounds of the license not because she voluntarily promised, but because she doesn't have any right to act at all except as the license permits.
But most proprietary software companies want more power than copyright alone gives them . These companies say their software is ``licensed'' to consumers, but the license contains obligations that copyright law knows nothing about. Software you're not allowed to understand, for example, often requires you to agree not to decompile it. Copyright law doesn't prohibit decompilation, the prohibition is just a contract term you agree to as a condition of getting the software when you buy the product under shrink wrap in a store, or accept a ``clickwrap license'' on line. Copyright is just leverage for taking even more away from users.
The GPL, on the other hand, subtracts from copyright rather than adding to it. The license doesn't have to be complicated, because we try to control users as little as possible. Copyright grants publishers power to forbid users to exercise rights to copy, modify, and distribute that we believe all users should have; the GPL thus relaxes almost all the restrictions of the copyright system. The only thing we absolutely require is that anyone distributing GPL'd works or works made from GPL'd works distribute in turn under GPL. That condition is a very minor restriction, from the copyright point of view. Much more restrictive licenses are routinely held enforceable: every license involved in every single copyright lawsuit is more restrictive than the GPL.
Because there's nothing complex or controversial about the license's substantive provisions, I have never even seen a serious argument that the GPL exceeds a licensor's powers. But it is sometimes said that the GPL can't be enforced because users haven't ``accepted'' it.
This claim is based on a misunderstanding. The license does not require anyone to accept it in order to acquire, install, use, inspect, or even experimentally modify GPL'd software. All of those activities are either forbidden or controlled by proprietary software firms, so they require you to accept a license, including contractual provisions outside the reach of copyright, before you can use their works. The free software movement thinks all those activities are rights, which all users ought to have; we don't even want to cover those activities by license. Almost everyone who uses GPL'd software from day to day needs no license, and accepts none. The GPL only obliges you if you distribute software made from GPL'd code, and only needs to be accepted when redistribution occurs. And because no one can ever redistribute without a license, we can safely presume that anyone redistributing GPL'd software intended to accept the GPL. After all, the GPL requires each copy of covered software to include the license text, so everyone is fully informed.
Despite the FUD, as a copyright license the GPL is absolutely solid. That's why I've been able to enforce it dozens of times over nearly ten years, without ever going to court. Next month, I'll explain how enforcement is really done.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
mirror of The following article
on
GPL's Strength
·
· Score: -1, Redundant
This essay was originally published in LinuxUser.
Free Software Matters: Enforcing the GPL, II Eben Moglen* September 10, 2001
Last month I described in general terms the legal theory of the GPL. This month, I'd like to explain how, contrary to the fear, uncertainty and doubt sown by Microsoft, the license is actually enforced.
Much murmuring has been going on in recent months to the supposed effect that the absence of judicial enforcement, in US or other courts, somehow demonstrates that there is something wrong with the GPL, that its unusual policy goal is implemented in a technically indefensible way, or that the Free Software Foundation, which authors the license, is afraid of testing it in court. Precisely the reverse is true. We do not find ourselves taking the GPL to court because no one has yet been willing to risk contesting it with us there.
So what happens when the GPL is violated? With software for which the Free Software Foundation holds the copyright (either because we wrote the programs in the first place, or because free software authors have assigned us the copyright, in order to take advantage of our expertise in protecting their software's freedom), the first step is a report, usually received by email to license-violation@gnu.org. We ask the reporters of violations to help us establish necessary facts, and then we conduct whatever further investigation is required.
We reach this stage dozens of times a year. A quiet initial contact is usually sufficient to resolve the problem. Parties thought they were complying with GPL, and are pleased to follow advice on the correction of an error. Sometimes, however, we believe that confidence-building measures will be required, because the scale of the violation or its persistence in time makes mere voluntary compliance insufficient. In such situations we work with organizations to establish GPL-compliance programs within their enterprises, led by senior managers who report to us, and directly to their enterprises' managing boards, regularly. In particularly complex cases, we have sometimes insisted upon measures that would make subsequent judicial enforcement simple and rapid in the event of future violation.
In approximately a decade of enforcing the GPL, I have never insisted on payment of damages to the Foundation for violation of the license, and I have rarely required public admission of wrongdoing. Our position has always been that compliance with the license, and security for future good behavior, are the most important goals. We have done everything to make it easy for violators to comply, and we have offered oblivion with respect to past faults.
In the early years of the free software movement, this was probably the only strategy available. Expensive and burdensome litigation might have destroyed the FSF, or at least prevented it from doing what we knew was necessary to make the free software movement the permanent force in reshaping the software industry that it has now become. Over time, however, we persisted in our approach to license enforcement not because we had to, but because it worked. An entire industry grew up around free software, all of whose participants understood the overwhelming importance of the GPL--no one wanted to be seen as the villain who stole free software, and no one wanted to be the customer, business partner, or even employee of such a bad actor. Faced with a choice between compliance without publicity or a campaign of bad publicity and a litigation battle they could not win, violators chose not to play it the hard way.
We have even, once or twice, faced enterprises which, under US copyright law, were engaged in deliberate, criminal copyright infringement: taking the source code of GPL'd software, recompiling it with an attempt to conceal its origin, and offering it for sale as a proprietary product. I have assisted free software developers other than the FSF to deal with such problems, which we have resolved--since the criminal infringer would not voluntarily desist and, in the cases I have in mind, legal technicalities prevented actual criminal prosecution of the violators--by talking to redistributors and potential customers. ``Why would you want to pay serious money,'' we have asked, ``for software that infringes our license and will bog you down in complex legal problems, when you can have the real thing for free?'' Customers have never failed to see the pertinence of the question. The stealing of free software is one place where, indeed, crime doesn't pay.
But perhaps we have succeeded too well. If I had used the courts to enforce the GPL years ago, Microsoft's whispering would now be falling on deaf ears. Just this month I have been working on a couple of moderately sticky situations. ``Look,'' I say, ``at how many people all over the world are pressuring me to enforce the GPL in court, just to prove I can. I really need to make an example of someone. Would you like to volunteer?''
Someday someone will. But that someone's customers are going to go elsewhere, talented technologists who don't want their own reputations associated with such an enterprise will quit, and bad publicity will smother them. And that's all before we even walk into court. The first person who tries it will certainly wish he hadn't. Our way of doing law has been as unusual as our way of doing software, but that's just the point. Free software matters because it turns out that the different way is the right way after all.
* Eben Moglen is professor of law and legal history at Columbia University Law School. He serves without fee as General Counsel of the Free Software Foundation. You can read more of his writing at moglen.law.columbia.edu.
"Sen. Hollings says he stands for American values but he tries to bring Big Brother into your house. Sen. Hollings says that big government should intrude into seeing what you watch and listen to on your television, computer, and stereo system."
it's on the front of C|Net news.com as well, they own com.com...
one simple solution for the detector software
on
Spy v. Spy
·
· Score: 2
The detector software (Ad-Aware, WHo's watcthing me.., etc.) will have to provide a "boot disk" option, like many virus scanners do, if they want to keep up... all you have to do then is create the disk on another computer, write protect it, and start up to scan for spyware.
Tempest refers to stray electromagnetic radiation that is "read" by appropriate radio equipment nearby, this article is about stray light emissions that are picked up by a photosensor.
The guy can get off pogey and go work at McDonald's. No sympathy whatsoever. He'd better not get any better treatment than they'd give a typical blue collar laborer.
Since overclocking often results in problems like FPU errors (just try running one of those intensive distributed computing projects and getting proper results) why bother?
Provided the ship isn't going too far (i.e. 20 light years), it could still receive transmissions from earth, like news, including audio and video perhaps, so that the language would remain constant.
Slashdot Mirror
Must I remind you of the Apple rainbow logo that was so popular in the 80's?
I think the decision to not target Mac fanatics must mean that the army is going to end the "don't ask, don't tell" policy.
What happens when Richard Reid Jr., blows up a bomb in his shoe? What happens to a blended body in this case? There have been examples of survivable aircraft terrorist attacks where a hole was blown in the fuselage but the aircraft was able to land...now what happens when the entire aircraft IS the wing?
Although many people believe they HAVE to use Gamespy Arcade to play their favorite game online, and some games bundle it on the CD and suggest you install it, most games also include their own in-game browsers and there are also alternatives available which don't try to force you into a chat room when ever you want to look for a game or shove banners in your face, although some (pingtool) are dead.
Actually it was done in Portugal to get around local regulations...
There's also superbit DVD, which provides an even higher resolution than conventional DVD.
Perhaps the pilot will control the lead plane and the others will automatically fall-in in formation?
Perhaps the government can install readers for these in public places, you can identify people carrying "problem" books, i.e. those promoting political discord, and track their movements.
Anyone from the UK here? You guys are saps for government intrusion. You don't even live in a democracy, but you think you do.
There are a lot of other uses for this UK chip plan--install readers for them in public places, and you can identify people carrying "problem" books, i.e. those promoting political discord, and track their movements.
Just wait until some hacker hacks dshield.org and puts 127.0.0.1 in the list
I think that as more spyware programs take tactics like that bundled with Radlight, a boot-disk image version of Ad-Aware is going to be needed for it to run properly, just like Virus scanners allow you to create a rescue disk. Eventually spyware programs are going to kill the ad-aware process as it starts. A boot disk version would allow you to run Ad-Aware (or similar) without interference from the spyware.
Please, beat anon with a wiffle bat. Thank you.
what the hell is that modded down for? the article will be unreachable when everyone on the east coast starts getting to work.
-----------
This essay was originally published in LinuxUser.
Free Software Matters:
Enforcing the GPL, I Eben Moglen* [slashdot.org]
August 12, 2001
Microsoft's anti-GPL offensive this summer has sparked renewed speculation about whether the GPL is ``enforceable.'' This particular example of ``FUD'' (fear, uncertainty and doubt) is always a little amusing to me. I'm the only lawyer on earth who can say this, I suppose, but it makes me wonder what everyone's wondering about: Enforcing the GPL is something that I do all the time.
Because free software is an unorthodox concept in contemporary society, people tend to assume that such an atypical goal must be pursued using unusually ingenious, and therefore fragile, legal machinery. But the assumption is faulty. The goal of the Free Software Foundation in designing and publishing the GPL, is unfortunately unusual: we're reshaping how programs are made in order to give everyone the right to understand, repair, improve, and redistribute the best-quality software on earth. This is a transformative enterprise; it shows how in the new, networked society traditional ways of doing business can be displaced by completely different models of production and distribution. But the GPL, the legal device that makes everything else possible, is a very robust machine precisely because it is made of the simplest working parts.
The essence of copyright law, like other systems of property rules, is the power to exclude. The copyright holder is legally empowered to exclude all others from copying, distributing, and making derivative works.
This right to exclude implies an equally large power to license--that is, to grant permission to do what would otherwise be forbidden. Licenses are not contracts: the work's user is obliged to remain within the bounds of the license not because she voluntarily promised, but because she doesn't have any right to act at all except as the license permits.
But most proprietary software companies want more power than copyright alone gives them . These companies say their software is ``licensed'' to consumers, but the license contains obligations that copyright law knows nothing about. Software you're not allowed to understand, for example, often requires you to agree not to decompile it. Copyright law doesn't prohibit decompilation, the prohibition is just a contract term you agree to as a condition of getting the software when you buy the product under shrink wrap in a store, or accept a ``clickwrap license'' on line. Copyright is just leverage for taking even more away from users.
The GPL, on the other hand, subtracts from copyright rather than adding to it. The license doesn't have to be complicated, because we try to control users as little as possible. Copyright grants publishers power to forbid users to exercise rights to copy, modify, and distribute that we believe all users should have; the GPL thus relaxes almost all the restrictions of the copyright system. The only thing we absolutely require is that anyone distributing GPL'd works or works made from GPL'd works distribute in turn under GPL. That condition is a very minor restriction, from the copyright point of view. Much more restrictive licenses are routinely held enforceable: every license involved in every single copyright lawsuit is more restrictive than the GPL.
Because there's nothing complex or controversial about the license's substantive provisions, I have never even seen a serious argument that the GPL exceeds a licensor's powers. But it is sometimes said that the GPL can't be enforced because users haven't ``accepted'' it.
This claim is based on a misunderstanding. The license does not require anyone to accept it in order to acquire, install, use, inspect, or even experimentally modify GPL'd software. All of those activities are either forbidden or controlled by proprietary software firms, so they require you to accept a license, including contractual provisions outside the reach of copyright, before you can use their works. The free software movement thinks all those activities are rights, which all users ought to have; we don't even want to cover those activities by license. Almost everyone who uses GPL'd software from day to day needs no license, and accepts none. The GPL only obliges you if you distribute software made from GPL'd code, and only needs to be accepted when redistribution occurs. And because no one can ever redistribute without a license, we can safely presume that anyone redistributing GPL'd software intended to accept the GPL. After all, the GPL requires each copy of covered software to include the license text, so everyone is fully informed.
Despite the FUD, as a copyright license the GPL is absolutely solid. That's why I've been able to enforce it dozens of times over nearly ten years, without ever going to court. Next month, I'll explain how enforcement is really done.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
This essay was originally published in LinuxUser.
Free Software Matters:
Enforcing the GPL, II
Eben Moglen*
September 10, 2001
Last month I described in general terms the legal theory of the GPL. This month, I'd like to explain how, contrary to the fear, uncertainty and doubt sown by Microsoft, the license is actually enforced.
Much murmuring has been going on in recent months to the supposed effect that the absence of judicial enforcement, in US or other courts, somehow demonstrates that there is something wrong with the GPL, that its unusual policy goal is implemented in a technically indefensible way, or that the Free Software Foundation, which authors the license, is afraid of testing it in court. Precisely the reverse is true. We do not find ourselves taking the GPL to court because no one has yet been willing to risk contesting it with us there.
So what happens when the GPL is violated? With software for which the Free Software Foundation holds the copyright (either because we wrote the programs in the first place, or because free software authors have assigned us the copyright, in order to take advantage of our expertise in protecting their software's freedom), the first step is a report, usually received by email to license-violation@gnu.org. We ask the reporters of violations to help us establish necessary facts, and then we conduct whatever further investigation is required.
We reach this stage dozens of times a year. A quiet initial contact is usually sufficient to resolve the problem. Parties thought they were complying with GPL, and are pleased to follow advice on the correction of an error. Sometimes, however, we believe that confidence-building measures will be required, because the scale of the violation or its persistence in time makes mere voluntary compliance insufficient. In such situations we work with organizations to establish GPL-compliance programs within their enterprises, led by senior managers who report to us, and directly to their enterprises' managing boards, regularly. In particularly complex cases, we have sometimes insisted upon measures that would make subsequent judicial enforcement simple and rapid in the event of future violation.
In approximately a decade of enforcing the GPL, I have never insisted on payment of damages to the Foundation for violation of the license, and I have rarely required public admission of wrongdoing. Our position has always been that compliance with the license, and security for future good behavior, are the most important goals. We have done everything to make it easy for violators to comply, and we have offered oblivion with respect to past faults.
In the early years of the free software movement, this was probably the only strategy available. Expensive and burdensome litigation might have destroyed the FSF, or at least prevented it from doing what we knew was necessary to make the free software movement the permanent force in reshaping the software industry that it has now become. Over time, however, we persisted in our approach to license enforcement not because we had to, but because it worked. An entire industry grew up around free software, all of whose participants understood the overwhelming importance of the GPL--no one wanted to be seen as the villain who stole free software, and no one wanted to be the customer, business partner, or even employee of such a bad actor. Faced with a choice between compliance without publicity or a campaign of bad publicity and a litigation battle they could not win, violators chose not to play it the hard way.
We have even, once or twice, faced enterprises which, under US copyright law, were engaged in deliberate, criminal copyright infringement: taking the source code of GPL'd software, recompiling it with an attempt to conceal its origin, and offering it for sale as a proprietary product. I have assisted free software developers other than the FSF to deal with such problems, which we have resolved--since the criminal infringer would not voluntarily desist and, in the cases I have in mind, legal technicalities prevented actual criminal prosecution of the violators--by talking to redistributors and potential customers. ``Why would you want to pay serious money,'' we have asked, ``for software that infringes our license and will bog you down in complex legal problems, when you can have the real thing for free?'' Customers have never failed to see the pertinence of the question. The stealing of free software is one place where, indeed, crime doesn't pay.
But perhaps we have succeeded too well. If I had used the courts to enforce the GPL years ago, Microsoft's whispering would now be falling on deaf ears. Just this month I have been working on a couple of moderately sticky situations. ``Look,'' I say, ``at how many people all over the world are pressuring me to enforce the GPL in court, just to prove I can. I really need to make an example of someone. Would you like to volunteer?''
Someday someone will. But that someone's customers are going to go elsewhere, talented technologists who don't want their own reputations associated with such an enterprise will quit, and bad publicity will smother them. And that's all before we even walk into court. The first person who tries it will certainly wish he hadn't. Our way of doing law has been as unusual as our way of doing software, but that's just the point. Free software matters because it turns out that the different way is the right way after all.
* Eben Moglen is professor of law and legal history at Columbia University Law School. He serves without fee as General Counsel of the Free Software Foundation. You can read more of his writing at moglen.law.columbia.edu.
©Eben Moglen [Send a comment] [PostScript] [PDF]
2001-09-18 Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
"Sen. Hollings says he stands for American values but he tries to bring Big Brother into your house. Sen. Hollings says that big government should intrude into seeing what you watch and listen to on your television, computer, and stereo system."
Why not build a bridge? There's a 8 mile bridge over icy waters in Canada
e x.htm
http://www.confederationbridge.com/en/accueil/ind
it's on the front of C|Net news.com as well, they own com.com...
The detector software (Ad-Aware, WHo's watcthing me.., etc.) will have to provide a "boot disk" option, like many virus scanners do, if they want to keep up... all you have to do then is create the disk on another computer, write protect it, and start up to scan for spyware.
If you're a Canadian, you have the right to submit your objection to these proposals, and there's a hearing to be held May 23.
Download the document, print it out, and submit your comments if you so care.
Tempest refers to stray electromagnetic radiation that is "read" by appropriate radio equipment nearby, this article is about stray light emissions that are picked up by a photosensor.
Mirror please, this is important stuff!
So you shouldn't have signed a lease for $1500 a month working in an industry that everyone knew was unstable. Declare bankruptcy and be done with it.
The guy can get off pogey and go work at McDonald's. No sympathy whatsoever. He'd better not get any better treatment than they'd give a typical blue collar laborer.
Since overclocking often results in problems like FPU errors (just try running one of those intensive distributed computing projects and getting proper results) why bother?
Provided the ship isn't going too far (i.e. 20 light years), it could still receive transmissions from earth, like news, including audio and video perhaps, so that the language would remain constant.