DSA public and private keys can use OpenSSL

Open SecureCRT and select Tools to create a public key. Click Next.

Select DSA mode for key mode.

Enter the encrypted password.

The byte length of the encryption, here it is encrypted with a length of 1024 bytes.

Move the mouse for the test. Move the mouse under the progress bar.

Wait for the installation to complete and place the public key to the server.

Step to read. Click Attribute Settings to set the password for the username and public key.

OK! This is the basic working principle of the RSA public key cryptography.

Yes, private key cryptography and public key decryption are how digital signatures work.

Use the Visual Studio 2005 Command Prompt under VS2005 to enter console mode (which automatically sets various environment variables).

Unzip the OpenSSL package and go to the OpenSSL directory.

perl configure vc-win32

Try to run the command in this directory, otherwise the configure file cannot be found, or specify the complete configure file path.

ms\do_ms

Run the ms do ms command in the decompression directory.

After the compilation of nmake -f is executed in the openSSL decompression directory, after the compilation is completed. The output file is in the out32dll, including the application executable, lib file, and dll file.

Note: When running the fifth step, the CL compiler complains. The Read of the Crypto des ENC file is the Posix Name for This Item is Deprecated, and it is recommended to use Read.

Hehe, I don't want to change all the read functions in OpenSSL to read. Look at the CL error ** error C2220, so go to MSDN to look:

warning treated as error - no object file generated

wx tells the compiler to treat all warnings as errors. since an error occurred, no object or executable file was generated.

It's because the wx option is set to treat all warnings as errors, so...

So open the file in the ms directory in the openssl directory, remove the wx option of cflag, and save it.

The signature in the certificate corresponds to the private key, and the public key and the private key in the certificate also match, and the certificate can be verified by the public key in the certificate.

Use OpenSSL, which comes with Linux. The common command is as follows: --Generate RSA private key (in traditional format) openssl genrsa -out RSA private 1024 -- Convert the private key in traditional format to openssl in PKCS 8 format PKCS8 -topk8 -inform pem -in rsa private -outform pem -nocrypt -- generate rsa public key openssl rsa -in rsa private -pubout -out rsa public

The common command is as follows: --Generate RSA private key (in traditional format) openssl genrsa -out RSA private 1024 -- Convert the private key in traditional format to openssl in PKCS 8 format PKCS8 -topk8 -inform pem -in rsa private -outform pem -nocrypt -- generate rsa public key openssl rsa -in rsa private -pubout -out rsa public