Difference between revisions of "SUNScholar/Secure Internet Connections"

From Libopedia
Jump to navigation Jump to search
m (→‎Letsencrypt/Certbot)
m (→‎Port 443 Firewall Access)
 
(6 intermediate revisions by the same user not shown)
Line 18: Line 18:
 
</font>
 
</font>
 
===Port 443 Firewall Access===
 
===Port 443 Firewall Access===
−
Secure internet connections are created using the secure port (443) which must be opened on the campus and local server firewall.
+
Secure internet connections are created using the secure port (443) '''which must be opened on the campus and local server firewall'''.
 
  http://wiki.lib.sun.ac.za/index.php/SUNScholar/Firewall
 
  http://wiki.lib.sun.ac.za/index.php/SUNScholar/Firewall
  
Line 40: Line 40:
 
==References==
 
==References==
 
===Tomcat===
 
===Tomcat===
 +
*https://tomcat.apache.org/tomcat-8.0-doc
 +
*https://tomcat.apache.org/tomcat-8.0-doc/config/http.html#SSL_Support
 +
----
 
*https://tomcat.apache.org/tomcat-7.0-doc
 
*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-7.0-doc/config/http.html#SSL_Support
 +
----
 
*https://tomcat.apache.org/tomcat-6.0-doc
 
*https://tomcat.apache.org/tomcat-6.0-doc
 
*https://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html
 
*https://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html
 +
----
 +
*http://wiki.apache.org/tomcat/FAQ/Security
 
*http://www.brandonchecketts.com/archives/convert-and-openssl-apache-ssl-certificate-to-a-pkcs12-tomcat
 
*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://www.tomcatexpert.com/knowledge-base/using-openssl-configure-ssl-certificates-tomcat
Line 54: Line 60:
  
 
===SSL/TLS===
 
===SSL/TLS===
−
*http://www.openssl.org
+
*'''http://www.openssl.org'''
 
*http://www.openssl.org/docs/apps/pkcs12.html
 
*http://www.openssl.org/docs/apps/pkcs12.html
 
*http://www.madboa.com/geek/openssl/
 
*http://www.madboa.com/geek/openssl/
Line 68: Line 74:
 
*https://www.maketecheasier.com/apache-server-ssl-support
 
*https://www.maketecheasier.com/apache-server-ssl-support
 
*https://mozilla.github.io/server-side-tls/ssl-config-generator
 
*https://mozilla.github.io/server-side-tls/ssl-config-generator
 +
*https://istlsfastyet.com
  
 
===Letsencrypt/Certbot===
 
===Letsencrypt/Certbot===
Line 79: Line 86:
 
*https://github.com/StuAtGit/LetsEncrypt
 
*https://github.com/StuAtGit/LetsEncrypt
 
*https://melo.myds.me/wordpress/lets-encrypt-for-tomcat-7-on-ds
 
*https://melo.myds.me/wordpress/lets-encrypt-for-tomcat-7-on-ds
 +
*https://www.sslforfree.com
  
 
===Monopoly Notes===
 
===Monopoly Notes===
Line 88: Line 96:
  
 
''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.''
 
''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.''
 +
 +
''Update - 2016/09/01. Letsencrypt is now allowing us to protect ourselves from the NSA!''
  
 
==News==
 
==News==

Latest revision as of 13:18, 27 March 2017

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

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.

Requirements

  • Secure connections are not needed if doing an evaluation of the software on a test server behind your institutions firewall.
  • It is assumed that DSpace has been installed according to the suggested guidelines here: http://wiki.lib.sun.ac.za/index.php/SUNScholar/DSpace.

Port 443 Firewall Access

Secure internet connections are created using the secure port (443) which must be opened on the campus and local server firewall. 

http://wiki.lib.sun.ac.za/index.php/SUNScholar/Firewall

SSL Certificate 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.

Procedure

Step 1 - Create the SSL certificates

Step 2 - Apply for a signed certificate

Step 3 - Get the intermediate CA certs

Step 4 - Configure 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

YouTube Video

References

Tomcat

SSL/TLS

Letsencrypt/Certbot

Monopoly Notes

Please note: A quiet monopoly has been created in the SSL cert business. Verisign buys Thawte, Verisign buys Geotrust, Symantec buys Verisign.

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.

Update - 2016/09/01. Letsencrypt is now allowing us to protect ourselves from the NSA!

News

Retrieved from "http://wiki.lib.sun.ac.za/index.php?title=SUNScholar/Secure_Internet_Connections&oldid=44727"