[tor-relays] Tor Cloud: still not listed

[Fabiano London]

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 at 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 at 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 at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20140118/585cf58f/attachment-0001.html>