The simplest way to generate a key pair is to run ssh-keygen without arguments. In this case, it will prompt for the file in which to store keys. Here's an example: klar (11:39) ssh-keygen Generating public/private rsa key pair. Jan 22, 2015 Cannot import the following key file: magellanicKey.pfx. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: VSKEY883A9453A40E283F. 32 rows The key container resides in the strong name CSP.-k keysize outfile: Generates a new.

-->

Note

As the name suggests, the private key is meant for you and only you. Never copy/save this on a server! The public key, however, is meant to be saved on the servers you intend to access, in the “/.ssh/authorizedkeys” file (or rather, pasted/added to this file).

Although .NET Core supports strong-named assemblies, and all assemblies in the .NET Core library are signed, the majority of third-party assemblies do not need strong names. For more information, see Strong Name Signing on GitHub.

There are a number of ways to sign an assembly with a strong name:

By using the Signing tab in a project's Properties dialog box in Visual Studio. This is the easiest and most convenient way to sign an assembly with a strong name.
By using the Assembly Linker (Al.exe) to link a .NET Framework code module (a .netmodule file) with a key file.
By using assembly attributes to insert the strong name information into your code. You can use either the AssemblyKeyFileAttribute or the AssemblyKeyNameAttribute attribute, depending on where the key file to be used is located.
By using compiler options.

You must have a cryptographic key pair to sign an assembly with a strong name. For more information about creating a key pair, see How to: Create a public-private key pair.

Create and sign an assembly with a strong name by using Visual Studio

Generate Strong Name Key File Online

In Solution Explorer, open the shortcut menu for the project, and then choose Properties.
Choose the Signing tab.
Select the Sign the assembly box.
In the Choose a strong name key file box, choose Browse, and then navigate to the key file. To create a new key file, choose New and enter its name in the Create Strong Name Key dialog box.

Generate Strong Name Key File Download

Note

In order to delay sign an assembly, choose a public key file.

Create and sign an assembly with a strong name by using the Assembly Linker

At the Developer Command Prompt for Visual Studio, enter the following command:

al/out:<assemblyName> <moduleName>/keyfile:<keyfileName>

Where:

assemblyName is the name of the strongly signed assembly (a .dll or .exe file) that Assembly Linker will emit.
moduleName is the name of a .NET Framework code module (a .netmodule file) that includes one or more types. You can create a .netmodule file by compiling your code with the /target:module switch in C# or Visual Basic.
keyfileName is the name of the container or file that contains the key pair. Assembly Linker interprets a relative path in relation to the current directory.

The following example signs the assembly MyAssembly.dll with a strong name by using the key file sgKey.snk.

For more information about this tool, see Assembly Linker.

Sign an assembly with a strong name by using attributes

Add the System.Reflection.AssemblyKeyFileAttribute or AssemblyKeyNameAttribute attribute to your source code file, and specify the name of the file or container that contains the key pair to use when signing the assembly with a strong name.
Compile the source code file normally.
Note
The C# and Visual Basic compilers issue compiler warnings (CS1699 and BC41008, respectively) when they encounter the AssemblyKeyFileAttribute or AssemblyKeyNameAttribute attribute in source code. You can ignore the warnings.

The following example uses the AssemblyKeyFileAttribute attribute with a key file called keyfile.snk, which is located in the directory where the assembly is compiled.

You can also delay sign an assembly when compiling your source file. For more information, see Delay-sign an assembly.

Sign an assembly with a strong name by using the compiler

Compile your source code file or files with the /keyfile or /delaysign compiler option in C# and Visual Basic, or the /KEYFILE or /DELAYSIGN linker option in C++. After the option name, add a colon and the name of the key file. When using command-line compilers, you can copy the key file to the directory that contains your source code files.

For information on delay signing, see Delay-sign an assembly.