linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: victor <ixnay@infonegocio.com>
To: "D. Stimits" <stimits@idcomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re[2]: Linux 2.2.20pre10
Date: Tue, 23 Oct 2001 02:37:57 +0200	[thread overview]
Message-ID: <133701065418.20011023023757@infonegocio.com> (raw)
In-Reply-To: <3BD4B06D.1A8DD39F@idcomm.com>
In-Reply-To: <Pine.LNX.4.30.0110221345131.17672-100000@anime.net> <017601c15b3e$51b12b70$2a040a0a@zeusinc.com> <20011023004947.U25701@khan.acc.umu.se> <021a01c15b51$62958810$2a040a0a@zeusinc.com> <3BD4B06D.1A8DD39F@idcomm.com>

Hello D.,

Tuesday, October 23, 2001, 1:49:01 AM, you wrote:

DS> Tom Sightler wrote:
>> 
>> > > Not forgotten, just trying to understand relevance.  How do these cases,
>> > > which all revolve around breaking commercial products and cause damage
>> to
>> > > the corporations that push them, apply to security in the open source
>> Linux
>> > > kernel to which the public is given all rights.
>> >
>> > For me, DeCSS is an application that has a purpose for watching DVD:s
>> > when I boot my G4 into Linux instead of MacOS.
>> 
>> For me too, but in other people's opinion it's a tool for pirates (I don't
>> share this opinion, however, I can see how some people, who don't understand
>> the difference, might have this opinion).  However, I don't think that a
>> security exploit in an open sourced OS is likely to be a "curcumvention
>> device" to even clueless people.
>> 
>> > And even those that actually use DeCSS only to gain their "copyright"
>> > (that is, provide you with your right to copy what you have purchased,
>> > for backup-purposes, for instance) or indeed those that illegaly copy
>> > DVDs, seldom do so to break commercial products and cause damage to the
>> > corporations that push them.
>> 
>> Agreed, but's that's how these corporations (or coporate representatives)
>> managed to get these cases to court.  However, I fail to see who is going to
>> be the prosecutor in the case of a security exploit against the open source
>> Linux kernel.  In every one of these cases, DeCSS, SDI, and eBook, the
>> encryption that was hacked was put in place by the companies specifically to
>> protect the copyrighted work.  The Linux kernel provides general access
>> controls and does not meet the following DMCA requirement to be a copyright
>> protection system:
>> 
>> "(B) a technological measure "effectively controls access to a work" if the
>> measure, in the ordinary course of its operation, requires the application
>> of information, or a process or a treatment, with the authority of the
>> copyright owner, to gain access to the work."
>> 
>> The part that is missing is the "authority of the copyright owner" portion.
>> In the case of CSS, SDI, and eBook, the copyright owners all specifically
>> allow access to the information only when using authorized means of viewing
>> the work.  Last I checked no copyright owner has said that ACL's are an
>> authorized means.

DS> SSSCA grants all this. SSSCA would have enormous impact here. If SSSCA
DS> passes, look out.
DS> http://www.newsforge.com/article.pl?sid=01/10/19/1546246&mode=thread


we would call it $$$ca :(((
Researchers and hobbyists seeking new uses for innovative technology might well find their experimentation and prototypes to be criminal under this law.
Other countries will not have similar requirements in their laws and may actively fear the imposition of anti-copy technologies
like always imposing their laws to the world
i expect that Europe dont accept that, but what i would expect if
Spain's president is one of the friend of USA...

DS> D. Stimits, stimits@idcomm.com

>> 
>> This is my main argument why I think Alan is safe to post security related
>> information in changelogs.  I just don't think there is any way for someone
>> to interpret this law to mean that posting that information is illegal.  Of
>> course, if he still doesn't want to I respect that opinion as well, but I'm
>> sure willing to do it.
>> 
>> > As for the Sklyarov-case, I'm pretty sure he'd been arrested even if his
>> > program had been an open source program under the GPL, freely
>> > distributed etc.
>> 
>> I would tend to agree, because Adobe initially filed the complaint for
>> damages he could have been arrested under the civil action.  However, once
>> Adobe agreed to drop the issue (I'm not sure they did, but it is my
>> understanding that they have) it didn't matter much, because they are not
>> required to pursue the criminal portion, the government alone can pursue it
>> from there.
>> 
>> BTW, I'm not trying to argue that the cases which use the DMCA are valid in
>> any way, I'm totally againts all of them as they definately impose on my
>> fair use rights, which is why I have never purchased an eBook, don't own a
>> DVD player (actually not 100% true, I have a DVD player in my laptop and
>> have used it for loading software and playing around with DVD playback under
>> Linux using some borrowed DVD's), and don't own music with any SDI
>> watermarks (that I know of).  If companies don't want to grant me fair use,
>> I don't want their products.
>> 
>> Later,
>> Tom
>> 
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
DS> -
DS> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
DS> the body of a message to majordomo@vger.kernel.org
DS> More majordomo info at  http://vger.kernel.org/majordomo-info.html
DS> Please read the FAQ at  http://www.tux.org/lkml/



-- 
Best regards,
 victor                            mailto:ixnay@infonegocio.com


  parent reply	other threads:[~2001-10-23  0:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 18:27 Linux 2.2.20pre10 Wayne.Brown
2001-10-22 18:38 ` Nick LeRoy
2001-10-22 18:40 ` Alexander Viro
2001-10-22 19:23   ` Paul Fulghum
2001-10-22 19:14 ` Tudor Bosman
2001-10-22 19:42   ` Mike Fedyk
2001-10-22 19:55   ` Tom Sightler
2001-10-22 20:42     ` Alan Cox
2001-10-22 20:45       ` Dan Hollis
2001-10-22 21:12         ` Tom Sightler
2001-10-22 21:35           ` Dan Hollis
2001-10-22 22:49           ` David Weinehall
2001-10-22 23:29             ` Tom Sightler
2001-10-22 23:49               ` D. Stimits
2001-10-23  1:32                 ` Tom Sightler
2001-10-23  0:37               ` victor [this message]
2001-10-22 21:04       ` Tom Sightler
2001-10-22 20:28   ` Alan Cox
2001-10-24 19:00   ` Riley Williams
2001-10-22 23:19 ` Luigi Genoni
2001-10-22 22:15 Sam Varshavchik
2001-10-22 22:37 ` Re[2]: " victor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=133701065418.20011023023757@infonegocio.com \
    --to=ixnay@infonegocio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stimits@idcomm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).