Uninstall the RPM or DEB

Use the following steps to uninstall the CCA RPM or DEB.

Procedure

  1. Uninstall any RPMs or DEBs that depend on the CCA RPM or DEB packages. If you try to uninstall the CCA RPM or DEB and dependent RPMs or DEBs are still installed, the uninstall RPM or DEB command will fail and list the names of dependent packages. Therefore, you can skip to Step 2 and come back to this step if Step 2 fails for that reason.
  2. Uninstall the CCA RPM or DEB.
    1. Login as root. You must be root to uninstall the RPM or DEB.
    2. You must use the full name. You can find the name by issuing one of the following commands:
      
      rpm -qa | grep csulcca /* for RPM */
      dpkg -l | grep csulcca /* for DEB */
      
    3. Uninstall the RPM or DEB with the following command:
      
      rpm -e <rpm_name>                              /* for RPM */
      dpkg -P <deb_name> or dpkg --purge <deb_name>  /* for DEB */
      
    Note:
    1. Groups are no longer deleted during the uninstall of CCA RPM or DEB. If you created any users with one of the groups created by the package install as their primary (note that the package install does NOT create any users, just groups), you can delete those users/groups yourself after uninstall, or remove such users before the uninstall of the RPM or DEB. This removes any potential security holes.
    2. The configuration file for the TKE catcher /etc/cca/catcher.conf is not deleted. The connection mode specified in this file (TLS_ON = TLS mode or TLS_OFF = TCP mode) is used for a follow-on installation.
    3. Card master keys (and other state information) are untouched by the host-side uninstall of the RPM or DEB.
    4. Key storage files are not deleted by the uninstall. All default and non-default key storage files are left as is. If you reinstall or install an upgraded package and load any new cards with the same master keys, you still can use your old key storage (old cards still have the old keys, see step 7.b of Install and configure the RPM or DEB).