[Koha] Securing login pages
ohiocore at gmail.com
Sat Aug 23 02:01:00 NZST 2008
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:
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
LibLime, Systems Administrator
On Fri, Aug 22, 2008 at 9:42 AM, Chris Cormack <chris at 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.
> On Sat, Aug 23, 2008 at 1:01 AM, Jason Stephenson <jstephenson at mvlc.org>
> > 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 at lists.katipo.co.nz
> > http://lists.katipo.co.nz/mailman/listinfo/koha
> Koha mailing list
> Koha at lists.katipo.co.nz
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Koha