vlock

Examples

• C: see api_examples/c
• C#: see api_examples/csharp

Full API outline

The function names are slightly obfuscated as with full names (SetKeyHookConfig instead of SetKHookConfig), Windows Defender was flagging vlock as RAT (lol)

struct KHConfig {
 // Whether Clearing the input counts as a failed attempt
 bool ClearCountsAsFail;
 // Whether pressing enter is required to confirm a password attempt
 bool RequireEnter;
 // The length of the password
 int PwLength;
 // The password
 const wchar_t* Pw;
 // A callback that will be invoked on a failed unlock attempt. The "pw" argument is the attempted password.
 // This is potentially an empty string if ClearCountsAsFail is true
 void (*OnFail)(const wchar_t* pw);
 // A callback that will be invoked on a successful unlock attempt
 void (*OnSuccess)();
 // A callback that will be invoked per character typed
 // inputBuf is a buffer that contains one or more characters corresponding to this keypress.
 // inputBufLength is a number indicating how many elements inputBuf contains. Reading anything past this element count leads to undefined behaviour
 // fullInput is the full input
 void (*OnInput)(wchar_t inputBuf[], int inputBufLength,
 const wchar_t* fullInput);
};
// Install the Keyboard Hook: Start listening to input
bool InstallKHook();
// Uninstall the Keyboard Hook
bool UninstallKHook();
// Whether the Keyboard hook is currently installed
bool IsKHookInstalled();
// Sets the current KHConfig. You MUST call this at least once before calling InstallKHook
void SetKHookConfig(KHConfig config);
// Disable the TaskManager
bool DisableTskMan();
// Enable the TaskManager
bool RestoreTskMan();

You should treat the arguments passed to your callback as immutable. Mutating them is not allowed.

Using any of the arguments passed to your callbacks after your callback has returned is not allowed. If you want to keep them around, make a copy