>I think you're missing the point. Protecting the content is as you say >unimportant if it's open content. But the big threat here is to the privacy of >the patrons. Your viewing history, if it gets into the wrong hands, could >easily put you or someone you care about at risk.
The big threat for me is that someone can unload a bogus thesis into my repository and on that basis claim to have a degree ... When a TLS connection gets established, the two parties negotiate the most secure option they both support. That negotiation is driven by the client, meaning that modern sanely configured clients will normally be very secure from passive listening attacks. Active attacks are more challenging to prevent, and raising the minimum security of the certs supported is one approach to do that. Cheers stuart ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
