Greetings!
We just released 0.3.5.18. You can find out about it here:
https://forum.torproject.net/t/release-0-3-5-18/1871
It is the last release of the 0.3.5.x series because it is reaching
end-of-life in 7 days.
Download at: https://dist.torproject.org
Inline ChangeLog:
Changes in version
Greetings,
We just released 0.4.6.9 and 0.4.7.3-alpha. You can find out about it here:
https://forum.torproject.net/t/release-0-4-6-9-and-0-4-7-3-alpha/1265
Download at: https://dist.torproject.org
Inline ChangeLog for both versions:
Changes in version 0.4.7.3-alpha - 2021-12-15
This
On 26 Oct (18:58:53), mick wrote:
> On Tue, 26 Oct 2021 11:48:54 -0400
> David Goulet allegedly wrote:
>
> > The Tor Network Team will from now on do its release announcement
> > through our new fancy shiny Discourse forum:
> > https://forum.torproject.net
>
Greetings!
The Tor Network Team will from now on do its release announcement through our
new fancy shiny Discourse forum: https://forum.torproject.net
If you are interested in getting notified for each release announcement, you
should follow this category (once you get an account):
On 22 Jan (22:31:45), Roman Mamedov wrote:
> On Fri, 22 Jan 2021 12:02:50 -0500
> Nick Mathewson wrote:
>
> > o Major bugfixes (authority, IPv6):
> > - Do not consider multiple relays in the same IPv6 /64 network to be
> > sybils. Fixes bug 40243; bugfix on 0.4.5.1-alpha.
>
> Each
On 07 Jan (15:38:46), s7r wrote:
> David Goulet wrote:
> > Tor relays supporting the HS DoS defense (intro points) at this point in
> > time
> > are not in majority. Basically >= 0.4.2.1-alpha relays do support it which
> > currently represents ~36% in b
On 19 Dec (12:38:35), brokenb...@danwin1210.me wrote:
> Hello I run a forum hidden service and a former user is constantly
> attacking it.
>
> I now have 0.4.2.5 installed and this is my torrc file the attacks still
> persist do I need to add anything else or change these numbers I thought
> this
On 12 Dec (15:09:03), drl...@danwin1210.me wrote:
Greetings,
> How do I configure my hidden service to use the latest Dos defense in tor
> 0.4.2.5.
>
> In my tor/torrc file underneath my hiddenservice info I added
>
> HiddenServiceEnableIntroDoSDefense 1
> HiddenServiceEnableIntroDoSRatePerSec
On 13 Oct (19:27:00), nusenu wrote:
> you might want to avoid using these Tor relays
Bad relay team has asked the dirauths to reject these relays from the network.
Cheers!
David
>
>
Hello everyone!
Been a long time since a torsocks release! Many fixes went into this new
version which all came from volunteers so huge thanks to you all for this
work! ChangeLog below for this version.
Please, let me know about any issues! I can't build on all systems so anyone
testing this on
On 17 Sep (15:06:11), Udo van den Heuvel wrote:
> On 15/09/2018 18:14, Udo van den Heuvel wrote:
> > I find a load of these bug mentions in the notices log.
>
> It happened again.
> Any devs reading here?
Hello Udo,
I've opened https://trac.torproject.org/projects/tor/ticket/27750 with this
On 16 Apr (14:37:00), George Kadianakis wrote:
> hi...@safe-mail.net writes:
>
> > I run both a V2 and V3 service on my Linux server. I'm using the same Tor
> > process with both. The torrc file is fairly standard, except I'm forcing
> > some custom entry nodes, and I compile Tor from source on
On 10 Feb (23:58:53), Konstantin Rybakov wrote:
> Dear developers,
>
> I am trying to develop a simple networking application based on node.js
> 'net' library. Server supposed to run in torified environment.
>
> My setup is linux Ubuntu 16.04.
On 16.04, "torsocks" package is 2.1.0 which old so
On 11 Feb (06:14:34), Lolint wrote:
> Hi
Hello!
>
> I have some questions about the coming switch to next-gen onion services:
>
> o What will happen to current onion services? Will they all be simply
> discontinued or will there be a process by which they will be automatically
> built again to
On 23 Dec (00:03:00), Ivan Markin wrote:
> David Goulet:
> > On 20 Dec (23:38:43), hi...@safe-mail.net wrote:
> >> I just think that this new single-hop system should have been reserved for
> >> a
> >> different Tor source/installation, dedicated only to
On 21 Dec (19:37:13), Aeris wrote:
> > Would anyone outside of myself and those two
> > people be able to determine the onion address
>
> Yes. Your onion address is published on a DHT, hosted accross all nodes with
> HSDir flag. Some bad behaviouring relays try to enumerate all onion addresses
On 20 Dec (23:38:43), hi...@safe-mail.net wrote:
> I just think that this new single-hop system should have been reserved for a
> different Tor source/installation, dedicated only to non-anonymous hidden
> services, not merge it with the regular Tor software. And this for security.
>
> I once
On 19 Dec (09:04:46), Allen wrote:
> AFAIK, HiddenServiceNumIntroductionPoints >= 3 is also for the benefit
> of the client, so if intro point #1 doesn't work for the client, it
> can try to connect at intro point #2, and then finally at intro point
> #3 before giving up. So let's say my Tor
On 17 Feb (22:10:44), Sebastian Hahn wrote:
> Hi blobby,
>
> > On 17 Feb 2016, at 21:17, blo...@openmailbox.org wrote:
> > Does Facebook still provide an onion link?
> >
> > Because I've tried https://www.facebookcorewwwi.onion/ and I get a
> > neverending loop in which the site loads and loads
On 10 Dec (19:04:02), nusenu wrote:
> take a look at the "e_prob" column:
>
> https://github.com/nusenu/tor-network-observations/blob/master/2015-12-10_relay-families.txt
>
>
> How did he manage to get such a high consensus weight
> (~10x ipredator's cw)?
>
>
>
> these four 0.2.7.5-dev
On 15 Jun (18:28:42), Allen wrote:
Hi Donncha,
One thing I think I'm seeing is that if I restart the tor process on a hidden
server, it chooses new introduction points and any clients that have a cached
service descriptor cannot access the hidden service until the cached
descriptor
On 28 May (14:54:55), Yuri wrote:
On 05/28/2015 06:25, David Goulet wrote:
What other pull requests are you talking about? There are a couple of
open tickets that need more time and thinking so I released this one
because of the amount of fixes that has been accumulating.
https://github.com
On 27 May (18:14:37), Yuri wrote:
On 05/27/2015 12:19, David Goulet wrote:
Hi everyone!
This is the release for version 2.1.0 of Torsocks. Special thanks to
Yawning that helped a lot with the new features, finding bugs and
providing patches! Also, thanks to all contributors and users out
On 28 May (02:38:04), Geoff Down wrote:
On Thu, May 28, 2015, at 02:29 AM, Geoff Down wrote:
On Wed, May 27, 2015, at 08:19 PM, David Goulet wrote:
Tarball:
https://people.torproject.org/~dgoulet/torsocks/torsocks-2.1.0.tar.bz2
(sig:
https://people.torproject.org
Hi everyone!
This is the release for version 2.1.0 of Torsocks. Special thanks to
Yawning that helped a lot with the new features, finding bugs and
providing patches! Also, thanks to all contributors and users out there
providing us with feedbacks! :)
Changes that are worth mentionning:
-
On 06 May (19:28:38), teor wrote:
Date: Tue, 5 May 2015 18:49:39 -0500
From: Tom Ritter t...@ritter.vg
On 5 May 2015 at 07:53, Fabian Keil freebsd-lis...@fabiankeil.de wrote:
Great.
A couple of comments (about v1.3):
Thanks! I made the changes and put up a 1.4
Page 141
On 16 Feb (00:27:40), James Murphy wrote:
On 02/15/2015 03:22 PM, blo...@openmailbox.org wrote:
I want to login to my VPS over SSH.
Is torsocks still a safe way to do this? A lot of the
documentation (such as it is) is several years old.
I would also like to know this. SSH
Hi everyone!
Following the discussion of bug #10007[1], this is the *stable* release 2.0.0
for torsocks. Nothing major went in since -rc7, see the change log below.
2014-08-11 torsocks 2.0.0
* Fix: compilation issue on Debian kfreebsd-i386
* Fix: add LICENSE file to repository
* Fix:
On 02 Jul (04:03:20), Matt Pagan wrote:
BlueStar88:
37lnq2veifl4kar7.onion:6697 is up and running fine.
When connecting with `screen torsocks irssi -c 37lnq2veifl4kar7.onion -p
6697` I get the error message:
[(status)] [Jul 01 22:33:27] WARNING torsocks[26459]: [connect]
Hi everyone!
Took me a while to do it but there it is! For those not following
torsocks development, this is a status report of the project.
As of April 4th 2014, the release candidate 7 was released. With that
release, the main code is now on torproject.org which is now the
official upstream of
Hi everyone!
This is the release candidate 7 for torsocks 2.x. Nothing major, fixes
and some code refactoring went in.
From this point on, the upstream torsocks git[1] is now updated with
that new code in the master branch but no stable release yet. With that,
my github repository will become a
Hi everyone!
Here is the release candidate 5 *and* 6 for Torsocks 2.x. Unfortunately,
right after the release 5, I've noticed a critical issue that made the
new allow inbound option misbehaved quite badly so I'm immediately
releasing rc6 containing that fix. Basically, you can ignore rc5 if you
Hi everyone!
After a big code review from Nick and help from a lot of people
contributing and testing, this is the release candidate 4 for the new
torsocks.
Hopefully this is the last stretched before pushing this effort upstream
but for that we need help with code/documentation review (again)
On 05 Nov (20:44:08), adrelanos wrote:
Lunar:
For those too lazy to build torsocks manually, I have just uploaded an
updated package to Debian experimental [1].
Given that David said he plans to discuss a new name for torsocks
soon... And also to keep compatibility with existing
On 23 Oct (06:11:59), adrelanos wrote:
Lunar:
David Goulet (2013-09-02):
After a week or so, the release candidate 2 is now out after receiving
various
contributions for BSD and OS X support.
A quick note. Please use the Github bug tracker for any issues
Greetings everyone!
After a week or so, the release candidate 2 is now out after receiving various
contributions for BSD and OS X support.
A quick note. Please use the Github bug tracker for any issues and *not*
trac.torproject.org. Until this code base is accepted as a potential replacement
for
Greetings everyone!
Two months ago I sent an email [1] to the tor-dev mailing list explaining some
important issues with torsocks. I proposed myself to do a complete rewrite for
the reasons detailed in the email.
I've released today the first release candidate for a 2.0.0 version.
I guess that could be an option useful to add to torsocks for that. As of now,
with the current version of torsocks (1.3.x), you can't.
We could add something like torsocks --only-onion ... ?
Thanks!
David
Moritz Bartl:
Hi,
Is there any way to torify applications so they can reach .onion
Hi,
I've been working on a re-engineering of torsocks recently and I would really
like to support Windows natively! However, since I'm far from a Win. developer,
some important portability issues need to be address.
On *nix system we LD_PRELOAD the program thus hijacking the necessary symbols to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
NotDashEscaped: You need GnuPG to verify this message
Just a quick note on China and IPsec.
Less than a month or so, I know and confirmed that a certain company
inside China still uses Cisco IPsec to communicate with their outside
division (EU). I
, 2012 at 12:08:27PM -0400, David Goulet wrote:
I'm looking to run a Tor exit node but IPv6 only.
Anyone do/did that and got useful information about that?
I don't know the state of the Tor network using IPv6. Is there
some statistics somewhere about the number of nodes (or
estimation) ? I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
This is a good start :)
https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs
Cheers!
David
Webmaster:
Can anyone suggest a vps provider that is friendly to tor hidden
services. This would not be for an exit node.
42 matches
Mail list logo
