Tor Cloud: still not listed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges. First, I am blind and I am not to read the "How to" in the Get started page of cloud.torproject.org, so I though all was configured, and had a surprise with the security group I have to define by myself. :) So my question is: would it be possible to make the step by step instructions accessible please ? Less pictures or more text in all cases, having text doesn't require to remove images. The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image. Else, how long in my relay will be listed? And which reasons could make my relay unavailable on atlas? I opened all four ports I found on the get started page but half an hour latter, it is still not listed. Thanks, - -- Patrick ZAJDA Skype : gansta93 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS1o1vAAoJEKPVT2DeSPb41WYIAKc3PWOf5RB0dUdo/Rcru2iF 8LceynqNjYbqyjJxwQbBIdpXkUHfoD1t2D9Tv8DYYrm0pLHrPWDzRZbbKHKPCiKI VlvrUy7TKyLPl6CKV3QztMMx62jGYsxitEOjy2b7GS2XyA1VnWu5JR8TgDNBeh4L KeP3CQOLKGS3dyqOfEjXzBpSb3sQQwJbzVjZJIZBaGMgqYbEVU7YsPdP/+e+1/0H V0T/uDTgquCE2eo7tXjgQLp97IAKIxrufJewaVnwJjTNDVwAxh5VigFhMbebf7yW rLo3PRGZMrCrJ5I9niGziGglmnnqWHmLxLIHRHx00TH1E+2fV+fPlWY3ssMwEuk= =SfE2 -----END PGP SIGNATURE-----
Hi Patrick! You did indeed setup a bridge, so it is expected that it won't be listed in atlas. This is also the expected behaviour of the Tor Cloud image as the idea is to leverage Amazon EC2 to provide an easy way for people to create bridges. If you want to run a relay, it is from my understanding unwise to do so on Amazon EC2, as they are very expensive and there are various other possibilities that are a lot cheaper. Nils 2014/1/15 Patrick ZAJDA <patrick@zajda.fr>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
First, I am blind and I am not to read the "How to" in the Get started page of cloud.torproject.org, so I though all was configured, and had a surprise with the security group I have to define by myself. :) So my question is: would it be possible to make the step by step instructions accessible please ? Less pictures or more text in all cases, having text doesn't require to remove images.
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image. Else, how long in my relay will be listed? And which reasons could make my relay unavailable on atlas? I opened all four ports I found on the get started page but half an hour latter, it is still not listed.
Thanks, - -- Patrick ZAJDA Skype : gansta93 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS1o1vAAoJEKPVT2DeSPb41WYIAKc3PWOf5RB0dUdo/Rcru2iF 8LceynqNjYbqyjJxwQbBIdpXkUHfoD1t2D9Tv8DYYrm0pLHrPWDzRZbbKHKPCiKI VlvrUy7TKyLPl6CKV3QztMMx62jGYsxitEOjy2b7GS2XyA1VnWu5JR8TgDNBeh4L KeP3CQOLKGS3dyqOfEjXzBpSb3sQQwJbzVjZJIZBaGMgqYbEVU7YsPdP/+e+1/0H V0T/uDTgquCE2eo7tXjgQLp97IAKIxrufJewaVnwJjTNDVwAxh5VigFhMbebf7yW rLo3PRGZMrCrJ5I9niGziGglmnnqWHmLxLIHRHx00TH1E+2fV+fPlWY3ssMwEuk= =SfE2 -----END PGP SIGNATURE-----
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Please! I am not participate in this forum anymore! Any e mail that coming after this will be reported to Uk intelligence police (M15) Be aware pls with all posts or e mails here ! Have a nice weekend to all
On 15 Jan 2014, at 14:16, Nils Kunze <kunze.nils@gmail.com> wrote:
Hi Patrick!
You did indeed setup a bridge, so it is expected that it won't be listed in atlas. This is also the expected behaviour of the Tor Cloud image as the idea is to leverage Amazon EC2 to provide an easy way for people to create bridges.
If you want to run a relay, it is from my understanding unwise to do so on Amazon EC2, as they are very expensive and there are various other possibilities that are a lot cheaper.
Nils
2014/1/15 Patrick ZAJDA <patrick@zajda.fr>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
First, I am blind and I am not to read the "How to" in the Get started page of cloud.torproject.org, so I though all was configured, and had a surprise with the security group I have to define by myself. :) So my question is: would it be possible to make the step by step instructions accessible please ? Less pictures or more text in all cases, having text doesn't require to remove images.
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image. Else, how long in my relay will be listed? And which reasons could make my relay unavailable on atlas? I opened all four ports I found on the get started page but half an hour latter, it is still not listed.
Thanks, - -- Patrick ZAJDA Skype : gansta93 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJS1o1vAAoJEKPVT2DeSPb41WYIAKc3PWOf5RB0dUdo/Rcru2iF 8LceynqNjYbqyjJxwQbBIdpXkUHfoD1t2D9Tv8DYYrm0pLHrPWDzRZbbKHKPCiKI VlvrUy7TKyLPl6CKV3QztMMx62jGYsxitEOjy2b7GS2XyA1VnWu5JR8TgDNBeh4L KeP3CQOLKGS3dyqOfEjXzBpSb3sQQwJbzVjZJIZBaGMgqYbEVU7YsPdP/+e+1/0H V0T/uDTgquCE2eo7tXjgQLp97IAKIxrufJewaVnwJjTNDVwAxh5VigFhMbebf7yW rLo3PRGZMrCrJ5I9niGziGglmnnqWHmLxLIHRHx00TH1E+2fV+fPlWY3ssMwEuk= =SfE2 -----END PGP SIGNATURE-----
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Wed, Jan 15, 2014 at 1:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
Hi all,
Hi,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
First, I am blind and I am not to read the "How to" in the Get started page of cloud.torproject.org, so I though all was configured, and had a surprise with the security group I have to define by myself. :) So my question is: would it be possible to make the step by step instructions accessible please ? Less pictures or more text in all cases, having text doesn't require to remove images.
Thanks, I have added this to our Trac ticket about updating the website: https://trac.torproject.org/projects/tor/ticket/8768)
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something?
From https://www.torproject.org/docs/bridges: Bridge relays (or "bridges" for short) are Tor relays that aren't listed in the main Tor directory (as opposed to relays). Since there is no complete public list of them, even if an ISP is filtering connections to all the known Tor relays, they probably won't be able to block all the bridges.
The difference between a Tor Cloud "obfsproxy bridge" and a "private bridge" is whether or not the bridge reports its address (IP address and port) to the Tor Project. If it does, the address will automatically be distributed to users who need it (through the help desk, bridges.torproject.org, etc). If it does not, it's up to you to distribute the address.
If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image. Else, how long in my relay will be listed?
Only relays are listed on atlas.torproject.org. While it is possible to run a relay on AWS, it's not recommended for the simple reason that a useful relay will use too much bandwidth and cost a lot of money (i.e. there are cheaper hosting alternatives if you wish to run a relay). -- Runa A. Sandvik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Runa, Le 15/01/2014 15:20, Runa A. Sandvik a écrit :
On Wed, Jan 15, 2014 at 1:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
Hi all,
Hi,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
First, I am blind and I am not to read the "How to" in the Get started page of cloud.torproject.org, so I though all was configured, and had a surprise with the security group I have to define by myself. :) So my question is: would it be possible to make the step by step instructions accessible please ? Less pictures or more text in all cases, having text doesn't require to remove images.
Thanks, I have added this to our Trac ticket about updating the website: https://trac.torproject.org/projects/tor/ticket/8768)
Thanks you!
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something?
From https://www.torproject.org/docs/bridges: Bridge relays (or "bridges" for short) are Tor relays that aren't listed in the main Tor directory (as opposed to relays). Since there is no complete public list of them, even if an ISP is filtering connections to all the known Tor relays, they probably won't be able to block all the bridges.
The difference between a Tor Cloud "obfsproxy bridge" and a "private bridge" is whether or not the bridge reports its address (IP address and port) to the Tor Project. If it does, the address will automatically be distributed to users who need it (through the help desk, bridges.torproject.org, etc). If it does not, it's up to you to distribute the address.
OK, so to be sure I understand: with an obfsproxy one, relay address and port are listed but not in atlas.torproject.org?
If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image. Else, how long in my relay will be listed?
Only relays are listed on atlas.torproject.org. While it is possible to run a relay on AWS, it's not recommended for the simple reason that a useful relay will use too much bandwidth and cost a lot of money (i.e. there are cheaper hosting alternatives if you wish to run a relay).
OK, I understand now and won't change anything. :) Thanks, - -- Patrick ZAJDA Skype : gansta93 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS1p9DAAoJEKPVT2DeSPb4EcgH/0IlRBDvAipWjIkzWObmG2uD jfe7hhyyvyCM9o9RPSbm/AXFvdrbjEB9xBMbOzXc3acsSh1MpzwYCOXqGzotSpUj MRC2ZU9cpdDYKM1AeSsm4SRNOtSHVcg0bWrxB3j1wPwXars130mAdsO1fl05RXNU dyqSnAfrPjhoGPxsWpmgFIQj1C1cJtT1aBBEYPoceI/BrWl0PpAWWRZphEkKpsso JrisReJ2gGeyB6C491MM3DJ5hgMwOFOsh1qYNuaHKoUqEy+ogoDJ5WfOVimYrvY9 UIFEY/UF4y91XzJbql06WZSRA+V8dCir3rnYUxiv7iA0yZbxIAudruawX5gNb6g= =PtVG -----END PGP SIGNATURE-----
On Wed, Jan 15, 2014 at 2:46 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
Le 15/01/2014 15:20, Runa A. Sandvik a écrit :
On Wed, Jan 15, 2014 at 1:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something?
From https://www.torproject.org/docs/bridges: Bridge relays (or "bridges" for short) are Tor relays that aren't listed in the main Tor directory (as opposed to relays). Since there is no complete public list of them, even if an ISP is filtering connections to all the known Tor relays, they probably won't be able to block all the bridges.
The difference between a Tor Cloud "obfsproxy bridge" and a "private bridge" is whether or not the bridge reports its address (IP address and port) to the Tor Project. If it does, the address will automatically be distributed to users who need it (through the help desk, bridges.torproject.org, etc). If it does not, it's up to you to distribute the address.
OK, so to be sure I understand: with an obfsproxy one, relay address and port are listed but not in atlas.torproject.org?
Yes, that's correct. The address will be distributed to users automatically. Thanks for running a bridge! -- Runa A. Sandvik
On Wed, Jan 15, 2014 at 3:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
[...]
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image.
If your bridge is set to publish its descriptor (should be default), you might be able to search for it using the new Globe tool: https://globe.torproject.org/ Regards Kostas
On Wed, Jan 15, 2014 at 3:08 PM, Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
On Wed, Jan 15, 2014 at 3:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
[...]
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image.
If your bridge is set to publish its descriptor (should be default), you might be able to search for it using the new Globe tool: https://globe.torproject.org/
Good point! I forgot about Globe. It seems https://globe.torproject.org/#/search/query=ec2 only lists 43 currently running bridges, while https://metrics.torproject.org/cloudbridges.png lists more than 300. Any idea why the numbers are so different? -- Runa A. Sandvik
On Wed, Jan 15, 2014 at 5:30 PM, Runa A. Sandvik <runa.sandvik@gmail.com>wrote:
On Wed, Jan 15, 2014 at 3:08 PM, Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
On Wed, Jan 15, 2014 at 3:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
[...]
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image.
If your bridge is set to publish its descriptor (should be default), you might be able to search for it using the new Globe tool: https://globe.torproject.org/
Good point! I forgot about Globe. It seems https://globe.torproject.org/#/search/query=ec2 only lists 43 currently running bridges, while https://metrics.torproject.org/cloudbridges.png lists more than 300. Any idea why the numbers are so different?
I haven't checked, but can't the cloud bridge operator change the nickname (just as any other operator can)? See e.g. https://globe.torproject.org/#/search/query=cloud (non-zero count of bridges there, too. Not sure if related, though.)
On 1/15/14 4:30 PM, Runa A. Sandvik wrote:
On Wed, Jan 15, 2014 at 3:08 PM, Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
On Wed, Jan 15, 2014 at 3:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
[...]
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image.
If your bridge is set to publish its descriptor (should be default), you might be able to search for it using the new Globe tool: https://globe.torproject.org/
Good point! I forgot about Globe. It seems https://globe.torproject.org/#/search/query=ec2 only lists 43 currently running bridges, while https://metrics.torproject.org/cloudbridges.png lists more than 300. Any idea why the numbers are so different?
Ah, that's because Globe limits results to 50 hits, in your case 7 relays and 43 bridges. It should tell users that only the first 50 hits are displayed. Opening a ticket. All the best, Karsten
On Wed, Jan 15, 2014 at 3:38 PM, Karsten Loesing <karsten@torproject.org> wrote:
On 1/15/14 4:30 PM, Runa A. Sandvik wrote:
On Wed, Jan 15, 2014 at 3:08 PM, Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
On Wed, Jan 15, 2014 at 3:30 PM, Patrick ZAJDA <patrick@zajda.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
I have set up an Amazon EC2 instance to run a Tor Relay, I chose Obfsproxy Bridges.
[...]
The second point is: I looked at the configuration, and noticed bridge is set to 1. I though it made the tor relay private, do I have miss-understood something? If I didn't miss-understand, that explains why it is still not listed on atlas.torproject.org, and there is a problem with the provided EC2 image.
If your bridge is set to publish its descriptor (should be default), you might be able to search for it using the new Globe tool: https://globe.torproject.org/
Good point! I forgot about Globe. It seems https://globe.torproject.org/#/search/query=ec2 only lists 43 currently running bridges, while https://metrics.torproject.org/cloudbridges.png lists more than 300. Any idea why the numbers are so different?
Ah, that's because Globe limits results to 50 hits, in your case 7 relays and 43 bridges. It should tell users that only the first 50 hits are displayed. Opening a ticket.
That makes sense. Thanks! -- Runa A. Sandvik
Has that illustrated for the developers that determined, motivated people can be confused by the terms? Bridge, exit and relay are clear terms but not when interchanged with bridge relay, exit node, exit relay, obfsproxy and others. Robert
participants (7)
-
Fabiano London -
I -
Karsten Loesing -
Kostas Jakeliunas -
Nils Kunze -
Patrick ZAJDA -
Runa A. Sandvik