It's more of a test of what will go very wrong or right. I have several Mac test machines so no worries if it messes one up.
Did you even read the article? It was talking about a vulnerability with Domain Name Servers. The standard, client version of the Mac doesn't have a DNS, it calls one. Usually your ISPs, which could be a BIND (Berkeley Internet Name Domain) server. The BIND client is your browser or any other application that makes calls to the DNS.
BTW, the problem affects all DNSs, BIND being just one of them.
Actually, there is a bind server daemon available even on the client version of MacOS X.
But, when using the default configuration of the OS, this bind server is never used. Moreover, it is not easy to activate it because it is started by the launchd daemon, and on the client version of the OS there is no simple way to modify its configuration : You have to use tools like Lingon.
So, it is here, it is for nuow vulnerable, but it is not used at all so there is no need to uninstall it. Just wait for the next Apple security update and the vulnerability will be corrected.
Did you even read the article? It was talking about a vulnerability with Domain Name Servers. The standard, client version of the Mac doesn't have a DNS, it calls one. Usually your ISPs, which could be a BIND (Berkeley Internet Name Domain) server. The BIND client is your browser or any other application that makes calls to the DNS.
BTW, the problem affects all DNSs, BIND being just one of them.
Yes I did, Microsoft & even Linux distributions released a patch to protect their client versions. This isn't just a server thing. Oddly enough Apple has yet to release one.. hehe even Sun released a fix in Java for it. This effected everyone.
Yes I did, Microsoft & even Linux distributions released a patch to protect their client versions. This isn't just a server thing. Oddly enough Apple has yet to release one.. hehe even Sun released a fix in Java for it. This effected everyone.
But were these changes due to the noted vulnerability or because of other issues with DNS? I puzzled over this when I read the article and decided that the author was saying that DNS had many issues and weaknesses, some exasperated by web browsers. And the author went on to state that Microsoft and others were fixing some of these other issues. I especially noted that The Register, which isn't shy at pocking their finger in anybody's eye, didn't even mention Safari or Firefox. If Microsoft did correct IE for this vulnerability and Safari had it but Apple hadn't corrected it, I would expect that The Register would trumpet it loud and clear.
I apologize for my previous post... when I don't get enough sleep I get really cranky and dumb. So please let me repost..
According to the US-CERT the DNS vulnerability does exist in FreeBSD, since I haven't seen any mention of Apple fixing this so far (again that I've seen). I think it's safe to say that OS X is also affected.
The position I?m in.. is that unless Apple publicly announced a time line for when they're going to fix it. The higher ups are going to give the order to complete remove BIND, as we don't need it.
Of course if and when Apple does fix it, my concern is how the updater will respond with BIND not being located on the HD.
I apologize for my previous post... when I don't get enough sleep I get really cranky and dumb. So please let me repost..
According to the US-CERT the DNS vulnerability does exist in FreeBSD, since I haven't seen any mention of Apple fixing this so far (again that I've seen). I think it's safe to say that OS X is also affected.
The position I’m in.. is that unless Apple publicly announced a time line for when they're going to fix it. The higher ups are going to give the order to complete remove BIND, as we don't need it.
Of course if and when Apple does fix it, my concern is how the updater will respond with BIND not being located on the HD.
Sorry again for my rather rude post.
The fixes have already been available for Linux distributions and I expect Apple to release a Security Patch to update to BIND 9.50+fixes.
Rich Mogull of TidBITS wrote an article (http://db.tidbits.com/article/9706) about this and has more information on the exploit and how the Mac is impacted. He says that the Mac OS server is the most vulnerable and that our client Macs, though less so, could also be impacted. Rich finishes the article by taking Apple to task for not distributing the BIND fix which he claims was one of the first tools to be fixed.
Rich Mogull of TidBITS wrote an article (http://db.tidbits.com/article/9706) about this and has more information on the exploit and how the Mac is impacted. He says that the Mac OS server is the most vulnerable and that our client Macs, though less so, could also be impacted. Rich finishes the article by taking Apple to task for not distributing the BIND fix which he claims was one of the first tools to be fixed.
Run your Software Update to get the security update fix.
Comments
Are you talking OS X Server? I honestly don't know if there is a BIND client but generally BIND is a server component.
Sorry, I should of been more specific.
I would like to remove BIND from the client version of OS X... say 10.4 & 10.5 (if possible).
If you wanna be more specific as to what you're trying to accomplish maybe we can find a work around
Again, I'm not 100% sure there is a client version of BIND but it would probably affect your DNS performance.
If you wanna be more specific as to what you're trying to accomplish maybe we can find a work around
Trying to remove BIND, because of the security vulnerabilities:
http://www.theregister.co.uk/2008/07..._fix_alliance/
It's more of a test of what will go very wrong or right. I have several Mac test machines so no worries if it messes one up.
Trying to remove BIND, because of the security vulnerabilities:
http://www.theregister.co.uk/2008/07..._fix_alliance/
It's more of a test of what will go very wrong or right. I have several Mac test machines so no worries if it messes one up.
Did you even read the article? It was talking about a vulnerability with Domain Name Servers. The standard, client version of the Mac doesn't have a DNS, it calls one. Usually your ISPs, which could be a BIND (Berkeley Internet Name Domain) server. The BIND client is your browser or any other application that makes calls to the DNS.
BTW, the problem affects all DNSs, BIND being just one of them.
But, when using the default configuration of the OS, this bind server is never used. Moreover, it is not easy to activate it because it is started by the launchd daemon, and on the client version of the OS there is no simple way to modify its configuration : You have to use tools like Lingon.
So, it is here, it is for nuow vulnerable, but it is not used at all so there is no need to uninstall it. Just wait for the next Apple security update and the vulnerability will be corrected.
Did you even read the article? It was talking about a vulnerability with Domain Name Servers. The standard, client version of the Mac doesn't have a DNS, it calls one. Usually your ISPs, which could be a BIND (Berkeley Internet Name Domain) server. The BIND client is your browser or any other application that makes calls to the DNS.
BTW, the problem affects all DNSs, BIND being just one of them.
Yes I did, Microsoft & even Linux distributions released a patch to protect their client versions. This isn't just a server thing. Oddly enough Apple has yet to release one.. hehe even Sun released a fix in Java for it. This effected everyone.
Yes I did, Microsoft & even Linux distributions released a patch to protect their client versions. This isn't just a server thing. Oddly enough Apple has yet to release one.. hehe even Sun released a fix in Java for it. This effected everyone.
But were these changes due to the noted vulnerability or because of other issues with DNS? I puzzled over this when I read the article and decided that the author was saying that DNS had many issues and weaknesses, some exasperated by web browsers. And the author went on to state that Microsoft and others were fixing some of these other issues. I especially noted that The Register, which isn't shy at pocking their finger in anybody's eye, didn't even mention Safari or Firefox. If Microsoft did correct IE for this vulnerability and Safari had it but Apple hadn't corrected it, I would expect that The Register would trumpet it loud and clear.
According to the US-CERT the DNS vulnerability does exist in FreeBSD, since I haven't seen any mention of Apple fixing this so far (again that I've seen). I think it's safe to say that OS X is also affected.
US-CERT Vulnerability Warning
The position I?m in.. is that unless Apple publicly announced a time line for when they're going to fix it. The higher ups are going to give the order to complete remove BIND, as we don't need it.
Of course if and when Apple does fix it, my concern is how the updater will respond with BIND not being located on the HD.
Sorry again for my rather rude post.
I apologize for my previous post... when I don't get enough sleep I get really cranky and dumb. So please let me repost..
According to the US-CERT the DNS vulnerability does exist in FreeBSD, since I haven't seen any mention of Apple fixing this so far (again that I've seen). I think it's safe to say that OS X is also affected.
US-CERT Vulnerability Warning
The position I’m in.. is that unless Apple publicly announced a time line for when they're going to fix it. The higher ups are going to give the order to complete remove BIND, as we don't need it.
Of course if and when Apple does fix it, my concern is how the updater will respond with BIND not being located on the HD.
Sorry again for my rather rude post.
The fixes have already been available for Linux distributions and I expect Apple to release a Security Patch to update to BIND 9.50+fixes.
Rich Mogull of TidBITS wrote an article (http://db.tidbits.com/article/9706) about this and has more information on the exploit and how the Mac is impacted. He says that the Mac OS server is the most vulnerable and that our client Macs, though less so, could also be impacted. Rich finishes the article by taking Apple to task for not distributing the BIND fix which he claims was one of the first tools to be fixed.
Run your Software Update to get the security update fix.