ServerBuddies Support Blog

How to Upgrade the trial License Key

To upgrade the trial license key through the Panel interface:

Log in to Panel as administrator.
On Home page, click Tools & Utilities > License Management > Order New Key.

The online store will open in a separate browser window. In this window, select the items and features you want to include into your license and click Submit. In the next steps, indicate the currency, number of license keys, provide contact details, billing address, and payment method, and submit the form. The new key will be sent to the specified e-mail address.

Save the new key to the hard drive on your local machine.
Open again the License Management screen in Parallels Plesk Panel (Home > Tools & Utilities > License Management) and click Upload Key.

Reference: http://parallels.com/

How to install a license key through the command line interface.

To install a Panel license key using the Panel CLI, you should first upload it to the machine with the Panel, and then install it with the license utility.

For example:

1. On Linux/Unix:

Reference: http://parallels.com/

How to install Red Hat GPG key for RPM verification.

If the Red Hat GPG key is not installed, install it from a secure, static location, such as a Red Hat installation CD-ROM or DVD.

All Red Hat Enterprise Linux packages are signed with the Red Hat GPG key. GPG stands for GNU Privacy Guard, or GnuPG, a free software package used for ensuring the authenticity of distributed files. For example, a private key (secret key) locks the package while the public key unlocks and verifies the package. If the public key distributed by Red Hat Enterprise Linux does not match the private key during RPM verification, the package may have been altered and therefore cannot be trusted.

use the following command to import it into the keyring (a database of trusted keys on the system):

To display a list of all keys installed for RPM verification, execute the following command:

It is extremely important to verify the signature of the RPM files before installing them to ensure that they have not been altered from the original source of the packages. To verify all the downloaded packages at once, issue the following command:

SSH Public key authentication

SSH Public key authentication works as follows:

The scheme is based on public-key cryptography, using cryptosystems where encryption and decryption are done using separate keys, and it is unfeasible to derive the decryption key from the encryption key. The idea is that each user creates a public/private key pair for authentication purposes.

The server knows the public key, and only the user knows the private key. ssh implements public key authentication protocol automatically, using either the RSA or DSA algorithms. Protocol 1 is restricted to using only RSA keys, but protocol 2 may use either. The HISTORY section of ssl(8) contains a brief discussion of the two algorithms.

The file ~/.ssh/authorized_keys lists the public keys that are permitted for logging in. When the user logs in, the ssh program tells the server which key pair it would like to use for authentication. The client proves that it has access to the private key and the server checks that the corresponding public key is authorized to accept the account.

The user creates his/her key pair by running ssh-keygen(1). This stores the private key in ~/.ssh/identity (protocol 1), ~/.ssh/id_dsa (protocol 2 DSA), or ~/.ssh/id_rsa (protocol 2 RSA) and stores the public key in ~/.ssh/identity.pub (protocol 1), ~/.ssh/id_dsa.pub (protocol 2 DSA), or ~/.ssh/id_rsa.pub (protocol 2 RSA) in the users home directory.

The user should then copy the public key to ~/.ssh/authorized_keys in his/her home directory on the remote machine. The authorized_keys file corresponds to the conventional ~/.rhosts file, and has one key per line, though the lines can be very long. After this, the user can log in without giving the password.

The most convenient way to use public key authentication may be with an authentication agent. See ssh-agent(1) for more information.

If you have an RSA PRIVATE KEY then you would have a password encrypted key.

This will not work with DirectAdmin since it would require someone to type in a password each time apache restarts.

You do not have to start over, you can convert this password protected key into a normal key by typing:

where you’d replace the bold values with appropriate values.

This will ask you for the password you specified when you created the original key.
It will then create a non-password-protected key that you can use for DA.

Source: http://directadmin.com/