It's already been done. It's called stunnel. Among other things it lets you do, you can specify a different host to connect to.
In other words, host A accepts connections on port 443 and can automatically encrypt the traffic and route it through to host B on port 80. It allows you to accept connections on multiple ports, each with its own mapping.
It also works with name virtual hosts, forwarding the name request through to the other host.
I think the main reason is that British TV usually knows when to give up the ghost and stop making shows. Whereas shows like the Simpsons go through cycles where it's really funny for a couple of years, then incredibly dull and predictable for a couple of years, rinse repeat, in the UK they'll stop making a show like Red Dwarf or The Vicar of Dibley when the writers run out of material.
Note, however, I said *usually* they'll stop writing when they run out of material. I'm looking at you, Casualty.
Intel 8945J integrated wireless on my laptop. Dual boot, Zenwalk Linux and XP MCE 2005. Until the most recent driver from Intel, the wireless card was *significantly* stabler under Linux. It's now just as stable under Windows (though I replaced by router with a new D-Link 802.11n router recently too), but the throughput at long range is still better in Linux.
As an example of the latter under Windows the useable range on my wlan caps out at about 25m. that's enough to cover my house, and much of the front lawn. Under Linux, I was able to connect to my network from the picnic table at the park across the street, about 100m. I was only getting 1mbit of throughput, probably less, but it was definitely getting better error correction and a more useable connection at that range than under Windows.
On the message board I administer, I had pretty good results by changing the way CAPTCHA worked... rather than a fill-in-the-blank method. People were provided with an image that had a well-known sentence or domain name, as well as the list of possible answers. So they'd see an image that looked like:
___ chase cats dogs budgies kittens
and were told "fill in the blank". In this case, the expected answer was "dogs". Something that was ridiculously easy for a human to solve, but required actual comprehension rather than simple text recognition.
Unfortunately, we ended up updating the forum software to phpbb3, and I have yet to get off my ass to hack the captcha to do what I want again.
As others have said, using ASCII art is too difficult. Too many different ways to spell things, and if you embed the spelling you're looking for in the image, then you're back at square 1.
There's an awful lot of redundancy and inter-networking going on in the Internet, but a concerted attack at the right points in the Internet could take them offline, and break those links between networks.
No, it wouldn't cause your computer to blow up. It wouldn't break your home network. It wouldn't break your ISP's network. But if AT&T, L3, Verizon/UUNet, GBLX, Qwest, Sprint, etc. couldn't talk to each other, you'd as good as break the Internet. Remember the connectivity issues that were caused last year when L3 and Cogent de-peered each other? And those are relatively small players. Imagine if it were AT&T and UUNet that de-peered each other.
Somebody who knows the architecture of the Internet and *really* wanted to take it down wouldn't have a hard time at it. Just target the peering points between the big networks.
As others have pointed out, there's other weak points in the network, too. Gateway protocols and DNS are vulnerable to attack, as well, for example.:)
You're right. You're not expecting a drive to fail every 6 weeks on the button. But MTBF is used for logistic planning... in the given example, you *should* be ok having 2 spare drives on hand. One to replace the one that you expect to die, and one to replace the one that dies while you're waiting on the replacement you just ordered to arrive.
There'll always be statistical skew when working with something like a mean time, and it is an oversimplification. I've only ever had 2 hard drives fail on me, for example. But that's the point with MTBF... to give you an idea of what kind of fail rate to expect so that you can plan how many spares you need to keep on hand. It's got nothing to do with the actual expected lifespan of an individual drive.
I'm guessing "The Contradictor" is for clicking that little exclamation point on somebody else's tag. Say somebody posted a tag "correlationiscausation" and you clicked the bang to make it "!correlationiscausation".:)
If they were smart, they'd have kept that little tidbit secret... quietly shuffle the domains off into never-land to help protect the world at large, and still allow them to be registered.
Have they never heard of a honey pot? Registering a domain in Canada requires you sign several contracts, become a member in CIRA, give them rights to your first born, etc.. Anonymous domain registration is not allowed in Canada, and until quite recently, registering a.CA domain name was restricted to Canadian citizens. It seems that if they know what domains the virus writer is going to try to register, let them register it and then you've got their home address and name.
This is Canada. We don't make noise. We write letters. And only if it's about something that's really really annoying.
It's also not really something we need to worry about in Canadian copyright law... all the ISOHunt people need to show is that they are not actually making the files available themselves. In Canadian copyright law, it's ok to copy/share materials as long as it's not for material gain, and you're not distributing on a large scale.
He was using an absurd, and known-false example as the logical extension of the person to whom he was replying's contention that 17V isn't enough to cause a fire. In carrying it to its logical extension and finding a ridiculous or contradictory result, he proved that the original contention was itself false.
Informative, and insightful too. Albeit, an insight I'm surprised nobody else seems to be making.
There's waste cellulose produced everywhere. Pulp & paper industries, lumber, farming... even crops grown for direct fermentation like corn produce waste cellulose that isn't used in the fermentation process (there isn't a lot of sugar in the silk & husks).
This isn't a replacement, it's a supplement. And it's one that can be used in direct conjunction with existing methods for producing biofuel, too... as I said, there's bits of corn that don't really have a lot (or any) sugar in them. What would happen if you mash up the corn, stalk, leaves, and all, into a soup for fermentation, and throw a batch of this bacteria into it for a few days before you add the yeast and start fermenting for real?
Ah, but in order to enforce it properly, the police would have to be driving an automated car, too. That wouldn't make for a very interesting high speed chase.
Even still, the question I'm wondering is if x86_64 uses licensed bits of x86 instructions in its specification. Because if that is the case, wouldn't that mean that Intel can theoretically have this also prohibited from use as well?
Theoretically, yes. Practically, no. While it does develop on prior art, it also implements something new, and so it's considered new technology. It'd be like me trying to copyright the letter e, and then suing you for using the word "the".
There's also no way that Intel would pull that trigger. Sure, they could stop AMD from producing chips which support x86. But they'd lose their rights to use x86-64. Seeing as so many of the computers in the world run Microsoft, that'd be corporate suicide: Microsoft, in its infinite wisdom, has deigned not to implement a 32-bit workaround to the 4GB memory addressing limit. As new computers are routinely being sold with 6GB or more RAM, they'd be writing themselves out of the market for future computer manufacture. While IA64 *is* a supported architecture in 64-bit Windows, nobody's developping for it since Intel decided to scrap the architecture and focus on building x86-64 CPU's. I'm not even sure it's on the supported list for Windows 7, to be honest...
They'd also lose out on a significant chunk of the market, as it would take time for them to start designing and building IA64-based chips again, during which time AMD, which would still be able to use x86-64 in its chip design would be able to dominate the market.
Yes, I'm oversimplifying the intricacies of CPU design. But it's easier to drop a part of your architecture that's really only there for backwards compatibility in the first place than it is to scrap an architecture completely and rework your existing technology to take advantage of an alternative so that your product can remain viable in the marketplace.
Or they're saying they're in touch with what some of their consumers have been saying for years. I have a whopping 5mp on my favourite digital camera, and it's plenty adequate for me. Why do I keep using that one, even though I have a 10mp point and shoot that's lighter, easier to carry, and sports a higher pixel density?
Because the 5mp camera has better optics, significantly better colour accuracy, and is an order of magnitude faster to start up and take pictures. It's started up in less than a second, it's able to take rapid fire pictures, and the shutter lag is 0.02ms. For 99.9% of what I do, I don't need the extra pixels, I need pictures that actually look good, and a camera that's fast enough to be useful.
You do realize that treaties usually take longer than a month to get written, negotiated, re-written, agreed-upon, written up, vetted, voted on, and passed, right?
This treaty isn't Obama's baby. It's part of Bush's legacy. And as others have said, it still has to be approved by congress, and the executive still has the right to veto it.
Now see... once they become proficient, I find that the ESL students have *better* written and spoken English than native-speakers.
I don't know why it is, but native English speakers don't have the rules of grammar and spelling drilled into their heads nearly as thoroughly as every other language I've studied. When I was an exchange student in France, for example, I remember my host family having conversations at the dinner table about grammar, and the 12-year old kid correcting her father on his improper use of the Subjunctive. And she was right!
That kind of thing just doesn't seem to happen in the English-speaking world.
Compared to some of the mods that people are doing, this one is pretty easy. The backlight usually isn't even physically attached to the lcd, and the LCD itself is about 0.5-1mm thick (depending on brand/type). Buy an off-the-shelf 2" LCD, remove the backlight, and connect it to the motherboard through the appropriate connector. There's probably a little bowing just because of the space considerations, but other than that it's not a difficult mod at all. As GP said, the backlight from the main LCD is already exposed, and I'd think the hardest part of the mod would be putting some kind of polyvinyl or acrylate coating on the back LCD to prevent it from scratching.
Laptop LCD's are remarkably easy to open up and work with. You just need the right kind of screwdriver.
If that's the case, then something's wrong with your configuration. My XP-based work computer has a power policy in place to hibernate every night at 8:00pm and wake up at 7:30am. I've never had a problem with an IP address on resume.
I've also never had problems with IP addresses on suspend/hibernate/resume on my main laptop, even though that dual-boots between XP and Linux.
See... a lot of that depends on your hardware configuration. I've had computers that took forever to come out of hibernation with as little as 512MB of RAM. I've also had systems that came out of hibernation with 8x as much RAM in under 10s, including the POST.
The speed of your hard drive seems to be the determining factor, everything else being equal. I won't buy a system with less than 7200rpm hard drive, even in laptops, specifically because of that. There are other factors that affect hibernate speed, such as how well the kernel is optimized for it, and whether your BIOS properly handles the requests, but I don't think I'm going out on a limb when I say that hibernation time is largely dependent on your hardware configuration, while boot time is largely dependent on software configuration and how many services/etc. you have at startup. As a general rule, the more you're doing with your system, the more attractive hibernation becomes.
Absolutely the fastest hibernate/resume system I ever had was actually Windows 2000. That was the one that could suspend/resume with 4GB of RAM in under 10s. By contrast, that system took about a minute to boot from cold. Needless to say, it only ever rebooted for patches.
Slashdot Mirror
It's already been done. It's called stunnel. Among other things it lets you do, you can specify a different host to connect to.
In other words, host A accepts connections on port 443 and can automatically encrypt the traffic and route it through to host B on port 80. It allows you to accept connections on multiple ports, each with its own mapping.
It also works with name virtual hosts, forwarding the name request through to the other host.
Any publicity is good publicity. While I don't really care about either site, I hadn't even heard of StalkDaily before this.
I think the main reason is that British TV usually knows when to give up the ghost and stop making shows. Whereas shows like the Simpsons go through cycles where it's really funny for a couple of years, then incredibly dull and predictable for a couple of years, rinse repeat, in the UK they'll stop making a show like Red Dwarf or The Vicar of Dibley when the writers run out of material.
Note, however, I said *usually* they'll stop writing when they run out of material. I'm looking at you, Casualty.
*raises hand*
Intel 8945J integrated wireless on my laptop. Dual boot, Zenwalk Linux and XP MCE 2005. Until the most recent driver from Intel, the wireless card was *significantly* stabler under Linux. It's now just as stable under Windows (though I replaced by router with a new D-Link 802.11n router recently too), but the throughput at long range is still better in Linux.
As an example of the latter under Windows the useable range on my wlan caps out at about 25m. that's enough to cover my house, and much of the front lawn. Under Linux, I was able to connect to my network from the picnic table at the park across the street, about 100m. I was only getting 1mbit of throughput, probably less, but it was definitely getting better error correction and a more useable connection at that range than under Windows.
*nods* yup.
Quality of reporting is better at Reuters too.
On the message board I administer, I had pretty good results by changing the way CAPTCHA worked... rather than a fill-in-the-blank method. People were provided with an image that had a well-known sentence or domain name, as well as the list of possible answers. So they'd see an image that looked like:
___ chase cats
dogs budgies kittens
and were told "fill in the blank". In this case, the expected answer was "dogs". Something that was ridiculously easy for a human to solve, but required actual comprehension rather than simple text recognition.
Unfortunately, we ended up updating the forum software to phpbb3, and I have yet to get off my ass to hack the captcha to do what I want again.
As others have said, using ASCII art is too difficult. Too many different ways to spell things, and if you embed the spelling you're looking for in the image, then you're back at square 1.
There's an awful lot of redundancy and inter-networking going on in the Internet, but a concerted attack at the right points in the Internet could take them offline, and break those links between networks.
No, it wouldn't cause your computer to blow up. It wouldn't break your home network. It wouldn't break your ISP's network. But if AT&T, L3, Verizon/UUNet, GBLX, Qwest, Sprint, etc. couldn't talk to each other, you'd as good as break the Internet. Remember the connectivity issues that were caused last year when L3 and Cogent de-peered each other? And those are relatively small players. Imagine if it were AT&T and UUNet that de-peered each other.
Somebody who knows the architecture of the Internet and *really* wanted to take it down wouldn't have a hard time at it. Just target the peering points between the big networks.
As others have pointed out, there's other weak points in the network, too. Gateway protocols and DNS are vulnerable to attack, as well, for example. :)
You're right. You're not expecting a drive to fail every 6 weeks on the button. But MTBF is used for logistic planning... in the given example, you *should* be ok having 2 spare drives on hand. One to replace the one that you expect to die, and one to replace the one that dies while you're waiting on the replacement you just ordered to arrive.
There'll always be statistical skew when working with something like a mean time, and it is an oversimplification. I've only ever had 2 hard drives fail on me, for example. But that's the point with MTBF... to give you an idea of what kind of fail rate to expect so that you can plan how many spares you need to keep on hand. It's got nothing to do with the actual expected lifespan of an individual drive.
I'm guessing "The Contradictor" is for clicking that little exclamation point on somebody else's tag. Say somebody posted a tag "correlationiscausation" and you clicked the bang to make it "!correlationiscausation". :)
Obligatory XKCD:
http://xkcd.com/326/
If you're going to correct somebody on something as silly as that, at least get it right....
Grammar = the spelling/construction of sentences to form semantic meaning.
Grammer = An actor, most notable for his role as Dr. Frasier Crane in Cheers and Frasier.
If they were smart, they'd have kept that little tidbit secret... quietly shuffle the domains off into never-land to help protect the world at large, and still allow them to be registered.
Have they never heard of a honey pot? Registering a domain in Canada requires you sign several contracts, become a member in CIRA, give them rights to your first born, etc.. Anonymous domain registration is not allowed in Canada, and until quite recently, registering a .CA domain name was restricted to Canadian citizens. It seems that if they know what domains the virus writer is going to try to register, let them register it and then you've got their home address and name.
Oh probably. Do you think they'll be able to channel an answer?
nono.. that's why he can't afford Windows... he had to sell the car and remortgage the house to buy the Mac.
This is Canada. We don't make noise. We write letters. And only if it's about something that's really really annoying.
It's also not really something we need to worry about in Canadian copyright law... all the ISOHunt people need to show is that they are not actually making the files available themselves. In Canadian copyright law, it's ok to copy/share materials as long as it's not for material gain, and you're not distributing on a large scale.
http://en.wikipedia.org/wiki/Reductio_ad_absurdum
He was using an absurd, and known-false example as the logical extension of the person to whom he was replying's contention that 17V isn't enough to cause a fire. In carrying it to its logical extension and finding a ridiculous or contradictory result, he proved that the original contention was itself false.
Informative, and insightful too. Albeit, an insight I'm surprised nobody else seems to be making.
There's waste cellulose produced everywhere. Pulp & paper industries, lumber, farming... even crops grown for direct fermentation like corn produce waste cellulose that isn't used in the fermentation process (there isn't a lot of sugar in the silk & husks).
This isn't a replacement, it's a supplement. And it's one that can be used in direct conjunction with existing methods for producing biofuel, too... as I said, there's bits of corn that don't really have a lot (or any) sugar in them. What would happen if you mash up the corn, stalk, leaves, and all, into a soup for fermentation, and throw a batch of this bacteria into it for a few days before you add the yeast and start fermenting for real?
Ah, but in order to enforce it properly, the police would have to be driving an automated car, too. That wouldn't make for a very interesting high speed chase.
Theoretically, yes. Practically, no. While it does develop on prior art, it also implements something new, and so it's considered new technology. It'd be like me trying to copyright the letter e, and then suing you for using the word "the".
There's also no way that Intel would pull that trigger. Sure, they could stop AMD from producing chips which support x86. But they'd lose their rights to use x86-64. Seeing as so many of the computers in the world run Microsoft, that'd be corporate suicide: Microsoft, in its infinite wisdom, has deigned not to implement a 32-bit workaround to the 4GB memory addressing limit. As new computers are routinely being sold with 6GB or more RAM, they'd be writing themselves out of the market for future computer manufacture. While IA64 *is* a supported architecture in 64-bit Windows, nobody's developping for it since Intel decided to scrap the architecture and focus on building x86-64 CPU's. I'm not even sure it's on the supported list for Windows 7, to be honest...
They'd also lose out on a significant chunk of the market, as it would take time for them to start designing and building IA64-based chips again, during which time AMD, which would still be able to use x86-64 in its chip design would be able to dominate the market.
Yes, I'm oversimplifying the intricacies of CPU design. But it's easier to drop a part of your architecture that's really only there for backwards compatibility in the first place than it is to scrap an architecture completely and rework your existing technology to take advantage of an alternative so that your product can remain viable in the marketplace.
Or they're saying they're in touch with what some of their consumers have been saying for years. I have a whopping 5mp on my favourite digital camera, and it's plenty adequate for me. Why do I keep using that one, even though I have a 10mp point and shoot that's lighter, easier to carry, and sports a higher pixel density?
Because the 5mp camera has better optics, significantly better colour accuracy, and is an order of magnitude faster to start up and take pictures. It's started up in less than a second, it's able to take rapid fire pictures, and the shutter lag is 0.02ms. For 99.9% of what I do, I don't need the extra pixels, I need pictures that actually look good, and a camera that's fast enough to be useful.
You do realize that treaties usually take longer than a month to get written, negotiated, re-written, agreed-upon, written up, vetted, voted on, and passed, right?
This treaty isn't Obama's baby. It's part of Bush's legacy. And as others have said, it still has to be approved by congress, and the executive still has the right to veto it.
Now see... once they become proficient, I find that the ESL students have *better* written and spoken English than native-speakers.
I don't know why it is, but native English speakers don't have the rules of grammar and spelling drilled into their heads nearly as thoroughly as every other language I've studied. When I was an exchange student in France, for example, I remember my host family having conversations at the dinner table about grammar, and the 12-year old kid correcting her father on his improper use of the Subjunctive. And she was right!
That kind of thing just doesn't seem to happen in the English-speaking world.
Compared to some of the mods that people are doing, this one is pretty easy. The backlight usually isn't even physically attached to the lcd, and the LCD itself is about 0.5-1mm thick (depending on brand/type). Buy an off-the-shelf 2" LCD, remove the backlight, and connect it to the motherboard through the appropriate connector. There's probably a little bowing just because of the space considerations, but other than that it's not a difficult mod at all. As GP said, the backlight from the main LCD is already exposed, and I'd think the hardest part of the mod would be putting some kind of polyvinyl or acrylate coating on the back LCD to prevent it from scratching.
Laptop LCD's are remarkably easy to open up and work with. You just need the right kind of screwdriver.
If that's the case, then something's wrong with your configuration. My XP-based work computer has a power policy in place to hibernate every night at 8:00pm and wake up at 7:30am. I've never had a problem with an IP address on resume.
I've also never had problems with IP addresses on suspend/hibernate/resume on my main laptop, even though that dual-boots between XP and Linux.
See... a lot of that depends on your hardware configuration. I've had computers that took forever to come out of hibernation with as little as 512MB of RAM. I've also had systems that came out of hibernation with 8x as much RAM in under 10s, including the POST.
The speed of your hard drive seems to be the determining factor, everything else being equal. I won't buy a system with less than 7200rpm hard drive, even in laptops, specifically because of that. There are other factors that affect hibernate speed, such as how well the kernel is optimized for it, and whether your BIOS properly handles the requests, but I don't think I'm going out on a limb when I say that hibernation time is largely dependent on your hardware configuration, while boot time is largely dependent on software configuration and how many services/etc. you have at startup. As a general rule, the more you're doing with your system, the more attractive hibernation becomes.
Absolutely the fastest hibernate/resume system I ever had was actually Windows 2000. That was the one that could suspend/resume with 4GB of RAM in under 10s. By contrast, that system took about a minute to boot from cold. Needless to say, it only ever rebooted for patches.