«

"Julia Briggs" <> writes:

>I think it's going to be impossible to implement any sort broad
>reaching protection with every OS -- because it's too late. That is,

Sure. Burn the CD. even a few hundred degrees should do.
A CD is MEANT usually to be read. If a program can read it, it can copy it.
This is like asking "I am publishing a book. Is there any way I can prevent
the readers from copying out phrases from the book?"


>too many operating systems have existed for too many years, at
>different version levels, with mass userbases, that such a feature
>wouldn't deter someone from popping a CD into a older machine? .....
>but what if some modification to the CD could cause it to error on
>"most" operating systems to deter casual duplication of files?


As I said, make it unreadable to all.


>Not quite the same, but see:
>http://www.cdmediaworld.com/hardware...otect_cd.shtml

>Apparently someone figured out a minor edit to the CD that causes it to
>copy a blank version of itself using popular copiers like NERO and
>EasyCD.

>No real 100% way to protect a CD against all attacks in this world, but
>maybe some other method like this can deter 99% of people from
>drag-and-dropping a file away from the CD folder. I know some people
>drag and drop away from CD folders into media players -- but I imagine
>there is a way.

>For the life of me I can't find the thread, but I clearly read in a old
>2000 posting that, I believe it was Sony, had disc-copy protection on
>some music CD's that prevented the user from drag-and-dropping files
>away from the CD!

>......Any existing commercial CD protection tools or ideas come to mind
>by anyone to achieve this feat? Julia

On 2005-09-11, Julia Briggs <> blabbed:
> Is there a hack, software utility or method to prevent a casual user
> from copying a file from a CD? thanks! Julia

The simple answer is: no.

There is no real way to prevent duplication. Music cds are not directly
accessable with filenames generally.... they have to be ripped. Other
types of cds generally you can just copy them off there is no way to
prevent that... if your program has to be able to read the disk, then
anything has to be able to read the disk. You can put copy protection
in your program to some degree (safedisk, etc) but those are easily
bypassable to... and they dont prevent copying from the disk they just
prevent the program from running if its not a legitimate copy of the
disk. shrug. copy protection is a waste of time... its a simple patch
for most people wanting to break it and it only annoys average
non-technical usrs who have a drive that doesnt like it or something
similar. Unique serial numbers are a more effective system or a
hardware key of some kind, but even those are abusable.

Seems to me like including a virtual machine along with the files might do
it


"Julia Briggs" <> wrote in message
news: oups.com...
> Is there a hack, software utility or method to prevent a casual user
> from copying a file from a CD? thanks! Julia
>

Bowgus wrote:
> Seems to me like including a virtual machine along with the files might do
> it
>
>
> "Julia Briggs" <> wrote in message
> news: oups.com...
>
>>Is there a hack, software utility or method to prevent a casual user
>>from copying a file from a CD? thanks! Julia
>>
>
>
>

Manually editing TOC for the file concerned to indicate a billion byte
file (references address space not physically on CD) stops many casual
copiers, though if someone is used to such methods the CD can still be
copied by the astute. This can cause other issues depending on how you
use the file.

You can call the direct address from the disk without going through the
TOC but if you call the file via the TOC an error will occur. This also
requires the data to be written to the specific address location.

To make it more difficult to duplicate the disk you can create an
inappropriate sector length that will cause copiers like Roxio and Nero
to fail, but you can induce incompatibility with non-multi-session
capable drives.

These methods require direct editing of the master media.

Winged

On 12 Sep 2005 11:21:37 -0700, Julia Briggs <> wrote:
> I think it's going to be impossible to implement any sort broad
> reaching protection with every OS -- because it's too late. That is,
> too many operating systems have existed for too many years, at
> different version levels, with mass userbases, that such a feature
> wouldn't deter someone from popping a CD into a older machine? .....
> but what if some modification to the CD could cause it to error on
> "most" operating systems to deter casual duplication of files?

All music CDs require software support for "drag and drop" of music
files because there really is no file system or files on a music CD.
Things have evolved so that the software is more closely integrated
and you don't notice the complexity.

IMO even if newer and more complex protection methods are used, if an
expert learns to crack the protection, there are few technical obstacles
to making it easy for a "drag and drop" implementation to be produced
that even casual Windows fans can use.

Yes there are legal obstacles to distributing such software; namely the
anti circumvention provisions of the DMCA, but none of that seems to have
kept software for copying DVDs out of the hands of the public.

Isaac

Hi Winged, could you simply elaborate a recommended tool and approach
to finding a file TOC? Thanks so much. Anything else you can share
regarding the inappropriate sector length would be excellent too.

I am hoping if Winged or another super-brain out there can respond to
the possibility he suggests below. Thank you so much. Kindest regards,
Julia

#
Winged/
Manually editing TOC for the file concerned to indicate a billion byte
file (references address space not physically on CD) stops many casual
copiers, though if someone is used to such methods the CD can still be
copied by the astute. This can cause other issues depending on how you
use the file.

You can call the direct address from the disk without going through the
TOC but if you call the file via the TOC an error will occur. This
also requires the data to be written to the specific address location.

To make it more difficult to duplicate the disk you can create an
inappropriate sector length that will cause copiers like Roxio and Nero
to fail, but you can induce incompatibility with non-multi-session
capable drives.

These methods require direct editing of the master media.

Winged

Here's an idea .. try "Google", "CD protection" ... 1st hit

Julia Briggs wrote:
> I am hoping if Winged or another super-brain out there can respond to
> the possibility he suggests below. Thank you so much. Kindest regards,
> Julia
>
> #
> Winged/
> Manually editing TOC for the file concerned to indicate a billion byte
> file (references address space not physically on CD) stops many casual
> copiers, though if someone is used to such methods the CD can still be
> copied by the astute. This can cause other issues depending on how you
> use the file.
>
> You can call the direct address from the disk without going through the
> TOC but if you call the file via the TOC an error will occur. This
> also requires the data to be written to the specific address location.
>
> To make it more difficult to duplicate the disk you can create an
> inappropriate sector length that will cause copiers like Roxio and Nero
> to fail, but you can induce incompatibility with non-multi-session
> capable drives.
>
> These methods require direct editing of the master media.
>
> Winged
>
Well the billion byte file for example can not be dragged and
dropped..error will occur. But as stated the usefulness of the file is
limited as the address space must be directly accessed.

The second method does not prevent drag and drop but makes media
duplication much more difficult especially if programmatic calls are
made in the software.

Another method to prevent drag and drop of the file is to remove it from
the TOC. This file can be direct accessed by direct addressing the
location directly however it does not prevent disk duplication, and
standard file access methods that go though the TOC will fail.

I know of no method that would prohibit a legal TOC file from being
dragged and dropped in any of the various CD formats.

Winged

Winged

If file(s) on a CD or DVD configured to auto-load is converted to a
billion byte+, would it run? Assuming Windows platforms here.