I think a good place to start would be to use the obfsproxy python api...
but of course you could create a PT without this api.
Here the unofficial tor PT wiki page:
https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports
Here you can look at example code of various PTs. Some use th
On Wed, Jan 29, 2014 at 08:42:05PM -0600, Ox Cart wrote:
> Thanks very much David, that's exactly what I needed!
>
> The pluggable transports page on the website still points at the old 180
> proposal. Do you know whom I should ping to get that updated to point at
> pt-spec.txt?
Fixed.
(Let us
Thanks very much David, that's exactly what I needed!
The pluggable transports page on the website still points at the old 180
proposal. Do you know whom I should ping to get that updated to point at
pt-spec.txt?
Cheers,
Ox
--
That was quick! Thanks Roger.
Cheers,
Ox
-
"I love people who harness themselves, an ox to a heavy cart,
who pull like water buffalo, with massive patience,
who strain in the mud and the muck to move things
On Wed, Jan 29, 2014 at 03:24:51PM -0600, Ox Cart wrote:
> I'm interested in writing a pluggable transport for Tor. Is this spec a good
> place to start?
>
> https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt
Better than proposal 180 is pt-spec.txt, which
On Wed, Jan 29, 2014 at 11:04 AM, George Kadianakis
wrote:
> On the other hand, if we wanted to use the HSDirs, we could imagine
> the HS sending some sort of revocation message to the responsible
> HSDirs so that they stop serving descriptors with compromised
> keys. Unfortunately, this scheme tr
I'm interested in writing a pluggable transport for Tor. Is this spec a
good place to start?
https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt
Cheers,
Ox
-
"I love p
On Thu, Jan 16, 2014 at 5:15 AM, Karsten Loesing wrote:
> Hi devs,
>
> you probably know that we use MaxMind's GeoIP database in various of our
> products (list may not be exhaustive):
[...]
> How do we switch? First option is to ship their binary database files
> and include their APIs [7] in o
To achieve offline key storage in the new HS design, hidden service
are using three layers of keys:
(Skip the next three paragraphs if you know this stuff)
Each hidden service has a "long-term master identity key". This is the
key that is encoded in its onion address.
Using the long-term identit
> OpenITP & TA3M have had a python dev ask if STEM or txtorcon need
> assistance =) For more details, talk to Sandy (sandraordo...@openitp.org).
Hi Griffin. Certainly, both projects would love to have some help! If
you're interested in both Stem and Txtorcon then this might strike
your fancy...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenITP & TA3M have had a python dev ask if STEM or txtorcon need
assistance =) For more details, talk to Sandy (sandraordo...@openitp.org).
~Griffin
- Original Message
Subject: [OpenITP Dev] Do u needa Python & Javascript vol
Hi Abhiram,
cool, that sounds nice. For the time being, I just query Onionoo directly and
work on the returned data. Once your helper is ready, I'll look whether it
makes sense to integrate your work, or just port everything to Django.
@all: maybe you want to check out
https://trac.torproject.org
Hello Guys,
Here is the progress from my side.
I have written a simple python helper module for Onionoo
communication, mostly inspired by "stemUtil" module from the current
weather implementation. For now, it checks for new documents with
Onionoo and exposes the data through some simple function
On 22/01/14 09:01, Karsten Loesing wrote:
Thanks for testing this! Will deploy the metrics-db changes on yatei.
Microdescriptor tarballs are now available on the metrics website:
https://metrics.torproject.org/data.html#relaydesc
All the best,
Karsten
___
14 matches
Mail list logo
