cmdkey | Enhanced command line editing for CMD.EXE | Command Line Interface library

The cmdkey tool just manages the credentials in the Credential Manager. You can see the UI through control /name Microsoft.CredentialManager if you're so inclined.

There are a handful of types. LegacyGeneric is just a catch-all for any kind of credential that isn't Windows-Integrated-Auth-specific, meaning Windows can't do anything special with it. This is in contrast to CRED_TYPE_DOMAIN_* credentials where Windows knows they're special and can do special things like use them for Kerberos, or protect them with Credential Guard. All of the types are documented. For completeness, there's actually also a third type that is sort of the logical successor to credman, which is the PasswordVault APIs. It uses the same functions under the cover, but is separated from win32 APIs.

Target indicates what the credential is intended to be used for or by. In the generic case it's an arbitrary value. In the domain case it's a service identifier that matches a hostname or realm to say that 'when connecting to this service you can use this cred'.

As such it's impossible to say what each target represents. Most of them are fairly obvious in name.

CRED_TYPE_GENERIC = 1 (0x1)

The credential is a generic credential. The credential will not be used by any particular authentication package. The credential will be stored securely but has no other significant characteristics.

CRED_TYPE_DOMAIN_PASSWORD = 2 (0x2)

The credential is a password credential and is specific to Microsoft's authentication packages. The NTLM, Kerberos, and Negotiate authentication packages will automatically use this credential when connecting to the named target.

CRED_TYPE_DOMAIN_CERTIFICATE = 3 (0x3)

The credential is a certificate credential and is specific to Microsoft's authentication packages. The Kerberos, Negotiate, and Schannel authentication packages automatically use this credential when connecting to the named target.

CRED_TYPE_DOMAIN_VISIBLE_PASSWORD = 4 (0x4)

This value is no longer supported. Windows Server 2003 and Windows XP: The credential is a password credential and is specific to authentication packages from Microsoft. The Passport authentication package will automatically use this credential when connecting to the named target.

Additional values will be defined in the future. Applications should be written to allow for credential types they do not understand.

CRED_TYPE_GENERIC_CERTIFICATE = 5 (0x5)

The credential is a certificate credential that is a generic authentication package. Windows Server 2008, Windows Vista, Windows Server 2003 and Windows XP: This value is not supported.

CRED_TYPE_DOMAIN_EXTENDED = 6 (0x6)

The credential is supported by extended Negotiate packages. Windows Server 2008, Windows Vista, Windows Server 2003 and Windows XP: This value is not supported.

Use the CredentialManager powershell module. It saves the password in the same place as cmdkey, but can take [PSCredential] objects directly without needing to convert to text.

The server calculates the checksum only of the half of the received header and data. Sent checksum should lead to calculated checksum become 0xffff. I assume you are sending to the server CommandKeyS structure and it's size is constant. I assume ChkSum on the server is of type _int16 and initialized to 0. I dont know C#, so replaced parts with C++ code hoping it's not too different. You can remove get function of ChKSum field and before sending the data call this function to initialize the checksum:

This behavior is cause by your use of Out-String.

Get-Content outputs multiple strings, one per line in the file - but Out-String stitches them back together into a single multi-line string:

Instead of using " " who take $x for a variable. Use ' ' and everything in it will be a character.

This is a line selector I've made previously that builds an Array containing the value of each Line and allows scrolling and selection of the value via the choice command. The :Load and :Extract labels are where the functions most relevant to your needs reside.

EDIT: The stripped down components modified for just the output you seek - Using the safer form of input (Choice Command). Note that if the number of options exceeds 9, Set /P will need to be used - though input should be validated.

The computer does not have the assembly. It seems you just need to install the runtime library

http://www.microsoft.com/en-us/download/details.aspx?id=34595

Install this one Windows6.1-KB2506143-***.msu for Windows 7

You can add Global Monitor For Events matching .flagsChanged to your view controller so you can check its modifierFlags intersection with deviceIndependentFlagsMask and check the resulting keys.

Declaration

PowerShellInstance.Invoke(); is synchronous, so your script will already wait for Powershell to complete. You don't need an if statement.

If you really want asynchronous execution you can invoke the script another way using BeginInvoke(). See https://docs.microsoft.com/en-gb/archive/blogs/kebab/executing-powershell-scripts-from-c - it explains both the synchronous and asynchronous approaches.