Unless you want to ship more data than that for some sort of local processing. Imagine (for example) a super-high-res MMORPG where you want to ship all the textures that the user might look at because the latency is too high.
I must be missing something. Dune was a little weird and I'd have to re-read it to be sure, but I'm pretty sure that Foundation and Ender's Game didn't have blatant magic in them the way Star Wars does...
We're going to have to use stronger encryption than that. It took me longer to figure out that I didn't have a rot13 script on my computer than it took me to write one.
No, none of us have that option. It would be great if we did, but that option is not available. Anyone who tries to do that will be thrown in fedral prision for tax evasion.
If that were true, that would suck pretty bad. Luckily, it's not true.
Someone who sets up an unsecured WAP is exactly as liable for how other people use it as NetZero or Juno were liable for their no-charge dialup users... i.e. not.
Situations come up all the time where using some specific frequency makes sense for some application, but using the frequency is illegal. Every time this happens, it costs money to work around. It's hard to calculate (or even blindly guess) what the costs of this sort of thing might be.
Just because you used to be able to get a job doing some specific thing where you live doesn't mean that won't change. Perhaps you need to move. Perhaps you need to get new job skills. The jobs exist.
LiteStep is pretty decent. It's equivilent to some of the middle-weight Linux window managers like AfterStep and Enlightenment.
Fluxbox is a lightweight window manager. If we had a scale of "Lightweightness" and set Explorer at 10 and LiteStep at 7, Fluxbox would be around a 3. (We need to leave 2, and 1 open for Blackbox and TWM)
Your comment isn't 100% clear, but you seem to be saying that there is a birthday attack on CBC mode.
Thinking about it for a bit, the best attack I can visualize has a ciphertext requirement of at least block size squared blocks (i.e. 2^128 blocks for a cipher with a 64 bit blocksize), and only accomplishes making CBC mode equivilent to ECB mode.
Is there a legitimate attack on a smaller block size, or is it just an issue of speeding up the block algorithim? References?
if you gave everyone in the world a mondern computer and had them ALL work on breaking it together it would on average take 1000 years.
That means that if you gave everyone in the world a million modern computers, it would take a little under 9 hours.
The problem is, "modern computers" can be replaced with "dedicated processors" and "everyone in the world" can be replaced with "each slot in the cracking array", so:
If you gave each slot in the 7 billion slot cracking array a million dedicated processors, you could break almost three keys a day.
Then if we increase the speed of a dedicated processor by a factor of... you see where this is going.
Actually, as key sizes get larger, the required effort to crack by brute force gets pretty silly.
According to Bruce Schneier's "Applied Cryptography" , I paraphrase:
With an ideal computer using the entire energy output of the sun for 32 years, you could cause a 192 bit counter to cycle through all it's possible values.
And, an actual quote:
"These numbers have nothing to do with the technology of the devices; they are the maximums that thermodynamics will allow. And they strongly imply that brute-force attacks against 256-bit keys will be infeasible until computers are built from something other than matter and occupy something other than space."
Although 3des uses 3*56 = 168 key bits, the difficulty of breaking it is equivilent to 112 bits due to a meet in the middle attack. To complicate it further, I'm pretty sure the 112 bits is a data storage requirement (i.e. 6.5*10^32 bytes / 10^32 is about a million trillion trillion).
How does a birthday attack apply to a cipher? It's clear how it would matter in the case of hash algorithims, but you can't get collisions with a cipher...?
Running a pure 32bit or pure 64bit system works as well as on any other platform. Running a hybrid system works pretty well, but has not been normal-userified yet.
As the parent stated, the current biggest issue is 32bit plugins not working with 64bit apps - a functional hybrid distro will fix this problem.
The other big problem had been running 32bit 3D games on a 64bit kernel - this now works perfectly, at least with Nvidia 3D cards.
Case Sensitivity: This really doesn't matter that much. For a normal user, the main use of the file system is saving and loading documents. To save a document, you need to type a filename. To load it, you select the filename from the list.
User permissions: The only time lack of permissions should come up in normal usage is installing packages - So a dialog pops and asks you for the root password.
File names: Which is easier "C:\Documents and Settings\Nat Tuck\My Documents" or "/home/nat"? It doesn't really matter. At this point, randomly browsing the filesystem from the root directory looks pretty weird in both systems, and the desktop environment simplfies it for you by throwing a link to your home directory on the desktop.
Software Installation: With a modern distro, you use packages to install your software. I'm as hardcore a linux user as you can get without having a kernel patch accepted, and all the user software on my machine was installed through my distro's standard package system. The only stuff I've installed by hand are some software development stuff. If I don't need to install stuff from source, your average user doesn't eithor.
For a truely inexperianced computer user, an already installed Linux setup is no more difficult to use than a Windows box, and realistically only slightly more difficult than a Mac.
The point where Linux is "harder" is when you have a somewhat experianced computer user who is already used to another system trying to use it for the first time. Such a user is not experianced enough to immediately see and deal with the differences, and yet experianced that he knows *exactly* how he would do what he wants on the system he's used to, and the fact that Linux is different frustrates him.
At this point there are only three reasons why Windows is considered easier than Linux:
* A lot of people are used to it.
* It comes pre-installed on most new systems.
* Since more people are used to Windows, more people are immediately available to help a new Windows user.
Although it would be *nice* if there were a standardized set of GUI design guidelines for Linux, it's not nessisary.
The differences between a KDE app and a GNOME app are insignificant from the perspective of an inexperianced user, and even something like lyx (which uses XForms) is not really different enough to mess any user up for more than a second or two.
I know people who have done self installs of Linux without touching the command line, and then used that installation for a while.
I can *assure* you that if anyone did a good job of building pre-installed Linux desktops, the only people who run Windows now and would have trouble migrating are the power users and gamers.
Slashdot Mirror
Hi-Def VOIP video phones? With multiple simultanious conversations?
Unless you want to ship more data than that for some sort of local processing. Imagine (for example) a super-high-res MMORPG where you want to ship all the textures that the user might look at because the latency is too high.
To be good, a movie has to be watchable. Metropolis fails.
The supergenre is called Speculative Fiction.
Speculative Fiction has non-intersecting subgenres Fantasy and Science Fiction (as well as some others).
The term you're looking for is Speculative Fiction. Science-Fiction is the subset where there's science (but no magic).
I must be missing something. Dune was a little weird and I'd have to re-read it to be sure, but I'm pretty sure that Foundation and Ender's Game didn't have blatant magic in them the way Star Wars does...
... unless you want to use any of the Reiser4 specific features.
We're going to have to use stronger encryption than that. It took me longer to figure out that I didn't have a rot13 script on my computer than it took me to write one.
h ijklm/'
perl -pe 'y/[A-Z]/[a-z]/; y/abcdefghijklmnopqrstuvwxyz/nopqrstuvwxyzabcdefg
No, none of us have that option. It would be great if we did, but that option is not available. Anyone who tries to do that will be thrown in fedral prision for tax evasion.
According to http://www.iraqbodycount.net/ :
The number of Iraq civilian casualties reported in the media is at least 11619.
What the ratio of Reported In the Media to total actual casualties might be is an open question.
If that were true, that would suck pretty bad. Luckily, it's not true.
Someone who sets up an unsecured WAP is exactly as liable for how other people use it as NetZero or Juno were liable for their no-charge dialup users... i.e. not.
Situations come up all the time where using some specific frequency makes sense for some application, but using the frequency is illegal. Every time this happens, it costs money to work around. It's hard to calculate (or even blindly guess) what the costs of this sort of thing might be.
Super Turbo Turkey Puncher is way better.
Just because you used to be able to get a job doing some specific thing where you live doesn't mean that won't change. Perhaps you need to move. Perhaps you need to get new job skills. The jobs exist.
LiteStep is pretty decent. It's equivilent to some of the middle-weight Linux window managers like AfterStep and Enlightenment.
Fluxbox is a lightweight window manager. If we had a scale of "Lightweightness" and set Explorer at 10 and LiteStep at 7, Fluxbox would be around a 3. (We need to leave 2, and 1 open for Blackbox and TWM)
Your comment isn't 100% clear, but you seem to be saying that there is a birthday attack on CBC mode.
Thinking about it for a bit, the best attack I can visualize has a ciphertext requirement of at least block size squared blocks (i.e. 2^128 blocks for a cipher with a 64 bit blocksize), and only accomplishes making CBC mode equivilent to ECB mode.
Is there a legitimate attack on a smaller block size, or is it just an issue of speeding up the block algorithim? References?
That means that if you gave everyone in the world a million modern computers, it would take a little under 9 hours.
The problem is, "modern computers" can be replaced with "dedicated processors" and "everyone in the world" can be replaced with "each slot in the cracking array", so:
If you gave each slot in the 7 billion slot cracking array a million dedicated processors, you could break almost three keys a day.
Then if we increase the speed of a dedicated processor by a factor of... you see where this is going.
Actually, as key sizes get larger, the required effort to crack by brute force gets pretty silly.
According to Bruce Schneier's "Applied Cryptography" , I paraphrase:
With an ideal computer using the entire energy output of the sun for 32 years, you could cause a 192 bit counter to cycle through all it's possible values.
And, an actual quote:
Although 3des uses 3*56 = 168 key bits, the difficulty of breaking it is equivilent to 112 bits due to a meet in the middle attack. To complicate it further, I'm pretty sure the 112 bits is a data storage requirement (i.e. 6.5*10^32 bytes / 10^32 is about a million trillion trillion).
How does a birthday attack apply to a cipher? It's clear how it would matter in the case of hash algorithims, but you can't get collisions with a cipher...?
Status of amd64 Linux:
Running a pure 32bit or pure 64bit system works as well as on any other platform. Running a hybrid system works pretty well, but has not been normal-userified yet.
As the parent stated, the current biggest issue is 32bit plugins not working with 64bit apps - a functional hybrid distro will fix this problem.
The other big problem had been running 32bit 3D games on a 64bit kernel - this now works perfectly, at least with Nvidia 3D cards.
Case Sensitivity: This really doesn't matter that much. For a normal user, the main use of the file system is saving and loading documents. To save a document, you need to type a filename. To load it, you select the filename from the list.
User permissions: The only time lack of permissions should come up in normal usage is installing packages - So a dialog pops and asks you for the root password.
File names: Which is easier "C:\Documents and Settings\Nat Tuck\My Documents" or "/home/nat"? It doesn't really matter. At this point, randomly browsing the filesystem from the root directory looks pretty weird in both systems, and the desktop environment simplfies it for you by throwing a link to your home directory on the desktop.
Software Installation: With a modern distro, you use packages to install your software. I'm as hardcore a linux user as you can get without having a kernel patch accepted, and all the user software on my machine was installed through my distro's standard package system. The only stuff I've installed by hand are some software development stuff. If I don't need to install stuff from source, your average user doesn't eithor.
For a truely inexperianced computer user, an already installed Linux setup is no more difficult to use than a Windows box, and realistically only slightly more difficult than a Mac.
The point where Linux is "harder" is when you have a somewhat experianced computer user who is already used to another system trying to use it for the first time. Such a user is not experianced enough to immediately see and deal with the differences, and yet experianced that he knows *exactly* how he would do what he wants on the system he's used to, and the fact that Linux is different frustrates him.
At this point there are only three reasons why Windows is considered easier than Linux:
* A lot of people are used to it.
* It comes pre-installed on most new systems.
* Since more people are used to Windows, more people are immediately available to help a new Windows user.
I've heard this argument a lot, and I disagree.
Although it would be *nice* if there were a standardized set of GUI design guidelines for Linux, it's not nessisary.
The differences between a KDE app and a GNOME app are insignificant from the perspective of an inexperianced user, and even something like lyx (which uses XForms) is not really different enough to mess any user up for more than a second or two.
I know people who have done self installs of Linux without touching the command line, and then used that installation for a while.
I can *assure* you that if anyone did a good job of building pre-installed Linux desktops, the only people who run Windows now and would have trouble migrating are the power users and gamers.