AMEN TO THAT.
All my friends in the area and I are on Comcast (still better than DSL, considering price), and a few in particular seem to have outages every week or so. There are random incidents of packet loss every few days that cause Trillian to drop my AIM connection. It's really quite annoying, but for the price (compared to a quality T1) you can't complain much.
There are 10k RPM SATA drives - look for the Western Digital Raptors. I think that with SATA's speed and hotplug capability, the end has finally come for SCSI. Sure, SCSI drives may on average be of a slightly higher build quality, but 1) I'm sure that'll change with more demand for SATA in servers and 2) you should be using RAID anyway.
Ah yes, Cornelius Pass Roadhouse. They have a new (within the last few years) addition called Imbrie Hall, which has excellent food. Check out the men's restroom in Imbrie too - cool plumbing (you'll know what I mean when you see it).
* Visit a McMennamin's hotel for lunch or dinner...
But don't expect good service or clean silverware.
Before amending this, full disclosure: the McMenamin brothers are my uncles.
That out of the way...
In general the service is quite good, we go to a few of their places fairly often and the food always comes pretty fast. Of course, there are always isolated incidents, but don't let that discourage anyone from trying the restaurants.
Actually, there is one small physical difference. One of the configuration bridges (the same things that set the clock multiplier) is cut on the XP, to disable multiprocessing. I've seen tutorials online to fill the bridge and thus convert back to MP; however, this is unreliable as the XPs aren't necessarily tested as MPs at the factory.
30 years is a long time for a software project to evolve. The question, however, is how much of the original code remains today. Lots of software, especially stuff that changes fast, is this way - I'm sure that not much of the Linux 0.01 code remains in the 2.6.0 tree. It's just a matter of replacing things one piece at a time (or completely rewriting things, in some cases).
I never said it was the most efficient algorithm. I was only responding to your comment about exhausting a list of primes, in order to show that there is a solution. Actually, I believe that there's a polynomial-time primality test that was discovered in the last few years; I don't remember any details though.
There's no need for a predetermined list of primes. Instead, just try dividing every number (or every odd maybe, as you've already tried 2) up to sqrt(n) into n. It's slightly redundant as you'll be testing primes and all their multiples up to n, but it's better than having a huge list of primes.
Then you would need the plaintext password in the database, because salt2 isn't constant.
Fundamentally, the exchanged data is hash(salt + [something]). Both the client and server need to know [something] in order to compute the hash, and an attacker, knowing [something], can construct the data that is sent - so you must ensure that the database on the server isn't compromised.
I don't think it would. A laser's light spectrum is very narrow; just one specific wavelenght. Laser pointers are generally red visible light (sometimes green) - and to melt solder, you'd want infrared, to heat it. The reason you can heat things with focused normal light (like sunlight under a magnifying glass) is because its spectrum is spread out and includes the infrared band. Visible laser's dont.
they'll probably put cat5 cables with 8 wires, which means the transition to 1000mbit will be easy.
Ethernet over CAT5 is restricted to 100m of cable between repeaters, so something tells me that they're not using copper Ethernet for a wide-area network. It's most likely fiber. However - I don't know much about fiber, but presumably upgrades would be even easier then (as long as you have the right type of fiber).
I'm 15 (a sophomore). I've got 7 machines in my room - 2 servers (my site and 2 friends), 2 desktops, a laptop, and two random/spare boxes. I've had unrestricted broadband since sixth grade (12 yrs old), and net access since about 3rd or 4th grade (~ 9-10 yrs old). My situation is pretty much the opposite of what you're describing - I'm the kid, controlling the net access for everyone else.
However, my parents have said that they trust me, and I don't abuse that. Trust me - people don't like draconian rules. If your kids are smart they'll know how to stay out of trouble, and you won't need filtering. You just have to trust that they will know what's best.
electric shock is the first thing that comes to mind.
Ah yes, all of those 1.5 volts running the CPU core can really do some serious damage...
Actually, you don't feel anything below about 50V. Conduction through the water adds more resistance, so that figure is higher. You'd need leakage into the power supply to do anything, highly unlikely as the PS is at the top of the case and the gravity vector points down.
Now, damage to the equipment itself is another matter. Conduction isn't much of an issue at low voltages, but corrosion and other water damage can mess things up. That is why you want to make sure that all the hoseclamps are tight.
Sorry that I'm not more familiar with quantum theory to answer specifically, but the security of OTP is that you _can't_ pick out the correct answer, because any output is possible given a key. It's equivalent to saying "If x is the key, x+23 is the decrypted message; crack the encryption!" It's simply impossible to know if you have the right answer.
I haven't really looked into specific methods of brute forcing, but I can imagine that there would be several different ways of telling when you have the right key. Sometimes the decrypted form will have some sort of header that you can look for as you search the key space. Other times you just have to look for English output (or JPEG data, or a nuclear launch sequence) that makes sense. It depends on the message contents.
Of course, OTP's uniqueness is that key space is as large as the output message space. With traditional encryption (say, DES with 56-bit keys) only a certain subset of outputs are possible for a given input, so the above problem of determining which is the plaintext is much easier.
As a sidenote, the cracking of public key encryption (given the public key) is probably the easiest to define: simply factor a number. Once you have done this, there is no doubt that it is the correct answer. Of course, in real use the number is on the order of hundreds of digits.
OTP works by having a completely random key that is as long as the data itself. It is then combined with the data in some way (say, for example, XOR) and reversed at the other end given the correct key.
The key (no pun intended) here is that there is no way to know when you have the correct key. With the XOR example, there exist keys that will produce every possible combination of output bits, and no way to tell which one is right. So trying to decrypt it is no different than generating random bit patterns the length of the data and seeing which output "looks right" - even looking for outputs that are valid English, you will encounter every possible sentence of the given data length.
Slashdot Mirror
0.0001% != 0.0001, 0.001% != 0.001, and 0.1% != 0.1. So multiply your result by (1%)^3 = 10^-6.
AMEN TO THAT. All my friends in the area and I are on Comcast (still better than DSL, considering price), and a few in particular seem to have outages every week or so. There are random incidents of packet loss every few days that cause Trillian to drop my AIM connection. It's really quite annoying, but for the price (compared to a quality T1) you can't complain much.
There are 10k RPM SATA drives - look for the Western Digital Raptors. I think that with SATA's speed and hotplug capability, the end has finally come for SCSI. Sure, SCSI drives may on average be of a slightly higher build quality, but 1) I'm sure that'll change with more demand for SATA in servers and 2) you should be using RAID anyway.
Ah yes, Cornelius Pass Roadhouse. They have a new (within the last few years) addition called Imbrie Hall, which has excellent food. Check out the men's restroom in Imbrie too - cool plumbing (you'll know what I mean when you see it).
* Visit a McMennamin's hotel for lunch or dinner...
But don't expect good service or clean silverware.
Before amending this, full disclosure: the McMenamin brothers are my uncles.
That out of the way...
In general the service is quite good, we go to a few of their places fairly often and the food always comes pretty fast. Of course, there are always isolated incidents, but don't let that discourage anyone from trying the restaurants.
I find qemu to be quite excellent x86 virtualization software. It's closer to VMware than Bochs, using dynamic translation.
Actually, there is one small physical difference. One of the configuration bridges (the same things that set the clock multiplier) is cut on the XP, to disable multiprocessing. I've seen tutorials online to fill the bridge and thus convert back to MP; however, this is unreliable as the XPs aren't necessarily tested as MPs at the factory.
30 years is a long time for a software project to evolve. The question, however, is how much of the original code remains today. Lots of software, especially stuff that changes fast, is this way - I'm sure that not much of the Linux 0.01 code remains in the 2.6.0 tree. It's just a matter of replacing things one piece at a time (or completely rewriting things, in some cases).
Well I spent the latter portion of 1987 as a fetus! Who says "HaHa" now?
That's weird to think: Perl is old enough to be in my class. Either I'm young, or Perl is old (or both...)
I never said it was the most efficient algorithm. I was only responding to your comment about exhausting a list of primes, in order to show that there is a solution. Actually, I believe that there's a polynomial-time primality test that was discovered in the last few years; I don't remember any details though.
There's no need for a predetermined list of primes. Instead, just try dividing every number (or every odd maybe, as you've already tried 2) up to sqrt(n) into n. It's slightly redundant as you'll be testing primes and all their multiples up to n, but it's better than having a huge list of primes.
Then you would need the plaintext password in the database, because salt2 isn't constant.
Fundamentally, the exchanged data is hash(salt + [something]). Both the client and server need to know [something] in order to compute the hash, and an attacker, knowing [something], can construct the data that is sent - so you must ensure that the database on the server isn't compromised.
I don't think it would. A laser's light spectrum is very narrow; just one specific wavelenght. Laser pointers are generally red visible light (sometimes green) - and to melt solder, you'd want infrared, to heat it. The reason you can heat things with focused normal light (like sunlight under a magnifying glass) is because its spectrum is spread out and includes the infrared band. Visible laser's dont.
they'll probably put cat5 cables with 8 wires, which means the transition to 1000mbit will be easy.
Ethernet over CAT5 is restricted to 100m of cable between repeaters, so something tells me that they're not using copper Ethernet for a wide-area network. It's most likely fiber. However - I don't know much about fiber, but presumably upgrades would be even easier then (as long as you have the right type of fiber).
I'm 15 (a sophomore). I've got 7 machines in my room - 2 servers (my site and 2 friends), 2 desktops, a laptop, and two random/spare boxes. I've had unrestricted broadband since sixth grade (12 yrs old), and net access since about 3rd or 4th grade (~ 9-10 yrs old). My situation is pretty much the opposite of what you're describing - I'm the kid, controlling the net access for everyone else.
However, my parents have said that they trust me, and I don't abuse that. Trust me - people don't like draconian rules. If your kids are smart they'll know how to stay out of trouble, and you won't need filtering. You just have to trust that they will know what's best.
electric shock is the first thing that comes to mind.
Ah yes, all of those 1.5 volts running the CPU core can really do some serious damage...
Actually, you don't feel anything below about 50V. Conduction through the water adds more resistance, so that figure is higher. You'd need leakage into the power supply to do anything, highly unlikely as the PS is at the top of the case and the gravity vector points down.
Now, damage to the equipment itself is another matter. Conduction isn't much of an issue at low voltages, but corrosion and other water damage can mess things up. That is why you want to make sure that all the hoseclamps are tight.
Sorry that I'm not more familiar with quantum theory to answer specifically, but the security of OTP is that you _can't_ pick out the correct answer, because any output is possible given a key. It's equivalent to saying "If x is the key, x+23 is the decrypted message; crack the encryption!" It's simply impossible to know if you have the right answer.
I haven't really looked into specific methods of brute forcing, but I can imagine that there would be several different ways of telling when you have the right key. Sometimes the decrypted form will have some sort of header that you can look for as you search the key space. Other times you just have to look for English output (or JPEG data, or a nuclear launch sequence) that makes sense. It depends on the message contents.
Of course, OTP's uniqueness is that key space is as large as the output message space. With traditional encryption (say, DES with 56-bit keys) only a certain subset of outputs are possible for a given input, so the above problem of determining which is the plaintext is much easier.
As a sidenote, the cracking of public key encryption (given the public key) is probably the easiest to define: simply factor a number. Once you have done this, there is no doubt that it is the correct answer. Of course, in real use the number is on the order of hundreds of digits.
OTP works by having a completely random key that is as long as the data itself. It is then combined with the data in some way (say, for example, XOR) and reversed at the other end given the correct key.
The key (no pun intended) here is that there is no way to know when you have the correct key. With the XOR example, there exist keys that will produce every possible combination of output bits, and no way to tell which one is right. So trying to decrypt it is no different than generating random bit patterns the length of the data and seeing which output "looks right" - even looking for outputs that are valid English, you will encounter every possible sentence of the given data length.
If I'm not mistaken, It's not actually matter that's traveling at a speed > c, it's just the border of space-time.
Fair enough... probably before I was born anyway.
kill -9 'ps -aef | grep /usr/bin/X11 | awk {...}
What, no killall(1) (pkill(1) on some OSes (NetBSD))?
Not to worry, I was not yet fully awake and thus my sense of humor was quite lacking at that time.
Wouldn't that make them 96bit cpus then?
No - the 64-bit extensions are either new instructions or a new processor mode, so a given datum is still either 32 or 64 bits wide, not both at once.
I'm guessing there's a sizable portion of the Slashdot population (such as me) not yet old enough to even have a car, let alone be a "gearhead"...
I did build a 3-speed transmission out of Lego once though, if that counts. (No, I'm serious! It even worked! Complete with a shifter lever!)