cked the email address.
>
> Thanks
>
> On Fri, 31 Aug 2018, 22:52 Matthew Glennon,
> wrote:
>
>> Anyone else getting nude photos and random links from Cynthia Coleman <
>> cynthiacoleman843...@ru.irzum.com> attached to this (and other thread(s)
>> lately? S
Anyone else getting nude photos and random links from Cynthia Coleman <
cynthiacoleman843...@ru.irzum.com> attached to this (and other thread(s)
lately? Spam obviously, but ugh.
Matthew Glennon
Want to make sure only I can read your message? Use PGP!
(Then paste the encrypted text into an
Could this be mitigated with a detection addon in Tor Browser? Detect that
the site may be blocked at the exit and offer to fetch a new circuit for
the site?
On Thu, Aug 30, 2018, 19:22 Nathaniel Suchy wrote:
> The exit is behind a filtered ISP. Opposed to a website blocking exits.
> That’s the
e best,
> Karsten
>
> _______
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon Request
https:/
/tor-relays
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://list
want to share
> the reason why you had a misconfigured sources.list
> file (maybe we can improve / avoid that somewhere)
>
> --
> https://twitter.com/nusenu_
> https://mastodon.social/@nusenu
>
> _______
> tor-relays mailing list
&g
t/tree/scripts/maint/fallback.whitelist
> [4]:
> https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.t
all guard and bridge relays configured like this?
>
>
>
> Maybe this should be a requirement for running a guard or bridge relay for
> this reason.
>
>
>
> What does everyone think?
>
>
>
> *From: *Matthew Glennon
> *Sent: *Friday, June 22, 2018 5:18 AM
> configure
> ORPort to be 443 or 80, to be reachable from behind messy firewalls.
>
> martin
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Thu, Jun 21, 2018 at 4:14 PM Ian Zimmerman wrote:
> On 2018-06-21 08:25, Matthew Glennon wrote:
>
> > Relays intending to act as Guards choose port 443 because it (and 80) are
> > usually reachable in the tightest of network security situations (where
> > traffic des
15 |
> | 20 | 14 |
> | 22 | 14 |
> | 143 | 14 |
> | 19001 | 13 |
> +-+--+
>
>
>
>
> --
> https://twitter.com/nusenu_
> https://mastodon.social/@nusenu
>
> _
t.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon Request
https://keybase.io/crazysane
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
That took even less time than I expected. The relay is back online and
should be in the consensus after a while.
On Mon, Jun 4, 2018 at 8:22 AM Matthew Glennon
wrote:
> When I installed my relay last year, I foolishly enabled disk encryption.
> This has caused a few automatic reboots or
torrc, but I wanted to alert the
masses in case I mess up and have to start over. The relay will be down
during the process, but it shouldn't take more than an hour or so.
https://metrics.torproject.org/rs.html#details/924B24AFA7F075D059E8EEB284CC400B33D3D036
--
Matthew Glennon
matthew@gle
1
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon Request
https:/
utbound email traffic if no TLS is used. Suggest
> to use a dedicated email address for this service.
> >
> > **Additional Ideas**
> >
> > * easy: integration into tor: show the URL pointing to the new Tor
> Weather service like the current link to the lifecycle blog
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon Request
https://keybase.io/crazysane
___
tor-rela
The Verizon Wireless network seems to be the same.
https://imgur.com/a/fw6X9ZY
On Wed, May 16, 2018 at 8:17 AM Matthew Glennon
wrote:
> My relay exhibits the same results on AS701, MCI Communications Services,
> Inc. d/b/a Verizon Business
>
> https://metrics.torproject.org/rs.
wouldn't want to go to the local cable company), I just want to
> > point out a blocked consensus server.
>
> I'm seeing the same thing from the greater Baltimore, MD area:
>
> traceroute to 86.59.21.38 (86.59.21.38), 64 hops max, 40 byte packets
> 1 172.16.3.1 (172.16.3.1) 0.172 ms 0.162
; --
> OpenPGP Key: 47BC7DE83D462E8BED18AA861224DBD299A4F5F3
> https://www.parckwart.de/pgp_key
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/li
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon Request
https://keybase.io/crazysane
_
t; https://mastodon.social/@nusenu
> twitter: @nusenu_
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Matthew Glennon
matthew@gle
Are the right people aware that Metrics has been like this for most of the
day? No matter what relay you look for it claims old data.
https://metrics.torproject.org/rs.html#details/9695DFC35FFEB861329B9F1AB04C46397020CE31
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon
t;
>
> The 'normal's above are ambiguous and conflicting.
> Replace them with 'non-exit' and 'exit'.
>
>
> Ah, actually no, replace them with "relay" and "relay".
>
> In that text, "normal relay" is as
ing
people back before (because everyone was unmeasured). Since that was
resolved but still no guard flag, I was becoming curious.
I'll just sit back and wait some more.
Matt
On Wed, Mar 21, 2018 at 1:23 PM Vasilis wrote:
> Hi Matthew,
>
> Matthew Glennon:
> > While I understan
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> Am 20. März 2018 7:38 PM schrieb Matthew Glennon :
>
> Arm just doesn't work anymore. Use nyx instead.
>
> On Tue, Mar 20, 2018 at 2:32 PM smichel0 wrote:
; SMichel
>
>
> Sent with ProtonMail <https://protonmail.com> Secure Email.
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
--
Mat
/924B24AFA7F075D059E8EEB284CC400B33D3D036
Thanks
--
Matthew Glennon
matthew@glennon.online
PGP Signing Available Upon Request
https://keybase.io/crazysane
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
, 2018 at 10:21 AM Matt Traudt wrote:
> On 2/28/18 10:15, Matthew Glennon wrote:
> > So if I'm understanding this correctly, we're still having problems with
> > a bw testing nodes and that is why my relay has the unmetered flag?
>
> Right. The bandwidth measuring s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
So if I'm understanding this correctly, we're still having problems with a
bw testing nodes and that is why my relay has the unmetered flag?
-BEGIN PGP SIGNATURE-
Version: Keybase OpenPGP v2.0.76
Comment: https://keybase.io/crypto
wsBcBAABCg
30 matches
Mail list logo
