Chris -- I think Jason means just serve the whole site as HTTPS, which is what we do and it works fine. No template modifications are required. The Apache config looks like: <VirtualHost *:443> ServerName whoever.kohalibrary.com SSLEngine on SSLCertificateFile /etc/apache2/ssl.crt/whoever.kohalibrary.com.crt SSLCertificateKeyFile /etc/apache2/ssl.key/whoever.kohalibrary.com.plainkey .... SSL protects against the exposure of data in transit, like say, during update of a borrower's password on the staff interface. Nothing special gets done to that data, so it is just POSTed like any other form. But SSL keeps it from being readily sniffable. It can also be used for more advanced forms of authentication like client side certs (but if you're not a government contractor, it's unlikely your library needs to be *that* locked down). --Joe Atzberger, LibLime, Systems Administrator On Fri, Aug 22, 2008 at 9:42 AM, Chris Cormack <chris@bigballofwax.co.nz>wrote:
Hi Jason
Yep that would work fine, if the login pages were separate urls, instead they can be the same url as a page you might not want to server ssl. Eg opac-main.pl :)
So you would have to rejig some timeplates too.
Chris
On Sat, Aug 23, 2008 at 1:01 AM, Jason Stephenson <jstephenson@mvlc.org> wrote:
If you are using Apache to serve your Koha pages, then you can configure individual pages to force SSL.
Check the Apache documentation for Location and SSL.
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha