SRSplus

Since the test server is updated from the live server occasionally, your STORED VALUE may reset to the current live value from time to time. Once the STORED VALUE reaches zero, the UNPAID CHARGES will increase until it reaches the limit specified in BUYING POWER. BUYING POWER will be sufficiently large to accommodate about 200,000 test registrations before your test BUYING POWER needs to be reset.

I'm having a lot of trouble trying to create a contact with the API. Why does it keep failing?
The CreateContact command has a lot of required fields. Make sure you are specifying all of them correctly. For example, the COUNTRY value is expected to be the two-letter upper case country code (i.e., ISO3166 country codes). Also, all fields must contain only ASCII characters. Refer to section 4.3 of the Developer's Guide for detailed information.

Can I specify a .tv nameserver for my domains?
Yes. First, you need to register the nameserver with the SRS command RegisterNameServer. This will ensure that the specified nameserver is correctly entered in the .tv zone file.

Step 1: Download OpenSSL Source
Go to http://www.openssl.org.
Click on "Source" in the left side menu.
Click on the link "openssl-x.y.z.tar.gz", where x.y.z is the latest distribution, usually identified with the words "[LATEST]" next to it.
Save the archive to a directory of your choosing.

Step 2: Unzip and Untar the Archive
Use the command "gunzip openssl-x.y.z.tar.gz", to uncompress the file.
Next, use the command "tar -xvf openssl-x.y.z.tar" to unpack the archived files.

Step 3: View the README File
It is always a good idea to view any README files. Also, take a look at the INSTALL file. These files typically include the same information presented here and should be considered the authoritative source for configuration and installation instructions.

Step 4: Configure and Compile
Run the configuration script with the command "./config"
Compile the source with the command "make"
Test the library with the command "make test"
Ensure that you are logged in as root or have superuser status via the "su" command. The next command will attempt to copy files to system directories.
Install with the command "make install"

The OpenSSL library is now installed. If you encounter problems with the above, refer to the INSTALL file and/or FAQ file, or visit the Documentation section of the openssl.org website.

Step 1: Download GnuPG Source
Go to http://www.gnupg.org.
Click on "Download" in the left side menu.
Click on the link "·GnuPG version 1.0.6 (1896k)" or use ftp to download the latest distribution. Save it to a directory one level up from where you want to store the GnuPG source since unpacking the archive will create a gnupg-1.0.6 directory.

Step 2: Unzip and Untar the Archive
Use the command "gunzip gnupg-1.0.6.tar.gz", to uncompress the file.
Next, use the command "tar -xvf gnupg-1.0.6.tar" to unpack the archived files.

Step 3: View the README File
It is always a good idea to view any README file. Also, take a look at the Install file. These files typically include the same information presented here and should be considered the authoritative source for configuration and installation instructions.

Step 4: Configure and Compile
Run the configuration script with the command "./configure"
Compile the source with the command "make"
Ensure that you are logged in as root or have superuser status via the "su" command. The next command will attempt to copy files to system directories.
Install the files with the command "make install"
You will now have an executable named gpg.exe in /usr/local/bin

Step 5: Set a GNUPGHOME Directory
Before running gpg.exe for the first time, you may want to set an environment variable for GNUPGHOME, which is the location gpg.exe will use for its databases. By default this directory is /home/username/.gnupg. If you prefer to use another location, perform the following:

Create an environment variable named GNUPGHOME and specify the desired location with the command "export GNUPGHOME=desired path"

Step 6: Run gpg.exe to Initialize Databases
The first time gpg.exe is executed, it creates and initializes its databases in the directory specified in GNUPGHOME (or in the default directory if GNUPGHOME does not exist).

Run the command "gpg --help"

Step 1: Download GnuPG Executable for Windows
Go to http://www.gnupg.org.
Click on "Download" in the left side menu.
Click on the link "·MS-Windows 95, 98 and NT (689k)" or use ftp to download the latest distribution. Save it to a directory one level up from where you want to store the GnuPG source since unzipping the archive will create a gnupg-w32-1.0.6 directory.

Step 2: Unzip the Archive
Use your favorite "unzip" program (e.g., WinZip) to uncompress the archive.

Step 3: View the README File
It is always a good idea to view any README files. These files typically include the same information presented here and should be considered the authoritative source for configuration and installation instructions.

Step 4: Create C:\gnupg Directory
By default, GnuPG uses the directory C:\gnupg to store its database. Create the directory before running gpg.exe for the first time.

Step 5: Add gpg.exe to PATH
Ensure that all programs can find gpg.exe by adding the directory where you installed gpg.exe to your PATH environment variable.

Step 6: Run gpg.exe to Initialize Databases The first time gpg.exe is executed, it creates and initializes its databases in the C:\gnupg directory.
Run the command "gpg --help"

The installation of GnuPG is now complete and ready for you to create your public/private keypair. See the HOW-TO Manage Keys with GnuPG document for further assistance.

Step 1: Keypair Creation
Run the command "gpg --gen-key"
Follow the on screen instructions, choosing the default choices for all options
Use the e-mail name you used when signing up for your SRSplus Partner account when prompted for the e-mail name of the key
Provide the full name of your organization as the description for the key

Step 2: Export the Public Key
Run the command "gpg --export -a > publickey.txt"
This creates a plain ASCII text file of your public key.
Send the file to registry@srsplus.com
(Once the key is received and processed, you will be sent back your partner ID and allowed access to the test SRS server).
Keep a copy of the file somewhere safe as a backup

Step 3: Export the Private Key
Run the command "gpg --export-secret-key -a > privatekey.txt"
This creates a plain ASCII text file of your private key.
Keep a copy of the file somewhere safe as a backup. Protect this file from theft and altering.

Step 4: Import the SRS Public Keys
A keyblock file named SRS.KEY is provided in the KEYS directory of each API distribution. Importing this keyblock will add two keys to your keyring, one for testregistry@srsplus.com and one for registry@srsplus.com. Accomplish this with the following command:

gpg --import SRS.KEY

You should verify the "fingerprints" of the keys. Run the following command and verify that the output matches:

gpg --list-keys

pub  1024D/83254FDB 2000-07-27 Test registry <testregistry@www.tv>
uid                            SRSPlus test account <testregistry@srsplus.com>
sub  1024g/DCFB3D2E 2000-07-27


pub  1024D/415202CC 2000-08-01 DotTV Registry <registry@www.tv>
uid                            SRS Plus <registry@srsplus.com>
sub  2048g/778C3D8A 2000-08-01

Step 5: Sign the SRS Keys
Once the keys have been imported, you need to locally sign the keys in order for them to be added to your list of "trusted" keys. Locally sign the keys with the following commands:

gpg --lsign-key 83254FDB
gpg --lsign-key 415202CC

Step 6: Ensure the Default Key
All versions of the SRS APIs expect the public key of the default key pair to be the one that was submitted to registry@srsplus.com. You must ensure that only one private key exists in your keyring and that it corresponds to the public key you submitted. If necessary, run the command gpg --delete-secret-key for each extraneous private key.