One of the features of BladeLogic is the ability to distribute software throughout the enterprise. This process opens the possibility that the software could be altered in some way - either by corruption or intentional modification.
Some other Distribution Tools use special protection methods to ensure the package content as delivered is the same as what was originally packaged. This protection is achieved e.g. by calculating a hash value that represents the package contents. This value is stored in the database and is authoritative for the package. When packages are distributed throughout the heirarchy and to targets this hash value is included and is used by the receiving target to validate the package is correct.
What about BladeLogic ? ... I could not find such protection mechanisms during my distribution tests ...
This is currently not supported. Open up a rfe request for this.
Thank you, Bill, that confirms my suspicions !