After deployment I only get: Server Error in '/' Application. -------------------------------------------------------------------------------- Required permissions cannot be acquired. Descriptio...
Currently, doesn't support SPFile objects so is not usable with document libraries since it skews the name making the item unreachable
Add a link to the CryptoCollaboration Operations page when a list item has been brought up, which will direct to the same location with the same property hydration. This ensure that a user has the ...
This task will trim interface components based on previously user interaction with CryptoCollaboration. In essence, this will create two fields: "IsEncrypted" of type SPFieldType.Boolean and "Algor...
Not very business critical, however the SPList.Title property is not set, it is returning the SPListItem.Name property which wasn't caught during testing, since they were both named "test" so appea...
Previously, during the installation of CryptoCollaboration the target in the solution manifest would put the shared sister assemblies in the GAC (Global Assembly Cache), thereby giving said assembl...
Currently, I can't get lookup fields (SPFieldLookup objects) to encrypt since the data is considered invalid during the update process of the data
Fixed the issue that allows SPFieldChoice types to be encrypted in a similar fashion as the rest of the field types.
Allow the encryption of documents as well as list items, scrambling both contents as well as metadata.
The exception handling is not currently enough for industry standards, particularly around malformed encryption key and initialization vectors. I am currently looking into enhancing this along with...
