Thank you Tim! For the record, GETINFO works ok in 0.2.8.4-rc (unstable).
HSFETCH still doesn't and I'll file a bug for it.
Razvan
On Thu, Jun 30, 2016 at 1:28 AM, Tim Wilson-Brown - teor wrote:
>
> > On 30 Jun 2016, at 06:42, Razvan Dragomirescu <
> razvan.dragomire...@veri.fi> wrote:
> >
> >
> On 29.06.2016, at 22:05, Iain R. Learmonth wrote:
>
> Hi All,
[…]
> You can find a live example of this patch at:
>
> https://irl.github.io/atlas/#/
>
> and a full list of changes are detailed in #6787.
>
> Please let me know if you can see any reason to not merge this, or if
> you have
> On 30 Jun 2016, at 06:42, Razvan Dragomirescu
> wrote:
>
> BTW, I have also tried the GETINFO command from the controller to fetch the
> hidden service descriptor directly from the host that has published it, but
> that doesn't work either. Fetching from the client side (after a connection
> On 30 Jun 2016, at 06:05, Iain R. Learmonth wrote:
>
> Hi All,
>
> On 29/06/16 09:56, Karsten Loesing wrote:
>> tl;dr: Globe is now retired in favor of an improved Atlas.
>
> Atlas is improved, but I'd like to improve it further. I've been
> tackling #6787 looking to improve the homepage and
BTW, I have also tried the GETINFO command from the controller to fetch the
hidden service descriptor directly from the host that has published it, but
that doesn't work either. Fetching from the client side (after a
connection) works fine:
AUTHENTICATE
250 OK
GETINFO hs/client/desc/id/js2usypscw
Hello everyone,
I seem to have found an issue (bug?) with the controller HSFETCH command -
I can't seem to be able to fetch hidden service descriptors for services
that use basic authentication. Tor appears to want to decrypt the
introduction points for some reason and also fails to look at the
Hi
Hi All,
On 29/06/16 09:56, Karsten Loesing wrote:
> tl;dr: Globe is now retired in favor of an improved Atlas.
Atlas is improved, but I'd like to improve it further. I've been
tackling #6787 looking to improve the homepage and make Atlas easier to
use for someone that isn't already a Tor expert.
Fair enough, this needs to be reviewed by a cryptographer once the dust
settles. I'm just trying to get a good grasp of what's possible within the
boundaries of the TOR network and how that translates to
cryptographic/security primitives I can use in this particular project
(like using the consensu
