SUNScholar/Secure Internet Connections
Back to Internet Security
For the need to use https, check: https://pressfreedomfoundation.org/encryption-works and https://ssd.eff.org
To check if your internet connection is secure, use: https://www.eff.org/https-everywhere
Contents
- 1 Introduction
- 2 Please Note
- 3 Step 1. Create the SSL certificates
- 4 Step 2. Apply for a signed certificate
- 5 Step 3. Intermediate CA certs
- 6 Step 4. Setup Tomcat to use the SSL certs
- 7 Step 5. Enable secure XMLUI logins
- 8 Step 6. Enable HTTPS by default
- 9 Step 7. Rebuild DSpace
- 10 Step 8. Check the secure connection
- 11 References
- 12 News
Introduction
This wiki page describes a method of securing communications to a DSpace installation on the internet.
To protect the user credentials of the members of the research community that your repository will serve, it is highly recommended that all logins to the system are encrypted using the procedure detailed below.
- Update - 2014/11/18
A free certificate authority service is launching in 2015 that will greatly simplify the configuration of a secure server. See the link below.
https://letsencrypt.org
Please Note
- It is assumed that DSpace has been installed according to the suggested guidelines here: http://wiki.lib.sun.ac.za/index.php/SUNScholar/DSpace.
- This is not needed if doing an evaluation of the software on a test server behind your institutions firewall.
TCP/UDP Port 443
- Secure internet connections are created using the secure port (443) which must be opened on the campus firewall for your particular server by the central IT department.
- The local Tomcat server itself MUST be listening on port 443 and your local server firewall MUST allow access to port 443. See links below.
- http://wiki.lib.sun.ac.za/index.php/SUNScholar/Secure_Internet_Connections/S04
- http://wiki.lib.sun.ac.za/index.php/SUNScholar/Firewall
SSL Defaults
The default location for certificates is: /etc/ssl/certs. This is where we will put the certificates. Other services should point to this folder for the certificates.
Step 1. Create the SSL certificates
Step 2. Apply for a signed certificate
Step 3. Intermediate CA certs
Step 4. Setup Tomcat to use the SSL certs
Step 5. Enable secure XMLUI logins
Step 6. Enable HTTPS by default
Step 7. Rebuild DSpace
Step 8. Check the secure connection
References
Tomcat
- https://tomcat.apache.org/tomcat-7.0-doc
- https://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support
- https://tomcat.apache.org/tomcat-6.0-doc
- https://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html
- http://www.brandonchecketts.com/archives/convert-and-openssl-apache-ssl-certificate-to-a-pkcs12-tomcat
- http://www.tomcatexpert.com/knowledge-base/using-openssl-configure-ssl-certificates-tomcat
- http://code.google.com/p/jianwikis/wiki/TomcatSSLWithAPR
- http://johnjianfang.blogspot.com/2009/06/ssl-configuration-for-tomcat.html
- http://mircwiki.rsna.org/index.php?title=Configuring_Tomcat_to_Support_SSL
- http://blog.lesc.se/2009/09/how-to-makejava-ssl-trust-certificate.html
SSL/TLS
- http://www.openssl.org
- http://www.openssl.org/docs/apps/pkcs12.html
- http://www.madboa.com/geek/openssl/
- http://news.netcraft.com/ssl-survey
- http://www.mulesoft.com/tomcat-ssl
- http://www.sslshopper.com
- http://www.sslshopper.com/ssl-faq.html
- http://www.sslshopper.com/article-most-common-openssl-commands.html
- http://www.clintharris.net/2009/self-signed-certificates
- https://www.ssllabs.com/projects/best-practices/index.html
- https://www.feistyduck.com/books/openssl-cookbook/
- http://askubuntu.com/questions/537293/how-do-i-disable-sslv3-in-tomcat
Monopoly Notes
Please note: A quiet monopoly has been created in the SSL cert business. Verisign buys Thawte, Verisign buys Geotrust, Symantec buys Verisign.
- http://en.wikipedia.org/wiki/Thawte
- http://en.wikipedia.org/wiki/Geotrust
- http://en.wikipedia.org/wiki/Verisign
- http://en.wikipedia.org/wiki/Symantec
Update - 2013/10/09. Now we know why a monopoly, so that the NSA can spy on everyone even with SSL certs. What a joke these certs are.