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.
===> The following configuration options are available for rt44-4.4.6_1:
DEVELOPER=off: Configure for Developers
DOCS=on: Build and/or install documentation
GD=on: Enable GD Graphs and Charts
GPG=on: Enable GnuPG support
GRAPHVIZ=off: Graphviz graph drawing support
SMIME=off: Enable Secure MIME support
====> Options available for the single DB: you have to select exactly one of them
MYSQL=on: MySQL database support
PGSQL=off: PostgreSQL database support
SQLITE=off: SQLite database support
====> Options available for the radio WEB: you can only select none or one of them
AP_MODFASTCGI=on: Deploy with apache and mod_fastcgi
AP_MODPERL=off: Deploy with apache and mod_perl
LIGHTTPD=off: Deploy with lighttpd and mod_fastcgi
SPAWN_FCGI=off: Deploy with spawn_fcgi
===> Use 'make config' to modify these settings
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/rt44/RT_SiteConfig.pm, by referring to
the default config file (/usr/local/etc/rt44/RT_Config.pm).
2. Configure the email and web gateways. Please refer to
'SETTING UP THE MAIL GATEWAY' in /usr/local/share/doc/rt44/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.
For install:
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/rt44/upgrade \
--action upgrade --prompt-for-dba-password
and answer the prompts.
www/rt44: Fix vulnerabilities
The following issues are addressed with these security updates:
- RT is vulnerable to unvalidated email headers in incoming email and the
mail-gateway REST interface.
This vulnerability is assigned CVE-2023-41259.
- RT is vulnerable to information leakage via response messages returned from
requests sent via the mail-gateway REST interface.
This vulnerability is assigned CVE-2023-41260.
- RT 5.0 is vulnerable to information leakage via transaction searches made by
authenticated users in the transaction query builder.
This vulnerability is assigned CVE-2023-45024.
- RT 5.0 can reveal information about data on various RT objects in errors and
other response messages to REST 2 requests.
(cherry picked from commit c2ce69e2f52b932bb6d5d52c174d6d06fe95bef1)
