On Mac OS X 10.5, if you connect two different ports on a host to two different networks and assign them with two different IP schemes then only one can act as the default gateway. This means that any incoming packets will all, by default, get responded to over the default gateway; despite which interface the packets came in on.
A number of you may have noticed the article on ZDNet that stated that Mac OS X now has built in Malware protection (actually, I guess Intego made it public). Despite the fact that the articles from Intego and then ZDNet were written prior to the release of the actual operating system (in their defense it was only 3 days prior) they have a point.
In a number of contexts, we hear about directory services plug-ins. A directory services plug-in is a way for a Mac OS X computer to leverage the DirectoryServices daemon to obtain account information (be it authentication or policy information) from a server.
I've borrowed from Peter Bukowinski's script that will lookup when an AD user's password is due to expire, and expanded upon it to run as a task in the OS X menu bar. The applet includes preference settings for the following: Adjust how often you are required to change your password (5 - 365 days).Automatically launch the applet at logon.
I had a hard time finding a step-by-step procedure for setting up OS X Server Wiki with Active Directory Integration (aside from just setting authentication to plain text on the Apple site) so, I wrote the following procedure.
This may work on Leopard Server as well, but I haven't tested it. There are several brute-force VPN protocol attacks rampant on the internet, and they may leave your VPN service in an unusable state by flooding it with connection requests.
I've been doing some pretty intensive research down here with iSCSI setups of various kinds. This market segment was a little rough a year ago...but it's much better now.
I just surfaced out of a situation with a Mac Server connected to ADwith Kerberos Authentication. Much help was received from Apple and I was given permission to share the "fix" for anyone else out thereattempting this type of solution.
If you have an Open Directory infrastructure, and you want to secure your connections between the client and Open Directory services using SSL, the simplest solution is to purchase SSL certificates and install the certificate on your Open Directory Master and each Replicas.
If you are in an environment where you are integrating Mac OS X with a 3rd party KDCs, you already know about builtin:krb5authnoverify addition to your /etc/authorization. But did you know that you can use the builtin:krb5authenticate option to provide better security by assuring that your KDC is not being spoofed?
