BSD Ports

Vulnerable: version 5.0.8 is affected by 2 known vulnerabilities. See below.

www/rt50 5.0.8 DragonFly

Industrial-grade ticketing system written in Perl

System
DragonFly
Repository
DPorts
Maintainer
[email protected] (as in FreeBSD)
License
GPLv2
Categories
www
Package size
14032.6 KiB, 45253.0 KiB installed

Description

RT is a battle-tested issue tracking system which thousands of organizations use for bug tracking, help desk ticketing, customer service, workflow processes, change management, network operations, youth counselling and even more. Organizations around the world have been running smoothly thanks to RT for over 10 years.

In the other systems

SystemPortVersion
DragonFlywww/rt505.0.8
FreeBSDwww/rt505.0.10
HardenedBSDwww/rt505.0.10
GhostBSDwww/rt505.0.10

Install

Binary package:

pkg install rt50

From DPorts:

cd /usr/dports/www/rt50 && make install clean

Dependencies

Run dependencies 100

Configuration

No options to configure.

Service scripts
none

Message after installing

To initialize RT's database:

$ sudo perl rt-setup-database --action init --dba dba --dba-password X

To clear a previously created RT database:

$ sudo perl rt-setup-database --action drop --dba dba --dba-password X

To complete the installation of this port, please follow these steps:

1. Edit /usr/local/etc/rt50/RT_SiteConfig.pm, by referring to
   the default config file (/usr/local/etc/rt50/RT_Config.pm).
2. Configure the email and web gateways.  Please refer to
   'SETTING UP THE MAIL GATEWAY' in /usr/local/share/doc/rt50/README
3. Restart Apache or whichever web delivery mechanism you selected..
4. Do remember to *CHANGE* the root's password for the web interface.
   The default is "password" (without the quotes.)
5. Configure RT per the instructions at
   http://www.bestpractical.com/rt/docs.html

RT does not work with perl taint mode (-T) you must disable it.
Note, some other ports like devel/bugzilla have you add this to your
httpd.conf.  This isn't actually a flaw of RT, but of a subset of the
CPAN modules that RT uses.

If you're upgrading RT then it is worth reading the UPGRADING document
at this point. Some extension you're using may have been integrated
into core. It's recommended to use new clean directory when you're
upgrading to new release (for example from 4.0.x to 4.2.x).

To upgrade your database schema, preserving ticket history:

1. Backup your RT database.
2. If upgrading to a new major release, create a new database named
   rt4 with appropriate rights for the rt_user and reload your
   database backup into it.
3. Run:

# /usr/local/sbin/rt-setup-database \
     --datadir /usr/local/share/doc/rt50/upgrade \
     --action upgrade --prompt-for-dba-password

and answer the prompts.

Known vulnerabilities 2