tag:blogger.com,1999:blog-7652481.post115703200845561814..comments2007-12-17T11:33:47.214-05:00David Biancohttp://www.blogger.com/profile/09760835714791462863noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7652481.post-57966903336027590102007-12-17T11:33:00.000-05:002007-12-17T11:33:00.000-05:00It's true. Not only is the server gone, but the directory services protocol my script uses has been obsoleted for some time now. I just haven't really had a need to revisit this since then.David Biancohttp://www.blogger.com/profile/09760835714791462863noreply@blogger.comtag:blogger.com,1999:blog-7652481.post-90811057344893170292007-12-09T03:40:00.000-05:002007-12-09T03:40:00.000-05:00Since may 2007, the belegost server is gone. See here:<BR/><BR/>http://archives.seul.org/or/talk/Oct-2007/msg00109.htmlRoberthttp://www.blogger.com/profile/04086049078742260708noreply@blogger.comtag:blogger.com,1999:blog-7652481.post-17130966191214346992007-08-25T09:15:00.000-04:002007-08-25T09:15:00.000-04:00I'm looking for a solution to that same problem.<BR/><BR/>I'm surprised TOR doesn't use HTTPS to retrieve the server list as that tends not to be blocked.Anastrophehttp://www.blogger.com/profile/13135725661611582563noreply@blogger.comtag:blogger.com,1999:blog-7652481.post-50827781817830350072007-07-20T12:14:00.000-04:002007-07-20T12:14:00.000-04:00Hey,<BR/><BR/>seems like our ISP (Etisalat) is blocking TOR directory servers. 18.244.0.114 and 86.59.21.38 are blocked, hence my client is unable to even create a cache of routers. <BR/><BR/>anyway of over coming it?curioushttp://www.blogger.com/profile/07399528565384172794noreply@blogger.com