RE: [OT] Re: How do you.....

new topic     » goto parent     » topic index » view thread      » older message » newer message

On 3 Jun 2003, at 20:45, C. K. Lester wrote:

> 
> 
> > > > Having a "3rd party" OS or socks driver simply means your
> > > > packets will be refused from internet routers with a error
> > msg along the
> > > lines
> > > > of "if we can't read it, you can't use our internet."
> > >
> > > What is the definition of "we can't read it?" Does that mean if
> > > they can't understand it?
> >
> > I don't know how to explain "read" to you. Hmm,,,, maybe
> > "decypher the bits so they may be printed out as language
> > tokens, and understood in mental images like a spoken word"?
> 
> I'm trying to understand what's being implied. So what if I send a message
> in Chinese or encoded somehow and they can't make it out? That means they're
> not
> going to let it through?!

Not quite exactly, but it could come to that (see Carnivore and Echelon). The 
more immeadiate situation is one of the internet packets of info, how the 
digital transmission bits are formatted, are arrainged. Each packet is a self-
contained database. If the fields are scrambled, or are formatted in the "old" 
way, they won't make sence, and won't go thru. For instance, if the new 
destination ip field falls on the old length and file type fields, or the new 
packet order field falls on the old source ip field.

> > > > If an app passes DRM...
> > >
> > > What does it mean to pass "DRM?"
> >
> > "pass DRM" = the OS will permit the application to run, or permit the
> > application to open a specified file. This means the file is
> > signed with a unique legally verifiable source signature, and the
> > OS knows it is legal too, and the file said it's ok for you to open it.
> 
> So if I want to send a Word document anonymously that's been encoded, are
> you saying DRM might not let it through?

Correct. There won't be any anonymity. Most likely, the first systems online 
will prompt the user (you sent it to) if they want to bypass "protection" and 
read it. Later systems, or systems you do not have root permissions on, will 
refuse to open the Word document. The computer may even refuse to accept 
it as email. That's the whole point of Palladium, to control what you have 
access to. The sender will haveto run a approved OS, and so will the 
recipient. If you run a DRM application, write a document, and send it to 
someone running an Amiga, or me on win95, or Irv on *nix, we will not be 
able to read it, even in the same application, unless you can code it to "not 
protected". And if thustly coded, and you send it to euman, his DRM box 
may refuse it. If euman writes an Eu program and compiles it on his DRM 
box, you will not be able to run it on your DRM box unless he sets it to allow 
it. Irv and i may be totally out of luck. RDS will need to get M$'s
certification,
and give M$ the source code, and pay big bucks,, or all DRM boxes will 
initially refuse to allow Eu to run, untill the owner drops all "protection".
The
box will notify MS protection was dropped. 

Getting back to the first question, i expect the internet will someday refuse 
to allow non-DRM data to pass, whether a human reads it or not, whether it 
is 1024bit encrypted or not. The server will log it, and and automatically 
checked for use patterns (like spamming, or viewing only porn urls). The 
DRM will be OS-specific, with the owner's unique id, and data about the 
computer glued onto each and every packet. Packet kiddies will lose out, 
abuse will be traceable, or simply not go anywhere. Open proxies will 
disappear. Anonymous web browsing will be history. Sharing exe's will be 
nostalgia. Altering binaries will result in one that won't run on a DRM box, 
even if you could open the binary. And if you want to watch the dvd of 
Matrix4 three times, you'll haveto re-buy it.

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu