Originally posted by: n0cmonkey
I know OpenBSD is less effected than most other systems.
And atleast one other open source OS is using the same method. I think it's the grsecurity patches for Linux, but I'm not positive.
Originally posted by: spidey07
Originally posted by: n0cmonkey
I know OpenBSD is less effected than most other systems.
And atleast one other open source OS is using the same method. I think it's the grsecurity patches for Linux, but I'm not positive.
yeah, but openBSD doesn't run the internet.
silly!
Originally posted by: n0cmonkey
Originally posted by: spidey07
Originally posted by: n0cmonkey
I know OpenBSD is less effected than most other systems.
And atleast one other open source OS is using the same method. I think it's the grsecurity patches for Linux, but I'm not positive.
yeah, but openBSD doesn't run the internet.
silly!
Not yet
I keep seeing reasons not to use some of those big names out there... Maybe if they paid attention to what Free and Open Source Software projects were doing...![]()
Originally posted by: spidey07
Originally posted by: n0cmonkey
Originally posted by: spidey07
Originally posted by: n0cmonkey
I know OpenBSD is less effected than most other systems.
And atleast one other open source OS is using the same method. I think it's the grsecurity patches for Linux, but I'm not positive.
yeah, but openBSD doesn't run the internet.
silly!
Not yet
I keep seeing reasons not to use some of those big names out there... Maybe if they paid attention to what Free and Open Source Software projects were doing...![]()
maybe if they were able to forward at multi-gigabit speeds without being so bus limited and feature limited.
puh-lease. I've had this argument with the BSD bigots before. It simply cannot do what a real piece of network hardware (designed from the ground up to move packets...specifically in hardware) can do.
BSD will always be limited to the underlying hardware and never will compete with a router
Originally posted by: Boscoh
Prediction: Those ISP's/companies using encrypted BGP links, auth, and/or anti-spoofing will not be directly affected by this. The smaller ISP's that dont know what they're doing and some of the idiots that work at the bigger ones who left their BGP links wide open might be affected, outages might occur, and hopefully the stupid ones will get fired to make room for the people who know their stuff to get jobs. Keep in mind, these protective measures in BGP are NOT a new thing, they've been around a while and for good reasons. If your links are wide open at this point, you need to be updating your resume and calling recruiters.
My $.02
Originally posted by: FreshPrince
authentication should be both ways, and I doubt many isps support that...
Originally posted by: cmetz
spidey07, IPsec AH with MD5 is almost exactly the same processor overhead as TCP MD5. The TCP MD5 thing was intended to be a temporary hack while waiting for IPsec AH to be standardized, then everybody was going to switch to it. Meanwhile many folks didn't use TCP MD5, waiting for the real thing instead. Today, neither Cisco nor Juniper to my knowledge support AH for this. Too bad, too, because the TCP MD5 has some problems.
IPsec doesn't have to == ESP.
Originally posted by: cmetz
spidey07, that doesn't bother me. What's scary is that some people seriously want to public-key authenticate every BGP route. 140,000 RSA signature checks to bring a link up...
