On Jun 17, 2014, at 17:09, Stuart Yeates stuart.yea...@vuw.ac.nz wrote:
On 06/17/2014 08:49 AM, Galen Charlton wrote:
On Sun, Jun 15, 2014 at 4:03 PM, Stuart Yeates stuart.yea...@vuw.ac.nz
wrote:
As I read it, 'Freedom to Read' means that we have to take active steps to
protect that rights
One of the reasons that EZProxy is so fast and resource-efficient is that
it is very lightweight. HTTPS to HTTP processing would require that
EZProzy, or another proxy layer behind it, provide an HTTPS endpoint.
Building this into EZProxy, I think, would not be a good fit for
their model.
I think
EZproxy already handles HTTPS connections for HTTPS enabled services today, and
on modern hardware (i.e. since circa 2005), cryptographic processing far
surpasses the speed of most network connections, so I do not accept the “it’s
too heavy” argument against it supporting the HTTPS to HTTP
Anyone thinking about these things is encouraged to read the thread
[CODE4LIB] EZProxy changes / alternatives ? in the archives of this list.
cheers
stuart
On 06/19/2014 05:28 AM, Andrew Anderson wrote:
EZproxy already handles HTTPS connections for HTTPS enabled services today, and
on modern
On 06/17/2014 08:49 AM, Galen Charlton wrote:
On Sun, Jun 15, 2014 at 4:03 PM, Stuart Yeates stuart.yea...@vuw.ac.nz wrote:
As I read it, 'Freedom to Read' means that we have to take active steps to
protect that rights of our readers to read what they want and in private.
[snip]
* building
On 06/18/2014 12:36 PM, Brent E Hanner wrote:
Stuart Yeates wrote:
Compared to other contributors to this thread, I appear to be (a) less
worried about state actors than our commercial partners and (b) keener
to see relatively straight forward technical fixes that just work 'for
free' across
Hi,
On Sun, Jun 15, 2014 at 4:03 PM, Stuart Yeates stuart.yea...@vuw.ac.nz wrote:
As I read it, 'Freedom to Read' means that we have to take active steps to
protect that rights of our readers to read what they want and in private.
[snip]
* building HTTPS Everywhere-like functionality into
On 6/16/14, 1:49 PM, Galen Charlton wrote:
However, I think that's only part of the picture for ILSs. Other parts
would include: * staff training on handling patron and circulation
data * ensuring that the ILS has the ability to control (and let users
control) how much circulation and search
