 |
||||||||||
|
 |
|
||||||||
|
||||||||||
|
|
|||||||||
|
||||||||||
|
Using OffHook in a Mac OS X Leopard Environment OffHook is not a "signed" application and will need to be authorized at first use after each reboot in OS X.5. Although Leopard permits administrative users to "sign" applications themselves, these signatures do not persist between reboots. As a result, it will be necessary to re-authorize OffHook each time it is launched. OffHook does play well with the "other" built-in Leopard firewall (ipfw), as long as the proper network port is open for UDP traffic. We are working on a way to properly sign OffHook for full compatibility with the Leopard firewall, but this probably won't be working for quite some time yet. For what it's worth, on 10.3 Panther and 10.4 Tiger, the default built-in firewall works fine with OffHook; you don't even need to open any ports (at least we didn't have to in our own testing). It's important to note that OffHook does not connect with other machines. OffHook merely broadcasts its own status on the local network, and receives such broadcasts from other users of the application. |
|
||||||||
|
© Copyright 2012 Redshank Software. All Rights Reserved. Contact us. |
|
||||||||
|
||||||||||
|
|
|
|
|
|
|
|
|
|
|