If your concern is security you shouldn't use OpenSSL in the first place.
My pick would be OpenBSD or Gentoo with LibreSSL if it's security wise.
Stable is for servers great because bleeding edge might break once in awhile
and for decent amount of uptime you want to keep it going without to worry
There is also https://dataclub.biz <-- exit + bitcoin payment NL/SW/LV servers
On July 28, 2016 3:41:04 PM GMT+02:00, tor relay wrote:
>
>> On July 28, 2016 at 2:48 PM Markus Koch
>wrote:
>>
>>
>> exit allowed?
>
>no, that is why I put "non-exit" in the subject of my email.
>
>https://trac.to
91 at the moment and they will soon gain more flags.
https://sourceforge.net/p/nepenthes/wiki/Home/
Seems like some sort of honeypot.
Most seem to be from AWS & Linode & Leaseweb USA.
On July 3, 2016 10:59:00 AM GMT+02:00, nusenu wrote:
>some new ones:
>http://article.gmane.org/gmane.network.onio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Abuse will always be there, and isn't bound by Tor exits only.
There is lots of this "malicious" traffic on the internet.
Mainly new/small ISPs will react heavily to abuse complaints because they don't
wanna end up on certain lists (IP ranges, bad n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
I have a couple relays / exits running.
Now my question is : how do you manage them is there any dashboard or CLI tools
to manage them ( statistics, ect.. )
I know the cli tool specially for Tor "arm"
Thanks alot.
- --
PGP : 29A4CE52
-BE
Maybe botnet ?
On May 7, 2016 2:46:31 PM GMT+02:00, Tristan wrote:
>Strange that some of the relays are running on Digital Ocean. Running a
>Tor
>relay of any kind is against their AUP.
>On May 7, 2016 2:32 AM, "nusenu" wrote:
>
>>
>>
>>
>https://gist.githubusercontent.com/nusenu/0c8ec0852a07b41
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Did you ask them what they say about Tor exit nodes?
It's common that they don't want Exit nodes on their VPS services.
Should always ask ISPs beforehand and how they deal with abuse complains.
On May 1, 2016 6:12:29 PM GMT+02:00, Markus Koch
wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On April 8, 2016 7:13:17 PM GMT+02:00, ng0 wrote:
>Tristan writes:
>
>> I think https://compass.torproject.org has all the info I need. After
>> grouping by AS name for the United States, I decided to go with
>Hostwinds.
>> They say 100Mbps unmet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Suddenly my relay lost all it's flags plus weird bandwidth drops while the
network is fully intact.
Tor version 0.2.7.6 - Ubuntu server 14.04
- --
PGP : 29A4CE52
-BEGIN PGP SIGNATURE-
iQI4BAEBCgAiGxxEbyA8eWFuZGVyZXNvbkByaXNldXAubmV0PgUCVvaC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
This happend before with my 512MB node, when it was set unlimited amount of
Mbit/sec.
Also swap might help.
On February 26, 2016 12:19:44 AM GMT+01:00, Stephen R Guglielmo
wrote:
>Hello,
>
>I have a VPS with 512 MB RAM. I run nothing on it except
As far as i know anything using glibc is affected, it says on the blog
ssh,curl,sudo for examples.
On February 17, 2016 6:06:50 PM GMT+01:00, starlight.201...@binnacle.cx wrote:
>Could someone with a solid understanding of how the Tor daemon
>interacts with DNS comment on whether and how CVE-2015
11 matches
Mail list logo