Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #116654

Re: Sucuri Warning (was tl;dr:)

From "David B." <DavidB@nomail.afraid.org>
Newsgroups alt.computer.workshop, comp.sys.mac.system, comp.sys.mac.misc
Subject Re: Sucuri Warning (was tl;dr:)
Date 2018-05-25 12:44 +0100
Organization A noiseless patient Spider
Message-ID <pe8sv5$hs6$1@dont-email.me> (permalink)
References (7 earlier) <8279gd1is5l703du938tios7a1ilrkfvc3@4ax.com> <pe4hom$jca$1@dont-email.me> <XnsA8EC80A98143DHT1@F826sQG92pVDYw.rfIzbhkNr7CoCxZUOJixBL5D0o7NPV15GI8H3Ec7GZv> <pe75r5$p8c$1@dont-email.me> <imlegddjp4a70em5oti0etsec8uenu9bdk@4ax.com>

Cross-posted to 3 groups.

Show all headers | View raw

On 25-May-18 1:22 AM, Shadow asked ...

> Why does it matter ?

According the the site certificate information, the cert is valid.  Use
your unidentified web browser to look at the details of a site's cert.
However, I noticed that the cert's CA (certificate authority) is using
the freebie Let's Encrypt which really isn't a CA.  Many sources
consider those certs as insecure.  Let's Encrypt never validates who
asked to get a certificate.  Since no money was exchanged, there is no
way to "follow the money".  The whole process is automated so there is
no overseer on issuance of the certs.

Sites using Let's Encrypt might as well as use their self-signed certs
for as "secure" as those would be regarding actually identifying the
registrant of a cert.  This is like users getting freebie e-mail certs
to do x.509 SMIME digital signing and encryption of their e-mails but
there is no validation of just WHO got that e-mail cert, only that the
registrant used the mailbox for which the e-mail cert was issued which
is hardly identifying who owns the cert.  Similar to sending the free
e-mail cert via e-mail to whoever requested it (to verify the registrant
has, at least, access to that e-mail account), Lets Encrypt uses ACME
(Automated Certificate Management Environment) to check the server is
the one that gets the site cert.  Uh huh, yep, that really identified
the registrant: the one asking for the cert is the one that validates it
was them that asked for it.  That's like getting a blank driver's
license and whatever you write on it, oh sure, that must be you.

Only because web browsers pre-install the Let's Encrypt root cert lets
users of those web browsers visit sites using that pseudo-CA.  The Let's
Encrypt root certificate is pre-installed in Google Chrome (wasn't a
while ago so Chrome would complain the Let's Encrypt-ed site was not
secure).  Mozilla added the root cert to Firefox because, gee, Mozilla
is one of the founders of Let's Encrypt (and, no, if you've used Firefox
for a long time then you know Mozilla does NOT have the user's security
fully prioritized but add lots of shit to assist web sites).  In Chrome,
you'll see the cert listed under Lets Encrypt.  In Firefox, it is listed
as IdenTrust.  Sites going cheap by getting free certs from Lets Encrypt
had problems at first because web browsers didn't have that pseudo-CA
listed/added to their cert store.

https://www.theregister.co.uk/2018/01/13/lets_encrypt_certificate_drama/
(do a search and you'll find other gotchas with Lets Encrypt)

It was a nuisance to have to pay for site certs and having to trust a
3rd party as the regulator but that had some validity and checking as
who got the cert.  With the freebies from Lets Encrypt, the registrant
validates themself (rolls eyes).

As for Securi, well, the part you omitted in your post was they said:

   Our automated scan was unable to run on your website.

Okay, that could be something as simple as the site uses robots.txt with
a directive telling web crawlers to NOT crawl their web site.  I tried
clicking on Securi's "More details" button for "Scanning errors" but
they just re-painted the same web page.  I was trying to see WHY they
report they cannot scan/crawl that web site.  I had to allow the
mxpnl.com source for scripts in both uMatrix and uBlock Origin to get
the script needed when clicking on the "More details" button.  Then all
they said was the same forbidden error they reported above.  No further
information.  They won't even tell you that actual error status that was
returned by the server when attempt to visit that page.  Instead they
just show "40x" as the error status.  Yeah, right, very unhelpful.

Apparently to get more details means having to sign-up at Securi.  Go
read:

https://sucuri.net/website-security-platform/signup

Then you'll see Securi is using their so-called web site scan as a lure
to get users (perhaps only the site owner) to buy into their site scan
service.  Dump Securi.  They're a lureware site.

If you want to externally validate a site's SSL certificate rather than
trusting what your own web browser reports, go to:

https://www.ssllabs.com/ssltest/

That will test lots of aspects of a site (SSL) cert.  That it reports
deficiencies does not mean the cert is invalid or misleading, only that
the site needs to improve.  Note that for www.tekrider.net, SSLlabs
reports it supports TLS 1.0 but not SSL 3.0.  Alas, TLS 1.0 was just a
renaming of SSL 3.0 but with some incompatibilities to differentiate it
from SSL 3.0.  A site using TLS 1.0 is no more secure than one using SSL
3.0.  SSllabs will note which ciphers are supported by the site,
including those the site will accept that are considered weak.

Although not specifically an overt red flag, I ponder what
dixie-metal-detectors.com (2nd site cert issued by GoDaddy but which
SSLlabs says is not trusted probably due to a SA [Subject Alternative]
mismatch on multiple domains to which the cert is registered) has to do
with tekrider.net (1st cert using free Lets Encrypt).  Also:

nslookup www.tekrider.net
gives an IP address of 192.251.238.3
(which hides using a private domain registration at GoDaddy)

but a reverse DNS lookup on 192.251.238.3
gives alvin.genwebserver.com
(which hides using a private domain registration at privacygarden.org)

and the IP address of 192.251.238.3 is in the IP pool owned by Webby
Enterprises LLC (webbytech.net) who appears to be the webhoster.

I'm not sure Securi is trying to provide for information on a site's
certificate but it appears they are a lure to a paid service.  Use
SSLlabs if you want more info on a site's cert than what your web
browser tells you.

-- 
David B.

Back to comp.sys.mac.system | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-19 14:22 +0100
  Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-19 12:21 -0300
    Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-20 09:55 +0100
      Re: tl;dr: Wolffan <akwolffan@gmail.com> - 2018-05-20 07:02 -0400
        Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-21 07:40 +0100
        Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-21 08:02 +0100
          Re: tl;dr: nospam <nospam@nospam.invalid> - 2018-05-21 09:20 -0400
            Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-21 15:22 +0100
              Re: tl;dr: nospam <nospam@nospam.invalid> - 2018-05-21 13:01 -0400
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-21 18:10 +0100
                Re: tl;dr: nospam <nospam@nospam.invalid> - 2018-05-21 15:12 -0400
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-21 12:51 -0700
              Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-21 18:51 -0300
              Re: tl;dr: Wolffan <akwolffan@gmail.com> - 2018-05-21 18:27 -0400
                Allow Applicatiosn from... JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-05-21 19:41 -0400
                Re: Allow Applicatiosn from... nospam <nospam@nospam.invalid> - 2018-05-21 19:47 -0400
                Re: Allow Applicatiosn from... JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-05-21 21:30 -0400
                Re: Allow Applicatiosn from... nospam <nospam@nospam.invalid> - 2018-05-21 21:42 -0400
                Re: Allow Applicatiosn from... Leonard Blaisdell <leoblaisdell@sbcglobal.net> - 2018-05-21 21:51 -0700
                Re: Allow Applicatiosn from... Steve Carroll <frelwizzen@gmail.com> - 2018-05-21 22:12 -0700
                Re: Allow Applicatiosn from... JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-05-22 16:11 -0400
                Re: Allow Applicatiosn from... Huge <Huge@nowhere.much.invalid> - 2018-05-22 21:14 +0000
                Re: Allow Applicatiosn from... Barry Margolin <barmar@alum.mit.edu> - 2018-05-22 12:20 -0400
                Re: Allow Applicatiosn from... JF Mezei <jfmezei.spamnot@vaxination.ca> - 2018-05-22 16:17 -0400
                Re: Allow Applicatiosn from... Huge <Huge@nowhere.much.invalid> - 2018-05-22 21:14 +0000
                Re: Allow Applicatiosn from... "David B." <DavidB@nomail.afraid.org> - 2018-05-22 21:27 +0100
                Re: Allow Applicatiosn from... Steve Carroll <frelwizzen@gmail.com> - 2018-05-22 15:08 -0700
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-21 18:48 -0700
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-22 08:21 +0100
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-22 03:23 -0700
                Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-22 11:55 -0300
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-22 16:38 +0100
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-22 09:23 -0700
                Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-22 19:46 -0300
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-22 16:12 -0700
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-22 20:22 -0700
                Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-23 21:08 +0100
                Re: Sucuri Warning (was tl;dr:) Alan Baker <alangbaker@telus.net> - 2018-05-23 13:24 -0700
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-23 13:32 -0700
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-23 17:34 -0300
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-23 22:09 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-23 23:14 +0000
                Re: Sucuri Warning (was tl;dr:) Alan Baker <alangbaker@telus.net> - 2018-05-23 16:29 -0700
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-23 17:09 -0700
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-24 12:00 +0100
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-24 04:22 -0700
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-23 22:11 -0300
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-24 03:05 -0700
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-24 05:24 -0700
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-24 16:31 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-24 16:31 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-24 21:03 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-24 21:29 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 12:47 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 12:27 +0000
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-25 06:47 -0700
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 14:53 +0100
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-27 18:15 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 15:16 -0300
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 21:50 +0100
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 18:24 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-25 21:01 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-25 21:23 -0700
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-24 15:00 -0700
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-24 21:22 -0300
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 12:44 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 12:27 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 13:52 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 13:31 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 14:54 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 14:05 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 15:48 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 15:36 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 17:14 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 17:13 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 19:38 +0100
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-25 14:54 -0500
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-25 20:39 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 13:51 +0100
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-27 06:49 -0700
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 14:57 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 16:29 +0100
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-27 18:15 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 15:24 -0300
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-27 10:54 -0500
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-27 18:15 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 15:14 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 13:20 +0100
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-25 20:22 -0700
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-25 13:29 -0500
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 13:28 +0100
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-27 10:48 -0500
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 15:03 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-27 18:15 +0000
                Re: Sucuri Warning (was tl;dr:) Tim Streater <timstreater@greenbee.net> - 2018-05-25 18:25 +0100
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-25 19:27 +0100
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-25 21:05 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 14:19 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 14:57 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 17:33 +0100
                Re: Sucuri Warning (was tl;dr:) Frozen North <frozennorth.ask@gmail.com> - 2018-05-27 13:20 -0400
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 18:40 +0100
                Re: Sucuri Warning (was tl;dr:) Frozen North <frozennorth.ask@gmail.com> - 2018-05-27 14:20 -0400
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 21:44 +0100
                Re: Sucuri Warning (was tl;dr:) Frozen North <frozennorth.ask@gmail.com> - 2018-05-27 17:02 -0400
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 22:04 +0100
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 18:26 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 15:37 -0300
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 20:37 +0100
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 18:12 -0300
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 21:50 +0000
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 17:53 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 19:02 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 18:47 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 20:53 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 21:50 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-28 05:23 -0700
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-27 18:15 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 22:02 +0100
                Re: Sucuri Warning (was tl;dr:) "Beauregard T. Shagnasty" <a.nony.mous@example.inwalid> - 2018-05-27 22:11 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 15:31 -0300
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-27 09:57 -0700
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-27 10:34 -0500
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-27 11:02 -0500
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-27 18:15 +0000
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 21:28 +0100
                Re: Sucuri Warning (was tl;dr:) Frozen North <frozennorth.ask@gmail.com> - 2018-05-27 16:48 -0400
                Re: Sucuri Warning (was tl;dr:) "David B." <DavidB@nomail.afraid.org> - 2018-05-27 21:53 +0100
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) eyes@wideshut.com (Sycho) - 2018-05-28 04:25 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Shadow <Sh@dow.br> - 2018-05-27 18:21 -0300
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-28 08:02 +0000
                Re: Sucuri Warning (was tl;dr:) Frozen North <frozennorth.ask@gmail.com> - 2018-05-25 10:50 -0400
                Re: Sucuri Warning (was tl;dr:) Steve Carroll <frelwizzen@gmail.com> - 2018-05-25 11:29 -0700
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-25 09:52 -0500
                Re: Sucuri Warning (was tl;dr:) Char Jackson <none@none.invalid> - 2018-05-25 09:56 -0500
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: Sucuri Warning (was tl;dr:) Diesel <me@privacy.net> - 2018-05-26 03:19 +0000
                Re: tl;dr: Wolffan <akwolffan@gmail.com> - 2018-05-22 22:37 -0400
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-23 06:25 +0100
                Re: tl;dr: nospam <nospam@nospam.invalid> - 2018-05-23 08:46 -0400
                Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-23 10:57 -0300
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-23 18:16 +0100
                Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-23 15:17 -0300
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-23 20:22 +0100
                Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-23 17:30 -0300
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-23 22:13 +0100
                Re: tl;dr: nospam <nospam@nospam.invalid> - 2018-05-23 17:59 -0400
                Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-23 22:10 -0300
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-23 18:12 -0700
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-23 12:29 -0700
                Re: tl;dr: Wolffan <akwolffan@gmail.com> - 2018-05-23 18:31 -0400
                Re: tl;dr: nospam <nospam@nospam.invalid> - 2018-05-23 18:33 -0400
          Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-21 18:42 -0300
            Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-22 10:15 +0100
              Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-22 12:00 -0300
                Re: tl;dr: "David B." <DavidB@nomail.afraid.org> - 2018-05-22 16:32 +0100
                Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-22 08:37 -0700
      Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-20 05:40 -0700
      Re: tl;dr: Shadow <Sh@dow.br> - 2018-05-20 10:31 -0300
        Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-20 07:29 -0700
  Re: "BurfordTJustice" <burford/associate@uk.MI15> - 2018-05-19 14:55 -0400
    Re: Steve Carroll <frelwizzen@gmail.com> - 2018-05-19 15:35 -0700
  Re: tl;dr: Steve Carroll <frelwizzen@gmail.com> - 2018-05-19 11:57 -0700
  (OT) David Brooks A known stalker! Diesel <me@privacy.net> - 2018-05-28 23:32 +0000
    Re: (OT) David Brooks A known stalker! Steve Carroll <frelwizzen@gmail.com> - 2018-05-28 20:31 -0700
      Re: (OT) David Brooks A known stalker! Steve Carroll <frelwizzen@gmail.com> - 2018-05-29 14:00 -0700

csiph-web