iCepa / Tor.framework

Tor framework for the iCepa project
Other
249 stars 55 forks source link

Tor git issue #1

Closed avaan closed 8 years ago

avaan commented 8 years ago

Hi,

I am facing below issue when I try to clone your code,

fatal: unable to access 'https://git.torproject.org/tor.git/': Server aborted the SSL handshake

i could not able to trouble shoot the issue. let me know how did you clone tor git.

conradev commented 8 years ago

It seems that the Tor Project's git and gitweb server is down. You could try pointing the submodule to a mirror!

EDIT: The git server is operating fine, can you access https://gitweb.torproject.com from your browser? Your internet connection might be censored/filtered/faulty.

avaan commented 8 years ago

Finally i was able to compile your project....

conradev commented 8 years ago

Awesome, glad to hear! Let me know if you run across any issues.

avaan commented 8 years ago

Hi... sorry to bother you. While running my app I am getting below errors.

Feb 18 10:11:15.489 [notice] Tor v0.2.6.10 running on Darwin with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.5.
Feb 18 10:11:15.490 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Feb 18 10:11:15.491 [notice] Configuration file "/private/var/mobile/Containers/Data/Application/EB4214A6-01A7-406D-8F32-BEF21DD4DBF4/.torrc" not present, using reasonable defaults.
Feb 18 10:11:15.691 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 18 10:11:15.710 [warn] Permissions on directory /var/mobile/Containers/Data/Application/EB4214A6-01A7-406D-8F32-BEF21DD4DBF4/Documents are too permissive.
Feb 18 10:11:15.711 [warn] Before Tor can create a control socket in "/var/mobile/Containers/Data/Application/EB4214A6-01A7-406D-8F32-BEF21DD4DBF4/Documents/control_port", the directory "/var/mobile/Containers/Data/Application/EB4214A6-01A7-406D-8F32-BEF21DD4DBF4/Documents" needs to exist, and to be accessible only by the user account that is running Tor.  (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)
Feb 18 10:11:15.713 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
Feb 18 10:11:15.715 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.
Feb 18 10:11:15.716 [err] Reading config failed--see warnings above.

trying to find the cause.....