Is it common practice to enable https* by default on Koha servers? Any arguments for or against? *by creating an Apache config file that includes the SSL cert. As an example, you can connect to Google either by http://google.com or by https://google.com, because Google has enabled this. The latter creates a secure, end-to-end connection. -- Greg Lawson Rolling Hills Consolidated Library 1912 N. Belt Highway St. Joseph, MO 64506
We have done this for both the Public and Staff interfaces and it works fine. Tom On 04/17/2012 01:21 PM, G. Laws wrote:
Is it common practice to enable https* by default on Koha servers? Any arguments for or against?
*by creating an Apache config file that includes the SSL cert. As an example, you can connect to Google either by http://google.com or by https://google.com, because Google has enabled this. The latter creates a secure, end-to-end connection.
-- ------------------------------------------------------------------------ Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: tom@nd.edu Notre Dame, IN 46556 "Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that!" Lewis Carroll - Through the Looking Glass ------------------------------------------------------------------------
participants (3)
-
Bob Birchall -
G. Laws -
Tom Hanstra