Re: [freenet-dev] 5 weeks till our SSL certificate expires

2017-02-23 Thread Freenet
Not only does Cloudflair ruin Tor access. https://www.lowendtalk.com/discussion/106740/serious-security-issue-at-cloudflare-change-all-your-passwords-now [00:20] cloudflare severely fucked up [00:20] .t https://bugs.chromium.org/p/project-zero/issues/detail?id=1139 [00:20] 1139 - cloudflare:

Re: [freenet-dev] 5 weeks till our SSL certificate expires

2017-02-23 Thread Freenet
An anonymous FMS user raised this point. freenet:USK@KOn1onAO97w3RNzAgcTsqSW6WAliG4EgevONnn4-qMs,k5~fkfH1PYnPABwkLAQSXUoeoX1Gh3fTXxk-pC2ujRM,AQACAAE/maybe-the-new-freenetproject.org-website/0/ Ian: > Re: deployment, I think the ideal would be automatic deployment from the > github repo on a

Re: [freenet-dev] preserving the links to the wiki

2017-02-23 Thread Ian Clarke
On Thu, Feb 23, 2017 11:19 AM, x...@freenetproject.org wrote:What about a stupid, plain old htaccess file? Don't know if that will work with our current plan to host on AWS, but hopefully there is some equivalent way to remap URLs that we can use. But we need to find a hoster for the mailing

Re: [freenet-dev] preserving the links to the wiki

2017-02-23 Thread xor
On Wednesday, February 22, 2017 11:11:04 PM Ian Clarke wrote: > I don't want to break links, but I also don't want that to become a blocker > for updating to the new website. > Hopefully there can be some way we can re-map URLs and then those that care > about breaking links can migrate the

Re: [freenet-dev] 5 weeks till our SSL certificate expires

2017-02-23 Thread Florent Daigniere
I'll work the details out; either that or using the CI tool to do it for us (deploy the artefacts from the CI build to s3) Florent On Thu, 2017-02-23 at 15:17 +, Ian wrote: >  Re: deployment, I think the ideal would be automatic deployment from > the github repo on a merge to a production

Re: [freenet-dev] 5 weeks till our SSL certificate expires

2017-02-23 Thread Ian
Re: deployment, I think the ideal would be automatic deployment from the github repo on a merge to a production branch.  I assume we can do that via an AWS Lambda? On Thu, Feb 23, 2017 12:40 AM, Dan Roberts ademan...@gmail.com wrote: The website is fully static and should be fine with s3 +