I'd say it mostly depends on your distribution. Mandrake 9.2 comes with SuperFreeS/WAN. SuSE is excellent too. You can get it working within minutes by adding just a few lines to ipsec.secrets and ipsec.conf.
RedHat on the other hand preferred to distribute CIPE (which turns out to be insecure)instead of FreeS/WAN, so you had to compile your own kernel or use binary modules from the FreeS/WAN site. Unfortunately these binary RPMs only contain the X.509 patch and no extra features like SuperFreeS/WAN.
Well, the author wrote: "The security risks from this code appear to be low. Microsoft do appear to be checking for buffer overruns in the obvious places". I found that a bit ironic because the next day an exploit was found.
Although an exploit was found, the security risk is low. That's probably true, because most people have upgraded from IE 5.x to 6.x or some other browser.
Still, I just checked the stats on a webpage about a moderately advanced security topic that I recently made. It turns out that almost 5% of the visitors use IE 5.x. Yikes...
"In short, there is nothing really surprising in this leak. Microsoft does not steal open-source code. Their older code is flaky, their modern code excellent. Their programmers are skilled and enthusiastic. Problems are generally due to a trade-off of current quality against vast hardware, software and backward compatibility."
But this IE exploit shows that the author was wrong on at least one account:
"The security risks from this code appear to be low. Microsoft do appear to be checking for buffer overruns in the obvious places. The amount of networking code here is small enough for Microsoft to easily check for any vulnerabilities that might be revealed: it's the big applications that pose more of a risk. This code is also nearly four years old: any obvious problems should be patched by now".
The problem is that Samsung and Siemens are now essentially being asked to license an OS from, and pay fees to, their largest competitor. As Microsoft just makes software, not the actual phones, it is not seen as a competitor in the same way, and licensing Windows Mobile may not be such a bitter pill to swallow.
Not a bitter pill? Well, there are not manyWindows Mobile Phone Edition licencees, but one of them got
royally screwed.
"There has been press recently about a potential dictionary attack under some conditions. In essence this says that if you choose a bad password (or key) to protect your system you may be vulnerable to dictionary attack. So what's new? The same applied to security systems the world over".
Most vendors refuse to release updated drivers with WPA/TKIP support for their 802.11b gear. They knowingly sell broken (read: WEP) hardware that they don't intend to fix. They rather want you to buy 802.11g gear for WPA support!
You know what, I'm fed up with this. Might just as well buy this Chinese gear then... (And run IPsec over it).
A few months ago Mi2g seemed to be of the opinion that Linux and other Unices were less vulnerable than Windows. Microsoft even complained
about that...
Slashdot Mirror
RedHat on the other hand preferred to distribute CIPE (which turns out to be insecure)instead of FreeS/WAN, so you had to compile your own kernel or use binary modules from the FreeS/WAN site. Unfortunately these binary RPMs only contain the X.509 patch and no extra features like SuperFreeS/WAN.
I believe Debian required some compiling too.
Oh, please. Everybody has been using at least 3DES for a long time. Except perhaps Cisco where you pay extra for strong encryption.
Perhaps they bought Virtual PC so that Xbox 1 games will run on Xbox 2? Similar to how Palm OS 5 deals with older programs?
I use WAP for radar images, similar to these. Mainly when I'm on the road.
Well, the author wrote: "The security risks from this code appear to be low. Microsoft do appear to be checking for buffer overruns in the obvious places". I found that a bit ironic because the next day an exploit was found.
Although an exploit was found, the security risk is low. That's probably true, because most people have upgraded from IE 5.x to 6.x or some other browser.
Still, I just checked the stats on a webpage about a moderately advanced security topic that I recently made. It turns out that almost 5% of the visitors use IE 5.x. Yikes...
"In short, there is nothing really surprising in this leak. Microsoft does not steal open-source code. Their older code is flaky, their modern code excellent. Their programmers are skilled and enthusiastic. Problems are generally due to a trade-off of current quality against vast hardware, software and backward compatibility."
But this IE exploit shows that the author was wrong on at least one account:
"The security risks from this code appear to be low. Microsoft do appear to be checking for buffer overruns in the obvious places. The amount of networking code here is small enough for Microsoft to easily check for any vulnerabilities that might be revealed: it's the big applications that pose more of a risk. This code is also nearly four years old: any obvious problems should be patched by now".
Not a bitter pill? Well, there are not manyWindows Mobile Phone Edition licencees, but one of them got royally screwed.
These card are relatively inexpensive. There's no particular reason to pick a Centrino laptop because of the built-in WLAN support.
Pesky Martians! :-)
Oh boy. I wouldn't want to be a developer of Windows Services for Unix.
You're sure to be at the bottom of the caste system there at Microsoft...
The person who moderated this as offtopic does not understand humour or should go out more :-)
http://www.net-security.org/article.php?id=619
"There has been press recently about a potential dictionary attack under some conditions. In essence this says that if you choose a bad password (or key) to protect your system you may be vulnerable to dictionary attack. So what's new? The same applied to security systems the world over".
Most vendors refuse to release updated drivers with WPA/TKIP support for their 802.11b gear. They knowingly sell broken (read: WEP) hardware that they don't intend to fix. They rather want you to buy 802.11g gear for WPA support!
You know what, I'm fed up with this. Might just as well buy this Chinese gear then... (And run IPsec over it).
I, for one, welcome our new Bangalore Overlords.
That's what they often do. Scores of Borland people went to Microsoft, for example.
The FBI simply renamed it to DCS1000. "We had a concern that it wasn't a good name for the system".
Or satellite pictures...
With a name like that, it was bound to fail!
But you're right, Mandrake will also release an x86-64 version of 9.2.
Hm, if that doesn't show his mindset, being from Utah and all...
Fortunately he didn't mention:
John(3:16)
Don't start about personality!
And now it's the other way around?
Well, yes. But you are missing the point.
With this GPS scheme you can do differentiated pricing. You can make certain roads on a certain time more expensive in an effort to steer traffic.
That does not have to be the case if your read this.
How about this rabbit-tiger hybrid?
That's no ordinary rabbit! 'Tis the most foul, cruel and bad-tempered rodent you ever set eyes on!