From: Robert Stanford via COFF <coff@tuhs.org>
To: coff@tuhs.org
Subject: [COFF] Re: Useful Shell Scripts Network Connections , Logins and Block hacking attempts
Date: Fri, 12 May 2023 18:14:29 +1000 [thread overview]
Message-ID: <e14ea150-3d8f-c33b-661a-392c836aee8e@stanford.com.au> (raw)
In-Reply-To: <20230512021317.GA3576@eureka.lemis.com>
On 12/5/23 12:13, Greg 'groggy' Lehey wrote:
> On Thursday, 11 May 2023 at 22:35:46 +0000, COFF wrote:
>> On Thursday, May 11th, 2023 at 3:06 PM, Dave Horsfall <dave@horsfall.org> wrote:
>>> On Thu, 11 May 2023, Ralph Corderoy wrote:
>>>
>>> It appears to be some jerk pretending to be Ken T; any fool can
>>> take a Gmail address (and they do).
>> I would be cautious with that sort of accusation...
> Agreed. My guess is that the poster is really called Ken. You can't
> blame him for that.
>
>
I cop the same thing with my domain. That's my surname and I was lucky
to score the domain (stanford.com.au) when it became available. I've
never tried to pass it off as anything else, yet every now and then I
encounter someone who gets a bee in their bonnet over it.
next prev parent reply other threads:[~2023-05-12 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJXSPs92h7yVVJm9UPp06zPQwRy-XkGPDhL-=uVT5sw=hEcLkQ@mail.gmail.com>
2023-05-10 23:56 ` [COFF] Fwd: " KenUnix
2023-05-11 0:12 ` [COFF] " Niklas Karlsson
2023-05-11 5:58 ` steve jenkin
2023-05-11 9:18 ` [COFF] " Ralph Corderoy
2023-05-11 22:06 ` Dave Horsfall
2023-05-11 22:35 ` segaloco via COFF
2023-05-12 2:13 ` Greg 'groggy' Lehey
2023-05-12 2:19 ` Adam Thornton
2023-05-12 2:34 ` Larry McVoy
2023-05-12 4:30 ` Tomasz Rola
2023-05-12 8:34 ` Ralph Corderoy
2023-05-12 13:58 ` Larry McVoy
2023-05-12 4:24 ` Tomasz Rola
2023-05-12 5:02 ` segaloco via COFF
2023-05-12 8:14 ` Robert Stanford via COFF [this message]
2023-05-12 16:40 ` Adam Thornton
2023-05-12 11:42 ` Ralph Corderoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e14ea150-3d8f-c33b-661a-392c836aee8e@stanford.com.au \
--to=coff@tuhs.org \
--cc=rob@stanford.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).