From: steve jenkin <sjenkin@canb.auug.org.au>
To: COFF <coff@tuhs.org>
Subject: [COFF] Re: Fwd: Useful Shell Scripts Network Connections , Logins and Block hacking attempts
Date: Thu, 11 May 2023 15:58:51 +1000 [thread overview]
Message-ID: <97CD9F08-E004-443E-89F9-2B9B23ADD53C@canb.auug.org.au> (raw)
In-Reply-To: <CAJXSPs-67AUTJeokOfm4+4fE8HP5saPH=Udqycrw0S2tgcK0jQ@mail.gmail.com>
> On 11 May 2023, at 09:56, KenUnix <ken.unix.guy@gmail.com> wrote:
>
> Useful Shell Scripts Network Connections , Logins and Block hacking attempts
I found this content on Medium as a ‘members only’ article, published 5 April, 2023.
A 2nd article of “useful shell scripts”
<https://medium.com/@Beck_Moulton/useful-shell-scripts-2-df9cbcf6bdd8>
Author handle is "Beck Moulton”, who does Java according to their Bio.
"Focus on the back-end field, do actual combat technology sharing”
<https://medium.com/@Beck_Moulton/about>
There’s Golang and Rust threads and more.
==============
I didn’t see any attribution of source in the articles.
The snippets have the feel to be from some standard source, but I didn’t identify it.
Previous post of ‘useful’ scripts (#1 vs #2) from 17 March, 2023.
<https://medium.com/@Beck_Moulton/useful-shell-scripts-f846350eb1ae>
#1 According to the PID input by the user, filter out all the information of the PID
#2 Display all information about the process according to the process name
#3 View information about the user based on the user name
#4 Check the connection status of tcp
#5 Display system performance
==============
A random github page from 2014, a “Linux Admin Cheatsheet”, for anyone wanting more.
Not a recommendation, not a comment on suitability or quality of content.
<https://github.com/crhuber/linux-cheatsheet>
==============
cheers
steve
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2023-05-11 5:59 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] " KenUnix
2023-05-11 0:12 ` [COFF] " Niklas Karlsson
2023-05-11 5:58 ` steve jenkin [this message]
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
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=97CD9F08-E004-443E-89F9-2B9B23ADD53C@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--cc=coff@tuhs.org \
/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).