the library is for my personal projects, is not in the public domain
On 3/21/14, kalgecin wrote:
> where can i find this library?
>
>
> On Fri, Mar 21, 2014 at 4:07 PM, Frank Young wrote:
>
>> I have implemented the protocol as a c++ static library which you can
>>
the library is for my personal projects, is not in the public domain
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Thanks for the headup but it is not that. Anyway, as posted in my last
post, i have fixed the issue.
thanks
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
well, after searching through your github, I realized you have not
even started anything on tor. I could give you a hand. I understand
the protocol very well and have implemented my own version of it.
___
tor-dev mailing list
tor-dev@lists.torproject.org
I have found out the issue, it relates to fixs made for time_t
variables in an earlier version of tor. Microsofts changes of time_t
from 32bit to 64bit caused you guys to stop the earlier assumptions
that time_t will be negative sometimes. It broke my implementation but
i have fixed it now. I think
I have implemented the protocol as a c++ static library which you can
link against.
I can give you headup if you wish
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
I have noticed that since the release of version 0.2.4.18-rc - 2013-11-16,
Attempts to fetch v2 rendezvous service descriptor are failing.
The issue seems to get worse as many people are updating their clients.
The calculation of decriptor ids based on specification in rend-spec.tx
doeesn't seems
sorry my mistake, talking about only RELAY DATA
On 5/3/13, Frank Young wrote:
> The payload format for RELAY_COMMAND_END and RELAY_DATA are not
> details in the tor protocol specifications.
> where can i get the payload format for these relay cells?
The payload format for RELAY_COMMAND_END and RELAY_DATA are not
details in the tor protocol specifications.
where can i get the payload format for these relay cells?
Thanks
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org
The digest of relay cells are running digests [ SHA_final() is never
called ], so the digest of each cell is dependent on the previously
computed digest destined for that node particular node.
Hashing is seeded with values determine by the OR which responded with
CREATED or REALY EXTENDED cell.
I h
Yes you are right, after decoding that value from base64 and
re-encoding it in base16, it can be used to get the router's
descriptor.
What i'm trying to get is the list of HSDIR responsible for a hidden service.
After calculating the descriptor for the hidden service, i need to
know the identity di
In a consensus, the item after nickname is base64 encoded "hash of a
router's identity key"
If this item is base64 decoded, is it the same as the "identity
digest" of the router?
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproj
igest and determine which 6 are responsible at
> the current time.
>
> https://gist.github.com/DonnchaC/5451637
>
>
>
> On Wed, Apr 24, 2013 at 11:23 AM, Frank Young wrote:
>
>> Dealing with v2 hidden service descriptors, how does a tor client get
>> the list of H
Dealing with v2 hidden service descriptors, how does a tor client get
the list of HSDIR are responsible for a certain onion address so it
can contact them for descriptor of the hidden service?.
According to rend-spec.txt the list of the responsible HSDIR for a
particular hidden service changes alm
/22/13, Roger Dingledine wrote:
> On Sun, Apr 21, 2013 at 08:19:38AM -0700, Frank Young wrote:
>>I'm really confused at the moment. Aren't each successive AES
>> counter operation independent of the previous?
>
> Yes. So it would seem your bug
After circuit extension to the second Node, I realized that the OR
at the second node can decrypt my cells and successfully process my
circuit extension request to increase my circuit length to three but i
can't decrypt the response from the same OR.
At first I thought maybe I was messing
16 matches
Mail list logo
