Index of /apache/tomcat/tomcat-3/rpms
Apache Tomcat 3.3.1a - RPM Distributions
Apache Tomcat 3.3.1a - RPM Distributions
This directory contains the RPM distributions for Tomcat 3.3.1a,
which is a patched release of Tomcat 3.3.1 Final.
Tomcat 3.3.1a is a security release. For details check
here.
Tomcat 3.3.1a RPM is more FHS compliant and run as user tomcat3 by default
- many RPM enhancements from suggestion from Keith Irwin
, Nicolas Mailhot and Jun Inamori.
A big thanks to all of them
- the RPM has been renamed tomcat3 to allow coexistence
with tomcat 4.x RPM
- the RPM is more FHS compliant :
bindir is in /etc/tomcat3/conf
confdir is in /etc/tomcat3/conf
logdir in /var/log/tomcat3
workdir in /var/spool/tomcat3
webapps and libs and modules in /var/tomcat3
ajp12.pid in /var/spool/tomcat3
ajp13.pid in /var/spool/tomcat3
- tomcat is run as user tomcat3 and the /usr/bin/tomcat3 command enforces
it .
startup.sh, shutdown.sh have been replaced by command tomcat3 and
jspc.sh by jspc3
- You could use /usr/bin/dtomcat3 instead to run tomcat under your
own account but be carefull in that case with new files access.
- Tomcat 3.3 NOW REQUIRES other RPM packages to be
installed :
- servletapi3, xerces-j2
You could find such packages at JPackage project
o Tomcat 3.3 has been compiled with JSSE support but
these jars are not provided due to crypto regulation
If you have JSSE jars on your system, jcert.jar, jsse.jar,
jnet.jar, just define JSSE_HOME in /etc/tomcat3/conf/tomcat3.conf
those JAR files will be added to thei system class path.
o Alternativaly Tomcat 3.3 has been also compiled with PureTLS
support so you could use it instead to have a 100% OSS SSL
solution. Tomcat will detect if JSSE and PureTLS are available
choose the one available, or PureTLS if both are available.
You should install puretls, cryptix32 and cryptix-asn RPM
on your system and link their jars to /var/tomcat3/lib/container
ie:
ln -s /usr/share/java/puretls.jar /var/tomcat3/lib/container
ln -s /usr/share/java/cryptix-3.2.0.jar /var/tomcat3/lib/container
ln -s /usr/share/java/cryptix-asn1.jar /var/tomcat3/lib/container
RPM will detect these jars and will install them automatically
for you at install time. Here is an example of a PEM encoded
file from Apache HTTPD
server. For more information on how to generate PEM file
go to http://www.openssl.org
or http://www.modssl.org.
Documentation is also available in tomcat :
http://localhost:8080/doc/tomcat-ssl-howto.html
With PureTLS you should have a PEM encoded file, which will
contain CERTIFICATE and KEY :
-----BEGIN CERTIFICATE-----
MIIEDDCCA3WgAwIBAgIBADANBgkqhkiG9w0BAQQFADCBuzELMAkGA1UEBhMCLS0x
EjAQBgNVBAgTCVNvbWVTdGF0ZTERMA8GA1UEBxMIU29tZUNpdHkxGTAXBgNVBAoT
EFNvbWVPcmdhbml6YXRpb24xHzAdBgNVBAsTFlNvbWVPcmdhbml6YXRpb25hbFVu
aXQxHjAcBgNVBAMTFWxvY2FsaG9zdC5sb2NhbGRvbWFpbjEpMCcGCSqGSIb3DQEJ
ARYacm9vdEBsb2NhbGhvc3QubG9jYWxkb21haW4wHhcNMDExMTEyMDgwMDM4WhcN
MDIxMTEyMDgwMDM4WjCBuzELMAkGA1UEBhMCLS0xEjAQBgNVBAgTCVNvbWVTdGF0
ZTERMA8GA1UEBxMIU29tZUNpdHkxGTAXBgNVBAoTEFNvbWVPcmdhbml6YXRpb24x
HzAdBgNVBAsTFlNvbWVPcmdhbml6YXRpb25hbFVuaXQxHjAcBgNVBAMTFWxvY2Fs
aG9zdC5sb2NhbGRvbWFpbjEpMCcGCSqGSIb3DQEJARYacm9vdEBsb2NhbGhvc3Qu
bG9jYWxkb21haW4wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMHDA8F4P5IF
hpMrGon9XGqn6MLOeIlOZyNlSqkF043a/1QnmB3FAEJniG3V4RfWxD3b4fbrjOLa
Ls88tZyIve1kUufqvvQ6xss/pAK8a3GIOoegcmSGenTEEGf4G/wti3bZUaJI3UWm
HK+eCajZPYkZ4kizo+qc+Bb/Dij1vUVXAgMBAAGjggEcMIIBGDAdBgNVHQ4EFgQU
V1sqsMx/BahBsrLmuBiQf+Kf0UEwgegGA1UdIwSB4DCB3YAUV1sqsMx/BahBsrLm
uBiQf+Kf0UGhgcGkgb4wgbsxCzAJBgNVBAYTAi0tMRIwEAYDVQQIEwlTb21lU3Rh
dGUxETAPBgNVBAcTCFNvbWVDaXR5MRkwFwYDVQQKExBTb21lT3JnYW5pemF0aW9u
MR8wHQYDVQQLExZTb21lT3JnYW5pemF0aW9uYWxVbml0MR4wHAYDVQQDExVsb2Nh
bGhvc3QubG9jYWxkb21haW4xKTAnBgkqhkiG9w0BCQEWGnJvb3RAbG9jYWxob3N0
LmxvY2FsZG9tYWluggEAMAwGA1UdEwQFMAMBAf8wDQYJKoZIhvcNAQEEBQADgYEA
uVkyDAtjdpzV03TqBCFHCWWydeP+SqL56W7wtVaqAk0UilvQgZs23Z3TmbbCMKB+
LRCSbr83dRaM7wgxlSCxz/XhSS+QR/J635SFE2Vbvr1xm4wmcX95RuZCeXKFYNgZ
NcaPeykpnW/Ba+I4inVBBClAZlrrCshAvWFzrU9nEbc=
-----END CERTIFICATE----
-----BEGIN RSA PRIVATE KEY-----
MIICXQIBAAKBgQDBwwPBeD+SBYaTKxqJ/Vxqp+jCzniJTmcjZUqpBdON2v9UJ5gd
xQBCZ4ht1eEX1sQ92+H264zi2i7PPLWciL3tZFLn6r70OsbLP6QCvGtxiDqHoHJk
hnp0xBBn+Bv8LYt22VGiSN1Fphyvngmo2T2JGeJIs6PqnPgW/w4o9b1FVwIDAQAB
AoGAFd9TvzU5x9wD0v0co9ML6aZGqibwiF9nWSGICgh0VyEPjYpiq4mfe9+AERYB
sNU3ldwKZ/szDjCe9BngTmlJNx6/exnbd9EMAk04VFXDVvegLYXImNtpwW7n+Zpc
aNgShka6Sz0nUklyMDZh0Gz7OuAnmY2ti3GghN4QIQO9paECQQDi6BmdO5mPrc+8
sdW7IAYWm/fk9n0pzzVh8s8TwNRIeoXtun9DN/OhcifaUoivSkkDXwYJTDxv3nb8
zY8jK1LfAkEA2pr604yR8phqr6Ho+HJ/NDE+EYFZWNdfeQs9UX8aLMmTYIgwZfa6
bSdS8Gw2+ZX2io7UBueYDu0+49XqCfuUiQJBAKyOU4RWIca5KITYPLCsftTM0a0m
ojKcaH1PeJkOCKIBwz3xmPxWXYmGVbZbE6Uyeen9ZorFliSA6r3/2P2m4cMCQDUA
sqQsRw686dEfvq7OhA0Ri20PIayqu5lLolhqKtyFG1iibKmsQtNIX5GvizzEoXxC
2SG7cWDdIQx4x0AYYZECQQDhhdRYi0gJdJEAMmdDkt/1qZhd1+4LzJV5ph4IxHCF
4+3QaHpsxaaN3YYzNP/4yg7aI5zRvoSGJKiK5BsSf+D9
-----END RSA PRIVATE KEY-----
here is an example of entry in server.xml, notice that you should
also define randomfile which should point to a writeable file.
<Http10Connector port="8443"
secure="true"
keystore="/etc/tomcat3/conf/server.crt"
keypass="tomcat"
randomfile="/var/spool/tomcat3/random.id" />
o Tomcat 3.3 is installed under /var/tomcat3
o A configuration file /etc/tomcat3/conf/tomcat3.conf is loaded
before Tomcat or Jasper start and could be used to tune JVM
params
- TOMCAT_HOME is now /etc/tomcat3 and TOMCAT_INSTALL is /var/tomcat3.
- a config file is available for init.d script tuning, tomcat3.conf
, in /etc/tomcat3/conf
- Warning, the webapps directory now lives in /var/tomcat3 instead of /etc/tomcat.
So you should take care of setting docBase to /var/tomcat3/webapps/yourapp
since the default goes to /etc/tomcat3/webapps/yourapp instead (cf etc/apps-examples.xml).
These packages are PGP signed by commiter for security.
Our keys are available here
You can verify each package with the following command:
rpm --checksig
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
rpm --checksig --nopgp
You may find online documentation for Tomcat 3.3.1
here.