Security Advisories / Bulletins / vendors Responses linked to Spring4Shell (CVE-2022-22965)
A B C D E F G H [I](https://gist.github.com/SwitHak/0be6e857174d6ba2a6973f9ff9030c
| --- | |
| # Page meta info, like heading, footer text and nav links | |
| pageInfo: | |
| title: Dashy | |
| description: Welcome to your new dashboard! | |
| navLinks: | |
| - title: GitHub | |
| path: https://github.com/Lissy93/dashy | |
| - title: Documentation | |
| path: https://dashy.to/docs |
Sometimes when creating a new CentOS 7 server, the drive is partioned with the root, boot and swap, and then all the rest of the space is given to the home directory.
Here, we are going to reduce the size of the /home partition and allocate the remaining space back to the root partition.
List the current block devices
convert ctime(timestamp/1000)
aid=* event_simpleName=DnsRequest | regex DomainName=".*\.top$|.*\.club$|.*\.xyz$|.*\.ru$|[0-9]+.*\.\w$" | stats values(ComputerName) count by DomainName| where count <4 | sort – count
| #!/bin/bash | |
| # craigphicks 2019 | |
| set -u | |
| function CreateCertificateAuthority { | |
| if [[ $# -ne 2 ]] ; then | |
| echo "two args only: CA common name, CA org name" | |
| exit 1 | |
| fi | |
| CA_CN=${1} |
sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -restart -agent
| #!/bin/sh | |
| <<ABOUT_THIS_SCRIPT | |
| ----------------------------------------------------------------------- | |
| Written by: William Smith | |
| Professional Services Engineer | |
| Jamf | |
| bill@talkingmoose.net | |
| https://github.com/talkingmoose/Jamf-Scripts | |
| /* | |
| Copy this function over the existing Code.gs file in a Google Sheet | |
| Save the Sheet/Script | |
| Publish App | |
| - Execute as You | |
| - Avaiable to Anyone (including anonymous) | |
| Authorize App when prompted | |
| The URL will act as the Webhook URL for Meraki to send alerts | |
| */ |
| server: | |
| ########################################################################### | |
| # BASIC SETTINGS | |
| ########################################################################### | |
| # Time to live maximum for RRsets and messages in the cache. If the maximum | |
| # kicks in, responses to clients still get decrementing TTLs based on the | |
| # original (larger) values. When the internal TTL expires, the cache item | |
| # has expired. Can be set lower to force the resolver to query for data | |
| # often, and not trust (very large) TTL values. | |
| cache-max-ttl: 86400 |