Re: [OS:N:] RFC for Free software consent based content mangement (was Reply to multiple posts at once)

On Thu, 2003-08-14 at 14:52, James Michael DuPont wrote:
> --- Jeremy Hogan <jhogjhoganhredhat> wrote:
> > 
> > > Ok, Ok you see no other way to pay for your morgmorgagen to take
> > away
> > > the rights of the students to view the source code of the software
> > and
> > > make other viewing tools? 
> > 
> > You see no other way to address this issue, perhaps by working on
> > building your project instead of talking about it, than by picking on
> > producers of content? 
> 
> Your right. 
> 
> I am going to stop making any more jabs at the hard working authors
> here. I am sorry that my tountounge out of control, my criticism is
> distracting from my points and giving people a reason to not address
> the valid points at hand.
> 
> This entire discussion has outlined a very clear common goal, on that
> you would agree to as well, I hope.
> 
> To determine the architecture of the content distribution and rights
> management that will allow authors to make an honest buck without
> violating the users rights.
> 
> Lets say that we have some content that an author worked hard on, and
> it should be distributed to people who decide that paying a reasonable
> fee.
> 
> Now the one issue is that even if the users should have the right to
> examine the source code of the software, we still need a way to prevent
> them from extracting the content out of that software. 
> 
> If you allow the user to modify the viewing software as to create an
> human readable and machine processable of the content instead of
> displaying it, then you are opening up the content for further
> duplication. Now we are precluding screen shots and OCR software here.
> Lets say that you want to deliver a rastrasterizedy of the content to
> the user at an agreed upon resolution. Vector graphics would again
> allow  too much export control.
> 
> So we have an agreement between a content provider and a content
> consumer for a delivery of a certain amount of content that meets a
> certain level of quality to a viewer that limits the users rights in a
> predefined manner.
> 
> Now, the viewer cannot store the content in a internal data format that
> is readable by an debugger, because it would be too easy to snarf that
> data out.
> 
> So, I think we can solve this problem very simply : You need to trust
> that the user will only use an agreed upon version of the viewer
> software.  This software can be free software, and the full source code
> may be made available, but the content provider does not agree to
> provide the content to any but an specified and verified set of modules
> to the user.
> 
> So I proposed the following architecture :
> 
> 1. The users are to be validated by a chip-card system, each user must
> have a way to authenticate their identity using a card issued by the
> content provider or a certificate authority. Simple PGP PGP SSH
> certificate can also be agreed here.
> 
> 2. The users agree to have a free software client module installed that
> is of a specified version. This software is able to make a network
> connection to the content provider and send a digitally signed and
> encrypted signature of itself to the content provider by a secure
> channel. This creates a secure session that can only be understood by
> the client module. The user agrees that he does not have the right to
> intercept this content which uses open and free software that he can
> inspect on his leisure. The session however is only good for one set of
> package, because the user might swap out the software once the session
> is set up. Hardware based checksumming might help speed up this
> signature process. BSD has such a software signature built in as well.
> The user agrees to allow the server to re-check/audit the validity of
> the client software on its leisure on a predefined interval,that way
> the server administrator  and users can agree on a set of security
> levels that are appropriate for the given application performance
> requirements.
> 
> 3. The user uses this session to request content that is sent securely
> to him/her.  The content is encrypted with an agreed upon encryption
> standard that will prevent the user from viewing the content. Only the
> client software session, given an authentication token from the
> provider and from the client will be able to for one time be able to
> decode the content. The software then deletes that content according to
> the agreed procedure.
> 
> 4. The user can then view the rastrasterizedge. That image could also
> be  water-marked and Id-ed. The agreement between the content provider
> and the user may define various rules preventing the removal of the
> various security water-marks. Of course the user can take that one
> raster and distribute it illegally. There is nothing that any of the
> DRM DRM do to prevent that.
> 
> 
> You see, this is a consent based security system that requires no
> freedoms are removed from the user. The content provider reserves the
> right to refuse delivery of content to any other version of the
> software, the client however has the freedom to modify this software
> and submit it to content providers for certification.
There is just one problem with this idea.  What company is going to take
the time to certify every, or even any, of the software sent them.  It
ain't going to happen.

Johnnie

> 
> I think such an consent based content management is much saner than
> using non-free file formats and non-free software.
> 
> What do you think?
> 
> =====
> James Michael DuPont
> http://introspector.sourceforge.net/
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> 
> 
> _______________________________________________
> Subscription and Archive: https://www.redhat.com/mailman/listinfo/open-source-now-list/
> -
> For K12OS technical help join K12OSN:
> <https://www.redhat.com/mailman/listinfo/k12osn>



_______________________________________________
Subscription and Archive: https://www.redhat.com/mailman/listinfo/open-source-now-list/
-
For K12OS technical help join K12OSN:
<https://www.redhat.com/mailman/listinfo/k12osn>