On Tue, 22 Aug 2017 15:55:37 -0700
Ryan Carboni wrote:
> If mtor is implemented, I don't see any loss of security over Tor.
> Although many web applications are currently designed for unicast.
MTor sounds like a fascinating concept.
--
tor-talk mailing list -
Weren't people speculating that tens of thousands of tor connections were
used to deanonymize web services like Doxbin?
If mtor is implemented, I don't see any loss of security over Tor.
Although many web applications are currently designed for unicast.
--
tor-talk mailing list -
On 08/22/17 00:15, Jacki M wrote:
Tor version 0.2.3.25 is no longer supported and that last comment on the mtor project
was more than a year ago, Latest commit f50af12 on Aug 17, 2016, so it looks like the
project is no longer in development and the version of tor it is based on is
extremely
Tor version 0.2.3.25 is no longer supported and that last comment on the mtor
project was more than a year ago, Latest commit f50af12 on Aug 17, 2016, so it
looks like the project is no longer in development and the version of tor it is
based on is extremely outdated, and not secure. Currently
Here is the white paper with MTor design:
https://www.degruyter.com/downloadpdf/j/popets.2015.2016.issue-2/popets-2016-0003/popets-2016-0003.pdf
And here is an implementation based on tor-0.2.3.25:
https://github.com/multicastTor/multicastTor/tree/master/shadow/build/tor
But ChangeLog
Hello,
Today I found that it is possible to force OpenSSL enable the use of CPU AES
acceleration even if it doesn't detect the "aes" CPU flag.
Many VPS hosts configure their hypervisors in a way that does not have the
flag passed through into VPSes, even though all their host nodes surely have