Apparently if any of your companies Intellectual property uses Verisigns DNS they own all your patents now relating to it once youve been re-directed to their sitefinder site accoding to their terms of agreement.
Except as otherwise set forth herein, all right, title and interest in and to all, [snip] (vi) all other intellectual property, proprietary rights or other rights related to intangible property which are used, developed, comprising, embodied in, or practiced in connection with any of the VeriSign services identified herein ("VeriSign Intellectual Property Rights") are owned by VeriSign or its licensors, and you agree to make no claim of interest in or ownership of any such VeriSign Intellectual Property Rights.
The full text is here http://sitefinder.verisign.com/terms.jsp Under the 11) Ownership section.
I think ALL GOVERNMENT software should be reviewed for PATENT INFRINGMENT. And of course, the infringing software must be removed after being found. Once they see how much they are screwed I think they would be forced to fix the patent system. Thats the ONLY way, I ever seen the software patent system changing.
Your development team should not be writing code for a single task. Code for a specific task / requirement is by its very nature, bug filled code. All code should be written to be re-usable code. Once the re-usable, library routines are written and debugged, simply reuse that code as it will not introduce additional bugs into the system. The only part of the application that would not be library routines is the "glue" code that maps the interface to those routines.
It would be fair practice and equally as competitive it the rest of the sites on the internet block IE now. I would hope that
Sun, AOL, IBM, and other large corps wouldblock IE and ask the user to upgrade.
I believe it would be in the interest of the crypto community for you to write a a clear
and concise document that even a congressman could read on the topic of cryptology.
Then we as a community could digitially sign it, and send it to our congress-persons as a petition.
The main topics you should cover would be:
1) What encryption does FOR us.
2) Who uses encryption for good reasons.
3) The problems with weakened encryption.
4) Possible economic impacts due to loss of
trusted communications.
5) How weakened encryption would be forced upon
our enemies( or how it couldnt be).
6) Synonyms like you implied to better qualify
encryption, such as "envelopes", or secruity
measures that re-iterate just what it is
that they would be weakening.
7) Point out all the ways the government ALREADY
has for "Breaking" encryption. Such as key-
stroke loggers, intercepting keys,
intelligence operations,etc.... and WHY they
are BETTER MEANS than weakening the encryption.
8) Point out what other tools they should have
taken away if they want weakened encryption,
such as key stroke loggers. Whats the point of
key stroke loggers if you dont need the
password?
Data compression is NOT data encryption but it can be impossible to read it.
Most compressed data streams rely on every byte of data sent before it to de-compress it. So if you didnt intercept the ENTIRE compressed archive its totally useless and its HIGHLY likely that you cant de-compress anything in it.
Would this mean that all but a few forms of data compression would be deemed illegal because it COULD be used a form of securing data? I hope not, but it may be a consequence.
Would all forms of protecting information require a backdoor or just encryption algorythms?
For example, a password protected Word Document?
Its not "encrypted" but its viewing is restricted.
The current state of the art in compression technology is benchmarked by Jeff Gilchrist at his site which includes current benchmarks in image compression technology too.
Slashdot Mirror
Why cant we just bring a community based replacement service online and blacklist verisigns root dns services?
Apparently if any of your companies Intellectual property uses Verisigns DNS they own all your patents now relating to it once youve been re-directed to their sitefinder site accoding to their terms of agreement.
Except as otherwise set forth herein, all right, title and interest in and to all, [snip] (vi) all other intellectual property, proprietary rights or other rights related to intangible property which are used, developed, comprising, embodied in, or practiced in connection with any of the VeriSign services identified herein ("VeriSign Intellectual Property Rights") are owned by VeriSign or its licensors, and you agree to make no claim of interest in or ownership of any such VeriSign Intellectual Property Rights.
The full text is here http://sitefinder.verisign.com/terms.jsp
Under the 11) Ownership section.
I think ALL GOVERNMENT software should be reviewed for PATENT INFRINGMENT. And of course, the infringing software must be removed after being found. Once they see how much they are screwed I think they would be forced to fix the patent system. Thats the ONLY way, I ever seen the software patent system changing.
Your development team should not be writing code for a single task. Code for a specific task / requirement is by its very nature, bug filled code. All code should be written to be re-usable code. Once the re-usable, library routines are written and debugged, simply reuse that code as it will not introduce additional bugs into the system. The only part of the application that would not be library routines is the "glue" code that maps the interface to those routines.
I am willing to pay dues to have lawyers
fight for our rights and to reverse the
defacto industry "standard" contracts.
Is there an IT/IS Union in the US I could
join?
It would be fair practice and equally as competitive it the rest of the sites on the internet block IE now. I would hope that
Sun, AOL, IBM, and other large corps wouldblock IE and ask the user to upgrade.
This is for PKZ.
I believe it would be in the interest of the crypto community for you to write a a clear
and concise document that even a congressman could read on the topic of cryptology.
Then we as a community could digitially sign it, and send it to our congress-persons as a petition.
The main topics you should cover would be:
1) What encryption does FOR us.
2) Who uses encryption for good reasons.
3) The problems with weakened encryption.
4) Possible economic impacts due to loss of
trusted communications.
5) How weakened encryption would be forced upon
our enemies( or how it couldnt be).
6) Synonyms like you implied to better qualify
encryption, such as "envelopes", or secruity
measures that re-iterate just what it is
that they would be weakening.
7) Point out all the ways the government ALREADY
has for "Breaking" encryption. Such as key-
stroke loggers, intercepting keys,
intelligence operations,etc.... and WHY they
are BETTER MEANS than weakening the encryption.
8) Point out what other tools they should have
taken away if they want weakened encryption,
such as key stroke loggers. Whats the point of
key stroke loggers if you dont need the
password?
Data compression is NOT data encryption but it can be impossible to read it.
Most compressed data streams rely on every byte of data sent before it to de-compress it. So if you didnt intercept the ENTIRE compressed archive its totally useless and its HIGHLY likely that you cant de-compress anything in it.
Would this mean that all but a few forms of data compression would be deemed illegal because it COULD be used a form of securing data? I hope not, but it may be a consequence.
Would all forms of protecting information require a backdoor or just encryption algorythms?
For example, a password protected Word Document?
Its not "encrypted" but its viewing is restricted.
How 'bout a passworded pkzip file?
The current state of the art in compression technology is benchmarked by Jeff Gilchrist at his site which includes current benchmarks in image compression technology too.