Breaking News
Newest First | Oldest First | Threaded View
User Rank
re: Data security in cloud computing - Part 2: Data encryption applications and limits
przemek0   8/1/2011 9:20:17 PM
To RWatkins, who wrote "The use of standard encryption systems (available to civilians) has been outlawed for military applications requiring any level of security for decades" On the contrary, the serious encryption is ONLY possible with standard methods that have been vetted thoroughly by professional cryptographers, and which depend on fundamental mathematical principles, not on some secret algorithm. Bruce Schneier put it nicely: "anyone can invent an encryption system that they themselves cannot break". It is true that there may be a technological or mathematical discovery that breaks the current encryption, but the chance of that is small compared to the chance of leakage of an encryption based on a secret algorithm.

User Rank
re: Data security in cloud computing - Part 2: Data encryption applications and limits
RWatkins   7/26/2011 1:47:55 PM
As a student of cryptography since middle-school days, now over 45 years, a lot of what is spouted here is great to protect one from relatively weak decryption attacks or for relatively short periods of time. The use of "standard" encryption systems (available to civilians) has been outlawed for military applications requiring any level of security for decades and for very good reason. Any public/private key system by definition has a mathematical relationship between the public key and the private key. The "back door" is as simple as to derive said relationship. The statements made in this article propagate the wrong attitude that data can be shared in open interfaces and connected to open computational resources that contain decryption software, all safely. To be truly safe, somewhere there must be a proverbial funnel with a check valve to prevent hacking, extraction, or analysis attacks on data. If your data is time critical and worthless in a matter of hours, all of this may not matter if you keep changing the algorithm, choose a good algorithm and sometimes vary it, and keep the key and algorithm away from prying software. However, if you really want to STORE information or keep information from competitors for longer periods of time, current techniques are a recipe for disaster. This is shown time and again in internet banking transactions where attacks have become increasingly sophisticated and fraud more and more prevalent.

User Rank
re: Data security in cloud computing - Part 2: Data encryption applications and limits
prabhakar_deosthali   7/26/2011 11:22:00 AM
It is very difficult to have a perfect world. So having a perfect Web with no viruses, no spy ware is something we can only hope for. Like all the physical security measures we take : most of them are prone for attack. The automatic teller machines have CCTV cameras to catch a person doing mis-deed. But we have cases where the thieves have covered the cameras with a cloth and stolen the whole machine itself . Combination locks are yet another security measures which can be decoded by a thief with sustained effort and sufficient amount of time. So in case of data encryption you are never 100% sure that your encryption key code is broken into. The only way I see is to be able to detect that your security has been broken into as early as you can and contain the damage by a scheme of revolving keys, like the frequency hopping techniques used in secure communications

User Rank
re: Data security in cloud computing - Part 2: Data encryption applications and limits
EREBUS0   7/26/2011 12:57:07 AM
The only way you can control Cloud content and access is to implement a solid series of encrypted techniques throughout the architecture. Single techniques can be broken, but if you use a comprehensive layering approach, you can make it too difficult for the casual vandal to penetrate and you can quickly identify when someone is doing more than just using the system for their legitamate purposes. Yes you will make it harder and more tedious to access the cloud, but I would bet that every common user would rather go through a little inconvience if they could be ensured of not having their data vandalized or stolen. Just think of it, a web where we don't get overwhelmed with spam, no viruses, just a clean environment where we can do our work and go about our business without worrying about someone screwing everything up. Now that would make a very pleasent web indeed. Thanks, Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.

Brought to you by:

Most Recent Comments
Most Recent Messages
4:48:30 PM
michigan0 Sang Kim First, 28nm bulk is in volume manufacturing for several years by the major semiconductor companies but not 28nm FDSOI today yet. Why not? Simply because unlike 28nm bulk the LDD(Lightly Doped Drain) to minimize hot carrier generation can't be implemented in 28nm FDSOI. Furthermore, hot carrier reliability becomes worse with scaling, That is the major reason why 28nm FDSOI is not manufacturable today and will not be. Second, how can you suppress the leakage currents from such ultra short 7nm due to the short channel effects? How thin SOI thickness is required to prevent punch-through of un-dopped 7nm FDSOI? Possibly less than 4nm. Depositing such an ultra thin film less then 4nm filum uniformly and reliably over 12" wafers at the manufacturing line is extremely difficult or not even manufacturable. If not manufacturable, the 7nm FDSOI debate is over!Third, what happens when hot carriers are generated near the drain at normal operation of 7nm FDSOI? Electrons go to the positively biased drain with no harm but where the holes to go? The holes can't go to the substrate because of the thin BOX layer. Some holes may become trapped at the BOX layer causing Vt shift. However, the vast majority of holes drift through the the un-dopped SOI channel toward the N+Source,...
Like Us on Facebook
Special Video Section
Once the base layer of a design has been taped out, making ...
In this short video we show an LED light demo to ...
The LTC2380-24 is a versatile 24-bit SAR ADC that combines ...
In this short video we show an LED light demo to ...
Wireless Power enables applications where it is difficult ...
LEDs are being used in current luxury model automotive ...
With design sizes expected to increase by 5X through 2020, ...
Linear Technology’s LT8330 and LT8331, two Low Quiescent ...
The quality and reliability of Mill-Max's two-piece ...
LED lighting is an important feature in today’s and future ...
The LT8602 has two high voltage buck regulators with an ...
Silego Technology’s highly versatile Mixed-signal GreenPAK ...
The quality and reliability of Mill-Max's two-piece ...
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...