SEcube open-source SDK
Class List
Here are the classes, structs, unions and interfaces with brief descriptions:
[detail level 12]
 NCryptoInitialisation
 CParametersL1CryptoInit default modes
 Cgroup_policyThe policy class is used to model a security policy adopted by a group. A policy for a group has 3 features: a maximum number of keys for the group, a common algorithm for all keys belonging to the group, a default cryptoperiod common to all keys belonging to the group
 Cse3Algo_SEcube Algorithm structure
 Cse3Key_SEcube Key structure
 Cse3Session_SEcube Communication session structure
 Cse_groupImplement the concept of group inside SEkey. Class members are kept private and suitable getter/setter methods are provided
 Cse_keyThe key class is used to model a key object. A key has several properties which are kept private (id, name, owner, status, algorithm, length, generation time, activation time, expiration time). Public methods are available to retrieve the values of private properties
 Cse_userThe user class is used to model a user object. User's attributes are private but methods are available to retrieve them
 CSEfileA SEfile object is used to manage a file encrypted with SEfile
 CSEFILE_HANDLEThe SEFILE_HANDLE struct This abstract data type is used to hide from higher level of abstraction its implementation. The data stored in here are the current physical file pointer position and the file descriptor OS-dependent data type
 CSEFILE_HEADERThe SEFILE_HEADER struct This data struct is used to define a 31 bytes field inside a sector while taking care of its inner composition
 CSEFILE_SECTORThe SEFILE_SECTOR struct This data struct is the actual sector organization. The total size should ALWAYS be equal to SEFILE_SECTOR_SIZE. The first sector is used to hold ONLY the header. Thanks to the union data type, the developer can simply declare a sector and then choose if it is the header sector or not
 CSEFILE_SQL_SECTORThe SEFILE_SQL_SECTOR struct This data struct is the actual sector organization for encrypted SQLite databases. The total size should ALWAYS be equal to SEFILE_SQL_SECTOR_SIZE. The first sector is used to hold ONLY the header. Thanks to the union data type, the developer can simply declare a sector and then choose if it is the header sector or not. This sector is similar to the original one but with higher overhead
 CSEKEY_HEADERThe header of each file encrypted with SEfile. This is the header that contains info for the SEkey system. It is stored as cleartext and it is not authenticated. The dimension is always SEKEY_HDR_LEN
 CstatementHandy RAII wrapper for sqlite3_stmt which requires call to sqlite3_finalize to avoid resource leakage. See the SQLite documentation for more informations about sqlite3_stmt
 Cuserdata_Structure used to enclose all elements required by the APIs to initialize a user device inside SEkey
 Cuserinfo_Simlpe struct used to store the details about the SEkey user which is using the application. ID and name are not really user when SEkey is in admin mode, they are used when SEkey is in user mode. The device serial number instead is always used and is crucial for the correct execution of the SEkey KMS