[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: remote access

To secure the connection between the client and server (encrypt
communications) we use a 128 bits certificate. The are many companies
providing secure certificates (SSL norm) like Verisign and RSA, to name
only those two.

S=E9bastien Nadeau
Universit=E9 Laval
sebastien.nadeau@bibl.ulaval.ca

At 11:26 2001-03-29 -0500, you wrote:

>Most large libraries are using proxy servers to provide remote access to
>their users. Do a search on Google for "library proxy" and see the number
>of hits you get!
>
>Smaller libraries (like mine) sometimes use other approaches such as
>referer URLs or publisher provided institutional usernames and passwords.
>
>If a publisher/aggregator asks if you are using a proxy server you should
>tell them; they could set up code that checks for proxy-relay headers and
>disallows proxy requests for unregistered proxy servers (a user in your IP
>address space could set up a rogue proxy server and allow open access to
>IP-authenticated resources)
>
>Problems with Squid as you are using it might be that usernames and
>passwords are sent in clear-text if you are using HTTP Basic
>Authentication. Also some browser versions don't work with proxy servers.
>I recently did a presentation on remote authentication, it is at
>http://library.smc.edu/rua.htm and a list of other resources is at
>http://library.smc.edu/rpa.htm
>
>Steve Hunt
>Santa Monica College Library
>hunt_steve@smc.edu