Secure Distributed Objects

Use socket-based SSL communications in the Mac OS X Distributed Objects system
Download

Secure Distributed Objects Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Freeware
  • Price:
  • FREE
  • Publisher Name:
  • Wade Tregaskis
  • Publisher web site:
  • Operating Systems:
  • Mac OS X
  • File Size:
  • 54 KB

Secure Distributed Objects Tags


Secure Distributed Objects Description

Use socket-based SSL communications in the Mac OS X Distributed Objects system Secure Distributed Objects provides a method for using socket-based SSL communications in the Mac OS X Distributed Objects system. It does so by providing a SecureSocketPort, NSPort subclass and other utilities.NOTE: Secure Distributed Objects is licensed and distributed under the terms of the BSD License. What's New in This Release: · No longer dependent on the Keychain framework, but the functionality has not changed (still accepts Certificate & Identity instances in the place of SecCertificateRef's and SecIdentityRef's). · Debugging output off by default now, since things seem to work well enough. Please make sure you re-enable this if you find a problem, as it aids greatly in bug fixing. · setExportLimitsDisabled: method removed, replaced with disableExportLimits. The old method had too many potential security problems with it. It will only be restored if they can be resolved. In the meantime, the replacement method works better anyway and should cover most uses. · Export limits are enabled by default now, due to the change noted above, so make sure to disable them manually if you can. Leaving export limits enabled creates a very significant security risk. · Removed a lot of junk code, and old debugging code. This has made things a bit easier to read, if nothing else. · Implemented a basic control protocol in parallel to the existing one. This makes the new version incompatible with previous versions, and will probably mean you can't communicate between the two. If a legacy mode is required, it can be added with minimal effort... I have declined to do so at present simply in the interests of cleanliness. · Automatic connectivity verification, in the form of a fairly elaborate ping/pong system. This is disabled by default, in the interest of preserving bandwidth. · Closing-notification, whereby graceful closes at one end of the connection trigger an immediate close at the other end. Still doesn't help in the situations where the connection is severed unexpectedly, but that's why the connectivity verification has been implemented. · Delegate support for manual authentication and connection management. If you use turn automatic authentication off (it's on by default) you will now have to provide a delegate that responds to the appropriate method. This makes sure some authentication is performed at some point, closing some potential bugs in this area. In the connection management area, your delegate can now specify whether a connection should be allowed or killed when it is made, so that you can screen hosts by name/address, port, etc. · Statistics recording, enabling you to see how many messages have gone through a particular port, how many pings, how many timeouts, etc. · A few small bug fixes here and there, as required.


Secure Distributed Objects Related Software