SecureString Unicode C Reference Documentation

SecureString

Current Version: 11.0.0

A string class that stores the characters in memory in 256-bit AES CBC encrypted form. The encryption key will be a randomly-generated key.

Create/Dispose

HCkSecureStringW instance = CkSecureStringW_Create();
// ...
CkSecureStringW_Dispose(instance);

HCkSecureStringW CkSecureStringW_Create(void);

Creates an instance of the HCkSecureStringW object and returns a handle ("void *" pointer). The handle is passed in the 1st argument for the functions listed on this page.

void CkSecureStringW_Dispose(HCkSecureStringW handle);

Objects created by calling CkSecureStringW_Create must be freed by calling this method. A memory leak occurs if a handle is not disposed by calling this function. Also, any handle returned by a Chilkat "C" function must also be freed by the application by calling the appropriate Dispose method, such as CkSecureStringW_Dispose.

Properties

DebugLogFilePath

void CkSecureStringW_getDebugLogFilePath(HCkSecureStringW cHandle, HCkString retval);
void CkSecureStringW_putDebugLogFilePath(HCkSecureStringW cHandle, const wchar_t *newVal);
const wchar_t *CkSecureStringW_debugLogFilePath(HCkSecureStringW cHandle);

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

A timeout property set to 0, indicating an infinite timeout.
A hang occurring within an event callback in the application code.
An internal bug in the Chilkat code causing the hang.

More Information and Examples

Example showing how to use DebugLogFilePath.

LastErrorHtml

void CkSecureStringW_getLastErrorHtml(HCkSecureStringW cHandle, HCkString retval);
const wchar_t *CkSecureStringW_lastErrorHtml(HCkSecureStringW cHandle);

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

LastErrorText

void CkSecureStringW_getLastErrorText(HCkSecureStringW cHandle, HCkString retval);
const wchar_t *CkSecureStringW_lastErrorText(HCkSecureStringW cHandle);

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

More Information and Examples

Concept of LastErrorText LastErrorText Standard Information

LastErrorXml

void CkSecureStringW_getLastErrorXml(HCkSecureStringW cHandle, HCkString retval);
const wchar_t *CkSecureStringW_lastErrorXml(HCkSecureStringW cHandle);

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

LastMethodSuccess

BOOL CkSecureStringW_getLastMethodSuccess(HCkSecureStringW cHandle);
void CkSecureStringW_putLastMethodSuccess(HCkSecureStringW cHandle, BOOL newVal);

Indicates the success or failure of the most recent method call: TRUE means success, FALSE means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages.

MaintainHash

void CkSecureStringW_getMaintainHash(HCkSecureStringW cHandle, HCkString retval);
void CkSecureStringW_putMaintainHash(HCkSecureStringW cHandle, const wchar_t *newVal);
const wchar_t *CkSecureStringW_maintainHash(HCkSecureStringW cHandle);

Introduced in version 9.5.0.71

If set to the name of a hash algorithm, then a hash of the current string value is maintained. This allows for the hash to be verified via the VerifyHash method. Possible hash algorithm names are "sha1", "sha256", "sha384", "sha512", "md5", "md2", "ripemd160", "ripemd128","ripemd256", and "ripemd320".

ReadOnly

BOOL CkSecureStringW_getReadOnly(HCkSecureStringW cHandle);
void CkSecureStringW_putReadOnly(HCkSecureStringW cHandle, BOOL newVal);

Introduced in version 9.5.0.71

Can be set to TRUE to make this secure string read-only (cannot be modified).

VerboseLogging

BOOL CkSecureStringW_getVerboseLogging(HCkSecureStringW cHandle);
void CkSecureStringW_putVerboseLogging(HCkSecureStringW cHandle, BOOL newVal);

If set to TRUE, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is FALSE. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

Version

void CkSecureStringW_getVersion(HCkSecureStringW cHandle, HCkString retval);
const wchar_t *CkSecureStringW_version(HCkSecureStringW cHandle);

Version of the component/library, such as "10.1.0"

More Information and Examples

How to get the Chilkat version at runtime.

Methods

Access

BOOL CkSecureStringW_Access(HCkSecureStringW cHandle, const wchar_t *outStr);
const wchar_t *CkSecureStringW_access(HCkSecureStringW cHandle);

Introduced in version 9.5.0.71

Returns the clear-text string value.

Returns TRUE for success, FALSE for failure.

Append

BOOL CkSecureStringW_Append(HCkSecureStringW cHandle, const wchar_t *str);

Introduced in version 9.5.0.71

Appends a clear-text string to this secure string. The in-memory data will be decrypted, the string will be appended, and then it will be re-encrypted. Can return FALSE if the string has been marked as read-only via the ReadOnly property.

Returns TRUE for success, FALSE for failure.

AppendSb

BOOL CkSecureStringW_AppendSb(HCkSecureStringW cHandle, HCkStringBuilderW sb);

Introduced in version 9.5.0.71

Appends a clear-text string contained in a StringBuilder to this secure string. The in-memory data will be decrypted, the string will be appended, and then it will be re-encrypted. Can return FALSE if the string has been marked as read-only via the ReadOnly property.

Returns TRUE for success, FALSE for failure.

AppendSecure

BOOL CkSecureStringW_AppendSecure(HCkSecureStringW cHandle, HCkSecureStringW secStr);

Introduced in version 9.5.0.71

Appends the contents of a secure string to this secure string. The in-memory data will be decrypted, the secure string will be appended, and then it will be re-encrypted. Can return FALSE if this string has been marked as read-only via the ReadOnly property.

HashVal

BOOL CkSecureStringW_HashVal(HCkSecureStringW cHandle, const wchar_t *encoding, const wchar_t *outStr);
const wchar_t *CkSecureStringW_hashVal(HCkSecureStringW cHandle, const wchar_t *encoding);

Introduced in version 9.5.0.71

Returns the hash value for the current value of this secure string. The encoding specifies the encoding to be used. It can be any of the binary encoding algorithms, such as "base64", "hex", and many more listed at Chilkat Binary Encodings

Returns TRUE for success, FALSE for failure.

LoadFile

BOOL CkSecureStringW_LoadFile(HCkSecureStringW cHandle, const wchar_t *path, const wchar_t *charset);

Introduced in version 9.5.0.71

Loads the contents of a file into this secure string. The current contents of this object are replaced with the new text from the file.

Returns TRUE for success, FALSE for failure.

SecStrEquals

BOOL CkSecureStringW_SecStrEquals(HCkSecureStringW cHandle, HCkSecureStringW secStr);

Introduced in version 9.5.0.71

Returns TRUE if the secStr equals the contents of this secure string.

Returns TRUE for success, FALSE for failure.

VerifyHash

BOOL CkSecureStringW_VerifyHash(HCkSecureStringW cHandle, const wchar_t *hashVal, const wchar_t *encoding);

Introduced in version 9.5.0.71

Verifies the hashVal against the hash value stored for the current value of this secure string. The MaintainHash property must've previously been set for this secure string to maintain an internal hash. The encoding specifies the encoding of the hashVal. It can be any of the binary encoding algorithms, such as "base64", "hex", and many more listed at Chilkat Binary Encodings

Returns TRUE for success, FALSE for failure.