On Wed, Jan 15, 2025 at 12:33:29PM -0300, x9p wrote:
>
> Hi,
>
> I am running a relay and other servers. Sometimes doing SSHD over Tor via a
> hidden service in a VPS in openbsd.amsterdam. In all my other setups, in other
> providers, I do not see this problem happening.
>
Hi misc,
I am running a relay and other servers. Sometimes doing SSHD over Tor
via a hidden service in a VPS in openbsd.amsterdam. In all my other
setups, in other providers, I do not see this problem happening.
Upon connecting for the first time, I do get a "banner line contains
in
Hi,
I am running a relay and other servers. Sometimes doing SSHD over Tor
via a hidden service in a VPS in openbsd.amsterdam. In all my other
setups, in other providers, I do not see this problem happening.
Upon connecting for the first time, I do get a "banner line contains
in
Original Message
Subject: Re: TOr
From:"hahahahacker2009"
Date:Fri, August 30, 2024 7:00 am
To: openbsd_fr...@mail2tor.com
--
VÃ o Th 6, 30 t
On Fri, 2024-08-30 at 04:11 -0400, openbsd_fr...@mail2tor.com wrote:
> Does OpenBSD support Tor?
Here's everything OpenBSD supports:
https://openbsd.app/
Cheers!
it does
e.g. https://community.torproject.org/relay/setup/bridge/openbsd/
On 30.08.24 10:11, openbsd_fr...@mail2tor.com wrote:
Does OpenBSD support Tor?
Does OpenBSD support Tor?
On Thu, Jun 15, 2023 at 07:17:45AM -, distantp...@danwin1210.de wrote:
>
> Thats it, "rcctl start tor" works flawlessly, "sh /etc/netstart" too, and
> "pfctl -f /etc/pf.conf" does not spit out any warnings or errors either,
Yes, at first blush by visu
>
>
> "pfctl -f /etc/pf.conf" does not spit out any warnings or errors either,
> so I first assumed it would work just as flawlessly then, but apparently
> it doesnt, because I cant ping any domain or wget any webpage, when I
>
If you add "log" rules to your pf.conf and the watch the pflog device
Hey there,
as I am completely new here, I might do something against the netiquette here
in the mailing lists, so correct me if I am wrong and I will try to adjust.
I am trying to set up a transparent Tor proxy on OpenBSD with pf(4), but I
couldnt find any helpful resources in the FAQ or the
works ok here. i installed tor-0.4.7.13 on my 7.2 home gateway, no
special setup. i have not done any fiddling with login.conf.
maybe you can set "Log debug syslog" and see what comes out?
fugu$ uname -a
OpenBSD fugu.offblast.org 7.2 GENERIC.MP#6 amd64
fugu$ grep '^[A-Z]'
bad.
I’ve just upgraded to 7.3-beta and updated the snowflake_proxy package
to version 2.5.1; here’s the updated contents of my torrc file:
$ grep '^[A-Z]' /etc/tor/torrc
Log notice syslog
RunAsDaemon 1
DataDirectory /var/tor
User _tor
UseBridges 1
ClientTransportPlugi
On 2023-03-11, Matt Wehowsky wrote:
> * Attempted to connect to the Tor network by using obfuscated bridges
> as well as by giving snowflake proxy a shot—nothing has changed
It doesn't help your problem with obfs4proxy but snowflake_proxy is for
providing access to other
Hey @misc,
Here’s a brief rundown of what I’ve been dealing with:
* tor(1) works flawlessly on my GNU/Linux machine with the exact same
torrc configuration file, yet it fails miserably on my 64-bit
netbook (amd64) running -current branch of OpenBSD 7.2
* Raised the value of
On 5/5/2021 at 5:34 PM, "Theo Buehler" wrote:
>
>On Wed, May 05, 2021 at 08:06:09AM -0300, Matheus Coelho wrote:
>> Hello List!
>>
>> I have a tor relay server and in version 6.9 of openbsd the log
>started
>> showing this message:
>>
On Wed, May 05, 2021 at 08:06:09AM -0300, Matheus Coelho wrote:
> Hello List!
>
> I have a tor relay server and in version 6.9 of openbsd the log started
> showing this message:
>
> tor_tls_finish_handshake: Bug: For some reason, wasV2Handshake didn't get
> set. Fi
Hello List!
I have a tor relay server and in version 6.9 of openbsd the log started
showing this message:
tor_tls_finish_handshake: Bug: For some reason, wasV2Handshake didn't get
set. Fixing that. (on Tor 0.4.5.7 )
I suspect something related to libressl according to this post:
What do you have set for Log notice in /etc/tor/torrc?
I run a tor relay without problems on 6.7 and use:
Log notice syslog
On Sun, 28 Jun 2020 at 13:59, Salvatore Cuzzilla
wrote:
> the issue is temporary “solved":
>
> 03:42:36 -ksh ToTo@APU2c4 ~ $ doas cat /etc/tor/torrc
the issue is temporary “solved":
03:42:36 -ksh ToTo@APU2c4 ~ $ doas cat /etc/tor/torrc | egrep "^Log "
Log debug file /dev/null
Log info file /dev/null
Log notice file /dev/null
it’s confirmed that something is not going well with the logs handling ...
On 25 Jun 2020, a
On 2020/06/25 14:59, Salvatore Cuzzilla wrote:
>
> Unfortunately the only think i know for sure is that the /var folder is
> constantly loosing free space & When i restart tor it gets back to
> normal. I can't (I don't know how to) figure out the involved files ...
>
Unfortunately the only think i know for sure is that the /var folder is
constantly loosing free space & When i restart tor it gets back to
normal. I can't (I don't know how to) figure out the involved files ...
"du" is not really helping nor "fstat" ... I
On 2020-06-24, Salvatore Cuzzilla wrote:
> After few attempts, I can't still don't understand what's going on
> it seems that the only way to free up the /var folder is to restart the
> tor's daemon.
>
> "pkill -HUP -u _tor -U _tor -x tor" didn't
After few attempts, I can't still don't understand what's going on
it seems that the only way to free up the /var folder is to restart the
tor's daemon.
"pkill -HUP -u _tor -U _tor -x tor" didn't help ...
Other ideas?
On 23.06.2020 11:50, Salvatore Cuzzilla
Hi Gabriel,
thanks for the hint!
I actually use to "rcctl reload tor" to rotate the logs.
I now switched to "pkill -HUP -u _tor -U _tor -x tor" let's see if it's helping!
Regards,
Salvatore.
June 23, 2020 12:53 PM, "Salvatore Cuzzilla" wrote:
>
Hi Folks,
I’m running a TOR node on my [APU2c4 (SSD) + OBSD 6.7]
somehow the TOR process is polluting my /var folder until, after few days, it’s
fulfilled (~6G).
In the beginning I thought that it was related to the daemon's logs, something
misconfigured within newsyslog.conf ... it’
rlos Lopez wrote:
> Good morning,
>
> I've been seeing a lot of "bad ip cksum" error messages in my OpenBSD’s
Tor gateway, like these:
from the tcpdump manual:
IP and Protocol Checksum Offload
Some network cards support IP and/or
On 2020-03-15, Carlos Lopez wrote:
> Good morning,
>
> I've been seeing a lot of "bad ip cksum" error messages in my OpenBSD’s Tor
> gateway, like these:
from the tcpdump manual:
IP and Protocol Checksum Offload
Some network cards support IP and/or protoco
Sorry, my mistake. I have only one match rule configured as:
match in all scrub (no-df max-mss 1440 random-id)
--
Regards,
C. L. Martinez
On 15/03/2020, 13:33, "Carlos Lopez" wrote:
Good morning,
I've been seeing a lot of "bad ip cksum" error mess
Good morning,
I've been seeing a lot of "bad ip cksum" error messages in my OpenBSD’s Tor
gateway, like these:
Mar 15 12:27:03.113986 rule 2._5.1/(match) [uid 0, pid 71416] pass in on vio0:
[orig src 172.22.55.4:49964, dst 172.217.19.142:443] 172.22.55.4.49964 >
1
> Am 14.02.2018 um 02:09 schrieb Chris Cappuccio :
>
> Revert uipc_socket.c rev 1.90. Does tor work properly again?
Because of https://marc.info/?l=openbsd-ports&m=151855574502582
I tried a newer snapshot and now tor works properly again.
signature.asc
Description: Messag
Oops, actually uipc_socket2.c
Revert uipc_socket.c rev 1.90. Does tor work properly again?
Thomas Weinbrenner [m...@tweinbrenner.net] wrote:
>
>
> > Am 12.02.2018 um 00:38 schrieb Jiri B :
> >
> > Hi,
> >
> > has anybody tried to run tor inside vmm guest?
> >
> > it&#
> Am 12.02.2018 um 00:38 schrieb Jiri B :
>
> Hi,
>
> has anybody tried to run tor inside vmm guest?
>
> it's horrible slow, just doing 'tor-resolve $dnsname' takes
> sometimes ages.
Perhaps this has nothing to do with vmm.
I am not a computer expert,
On Mon, Feb 12, 2018 at 12:38:00AM -0800, Mike Larkin wrote:
> > > > it's horrible slow, just doing 'tor-resolve $dnsname' takes
> > > > sometimes ages.
> > > > [...]
> [...]
>
> What did the guest pick for timecounter? (sysctl kern.tim
On Mon, Feb 12, 2018 at 03:07:31AM -0500, Jiri B wrote:
> On Sun, Feb 11, 2018 at 04:47:02PM -0800, Mike Larkin wrote:
> > > has anybody tried to run tor inside vmm guest?
> > >
> > > it's horrible slow, just doing 'tor-resolve $dnsname' takes
> >
On Sun, Feb 11, 2018 at 04:47:02PM -0800, Mike Larkin wrote:
> > has anybody tried to run tor inside vmm guest?
> >
> > it's horrible slow, just doing 'tor-resolve $dnsname' takes
> > sometimes ages.
> > [...]
> > is it related to vmm ssl issu
On Sun, Feb 11, 2018 at 06:38:49PM -0500, Jiri B wrote:
> Hi,
>
> has anybody tried to run tor inside vmm guest?
>
> it's horrible slow, just doing 'tor-resolve $dnsname' takes
> sometimes ages.
>
> # dmesg | head -n 4
> OpenBSD 6.2-current (GE
Hi,
has anybody tried to run tor inside vmm guest?
it's horrible slow, just doing 'tor-resolve $dnsname' takes
sometimes ages.
# dmesg | head -n 4
OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 10 00:05:49 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENE
only ~358 are OpenBSD) so thank you for running one!
I would also recommend that you subscribe to the tor-relays mailing list.
Tor opens a lot of network sockets. It is helpful to raise kern.maxfiles
in /etc/sysctl.conf. I add kern.maxfiles=2
On Sun, Jun 25, 2017 at 11:43 AM, Ax0n wrote:
> does pkg_add tor
> does rcctl enable tor
> does rcctl start tor
>
> Welcome to your new onion relay node. It
does pkg_add tor
does rcctl enable tor
does rcctl start tor
Welcome to your new onion relay node. It will relay and it will also listen
on port 9050 as a socks proxy for local applications.
On Jun 25, 2017 10:41, "nicehat" wrote:
> I'm looking for some good links on setting u
Sorry, link here
https://unix.stackexchange.com/questions/327804/how-to-create-a-darknet-tor-web-site-in-linux/327805
On 25 June 2017 at 17:33, Rui Ribeiro wrote:
> While not answering your question, this related post and links should be
> useful, I hope.
>
> Regards
>
> On
While not answering your question, this related post and links should be
useful, I hope.
Regards
On 25 June 2017 at 16:39, nicehat wrote:
> I'm looking for some good links on setting up a OBSD based Tor relay.
> I had a few good ones but they have since gone into hiding.
> An
On Sun, Jun 25, 2017 at 5:39 PM, nicehat wrote:
> I'm looking for some good links on setting up a OBSD based Tor relay.
> I had a few good ones but they have since gone into hiding.
> Anyone with some experience/tips would be helpful
> Regards
> Happy Camper
https://torbsd
I'm looking for some good links on setting up a OBSD based Tor relay.
I had a few good ones but they have since gone into hiding.
Anyone with some experience/tips would be helpful
Regards
Happy Camper
Sent with [ProtonMail](https://protonmail.com) Secure Email.
On Sun, Jan 8, 2017 at 7:02 AM, Sebastien Marie wrote:
> On Sun, Jan 08, 2017 at 03:26:01PM +1100, Joel Sing wrote:
> > On Saturday 07 January 2017 21:14:29 Olivier Antoine wrote:
> > > Hi all,
> > >
> > > Is it only me or Tor no longer works on -current ?
&
On Sun, Jan 08, 2017 at 03:26:01PM +1100, Joel Sing wrote:
> On Saturday 07 January 2017 21:14:29 Olivier Antoine wrote:
> > Hi all,
> >
> > Is it only me or Tor no longer works on -current ?
>
> I believe this should already be rectified in -current (via a parti
On Saturday 07 January 2017 21:14:29 Olivier Antoine wrote:
> Hi all,
>
> Is it only me or Tor no longer works on -current ?
I believe this should already be rectified in -current (via a partial
reversion
of src/lib/libcrypto/x509/x509_vfy.c r1.54). Thanks for the report.
> E
Hi all,
Is it only me or Tor no longer works on -current ?
Every port or compiled version of stable or unstable branch of Tor on a
fresh OpenBSD snapshot fail at the same bootstrap stageâ¦
Don't know since when exactly, but the last snapshot working for me was :
OpenBSD 6.0-current (GENER
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://trac.torproject.org/projects/tor/ticket/16651
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJVski/AAoJEFv7XvVCELh0BkkQALoK6yMEqEAqF8VKpESTxDop
joWwFTaylYakHGF3HqILE4/P7T6uqZIz+8xCnNwM0p1LRPMpL/AVvh4/tRa4L/z2
On Thu, Jul 23, 2015 at 05:40:54PM +0200, nusenu wrote:
> as we have learned from Nicholas, OpenBSD will stay with libevent
> 1.4.x for the time being.
>
> Do you have any plans to make the Tor port use libevent 2.x from
> ports?
>
> Background: Tor on OpenBSD usi
Hi Pascal,
as we have learned from Nicholas, OpenBSD will stay with libevent
1.4.x for the time being.
Do you have any plans to make the Tor port use libevent 2.x from ports?
Background:
Tor on OpenBSD using libevent 1.4.15 is significantly "slower" (less
throughput) compared to other
> Since theo@ said I could, I think I'll continue to use my 32-bit-only
> x86 CPUs until a compelling reason arises to replace them.
As long as the cpu shows NXE in dmesg.
On 2015-07-15 15:05, Theo de Raadt wrote:
PIE and ASLR other security features are either turned off on i386, in
compatibility modes, or are dialled down versions. It's not just about
a small speed difference, there are big security differences between
the architectures.
That is false.
OpenBS
> PIE and ASLR other security features are either turned off on i386, in
> compatibility modes, or are dialled down versions. It's not just about
> a small speed difference, there are big security differences between
> the architectures.
That is false.
> OpenBSD adds most of the security feature
On Wed, 15 Jul 2015 14:20:06 -0400
Josh Grosse wrote:
> On 2015-07-15 11:52, Chris Cappuccio replied to Michael McConville.
> First, a quick reply to Michael:
>
> > Michael McConville [mmcco...@sccs.swarthmore.edu] wrote:
> >>
> >> Someone correct me if I'm wrong, but it seems that the days of
On 2015-07-15 11:52, Chris Cappuccio replied to Michael McConville.
First, a quick reply to Michael:
Michael McConville [mmcco...@sccs.swarthmore.edu] wrote:
Someone correct me if I'm wrong, but it seems that the days of i386
images being reasonable to run on amd64 hardware are coming to an en
Michael McConville [mmcco...@sccs.swarthmore.edu] wrote:
>
> Someone correct me if I'm wrong, but it seems that the days of i386
> images being reasonable to run on amd64 hardware are coming to an end.
> i386 support appears to be a fading priority for most projects and the
> subset of amd64 featu
On 2015-07-15, Peter Hessler wrote:
> On 2015 Jul 15 (Wed) at 05:27:37 +0200 (+0200), L.R. D.S. wrote:
>:Not that "nice". This hardware have many fancy things like UEFI and intel
>:ME.
>:I run i386 mostly because the /amd64.html say that "it is thus safer to
>:run those machines in i386 mode"
>
>
On Wed, Jul 15, 2015 at 05:36:30AM +0200, Peter Hessler wrote:
> On 2015 Jul 15 (Wed) at 05:27:37 +0200 (+0200), L.R. D.S. wrote:
> > Not that "nice". This hardware have many fancy things like UEFI and
> > intel ME.
>
> > I run i386 mostly because the /amd64.html say that "it is thus safer
> > to
On 2015 Jul 15 (Wed) at 05:27:37 +0200 (+0200), L.R. D.S. wrote:
:Not that "nice". This hardware have many fancy things like UEFI and intel
:ME.
:I run i386 mostly because the /amd64.html say that "it is thus safer to
:run those machines in i386 mode"
That is an incredibly ancient comment, and is
Nevermind, the system time was wrong to tor could not use tls correctly.
> You changed your PKG_PATH or pkg.conf to that URL and ran 'sudo pkg_add
> -u', right?
Yes, of course. I just wanted to state that I downloaded the package from
the mother-server, not a mirror.
&
On Wed, Jul 15, 2015 at 02:28:38AM +0200, L.R. D.S. wrote:
> The package is from
> http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/
>
> [...]
>
> OpenBSD 5.8-beta (GENERIC.MP) #1024: Tue Jul 14 00:44:38 MDT 2015
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
On Wed, Jul 15, 2015 at 02:28:38AM +0200, L.R. D.S. wrote:
> I did the update of a box today, from 5.7 to 5.8 snapshot. Everything
> is working fine, except the tor package. On 5.7 it work normally,
> without any additional configurations, but in 5.8 it cannot complete
> connections.
I did the update of a box today, from 5.7 to 5.8 snapshot. Everything is
working fine, except
the tor package. On 5.7 it work normally, without any additional
configurations, but in 5.8 it
cannot complete connections. I watched my interface (re0) with tcpdump when
trying a connection
and the
p the default state limit, very far
even on anything semi-modern. the default limit of 10k states is good
for workstations and the like or tiny embedded-style deployments. I've
gone up to 2M, things get a bit slow if your state table really is
that big but everything keeps working.
>
teor writes:
> Tor 0.2.6.2-alpha (just in the process of being released) has some
> changes to queuing behaviour using the KIST algorithm.
>
> The KIST algorithm keeps the queues inside tor, and makes
> prioritisation decisions from there, rather than writing as much as
> poss
On 2015-01-01, Miod Vallat wrote:
>> > I should have also specified that I didn't just go ahead and enable them
>> > because I wasn't sure if they're considered safe. I like abiding by
>> > OpenBSD's crypto best practices when possible.
>> >
>> > Is there any reason why they're disabled by defaul
I've tuned PF parameters in the past, but it doesn't seem to be the
issue. My current pfctl and netstat -m outputs suggest that there are
more than enough available resources and no reported failures.
I remember someone on tor-...@list.nycbug.org suggesting that it could
be at least par
On 2014-12-31 11:21, Libertas wrote:
For those not familiar, a Tor relay will eventually have an open TCP
connection for each of the other >6,000 active relays, and (if it allows
exit traffic) must make outside TCP connections for the user's requests,
so it's pretty file-hung
> > I should have also specified that I didn't just go ahead and enable them
> > because I wasn't sure if they're considered safe. I like abiding by
> > OpenBSD's crypto best practices when possible.
> >
> > Is there any reason why they're disabled by default?
>
> Compiler bugs generate incorrect
Libertas writes:
> Some of the people at tor-...@lists.nycbug.org and I are trying to
> figure out why Tor relays under-perform when running on OpenBSD. Many
> such relays aren't even close to being network-bound,
> file-descriptor-bound, memory-bound, or CPU-bound, but relay
On Wed, Dec 31, 2014 at 19:42, Libertas wrote:
> Thanks for this!
>
> I should have also specified that I didn't just go ahead and enable them
> because I wasn't sure if they're considered safe. I like abiding by
> OpenBSD's crypto best practices when possible.
>
> Is there any reason why they're
On 1 Jan 2015, at 07:39 , Greg Troxel wrote:
> Libertas writes:
>
>> Some of the people at tor-...@lists.nycbug.org and I are trying to
>> figure out why Tor relays under-perform when running on OpenBSD. Many
>> such relays aren't even close to being network-bo
her note, I was skeptical about this being the cause because even
OpenBSD Tor relays using only <=12% of their CPU capacity have the
characteristic underperformance. Unless there's a latency issue caused
by this, I feel like it's probably something else.
On another note, I'm looking in
On Thu, 1 Jan 2015, at 11:49 AM, Libertas wrote:
> I also completely forgot to mention the below warning, which Tor
> 0.2.5.10 (the current release) gives when run on OpenBSD 5.6-stable
> amd64:
>
> > We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later,
> &g
I also completely forgot to mention the below warning, which Tor
0.2.5.10 (the current release) gives when run on OpenBSD 5.6-stable amd64:
> We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later,
> but with a version of OpenSSL that apparently lacks accelerated
> support for
21, 2014 at 12:30:57PM -0500, Libertas wrote:
>> Hmm, have you been keeping an eye on your logs? I eventually got a
>> warning telling me that Tor had to stop opening connections because it
>> couldn't open any more files. Regardless, Tor frequently opens thousands
>>
returned >12,500. If
> anyone else reading this has an active Tor relay running OpenBSD with
> unaltered file limits, I'd appreciate it if you could run the same
> command and let us know what you get. Running 'sudo lsof -u _tor | wc
> -l' would also be useful, as it
It shouldn't be an issue with clients IIRC, as they only maintain a few
circuits.
I just ran 'sudo lsof | wc -l' on a Linux guard relay that moves a
little less than 1 MB/s (not much traffic), and it returned >12,500. If
anyone else reading this has an active Tor relay ru
On Fri, Nov 21, 2014 at 12:30:57PM -0500, Libertas wrote:
> Hmm, have you been keeping an eye on your logs? I eventually got a
> warning telling me that Tor had to stop opening connections because it
> couldn't open any more files. Regardless, Tor frequently opens thousands
> of
On Fri, Nov 21, 2014 at 12:30:57PM -0500, Libertas wrote:
> Hmm, have you been keeping an eye on your logs? I eventually got a
> warning telling me that Tor had to stop opening connections because it
> couldn't open any more files. Regardless, Tor frequently opens thousands
> of
Hmm, have you been keeping an eye on your logs? I eventually got a
warning telling me that Tor had to stop opening connections because it
couldn't open any more files. Regardless, Tor frequently opens thousands
of files, while the default hard limit for OpenBSD users is 512-1024
files. My
On Fri, Nov 21, 2014 at 05:51:52PM +0100, Stefan Sperling wrote:
> In which configuration does tor need to open many files?
> I've been running a tor relay on OpenBSD for more than a year without
> any adjustments to ulimits and didn't notice any problems.
I can second this.
On Fri, Nov 21, 2014 at 11:28:56AM -0500, Libertas wrote:
> Can anyone do me a favor and let me know whether this short guide, along
> with the correction described in the comments, is correct?
>
> https://trac.torproject.org/projects/tor/ticket/13702
In which configuration does tor
Can anyone do me a favor and let me know whether this short guide, along
with the correction described in the comments, is correct?
https://trac.torproject.org/projects/tor/ticket/13702
wrote:
>>
>> > Could you try a connection without the control port?
>>
>> I'm afraid that's mandatory.
>
>Can you test with firefox or another browser to make sure it's a
>tor/polipo problem?
>
>>
>> Do I even need Polipo, can'
># proxyAddress = "0.0.0.0"# IPv4 only
>
>
>If you use one machine for everything, you should point your
>browser proxy
>config at 127.0.0.1:8123
Hi,
I'm still getting connection refused when trying to connect:
./m
On Wed, Oct 22, 2014 at 5:12 PM, wrote:
> Hi,
>
> Does anyone know what's wrong with my Tor + Polipo setup? So far I've done
> `pkg_add tor && pkg_add polipo`, uncommented `socksParentProxy` and
> `socksProxyType` in `/etc/polipo/config` and then `/etc/rc.d
Hi,
Does anyone know what's wrong with my Tor + Polipo setup? So far I've done
`pkg_add tor && pkg_add polipo`, uncommented `socksParentProxy` and
`socksProxyType` in `/etc/polipo/config` and then `/etc/rc.d/tor start &&
/etc/rc.d/polipo start`. However I'm still
> systems it works fine through torsocks. And the
> user and group _tor are made for the purpose.
>
> If I asked something pretty obvious, I'd like to
> learn links for up to date articles.
You can update tor to the last version from ports. The package is not
available yet.
I see no recent posts on the subject. Repository
about 2 weeks ago shows a version 0.2.4.22p0. At
the moment I cannot find manual for openbsd, on the
net.
What is prefered way to use it right now? On other
systems it works fine through torsocks. And the
user and group _tor are made for the purpose
On Sat, Jan 26, 2013 at 05:03:28PM -0500, Jiri B wrote:
> On Sat, Jan 26, 2013 at 02:11:06PM +0100, Sébastien Marie wrote:
> > Hi,
> >
> > I would like to have some help for perform a network isolation using
> > rtable, to use tor without network leak.
> &
On Sat, Jan 26, 2013 at 02:11:06PM +0100, Sébastien Marie wrote:
> Hi,
>
> I would like to have some help for perform a network isolation using rtable,
> to use tor without network leak.
> I use -current. The host is a workstation (no forwarding set in sysctl).
I just run a progr
Hi,
I would like to have some help for perform a network isolation using rtable, to
use tor without network leak.
I use -current. The host is a workstation (no forwarding set in sysctl).
The purpose is to have dedicate rtable where "program that should use tor" live
(route -T 1 exec
On Sun, 3 Jan 2010 08:15:55 + Josh Rickmar
wrote:
> On Sun, Jan 03, 2010 at 12:31:55AM -0800, J.C. Roberts wrote:
> > > Long
> > > time ago I did try development versions of NetBSD and FreeBSD
> > > because I needed support for hardware that -stable didn't have,
> > > and they were quite shak
On Sun, Jan 03, 2010 at 12:31:55AM -0800, J.C. Roberts wrote:
> > Long
> > time ago I did try development versions of NetBSD and FreeBSD because
> > I needed support for hardware that -stable didn't have, and they were
> > quite shaky. Or do you guys just want more people to use -current for
> > th
On 2010-01-02, nixlists wrote:
> If I upgrade to -current, don't I risk stability and security issues;
"stable" mostly refers to API changes; neither -current nor
-stable should be particularly unreliable (and security should
be the same or better in -current).
On Sat, 2 Jan 2010 18:45:00 -0500 nixlists wrote:
> If I upgrade to -current, don't I risk stability and security issues;
> or are the chances of that are very low as far as this OS goes?
(sigh)
If you run *any* software, you are running the risk of stability
and security issues! --It's just a
I can compare OpenBSD to dev versions of OpenSolaris, DragonflyBSD,
NetBSD or some stable Linux distro and I must say that OpenBSD is more
stable and useful in its current version then any other OS in its
stable version. Read this http://www.openbsd.org/faq/faq5.html#Flavors
and especially this par
1 - 100 of 128 matches
Mail list logo
