[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-dev] tor-dev Digest, Vol 97, Issue 19
Attn: Iain Learmonth <irl@xxxxxxxxxxxxxx>
Thank you for your thoughtful response. Perhaps this was the wrong mailing list in some ways.
Backing up on Iain's email conversation, I have always built my desktop computers from scratch. Salvaged hardware and researched drivers, etc. There is nothing pre-installed. (My colleagues affectionately call me the Queen of Setup and Config.") By design. I have an OEM version of XP that I put on initially, but that is only the start. Since xp is not locked down like Windows 7 and beyond, I then reconfigure so much! You would be right in assuming that a standard xp install is a security risk. But I am constantly tracing packets, studying the traffic at the back end to see where the leaks are. Then I figure out what I can do to plug / understand the leaks. Partly therefore, xp is a learning / testing tool.
I use xp for basic apps. But I would sooner drink lye than use Windows 7 and beyond. Therefore, as you already suggested, I did have a dual boot with a Parrot distribution. That is, until my sata drive died. Upon purchase, I will return to the dual boot or to two machines. So therefore, I am back to xp for the time being. Until such time as I have the dual/two machine option again, I surely would like to be able to update as much of Tor as I can. (I know that you are serving the masses and not an individual person).
Anyhow, I love Tor and I love having kindred spirits that 'get' security. Thank you for what you are doing.
~Emily
On Tue, Feb 19, 2019, at 12:00 PM, tor-dev-request@xxxxxxxxxxxxxxxxxxxx wrote:
> Send tor-dev mailing list submissions to
> tor-dev@xxxxxxxxxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> or, via email, send a message with subject or body 'help' to
> tor-dev-request@xxxxxxxxxxxxxxxxxxxx
>
> You can reach the person managing the list at
> tor-dev-owner@xxxxxxxxxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of tor-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: xp + T (Iain Learmonth)
> 2. Sending multiple streams throuh a single Tor circuit
> (Piyush Kumar Sharma)
> 3. Re: Sending multiple streams throuh a single Tor circuit (meejah)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 18 Feb 2019 14:32:11 +0000
> From: Iain Learmonth <irl@xxxxxxxxxxxxxx>
> To: tor-dev@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-dev] xp + T
> Message-ID: <4b405fbe-6130-ef98-1a8d-74bcacc8bc5f@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> On 13/02/2019 16:56, neel@xxxxxxxxx wrote:
> > I don't think this is the right mailing list.
>
> This is entirely the correct mailing list as it is discussing a
> technical policy of the network team. This policy can be found here:
>
> https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/SupportedPlatforms
>
> > You probably shouldn't be using Windows XP, otherwise the EOL'd OS would
> > be a weak point in security. One option could be to dual-boot Windows XP
> > and Linux/*BSD, using Linux/*BSD for Tor and browsing, and XP for
> > applications that haven't been ported.
>
> It is worth remembering that most people do not have the privileges to
> install software on the computers that they use.
>
> Unfortunately, the current policy of the network team is that they will
> not even accept patches for Windows XP support and will merge changes
> that break Windows XP support.
>
> I would be interested in statistics that show the current Windows XP
> user base, especially in countries with users that can most benefit from
> Tor. The policy has been drawn up primarily on technical considerations
> but if it is shown that this has negative impacts for large numbers of
> users then it may be reconsidered.
>
> Thanks,
> Iain.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: OpenPGP digital signature
> URL:
> <http://lists.torproject.org/pipermail/tor-dev/attachments/20190218/a07b928c/attachment-0001.sig>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 18 Feb 2019 23:33:32 +0530
> From: Piyush Kumar Sharma <piyushs@xxxxxxxxxxx>
> To: tor-dev@xxxxxxxxxxxxxxxxxxxx
> Subject: [tor-dev] Sending multiple streams throuh a single Tor
> circuit
> Message-ID:
> <CAGkdf3fgFbqWYuLt-uEMT_XvaLoxkJbqCPYiosnY8Mw5teECyA@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> Hello all,
>
> I am a PhD student, and am working on some measurements in Tor.
> I am stuck at a point where i need to send multiple applications(streams)
> traffic through a single circuit.
> I am currently using torsocks/torify to send traffic of these multiple
> applications through Tor.
> The main problem is that, despite trying many different ways to achieve the
> same (sending multiple streams through a single circuit), i am not
> successful.
>
> Things i have tried :
> 1.) Force Tor process to create only a single circuit at a time preventing
> any new circuit creation, so that any new stream would be attached to this
> only available circuit. To acheive this i have set the following Tor
> options :
> set __DisablePredictedCircuits to 1
> set MaxClientCircuitsPending to 1
> set newcircuitperiod to 999999999
> set maxcircuitdirtiness to 999999999
> The problem with the above method is that it seems to work sometimes
> randomly. But most of the times for some reason, a new circuit is still
> created.
>
> 2.) Next, i assumed that maybe running torify multiple times for each
> application is the culprit, as it may try to create new circuit for each
> run. So i created a new bidirectional stream using socat, which listens on
> a local TCP port, and forwards the data to the Tor SOCKS port assuming that
> it will lead to a singe connection to local SOCKS.
> Even this did not work and still new circuits were created randomly.
>
> 3.) Next i tried to attach streams to circuits manually, using the stem
> library following the link :
> https://stem.torproject.org/tutorials/to_russia_with_love.html#custom-path-selection
> . This seemed to work initially, but then after every 4-5 runs, the
> streams
> seemed to detach automatically. Moreover, the original circuit crashed
> too.
>
> It would be great, if someone could tell a simple way to achieve the same,
> or would point me to any mistakes that can be improved in the above
> methodologies to make them work.
>
> Regards
>
> Piyush
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <http://lists.torproject.org/pipermail/tor-dev/attachments/20190218/6a263872/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 18 Feb 2019 22:08:25 +0400
> From: meejah <meejah@xxxxxxxxx>
> To: tor-dev@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-dev] Sending multiple streams throuh a single Tor
> circuit
> Message-ID: <86va1h0y1y.fsf@xxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
>
>
> You could give the command-line tool "carml" a try. See here:
>
> https://carml.readthedocs.io/en/latest/
>
> You'll want to use something like "carml circ *,*,*" to build a 3-hop
> circuit through Tor-chosen relays (or replace any of the *'s with a
> fingerprint) and then "carml stream --attach <circ-number>" to attach
> streams.
>
> --
> meejah
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> tor-dev mailing list
> tor-dev@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
>
>
> ------------------------------
>
> End of tor-dev Digest, Vol 97, Issue 19
> ***************************************
>
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev