[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-relays] Hiding or masking running tor process..
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Yeah k0nsel you got me..
My provider always locks my vps cause I supposed to breach there SLAs running Tor!
I tried to explain but they suddenly after years refer to some SLA paragraphs that I disagree with...I terminated my agreement but they won't leave me out before 09/2016 so I always start Tor after unlocking system until locking..looping processð
Regards
Am 15. April 2016 10:07:42 MESZ, schrieb tor-relays-request@xxxxxxxxxxxxxxxxxxxx:
>Send tor-relays mailing list submissions to
> tor-relays@xxxxxxxxxxxxxxxxxxxx
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>or, via email, send a message with subject or body 'help' to
> tor-relays-request@xxxxxxxxxxxxxxxxxxxx
>
>You can reach the person managing the list at
> tor-relays-owner@xxxxxxxxxxxxxxxxxxxx
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of tor-relays digest..."
>
>
>Today's Topics:
>
> 1. Using your own Relay as Entry Node (fr33d0m4all)
> 2. Re: Using your own Relay as Entry Node (Yawning Angel)
> 3. Re: Using your own Relay as Entry Node (Tristan)
> 4. Re: Using your own Relay as Entry Node
> (starlight.2016q1@xxxxxxxxxxx)
> 5. Hiding or masking running tor process.. (rush23@xxxxxxx)
> 6. Re: Hiding or masking running tor process.. (dawuud)
> 7. Re: Hiding or masking running tor process.. (k0nsl)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 14 Apr 2016 21:38:15 +0000
>From: fr33d0m4all <fr33d0m4all@xxxxxxxxxx>
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: [tor-relays] Using your own Relay as Entry Node
>Message-ID: <57100DC7.9080905@xxxxxxxxxx>
>Content-Type: text/plain; charset=utf-8
>
>Hi,
>I've seen some time ago a discussion about using your own Tor Relay as
>an Entry Node, but I'd like to have your opinion in the following two
>scenarios (if it makes any difference switching from 1 to 2):
>
>1) You point at your node when you're in the same network where the
>node
>resides (I mean always by setting EntryNodes in torrc, not by using it
>as a SOCKS proxy)
>
>2) You point at your node from a different network than the one in
>which
>the relay is
>
>I think that if your node is being used by others, you would simply be
>one of the lots of users passing through it, with the advantage of
>removing the risk of a bad Entry node, what do you think about that?
>
>And about using it as a SOCKS proxy to enter the Tor network? Do the
>same considerations apply or is it even worse to use a relay as a SOCKS
>proxy?
>
>I'm sure that I've read about reasons to avoid using your own node, but
>I don't remember the considerations about this argument...
>
>Best regards,
> Fr33d0m4All
>
>--
>
>_____________________________________________________________
>
> PGP Key: 0DA8 7293 D561 3AEE A3C0 7F63 101F 316A F30E ECB4
> IRC Nick: fr33d0m4all (OFTC & Freenode)
>_____________________________________________________________
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 14 Apr 2016 22:24:30 +0000
>From: Yawning Angel <yawning@xxxxxxxxxxxxxxx>
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: Re: [tor-relays] Using your own Relay as Entry Node
>Message-ID: <20160414222430.78b9255e@xxxxxxxxxxxxxxx>
>Content-Type: text/plain; charset="us-ascii"
>
>On Thu, 14 Apr 2016 21:38:15 +0000
>fr33d0m4all <fr33d0m4all@xxxxxxxxxx> wrote:
>> And about using it as a SOCKS proxy to enter the Tor network? Do the
>> same considerations apply or is it even worse to use a relay as a
>> SOCKS proxy?
>
>This is horrible and should *NEVER* be done, assuming any network not
>physically controlled by you is between you and the SOCKS proxy
>server[0], simply based on the request (and authentication if you
>chose to use such things) being in the clear.
>
>Regards,
>
>--
>Yawning Angel
>
>[0]: So, SOCKS over an internal network to a VM/magical anonymity box
>may be ok (depending on your threat model). SOCKS to a VPS somewhere
>is essentially always a bad idea.
>-------------- next part --------------
>A non-text attachment was scrubbed...
>Name: not available
>Type: application/pgp-signature
>Size: 819 bytes
>Desc: OpenPGP digital signature
>URL:
><http://lists.torproject.org/pipermail/tor-relays/attachments/20160414/20b5b36b/attachment-0001.sig>
>
>------------------------------
>
>Message: 3
>Date: Thu, 14 Apr 2016 17:31:13 -0500
>From: Tristan <supersluether@xxxxxxxxx>
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: Re: [tor-relays] Using your own Relay as Entry Node
>Message-ID:
> <CAKkV4FFxzEDuXoXeyFOpaYj-krUMWWrzOOg6_oJxUFMNFcpLMg@xxxxxxxxxxxxxx>
>Content-Type: text/plain; charset="utf-8"
>
>Using a relay as a SOCKS proxy is fine for the local network, just
>don't
>open it to the outside world.
>
>Using your relay as an entry uses it as part of the circuit.
>
>Using your relay as a local proxy creates a new circuit (without using
>your
>node in the circuit)
>On Apr 14, 2016 5:26 PM, "Yawning Angel" <yawning@xxxxxxxxxxxxxxx>
>wrote:
>
>> On Thu, 14 Apr 2016 21:38:15 +0000
>> fr33d0m4all <fr33d0m4all@xxxxxxxxxx> wrote:
>> > And about using it as a SOCKS proxy to enter the Tor network? Do
>the
>> > same considerations apply or is it even worse to use a relay as a
>> > SOCKS proxy?
>>
>> This is horrible and should *NEVER* be done, assuming any network not
>> physically controlled by you is between you and the SOCKS proxy
>> server[0], simply based on the request (and authentication if you
>> chose to use such things) being in the clear.
>>
>> Regards,
>>
>> --
>> Yawning Angel
>>
>> [0]: So, SOCKS over an internal network to a VM/magical anonymity box
>> may be ok (depending on your threat model). SOCKS to a VPS somewhere
>> is essentially always a bad idea.
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://lists.torproject.org/pipermail/tor-relays/attachments/20160414/85cea375/attachment-0001.html>
>
>------------------------------
>
>Message: 4
>Date: Thu, 14 Apr 2016 21:39:44 -0400
>From: starlight.2016q1@xxxxxxxxxxx
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: Re: [tor-relays] Using your own Relay as Entry Node
>Message-ID: <6.2.5.6.2.20160414213758.04b31638@xxxxxxxxxxx>
>Content-Type: text/plain; charset="us-ascii"
>
>You may find the information in this ticket
>of interest, particularly the cited comment:
>
>https://trac.torproject.org/projects/tor/ticket/16824#comment:23
>
>
>
>------------------------------
>
>Message: 5
>Date: Fri, 15 Apr 2016 07:48:25 +0200
>From: rush23@xxxxxxx
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: [tor-relays] Hiding or masking running tor process..
>Message-ID: <5D345D5E-316B-4BD9-8B3C-76C50DE7E46E@xxxxxxx>
>Content-Type: text/plain; charset=UTF-8
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>Hey everybody,
>
>is there any way to hide running a tor process on a server??
>My vps hoster monitors which processes consume most of the resources,
>so just hiding would be best especially when it looks like a 'not tor'
>process..?
>
>I appreciate any helpful hints...
>
>Cheers
>0x23
>- --
>-----BEGIN PGP SIGNATURE-----
>
>iQIzBAEBCgAdFhwweDIzIDxydXNoMjNAZ214Lm5ldD4FAlcQgJkACgkQOKD1ON7f
>MNhrpA/+KH3CXchdIH5ZpXsYe4rDUO2bCAo0lAtZHOogzngmqtJg22Tb9aKnSLBQ
>sLrtRLHgvGS17Ru3bzSqcSh7SE5vlKi3fFuRqB4f7aWHBreBKLCuOXOsp8YLjf2n
>f/KZxa0h9lATtjvhG8dKNUVZ7pBEX1awQPO56fkapbArqAg/dKPgggAlmcAhLgO+
>4jjPuk8B+fUlgVtRPaK3Igq4YTyRTkrQmiozM0q7A/4Jj1Sw2Bi8QBoUk1vCOR9y
>CBbrH7t/kkvts7DhmngjJX6Dc1bPCMkHAAisu+NhUXMVH6SMRrfVzJNR1sgD6BYO
>oq8J35xYQKCmppLrHRCQ/6YMqDnX27rk3z672AD8EiqZz4uynlrljsNnodmzIzbe
>eFog7KXaOjIcVH+EUpU1wAXIb0klg3mI9GfA6CYq342xPnNXVoyVqZOTdt3BlZpx
>rbF6M6ihF1YH2/RQluckCyUkxaO6sG9zPbtCY1LVLvppOHCRjNIPVxJ/pWhBbyQz
>Q4SH7VSJwS8KVtxa/yZe4sX4+h0lY/Opkg0F20Rsmf4522YCsn2rEYk5VveNj1yd
>NJ7mHqldfghp4IRROhneLX9tXz2S/hZtcibsWpnuaVC6n83yosAiErSEUbCHHmDI
>ZCFlfCO1UhvFGFiGanpLez62b1GGn/KHq0BeUzuIpHkXVK6mxRg=
>=Ovl+
>-----END PGP SIGNATURE-----
>
>
>
>------------------------------
>
>Message: 6
>Date: Fri, 15 Apr 2016 09:36:30 +0000
>From: dawuud <dawuud@xxxxxxxxxx>
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: Re: [tor-relays] Hiding or masking running tor process..
>Message-ID: <20160415093630.GA6712@xxxxxxxxxx>
>Content-Type: text/plain; charset="utf-8"
>
>
>Dear 0x23,
>
>This is a totally rediculous question... but Oh yes you can certainly
>replace top, ps etc.
>with your own customized versions that exclude the tor process. You
>have root access, yes?
>
>Why would you even want to do this? I don't understand.
>Don't you know that society praises tor relay operators for
>contributing?
>
>Sincerely,
>david
>
>On Fri, Apr 15, 2016 at 07:48:25AM +0200, rush23@xxxxxxx wrote:
>> Hey everybody,
>>
>> is there any way to hide running a tor process on a server??
>> My vps hoster monitors which processes consume most of the resources,
>so just hiding would be best especially when it looks like a 'not tor'
>process..?
>>
>> I appreciate any helpful hints...
>>
>> Cheers
>> 0x23
>> --
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>-------------- next part --------------
>A non-text attachment was scrubbed...
>Name: signature.asc
>Type: application/pgp-signature
>Size: 801 bytes
>Desc: not available
>URL:
><http://lists.torproject.org/pipermail/tor-relays/attachments/20160415/4fa155b4/attachment-0001.sig>
>
>------------------------------
>
>Message: 7
>Date: Fri, 15 Apr 2016 09:58:49 +0200
>From: k0nsl <i.am@xxxxxxxxx>
>To: tor-relays@xxxxxxxxxxxxxxxxxxxx
>Subject: Re: [tor-relays] Hiding or masking running tor process..
>Message-ID: <987970e3-3563-79db-f02f-6b2c70704fe2@xxxxxxxxx>
>Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>David,
>
>I'm assuming he wants to hide the process due to provider killing the
>tor process. There are hosts whom are using incredibly lame methods for
>
>detecting the tor process ? so simply renaming it can often bypass.
>
>At any rate, if my assumption is correct, well, I don't suggest
>engaging
>in that practice. It's better to find a host which allows one to
>operate
>tor.
>
>Best wishes,
>
>-k0nsl
>
>On 2016-04-15 11:36, dawuud wrote:
>> Dear 0x23,
>>
>> This is a totally rediculous question... but Oh yes you can certainly
>replace top, ps etc.
>> with your own customized versions that exclude the tor process. You
>have root access, yes?
>>
>> Why would you even want to do this? I don't understand.
>> Don't you know that society praises tor relay operators for
>contributing?
>>
>> Sincerely,
>> david
>>
>> On Fri, Apr 15, 2016 at 07:48:25AM +0200, rush23@xxxxxxx wrote:
>>> Hey everybody,
>>>
>>> is there any way to hide running a tor process on a server??
>>> My vps hoster monitors which processes consume most of the
>resources, so just hiding would be best especially when it looks like a
>'not tor' process..?
>>>
>>> I appreciate any helpful hints...
>>>
>>> Cheers
>>> 0x23
>>> --
>>>
>>> _______________________________________________
>>> tor-relays mailing list
>>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>>
>>>
>>> _______________________________________________
>>> tor-relays mailing list
>>> tor-relays@xxxxxxxxxxxxxxxxxxxx
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
><http://lists.torproject.org/pipermail/tor-relays/attachments/20160415/d735d94c/attachment.html>
>
>------------------------------
>
>Subject: Digest Footer
>
>_______________________________________________
>tor-relays mailing list
>tor-relays@xxxxxxxxxxxxxxxxxxxx
>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
>------------------------------
>
>End of tor-relays Digest, Vol 63, Issue 26
>******************************************
- --
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFhwweDIzIDxydXNoMjNAZ214Lm5ldD4FAlcQ1FAACgkQOKD1ON7f
MNjH3BAAnrQ8xINp0knwJdHpfozLyVcIkhw+NVpEfilRlQLQw9Q7+YjdMH8ACIYn
TvTnvtBqskkcjCZPr5bxMtc+DRWSlJK7dbzVgCRztqOX9I0VAzXQ2UZ6M99wVgat
WnkUtDr/V7eYzE3/3ZU3tx7sIZY+3dFH+NwIPid2NCh0KZqq0JS2EjrCO0LAWFkl
Gcbbq/z/znGNC2lm5li9Sozh3iq+wFGh9AvWCs6uzsxDNmOlYT4/beSRiN7IcxLV
xArVzgq9jLlnF2ICwtrR9bvB3JpNYvqRTdBB9qYutFRqvk7Rs2ElUTjLz/tzPpaX
3o3qvC4/9wMTap9wTd3hFBxngBGi5uT8itQ2Ugr1XPuh8bAjWR/km0k2nlM/2C/s
QdOa4GWHHEHI2pu16XYp13Yl7TEejyaxhLKQJquOToAd79W/i4nHU7aBr8/z1q6m
/3LNdLUymXZU8KR7cWUZPagUpMOWByvvvnr5aJbRTUuhKvLmAnJ3WWlk0kI6Wp3A
skPbpMjPLzzJ7JhVOLTnQuU56SGghPSCTXVR1z21onCmZ6z4JmUqw0EBLu7JW/bc
V9O9f7UhfhS/qrVWnWbm4boDHnnQ60MyDt+w+ESqUQmNza5xdgRR9lasNhMi5Myf
vXHbm5Oerm7f/ggzCpKgYR1wSfBj7FYgCUkXVsVdHVznga5Jjpw=
=ytFr
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays