[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #32105 [Circumvention/BridgeDB]: bridges@xxxxxxxxxxxxxx don't respond
#32105: bridges@xxxxxxxxxxxxxx don't respond
------------------------------------+---------------------------
Reporter: mh828 | Owner: phw
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Circumvention/BridgeDB | Version:
Severity: Normal | Resolution: fixed
Keywords: BugSmashFund | Actual Points: 0.3
Parent ID: | Points:
Reviewer: cohosh | Sponsor: Sponsor30
------------------------------------+---------------------------
Changes (by phw):
* keywords: => BugSmashFund
* status: merge_ready => closed
* resolution: => fixed
* actualpoints: => 0.3
Comment:
Replying to [comment:14 cohosh]:
> Looks good.
[[br]]
Thanks, merged.
[[br]]
> I'm not sure whether the point of this repository is to also make it so
that other people can set up their own bridgedb instance and easily
configure it to work out of the box. If so, it would be nice to factor out
some strings like `bridges.torproject.org` into variables at the top of
procmailrc so they are more easily configured.
>
> That being said, I'm sure it wouldn't work out the box as is anyway so
maybe this isn't important.
[[br]]
I think the purpose of bridgedb-admin is to keep track of administrative
scripts that we use to manage BridgeDB, e.g., systemd service files, a
logrotate config, and our apache config. It's not meant to work out-of-
the-box for third parties but it would probably be very helpful when
setting up a BridgeDB instance.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32105#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs