On Fri, May 17, 2013 at 3:12 AM, leif <
not.r...@online.de> wrote:
> Volker Braun wrote:
>>
>> If its ISP-specific then presumably thats because they force all http
>> through a not-so-transparent proxy.
>>
>> The proper solution IMHO would be to enable SSL on all
>> development-related web pages.
>
>
> +1
>
> -leif
+1
I'll do this as soon as I get time, paying for the SSL certs (a few
bucks a year) using Sage Foundation donations (it seems like a good
use of that money!). What's a list of domains that we should really
switch to using SSL for?
William
>
>
>> That should just be common sense for data
>> integrity and password safety reasons.
>
>
> --
> () The ASCII Ribbon Campaign
> /\ Help Cure HTML E-Mail
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
sage-devel+...@googlegroups.com.
> To post to this group, send email to
sage-...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/sage-devel?hl=en.
> For more options, visit
https://groups.google.com/groups/opt_out.
>
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org