LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  June 2014

CODE4LIB June 2014

Subject:

Re: Does 'Freedom to Read' require us to systematically privilege HTTPS over HTTP?

From:

Cary Gordon <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 18 Jun 2014 08:20:26 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (94 lines)

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 that it would be simpler to just do everything in nginx, or
possibly node.

Cary

On Wednesday, June 18, 2014, Andrew Anderson <[log in to unmask]> wrote:

> On Jun 17, 2014, at 17:09, Stuart Yeates <[log in to unmask]
> <javascript:;>> wrote:
>
> > On 06/17/2014 08:49 AM, Galen Charlton wrote:
> >> On Sun, Jun 15, 2014 at 4:03 PM, Stuart Yeates <[log in to unmask]
> <javascript:;>> 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 LMSs (such
> functionality
> >>> may already exist, I'm not sure)
> >>
> >> Many ILSs can be configured to require SSL to access their public
> >> interfaces, and I think it would be worthwhile to encourage that as a
> >> default expectation for discovery interfaces.
> >>
> >> 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 history data gets retained
> >> * ensuring that the ILS backup policy strikes the correct balance
> >> between having enough for disaster recovery while not keeping
> >> individually identifiable circ history forever
> >> * ensuring that contracts with ILS hosting providers and services that
> >> access patron data from the ILS have appropriate language concerning
> >> data retention and notification of subpoenas.
> >
> > 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 large classes of library systems. Things like:
> >
> > * An ILS module that pulls the HTTPS Everywhere ruleset from
> https://gitweb.torproject.org/https-everywhere.git/tree/HEAD:/src/chrome/content/rules
> and applies those rules as a standard data-cleanup step on all imported
> data (MARC, etc).
> >
> > * A plugin to the CMS that drives the library's websites / blogs /
> whatever and uses the same rulesets to default all links to HTTPS.
> >
> > * An EzProxy plugin (or howto) on silently redirectly users to HTTPS
> over HTTP sites.
> >
> > cheers
> > stuart
>
> This is something that I have been interested in as well, and I have been
> asking our content providers when they will make their content available
> via HTTPS, but so far with very little uptake.  Perhaps if enough customers
> start asking, it will get enough exposure internally to drive adoption of
> HTTPS for the content side.
>
> I looked into what EZproxy offers for the user side, and that product does
> not currently have the ability to do HTTPS to HTTP proxying, even though
> there is no technical reason why it could not be done (look at how many
> HTTPS sites run Apache in a reverse proxy to HTTP servers internally for
> load balancing, etc.)
>
> EZproxy makes the assumption that a HTTP resource will always be accessed
> over HTTP, and you cannot configure a HTTPS entry point to HTTP services to
> at least secure the side of the communication channel that is going to
> contain more identifiable information about the user, before it becomes
> aggregated into the general proxy stream.
>
> --
> Andrew Anderson, Director of Development, Library and Information
> Resources Network, Inc.
> http://www.lirn.net/ | http://www.twitter.com/LIRNnotes |
> http://www.facebook.com/LIRNnotes
>


-- 
Cary Gordon
The Cherry Hill Company
http://chillco.com

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager