This will generate two files, “keypair” and “keypair.pub”. “keypair” being the private key that you need to keep secure, and “keypair.pub” being the public key, that can be put on servers that you want to be able to log into with the private key.
![]() ![]()
You will have to generate a private and a public encryption key in order to securely send the order information to FastSpring.
There are two ways on how to generate these keys. The easy way or the long way. The easy way is only possible, if your server is supporting openssl functionalities needed for encryption key generation. These openssl functionalities will be detected by the plugin and so, depending on your server, you will either see the “Generate private and public key” button in the plugin settings page or you wont. If you see the button, then you will be able to use the easy way, if you don’t then please look at the instructions for the long way.
Easy way
That’s it! ?
Long way
The private and public keys will have to be generated on your computer, so let’s look at how to generate them.
Generate the private/public keys
The generation of these private/public keys differ, depending on which computer operating system you are using. Please follow the instructions for the OS your computer is using.
macOS and Linux
On macOS and on Linux, you should open the terminal program and execute the commands displayed below:
Create a 2048-bit RSA private key. Don’t share this key with anyone, use it only in the EDD FastSpring plugin settings. This key will be used to encrypt the orders. Use this command to generate the privatekey.pem file which will contain your private key. The file will be created in the position, that the terminal is currently located in (usually your home directory).
openssl genrsa -out privatekey.pem 2048
Create a 2048-bit RSA public key. Only share this key with FastSpring. FastSpring will use your public key PEM file publiccert.pem to decrypt the orders. The file will be created in the position, that the terminal is currently located in (usually your home directory). After you run this command a few short questions will be presented to you, which you can skip, by hitting “enter” key for each of them.
openssl req -new -key privatekey.pem -x509 -days 3650 -out publiccert.pem
Now that you have generated these keys, you have to configure the EDD FastSpring plugin and the FastSpring Dashboard, so look at these instructions in the sections below.
Windows
For generation of these private/public keys your computer needs OpenSSL. Windows does not have that installed by default, so we will have to do that ourselves.
Symmetric Key
Public Key Definition
So, the OpenSSL is now installed on your Windows computer and we can generate the private and public keys.
Click on your Windows start button and search for “Command Prompt” (cmd), right click on the “Command Prompt” and choose to “Run as administrator”. Click on “yes”, when the window for the administration conformation pops up.
Copy and paste this command into the cmd and hit enter (this will position the cmd location to your desktop, where we will generate the private/public keys):
cd %userprofile%Desktop
Depending on which version of Windows you have and therefore which version of OpenSSL you installed, you will have to use a specific path to the OpenSSL executable.
By default the paths are:
I’m using the win64 version, so I’ll use that path in the example, if you are using the win32, then just change the “64” in the path to “32”.
Create a 2048-bit RSA private key. Don’t share this key with anyone, use it only in the EDD FastSpring plugin settings. This key will be used to encrypt the orders. Use this command to generate the privatekey.pem file which will contain your private key.
C:OpenSSL-Win64binopenssl.exe genrsa -out privatekey.pem 2048
Create a 2048-bit RSA public key. Only share this key with FastSpring. FastSpring will use your public key PEM file publiccert.pem to decrypt the orders. After you run this command a few short questions will be presented to you, which you can skip, by hitting “enter” key for each of them.
C:OpenSSL-Win64binopenssl.exe req -new -key privatekey.pem -x509 -days 3650 -out publiccert.pem
Now that you have generated these keys, you have to configure the EDD FastSpring plugin and the FastSpring Dashboard, so look at these instructions in the sections below.
EDD FastSpring settings
Open the privatekey.pem file you generated earlier with a text editor (right-click to the file and choose to open with any text editor like Sublime Text or native text editor of your OS). Copy the content of this file.
Go to your WordPress admin dashboard and navigate to the EDD FastSpring plugin settings (Downloads » Settings » Payment Gateways » FastSpring).
Paste the private key content into the Private encryption key setting. Save the settings.
FastSpring dashboard configuration
Login to your FastSpring dashboard and navigate to Integrations » Store Builder Library. Upload the publiccert.pem file to the Public Certificate option.
If you have any issues with generating these keys or questions, you can always contact our support and we will help you out ?
SSH allows for both password based authentication, as well as public key authentication. Public key authentication is generally regarded as being more secure, as it isn’t as prone to brute force login attempts (if you disable password based authentication). The private key can also have a passphrase associated with it, which makes public key authentication even more secure if needed.
Sometimes cloud servers will let you put a public key in as a authorized authentication key when the cloud server is created, preventing the need for password based authentication to be enabled by default. Generate a new SSH public and private key pair:
“Identifying comment” can be any string that will assist in determining which key this is. “username@hostname” of the machine where you are connecting from would be a good example.
eg:
This will generate two files, “keypair” and “keypair.pub”. “keypair” being the private key that you need to keep secure, and “keypair.pub” being the public key, that can be put on servers that you want to be able to log into with the private key.
Change the filename to suit your needs. This example uses “keypair” for the examples. The contents of the public key file “keypair.pub” can be inserted into the ~/.ssh/authorized_keys file on the machine that you want to be able to connect into remotely. This must be done for the specific user. Insert public key into authorized keys View the contents of the public key file:
eg:
Take note of the output, and copy it into the clipboard if possible, or use some other method to get this file/data onto the remote machine, as it will be used in the next step.
On the remote server you want to be able to log into:
If you have chosen to copy the public key file to the remote host instead, you can issue the following command instead:
Logging into remote ssh server using the private key file
To connect to the remote host using SSH you can use the following command:
This will use the private key called “keypair” created earlier, and assuming the remote server has the public key added to the “user” users authorized_keys file, you should be able to log into the remote system.
Setting a static IP address on Ubuntu 18.04 and higher using netplanMarch 19, 2020Installing NGINX, PHP, and MySQL on Ubuntu 10.04 LTS using php-cgiApril 5, 2012Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |