Then they'll just start hopping domains, not sticking with one long enough to land on the blacklist. They might even subsidize services to give free 3rd-level domain redirects just so they could have an effectively infinite number of domains.
Alternatively, I could set up a somewhat convincing spam-marketing site somewhere, then once I'd been blacklisted, change the DNS to point at whatever victim I chose.
This plan would have the effect of turning the email system into a DDoS amplifier. A simple email sent through some SMTP server somewhere saying "Enlarge your penis! http://12.34.56.78:1234" to multiple recipients would greatly increase an attacker's effective DoS bandwidth.
First off, there is (in my humble opinion) no way to guarantee the safety of data that is accessible by machines connected to the internet, no matter how many firewalls are in place. Even something as stupid as having web access on a work machine may one day cause you grief, no matter the security, no matter what operating system. A Trojan Horse, whether something whipped up by a hacker with you as the specific target or a worm coming in from the wild, can access files on your machine and then send them elsewhere. The only true, secure solution is to put two computers on everyone's desk, one for outside access, and one internal-only. You'll also need to police the systems so no employees try to sneak a connection between the two.
Taking work home is even worse. Buy your employees dedicated laptops -- then lock the OSes so that the network will only work on your intranet. Otherwise, again, your precious data may be exposed to the outside world.
Go out and find a cheap web account with POP that only charges a few dollars a month. Then install a script-based email client. The end result will have no annoying advertising, and you'll have web space and your own domain to play with to boot.
"I'll wait until it's out on cable." "I'll wait until it's out on DVD."
The only reason people still go to the movies is because they can't get an experience like it at home. Advances in home theater tech -- HDTV, Dolby 6.1 -- and disruptions in the theaters -- babies crying, thrown popcorn -- are making the movie theater less popular. They're being amazingly stupid by adding even more annoyances.
The reason for ES5's inclusion of the function is as bad as the function itself; if ES5 is remotely upgradeable without the user's okay, then the upgrade may contain malicious code.
Depending on how the RIAA is getting their lists, the article is at best fallacious and at worst deceptive.
Supposedly the RIAA is going after people who've been sharing more than a thousand titles. It is highly unlikely the RIAA would've gotten this information by sniffing the network or by putting out queries; it would just be too impractical. Gnutella hosts will very often put a list of what they're sharing up in the form of a web page, and if the RIAA were reading the page, they'd be retrieving it directly from the user's verifiable IP.
Similarly, other networks have the option to "browse this person's list". From what I understand none of these networks route the results of such requests through any sort of indirection; the data is also transferred via a direct connection to the "offender's" machine.
Pretty soon, you'll have people believing they can buy what they see in TV shows. Me, I'm going to walk into my local Best Buy and ask where the neuralyzers are, or go to Circuit City and try to find a phaser.
Microsoft's letter is interesting in that they seem to be warning Lindows about something they have no jurisdiction over. Robertson is taking a big risk with the site; he's covering the bill, and if he isn't being very careful with his language and procedures, the judge could throw out claims filed through the site and Lindows would be short a large chunk of cash.
SQL injection would be a potential problem, but in this case the application isn't designed for public use. In order for someone to access the web pages he would need a valid user name and password. It's assumed that people with that information would be valid users and wouldn't abuse the system.
If it's a web app, you could make it available via https and give people usernames and passwords. ssl is a pretty secure solution, despite the recent exploits; and if you keep up with your patches, forwarding port 443 to your web server won't be an awful security problem. Your largest issues will be insecure passwords and brute-force attacks on them.
Alternatively you could add VPN access to your intranet, allowing remote users to log in via an encrypted tunnel. This would have benefits and drawbacks over the above method; it would be more secure, but less accessible. (You may not consider this a bad thing.) The key, if done correctly, would be more secure than a password a user could remember, but it might also be treated less securely and stolen from a remote machine.
I would recommend you print on smaller sheets and transfer the ink to the surface, rather than try to create such a large printing device. I do know they make sheets designed to "iron-on" transfer to other surfaces; whether the surface you plan to use is appropriate, I don't know.
I just dropped an IDE drive into a system with a SATA main drive; and the IDE drive turned out to have a prior boot order. If it'd had an OS on it, I might have had a lot of trouble getting things straightened out again.
Firewire is SLOW. You're taking drives capable of bursting 100 or 133 megabytes per second and plugging them into a bus that maxes out at 50, with a practical limit of half that. Also, aren't those little bridges expensive? You might be better off getting a RAID controller and boosting your throughput to 1/2 gigabyte per second or better.
Of course, Firewire is a lot more convenient. But if you want convenience, why not just buy single-drive externals and stack them? I suppose you may have an old case lying around, but I'd personally find a bunch of drives that were easily separable more useful. If I needed to take the data on one with me, I could just unhook it and bring it along.
If your system boots the new drive instead of your old one, then you have the choice of wiping the new drive from within Lindows, an OS you may not be familiar with and which may complain about being erased while you're running it, or of booting off the Windows install CD and zapping the partition from there. I'd consider this a rather annoying inconvenience I'd prefer to avoid.
(1) Shut down computer. (2) Install hard drive, connect power and IDE cables. (3) Turn computer back on and make sure it autodetects the drive. (4) Tear your hair out as the computer proceeds to boot Lindows instead of (FreeBSD/Windows/Linux/Plan9). (5) Uninstall the hard drive, and sigh in relief as your old set-up proceeds to boot normally. (6) Return the hard drive to the store, yelling and screaming until they agree not to charge you a restocking fee.
The OS could, on boot, read update information off a directory on the hard drive. For that matter, if it were done cleverly, it might even be able to load its kernel image from it.
The advantage of having control over the environment the game runs in is enormous. Of course, it also means the machine would be useless for background tasks, and no one could interrupt you with something more important...
Aaah, who am I kidding; nothing's more important than the game! ph34r m3 l4m3rz! d13!
If you want to conserve the network's bandwidth, get multicast up and running. Multicast is by far the most efficient way to distribute data, free or otherwise. Tell your ISP that, when they get IPv6 up and running, you want to have access to multicast content.
Slashdot Mirror
Then they'll just start hopping domains, not sticking with one long enough to land on the blacklist. They might even subsidize services to give free 3rd-level domain redirects just so they could have an effectively infinite number of domains.
Alternatively, I could set up a somewhat convincing spam-marketing site somewhere, then once I'd been blacklisted, change the DNS to point at whatever victim I chose.
This plan would have the effect of turning the email system into a DDoS amplifier. A simple email sent through some SMTP server somewhere saying "Enlarge your penis! http://12.34.56.78:1234" to multiple recipients would greatly increase an attacker's effective DoS bandwidth.
Sounds like there's a need for a community around this gizmo, where people can trade their scripts, etc.
most notably that "...recording at 24 times normal speed is possible when copying previously recorded video... to a DVD-R optical disc"
Gamers -- and video pirates -- around the world, rejoice!
First off, there is (in my humble opinion) no way to guarantee the safety of data that is accessible by machines connected to the internet, no matter how many firewalls are in place. Even something as stupid as having web access on a work machine may one day cause you grief, no matter the security, no matter what operating system. A Trojan Horse, whether something whipped up by a hacker with you as the specific target or a worm coming in from the wild, can access files on your machine and then send them elsewhere. The only true, secure solution is to put two computers on everyone's desk, one for outside access, and one internal-only. You'll also need to police the systems so no employees try to sneak a connection between the two.
Taking work home is even worse. Buy your employees dedicated laptops -- then lock the OSes so that the network will only work on your intranet. Otherwise, again, your precious data may be exposed to the outside world.
Go out and find a cheap web account with POP that only charges a few dollars a month. Then install a script-based email client. The end result will have no annoying advertising, and you'll have web space and your own domain to play with to boot.
"I'll wait until it's out on cable."
"I'll wait until it's out on DVD."
The only reason people still go to the movies is because they can't get an experience like it at home. Advances in home theater tech -- HDTV, Dolby 6.1 -- and disruptions in the theaters -- babies crying, thrown popcorn -- are making the movie theater less popular. They're being amazingly stupid by adding even more annoyances.
...they're trying to cache two-word searches.
And aren't doing too well at it.
The reason for ES5's inclusion of the function is as bad as the function itself; if ES5 is remotely upgradeable without the user's okay, then the upgrade may contain malicious code.
If someone can write HEllO WORld with Malbolge, I'm sure they can do that audio thing.
...by getting the site slashdotted.
Depending on how the RIAA is getting their lists, the article is at best fallacious and at worst deceptive.
Supposedly the RIAA is going after people who've been sharing more than a thousand titles. It is highly unlikely the RIAA would've gotten this information by sniffing the network or by putting out queries; it would just be too impractical. Gnutella hosts will very often put a list of what they're sharing up in the form of a web page, and if the RIAA were reading the page, they'd be retrieving it directly from the user's verifiable IP.
Similarly, other networks have the option to "browse this person's list". From what I understand none of these networks route the results of such requests through any sort of indirection; the data is also transferred via a direct connection to the "offender's" machine.
Pretty soon, you'll have people believing they can buy what they see in TV shows. Me, I'm going to walk into my local Best Buy and ask where the neuralyzers are, or go to Circuit City and try to find a phaser.
Microsoft's letter is interesting in that they seem to be warning Lindows about something they have no jurisdiction over. Robertson is taking a big risk with the site; he's covering the bill, and if he isn't being very careful with his language and procedures, the judge could throw out claims filed through the site and Lindows would be short a large chunk of cash.
...marshmallows.
Maybe we can combine the methods, add graham crackers, and create C-smores!
SQL injection would be a potential problem, but in this case the application isn't designed for public use. In order for someone to access the web pages he would need a valid user name and password. It's assumed that people with that information would be valid users and wouldn't abuse the system.
If it's a web app, you could make it available via https and give people usernames and passwords. ssl is a pretty secure solution, despite the recent exploits; and if you keep up with your patches, forwarding port 443 to your web server won't be an awful security problem. Your largest issues will be insecure passwords and brute-force attacks on them.
Alternatively you could add VPN access to your intranet, allowing remote users to log in via an encrypted tunnel. This would have benefits and drawbacks over the above method; it would be more secure, but less accessible. (You may not consider this a bad thing.) The key, if done correctly, would be more secure than a password a user could remember, but it might also be treated less securely and stolen from a remote machine.
I would recommend you print on smaller sheets and transfer the ink to the surface, rather than try to create such a large printing device. I do know they make sheets designed to "iron-on" transfer to other surfaces; whether the surface you plan to use is appropriate, I don't know.
I just dropped an IDE drive into a system with a SATA main drive; and the IDE drive turned out to have a prior boot order. If it'd had an OS on it, I might have had a lot of trouble getting things straightened out again.
Well, that was a bit difficult to determine, considering his web page is thoroughly slashdotted.
Firewire is SLOW. You're taking drives capable of bursting 100 or 133 megabytes per second and plugging them into a bus that maxes out at 50, with a practical limit of half that. Also, aren't those little bridges expensive? You might be better off getting a RAID controller and boosting your throughput to 1/2 gigabyte per second or better.
Of course, Firewire is a lot more convenient. But if you want convenience, why not just buy single-drive externals and stack them? I suppose you may have an old case lying around, but I'd personally find a bunch of drives that were easily separable more useful. If I needed to take the data on one with me, I could just unhook it and bring it along.
If your system boots the new drive instead of your old one, then you have the choice of wiping the new drive from within Lindows, an OS you may not be familiar with and which may complain about being erased while you're running it, or of booting off the Windows install CD and zapping the partition from there. I'd consider this a rather annoying inconvenience I'd prefer to avoid.
(1) Shut down computer.
(2) Install hard drive, connect power and IDE cables.
(3) Turn computer back on and make sure it autodetects the drive.
(4) Tear your hair out as the computer proceeds to boot Lindows instead of (FreeBSD/Windows/Linux/Plan9).
(5) Uninstall the hard drive, and sigh in relief as your old set-up proceeds to boot normally.
(6) Return the hard drive to the store, yelling and screaming until they agree not to charge you a restocking fee.
The OS could, on boot, read update information off a directory on the hard drive. For that matter, if it were done cleverly, it might even be able to load its kernel image from it.
The advantage of having control over the environment the game runs in is enormous. Of course, it also means the machine would be useless for background tasks, and no one could interrupt you with something more important...
Aaah, who am I kidding; nothing's more important than the game! ph34r m3 l4m3rz! d13!
If you want to conserve the network's bandwidth, get multicast up and running. Multicast is by far the most efficient way to distribute data, free or otherwise. Tell your ISP that, when they get IPv6 up and running, you want to have access to multicast content.