Dear Team,
I have good news, Rabbi Rob Thomas (robt@cymru.com) is going to cover the costs associated with keeping meek alive.
So far I have setup 2 new accounts with Amazon and Azure and working to confirm the functionality. https://d183ohpl22nq2f.cloudfront.net/ https://meek.azureedge.net/
Cloudfront is working fine and i'm trying to resolve issues with the Azure CDN. Is there a ticket I can update with these details? I think I should also bring up a backend server (bridge) and share the new config lines for the Tor Browser Bundle. I'm hoping to get all this done by Monday or sooner.
Thank you David for keeping this service operational for so long and thank you Rob for keeping it alive!
All the best, Sina
"Be the change that you wish to see in the world." - Mahatma Gandhi
----- On Jan 19, 2017, at 2:17 AM, Yawning Angel yawning@schwanenlied.me wrote:
On Mon, 9 Jan 2017 20:08:03 -0800 David Fifield david@bamsoftware.com wrote:
On Mon, Jan 09, 2017 at 03:06:17PM -0800, Shari Steele wrote:
Hey David. How much money do we need for 2017?
The total for meek-azure November 2015 to November 2016 was $6290.69, or about $525 a month on average. I believe it could go 2× or higher if we relaxed rate limits. meek-amazon is higher, $13756.30 or $1150/month over the same time period.
Has there been any progress on finding alternative funding for this? dcf's comments on trac indicate "no", which would be unfortunate.
-- Yawning Angel
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Hi all,
Hurrah for Rabbi Rob, Lauren, David, Nima, Sina, and the other people who are focusing on this.
There are only ~1,200 Tor users in China right now and 5,000 in Iran. Looking forward to Snowflake, localization, and other plans to drive up those numbers.
Will tweet about this development (with help) in Chinese, Farsi, and other languages when the time is right.
Cheers,
Katie
Sina Rabbani:
Dear Team,
I have good news, Rabbi Rob Thomas (robt@cymru.com) is going to cover the costs associated with keeping meek alive.
So far I have setup 2 new accounts with Amazon and Azure and working to confirm the functionality. https://d183ohpl22nq2f.cloudfront.net/ https://meek.azureedge.net/
Cloudfront is working fine and i'm trying to resolve issues with the Azure CDN. Is there a ticket I can update with these details? I think I should also bring up a backend server (bridge) and share the new config lines for the Tor Browser Bundle. I'm hoping to get all this done by Monday or sooner.
Thank you David for keeping this service operational for so long and thank you Rob for keeping it alive!
All the best, Sina
"Be the change that you wish to see in the world." - Mahatma Gandhi
----- On Jan 19, 2017, at 2:17 AM, Yawning Angel yawning@schwanenlied.me wrote:
On Mon, 9 Jan 2017 20:08:03 -0800 David Fifield david@bamsoftware.com wrote:
On Mon, Jan 09, 2017 at 03:06:17PM -0800, Shari Steele wrote:
Hey David. How much money do we need for 2017?
The total for meek-azure November 2015 to November 2016 was $6290.69, or about $525 a month on average. I believe it could go 2× or higher if we relaxed rate limits. meek-amazon is higher, $13756.30 or $1150/month over the same time period.
Has there been any progress on finding alternative funding for this? dcf's comments on trac indicate "no", which would be unfortunate.
-- Yawning Angel
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Wow, this is amazing! Heartfelt thanks to Rabbi Rob and Sina and David. Shari
On Jan 20, 2017, at 9:50 AM, Sina Rabbani sina@redteam.net wrote:
Dear Team,
I have good news, Rabbi Rob Thomas (robt@cymru.com) is going to cover the costs associated with keeping meek alive.
So far I have setup 2 new accounts with Amazon and Azure and working to confirm the functionality. https://d183ohpl22nq2f.cloudfront.net/ https://meek.azureedge.net/
Cloudfront is working fine and i'm trying to resolve issues with the Azure CDN. Is there a ticket I can update with these details? I think I should also bring up a backend server (bridge) and share the new config lines for the Tor Browser Bundle. I'm hoping to get all this done by Monday or sooner.
Thank you David for keeping this service operational for so long and thank you Rob for keeping it alive!
All the best, Sina
"Be the change that you wish to see in the world." - Mahatma Gandhi
----- On Jan 19, 2017, at 2:17 AM, Yawning Angel yawning@schwanenlied.me wrote:
On Mon, 9 Jan 2017 20:08:03 -0800 David Fifield david@bamsoftware.com wrote:
On Mon, Jan 09, 2017 at 03:06:17PM -0800, Shari Steele wrote:
Hey David. How much money do we need for 2017?
The total for meek-azure November 2015 to November 2016 was $6290.69, or about $525 a month on average. I believe it could go 2× or higher if we relaxed rate limits. meek-amazon is higher, $13756.30 or $1150/month over the same time period.
Has there been any progress on finding alternative funding for this? dcf's comments on trac indicate "no", which would be unfortunate.
-- Yawning Angel
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project
Sina Rabbani transcribed 2.5K bytes:
Dear Team,
I have good news, Rabbi Rob Thomas (robt@cymru.com) is going to cover the costs associated with keeping meek alive.
So far I have setup 2 new accounts with Amazon and Azure and working to confirm the functionality. https://d183ohpl22nq2f.cloudfront.net/ https://meek.azureedge.net/
Cloudfront is working fine and i'm trying to resolve issues with the Azure CDN. Is there a ticket I can update with these details? I think I should also bring up a backend server (bridge) and share the new config lines for the Tor Browser Bundle. I'm hoping to get all this done by Monday or sooner.
Thank you David for keeping this service operational for so long and thank you Rob for keeping it alive!
All the best, Sina
Wow, this is great! Thanks!
Do you all have any plans to resurrect the Google AppEngine meek? I've been talking with the NoiseTor people, and they really wanted to help with meek costs in some way, and also they think they collectively know enough Googlers to get that re-set up (and potentially have bandwidth donated).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Do you all have any plans to resurrect the Google AppEngine meek? I've been talking with the NoiseTor people, and they really wanted to help with meek costs in some way, and also they think they collectively know enough Googlers to get that re-set up (and potentially have bandwidth donated).
We would love to resurrect the Google AppEngine meek, yes indeed!
Thank you, Isis!
- -- Rabbi Rob Thomas Team Cymru "It is easy to believe in freedom of speech for those with whom we agree." - Leo McKern
On Fri, Jan 20, 2017 at 05:50:08PM +0000, Sina Rabbani wrote:
Cloudfront is working fine and i'm trying to resolve issues with the Azure CDN. Is there a ticket I can update with these details?
Once we have the details worked out, I'll make a ticket containing the patch for tor-browser-bundle.git.
Here are a couple of past tickets changing aspects of the bridges: https://bugs.torproject.org/16634 https://bugs.torproject.org/17473
On Fri, Jan 20, 2017 at 05:50:08PM +0000, Sina Rabbani wrote:
I have good news, Rabbi Rob Thomas (robt@cymru.com) is going to cover the costs associated with keeping meek alive.
So far I have setup 2 new accounts with Amazon and Azure and working to confirm the functionality. https://d183ohpl22nq2f.cloudfront.net/ https://meek.azureedge.net/
Cloudfront is working fine and i'm trying to resolve issues with the Azure CDN. Is there a ticket I can update with these details? I think I should also bring up a backend server (bridge) and share the new config lines for the Tor Browser Bundle. I'm hoping to get all this done by Monday or sooner.
I opened a ticket to make the change for meek-azure: https://bugs.torproject.org/21342
I was thinking we should do meek-azure first and later meek-amazon, so as not to have all our eggs in one basket in case of an unanticipated problem.
With the recent releases of Tor Browser 6.5.1 and 7.0a2, Tor Browser users will now be using the new CDN backend and bridge when they select meek-azure. This will be a good time to monitor bridge usage and check if anything unexpected happens.
If all goes well, we can queue up meek-amazon for the next release.
On Wed, Mar 08, 2017 at 11:42:15PM -0800, David Fifield wrote:
With the recent releases of Tor Browser 6.5.1 and 7.0a2, Tor Browser users will now be using the new CDN backend and bridge when they select meek-azure. This will be a good time to monitor bridge usage and check if anything unexpected happens.
If all goes well, we can queue up meek-amazon for the next release.
The new meek-azure backend seems to be working with no problems. The bridge is picking up users: https://atlas.torproject.org/#details/8F4541EEE3F2306B7B9FEF1795EC302F6B84DA...
Are we ready to do the same thing for meek-amazon? Let me know and I'll file a ticket.
Dear David and Team,
I have the Amazon CDN up and running, however today when i tried to test it I realized that the backend bridge which is operated by klaus.layer@jama.is is down. I sent a note to both David and Klaus to learn more.
We are happy to also provide the bridge for the amazon front, I am waiting to hear back so I know what my next step should be.
All the best, Sina
p.s. This is the bridge line that was working a couple of months ago:
meek 0.0.2.0:2 97700DFE9F483596DDA6264C4D7DF7641E1E39CE url=https://d183ohpl22nq2f.cloudfront.net/ front=a0.awsstatic.com
On 4/1/17 19:40, David Fifield wrote:
On Wed, Mar 08, 2017 at 11:42:15PM -0800, David Fifield wrote:
With the recent releases of Tor Browser 6.5.1 and 7.0a2, Tor Browser users will now be using the new CDN backend and bridge when they select meek-azure. This will be a good time to monitor bridge usage and check if anything unexpected happens.
If all goes well, we can queue up meek-amazon for the next release.
The new meek-azure backend seems to be working with no problems. The bridge is picking up users: https://atlas.torproject.org/#details/8F4541EEE3F2306B7B9FEF1795EC302F6B84DA...
Are we ready to do the same thing for meek-amazon? Let me know and I'll file a ticket.
On Mon, Apr 10, 2017 at 04:14:38PM -0400, Sina Rabbani wrote:
I have the Amazon CDN up and running, however today when i tried to test it I realized that the backend bridge which is operated by klaus.layer@jama.is is down. I sent a note to both David and Klaus to learn more.
The backend bridge is working for me, so I have opened a ticket: https://bugs.torproject.org/21918
On Tue, Apr 11, 2017 at 01:27:42AM -0700, David Fifield wrote:
On Mon, Apr 10, 2017 at 04:14:38PM -0400, Sina Rabbani wrote:
I have the Amazon CDN up and running, however today when i tried to test it I realized that the backend bridge which is operated by klaus.layer@jama.is is down. I sent a note to both David and Klaus to learn more.
The backend bridge is working for me, so I have opened a ticket: https://bugs.torproject.org/21918
Tor Browser 6.5.2 was just released, so the new Amazon CDN configuration should start seeing traffic. https://blog.torproject.org/blog/tor-browser-652-released
Thank you David and everyone involved in making this happen. Many thanks to Klaus for operating the relay behind the Amazon front.
All the best, Sina
On 4/19/17 16:18, David Fifield wrote:
On Tue, Apr 11, 2017 at 01:27:42AM -0700, David Fifield wrote:
On Mon, Apr 10, 2017 at 04:14:38PM -0400, Sina Rabbani wrote:
I have the Amazon CDN up and running, however today when i tried to test it I realized that the backend bridge which is operated by klaus.layer@jama.is is down. I sent a note to both David and Klaus to learn more.
The backend bridge is working for me, so I have opened a ticket: https://bugs.torproject.org/21918
Tor Browser 6.5.2 was just released, so the new Amazon CDN configuration should start seeing traffic. https://blog.torproject.org/blog/tor-browser-652-released
tor-project@lists.torproject.org