My take on his "revolutionary" idea is that he has the idea of taking the OTP and using the XORed value of the plaintext and the OTP to determine the next offset value to use for the OTP. Effective, but still more or less an OTP. Plaintext attacks are slightly less dangerous, but still an OTP.
The biggest problem is turning the OTP into a "many-time pad" is that it's effectiveness is degraded each time it is used. It has been some years since I have checked out the sci.crypt groups for the most recent fads in encryption, but something tells me this idea has popped up more than once. If it hasn't, let this serve as the prior art to all future patents.
The proper use of the one-time pad requires what the name implies, one-time.
I had been browsing at 4 and the only comments I had seen were vaporware, digital lacks control, and obsolete concept. In the consumer market that may be the case, but in the professional market it is a different story. I have been looking into the Kodak DCS Pro Back 645 which is designed for the Mamiya and Contax 645 camera bodies. Take a look at
This is not vaporware, an obsolete concept, nor does it lack control since it could be used with any of the existing lenses, extenders, bellows, etc. that are made for these cameras. It would seem the correct answer for the question posed is "Yes, it is possible to turn a standard camera into a digital camera and performance is good (ISO 100-400, 36 bit color, 16 megapixel sensor, etc.)." The only caveats are that it is made for professional high end equipment and it costs more than your car.
This is what gives VB a bad name...
on
KBasic
·
· Score: 2
Arrays. Say you've got a function which returns an array of some sort - let's say an array of variants to make it easy. How do you return an array of 0 items cleanly?
No problem. Have you thought of checking to see if the array is empty? Or raising an error in the function (seems like 0 elements would be an error condition in most cases). Or maybe using error handling...
Object-Orientation. Ever attempted type-safe inheritance or polymorphism in VB? Variants do not count.
There are some OO issues, but have you ever looked at the Implements keyword?
String Concatenation.
VB does do a poor job of string concatenation - but there are ways around that. The problem lies in the memory management involved in resizing the string. The solution is to create a fixed length string of desired size and then replace the contents of the string with your data.
...and I code in it (almost) every day.
That is a really sad statement. Maybe you should start trying to improve your skills and stop complaining. It is possible to write poor code in any language. Unfortunately, the ease of use of VB allows below average programmers to pass themselves off as lead developers when in fact they have a minimal grasp of the language. A good good developer needs to have a grasp of the the way the language operates. A good understanding and knowledge of the strengths and weaknesses of any language is essential. If you don't have the patience to learn the language fully, perhaps you should switch to another language or stop calling yourself a programmer. VB has a bad reputation as it is, it doesn't any more below average programmers writing buggy apps...
Slashdot Mirror
My take on his "revolutionary" idea is that he has the idea of taking the OTP and using the XORed value of the plaintext and the OTP to determine the next offset value to use for the OTP. Effective, but still more or less an OTP. Plaintext attacks are slightly less dangerous, but still an OTP.
The biggest problem is turning the OTP into a "many-time pad" is that it's effectiveness is degraded each time it is used. It has been some years since I have checked out the sci.crypt groups for the most recent fads in encryption, but something tells me this idea has popped up more than once. If it hasn't, let this serve as the prior art to all future patents.
The proper use of the one-time pad requires what the name implies, one-time.
Moderators, please mod up this parent.
c ts/cameras/dcsProBack645/features.jhtml
I had been browsing at 4 and the only comments I had seen were vaporware, digital lacks control, and obsolete concept. In the consumer market that may be the case, but in the professional market it is a different story. I have been looking into the Kodak DCS Pro Back 645 which is designed for the Mamiya and Contax 645 camera bodies. Take a look at
http://www.kodak.com/global/en/professional/produ
This is not vaporware, an obsolete concept, nor does it lack control since it could be used with any of the existing lenses, extenders, bellows, etc. that are made for these cameras. It would seem the correct answer for the question posed is "Yes, it is possible to turn a standard camera into a digital camera and performance is good (ISO 100-400, 36 bit color, 16 megapixel sensor, etc.)." The only caveats are that it is made for professional high end equipment and it costs more than your car.
Arrays. Say you've got a function which returns an array of some sort - let's say an array of variants to make it easy. How do you return an array of 0 items cleanly?
...and I code in it (almost) every day.
No problem. Have you thought of checking to see if the array is empty? Or raising an error in the function (seems like 0 elements would be an error condition in most cases). Or maybe using error handling...
Object-Orientation. Ever attempted type-safe inheritance or polymorphism in VB? Variants do not count.
There are some OO issues, but have you ever looked at the Implements keyword?
String Concatenation.
VB does do a poor job of string concatenation - but there are ways around that. The problem lies in the memory management involved in resizing the string. The solution is to create a fixed length string of desired size and then replace the contents of the string with your data.
That is a really sad statement. Maybe you should start trying to improve your skills and stop complaining. It is possible to write poor code in any language. Unfortunately, the ease of use of VB allows below average programmers to pass themselves off as lead developers when in fact they have a minimal grasp of the language. A good good developer needs to have a grasp of the the way the language operates. A good understanding and knowledge of the strengths and weaknesses of any language is essential. If you don't have the patience to learn the language fully, perhaps you should switch to another language or stop calling yourself a programmer. VB has a bad reputation as it is, it doesn't any more below average programmers writing buggy apps...