If AOL and hotmail alone required valid everse DNS the rest of the world would follow suit in short order.
Not very likely, for this would break large part of the e-mail infrastructure. There are many virtual hosters whose reverse DNS does not match the domain they are hosting. Or in my case with static IP home DNS that does resolves to something, but my domain name. And I suppose we can say bye, bye to many backup MX servers as well.
If the sender's domain is the only domain sending mail from a specific IP
address, we recommend that the reverse DNS entry (PTR Record) match the
domain name (A Record), but we do not require it.
AOL does require that all connecting Mail Transfer Agents have established
reverse DNS, regardless of whether it matches the domain.
Reverse DNS must be in the form of a fully-qualified domain name - reverse DNS
containing in-addr.arpa are not acceptable, as these are merely placeholders
for a valid PTR record. Reverse DNS consisting only of IP addresses are also not acceptable, as
they do not correctly establish the relationship between domain and IP address.
your ignorance is great, pf is already ported to FreeBSD for quite some time as a kernel loadable module, and it will be integrated with 5.3-RELEASE. Have you copy-pasted a FreeBSD flaming text a year old ?
Please.
Of course the trolls just copy/paste/edit, and it's a sign of their inferior and feeble mind. Not that they have any mind at all; it's just mindless copy/paste/edit, when they manage not to bungle the "edit" too much.
Most of them don't even do a copy/paste/edit : they download a script that does all the work for them. Quite frankly, I'm not sure that they are capable to do a copy/paste/edit.
This is why you never see any spark of intelligence or originality in their posting; it's the same post over and over and over and over and over again.
Packets per second says a lot about the stack, bits per second says more about the interface driver.
Packets per second says alot about the NIC as well. Use one of those cheap (cheap, like in bad quality) Realtek cards, and do a "ping -f" while watching top. See the CPU usage increase alot. Now, try some better cards, and you don't see the same.
It is usually high packets per second that brings a machine to its knees, as opposed to bits or bytes per second.
Indeed, in this is very you will see a very marked difference between low and high quality network cards. For instance, the common Realtek NIC offloads alot onto the CPU, and induce many interrupts. While high quality cards, like Intel gigabit, will do much prosessing on the card itself. A "ping -f" while using top can be instructive.
Don't mod me down, I'm serious... the warez scene is the biggest contributer making software free (in the financial sense), and it's healthy for the industry. Seriously, what percentage of the apps on your Windows machine did you pay for, inclusing the OS itself?
I don't have any cracked software on my wife's Windows 2000 Pro machine, including the OS itself. And the games I play there I've either paid for, or are open source (NetHack, mainly).
My guess that you are just a leach. When was the last time you filed a bug report, or sendt away a patch?
We should remember that some countries in effect have still to undergo the Englightenment, that even in countries that did, many people remain who hold irrational and antiscientific views, and that in some countries the Counter-reformation was successful.
Some countries are even undergoing an Unenglightenment. Sadly and very dangerously, USA is in that process with it's corporate controlled media that are essensially mouthpieces for state propaganda. Just look at the Bush administration long string of lies for going to war against Iraq that was repeated by the press.
When I first used mergemaster I thought it was the greatest thing since before that I had to tediously hand-pick through/usr/src/etc on OpenBSD and NetBSD in order to keep/etc up-to-date.
OpenBSD has mergemaster in ports, while NetBSD uses etcupdate.
Just like 5.3 BETA1, BETA2 does not detect my network card automatically, and nothing I do makes any difference (it's always been found by every Linux distribution and all other BSDs, including all previous releases of FreeBSD since 4.7).
Similar problem with my testing of 5.3 BETA1 : A wireless NIC that worked in current (when I tried it earlier this spring) is now not detected. Hope that is fixed with BETA2.
I thought the buffer overrun protection was AMD's idea, with the NX page flag.
NX (No eXecute) bit for CPU has been around for a while (for Alpha, and Sun's SPARC, for instance), and is not an AMD invention. On the other hand, AMD should be given credit for introducing such a security featuer in their new CPU. Intel has steadfastly refuced to implement such security features on x86, until forced by AMD.
Unless someone can give me specific examples of why this violates the GPL and other open source licenses other than "Its Microsoft and Microsoft is evil" I do plan to deliver a software application utilizing this technology for Linux
It (clinic) started with just three doctors, but since the Americans bombed one of the hospitals, and were currently sniping people as they attempted to enter/exit the main hospital, effectively there were only 2 small clinics treating all of Falluja. The other has been set up in a car garage.
As I was there, an endless stream of women and children who'd been sniped by the Americans were being raced into the dirty clinic, the cars speeding over the curb out front as their wailing family members carried them in.
One woman and small child had been shot through the neck -- the woman was making breathy gurgling noises as the doctors frantically worked on her amongst her muffled moaning.
The small child, his eyes glazed and staring into space, continually vomited as the doctors raced to save his life.
After 30 minutes, it appeared as though neither of them would survive.
One victim of American aggression after another was brought into the clinic, nearly all of them women and children.
This scene continued, off and on, into the night as the sniping continued.
What happend to the ideal of athletic competition? Sure, it's still in the charter, somewhere. But now I don't even watch the games anymore since it's has become a commercial yippo of corruption, drug abuse, cheating, money and nationalism (those athletes running around draped in their country's flag).
But, with all of the terrorist threats lately, bringing passport documents into the digital world is sure to increase security.
Why should that increase security? Perhaps there will be even more opportunities for forgeries.
From Bruce Schneier'
Crypto-Gram
There's one other problem with identity documents: the ease of getting legitimate documents in fraudulent names. Several of the 9/11 terrorists obtained fraudulent IDs from the Virginia Department of Motor Vehicles by paying a corrupt employee $1000 each. These weren't fake IDs. These were real IDs in fake names, with all the holograms and micro printing and whatever else the driver's licenses have to make them hard to forge.
Re:Sorry for repeating the blindingly obvious, but
on
The Spyware Inferno
·
· Score: 0, Offtopic
what spywares? what spyware removal software? what worms? what "20 minutes is the average amount of time for your computer to get infected to death"?
I use Linux exclusively and I can relate less and less with what Slashdot talks about these days. Which is ironic if you think about it...
Quite ironic indeed. Along Slashdotters with screaming for the latest binary only 3D driver from NVIDIA, and the latest binary only Flash, or some binary only wireless driver. So when the company deign to release something binary only, that might or might work with a particularly kernel, they are hailed as champions of Open Source. Truth is, those companies don't even release documentation at all, so writing a free driver is quite difficult. Oh yeah, I forgot : Now we can even use binary only drivers written for Microsoft Windows on FreeBSD. What a progress!
Maybe I'm overly pessimistic because I'm transposing my personal non-tech feelings on everything today (I am in the doghouse with the girl-friend, long story),
Your girl-friend is not a canine, I hope. Not that this is any of my business, though.
with well-understood types of solutions, one could presumely setup a "factory". Indeed, the off-shoring of programming task is part of that. On the other hand, there are programming/designing tasks where not even the problem is that well understood, or that require a high degree of independent, creative thinking.
I'm actually interested in reading the same e-mails on my dual-boot machine (windows + linux). It's very time consuming to have to switch to linux to find some important e-mail, because you have it in your linux e-mail client.
If you ISP's mailserver offer IMAP, then you can access the e-mail from both linux/windows since the e-mail is stored on the server. You might run out of space on the server if you get many e-mails and don't delete so often. Several e-mail clients can be configured to download the entire message, in case the mailserver is not accessible.
You can setup IPSec for your wireless network. Or if that becomes to troublesome to setup, you can use
OpenVPN
that is easy to configure and has a client for Windows as well.
After reading a few posts on this thread, I find it peculiar that so many slashdotters don't know that IPSec or related vpn products can be used to secure wireless.
My question to the crowd is, how effective would existing wireless encryption standards be at disabling AirPwn?
Use IPSec instead of WEP for the wireless network, and AirPwn would not amount to much more than DoS. OpenBSD has IPSec in the base install, and is fairly easy to setup.
ssh with protocoll 2 is also safe. If you connect to someone impersonating the ssh server, and you try to connect, ssh will give a warning that the keys on the ssh server has changed.
Slashdot Mirror
Not very likely, for this would break large part of the e-mail infrastructure. There are many virtual hosters whose reverse DNS does not match the domain they are hosting. Or in my case with static IP home DNS that does resolves to something, but my domain name. And I suppose we can say bye, bye to many backup MX servers as well.
What AOL sensibly require is :
Of course the trolls just copy/paste/edit, and it's a sign of their inferior and feeble mind. Not that they have any mind at all; it's just mindless copy/paste/edit, when they manage not to bungle the "edit" too much.
Most of them don't even do a copy/paste/edit : they download a script that does all the work for them. Quite frankly, I'm not sure that they are capable to do a copy/paste/edit. This is why you never see any spark of intelligence or originality in their posting; it's the same post over and over and over and over and over again.
Packets per second says alot about the NIC as well. Use one of those cheap (cheap, like in bad quality) Realtek cards, and do a "ping -f" while watching top. See the CPU usage increase alot. Now, try some better cards, and you don't see the same.
Indeed, in this is very you will see a very marked difference between low and high quality network cards. For instance, the common Realtek NIC offloads alot onto the CPU, and induce many interrupts. While high quality cards, like Intel gigabit, will do much prosessing on the card itself. A "ping -f" while using top can be instructive.
I don't have any cracked software on my wife's Windows 2000 Pro machine, including the OS itself. And the games I play there I've either paid for, or are open source (NetHack, mainly).
My guess that you are just a leach. When was the last time you filed a bug report, or sendt away a patch?
Some countries are even undergoing an Unenglightenment. Sadly and very dangerously, USA is in that process with it's corporate controlled media that are essensially mouthpieces for state propaganda. Just look at the Bush administration long string of lies for going to war against Iraq that was repeated by the press.
OpenBSD has mergemaster in ports, while NetBSD uses etcupdate.
Similar problem with my testing of 5.3 BETA1 : A wireless NIC that worked in current (when I tried it earlier this spring) is now not detected. Hope that is fixed with BETA2.
NX (No eXecute) bit for CPU has been around for a while (for Alpha, and Sun's SPARC, for instance), and is not an AMD invention. On the other hand, AMD should be given credit for introducing such a security featuer in their new CPU. Intel has steadfastly refuced to implement such security features on x86, until forced by AMD.
RTFA
Agreed. I'm running spamd (that implements greylisting) on my firewall. Very efficient, but I would not call it a "firewall", though.
And of course, like AA : Slaughtering Civilians In Falluja :
What happend to the ideal of athletic competition? Sure, it's still in the charter, somewhere. But now I don't even watch the games anymore since it's has become a commercial yippo of corruption, drug abuse, cheating, money and nationalism (those athletes running around draped in their country's flag).
Why should that increase security? Perhaps there will be even more opportunities for forgeries. From Bruce Schneier' Crypto-Gram
There's one other problem with identity documents: the ease of getting legitimate documents in fraudulent names. Several of the 9/11 terrorists obtained fraudulent IDs from the Virginia Department of Motor Vehicles by paying a corrupt employee $1000 each. These weren't fake IDs. These were real IDs in fake names, with all the holograms and micro printing and whatever else the driver's licenses have to make them hard to forge.
Quite ironic indeed. Along Slashdotters with screaming for the latest binary only 3D driver from NVIDIA, and the latest binary only Flash, or some binary only wireless driver. So when the company deign to release something binary only, that might or might work with a particularly kernel, they are hailed as champions of Open Source. Truth is, those companies don't even release documentation at all, so writing a free driver is quite difficult. Oh yeah, I forgot : Now we can even use binary only drivers written for Microsoft Windows on FreeBSD. What a progress!
Your girl-friend is not a canine, I hope. Not that this is any of my business, though.
with well-understood types of solutions, one could presumely setup a "factory". Indeed, the off-shoring of programming task is part of that. On the other hand, there are programming/designing tasks where not even the problem is that well understood, or that require a high degree of independent, creative thinking.
If you ISP's mailserver offer IMAP, then you can access the e-mail from both linux/windows since the e-mail is stored on the server. You might run out of space on the server if you get many e-mails and don't delete so often. Several e-mail clients can be configured to download the entire message, in case the mailserver is not accessible.
No, SSH protocoll 1 is vulnerable to man in the middle attacks. There is even a program called dsniff that do MITM attacks against SSH protocol 1.
So, for those that secure their wireless network, this is just a DoS tool.
Configure IPSec properly for your wireless network, and this amounts to no more than DoS.
After reading a few posts on this thread, I find it peculiar that so many slashdotters don't know that IPSec or related vpn products can be used to secure wireless.
You'll have a hard time exploiting a properly configured IPSec.
Use IPSec instead of WEP for the wireless network, and AirPwn would not amount to much more than DoS. OpenBSD has IPSec in the base install, and is fairly easy to setup.
ssh with protocoll 2 is also safe. If you connect to someone impersonating the ssh server, and you try to connect, ssh will give a warning that the keys on the ssh server has changed.