Did you just install kernel-cachyos and got hit by bad shim signature when booting? Me too. This is how I fixed it.
First, make sure you have Secure Boot with mokutil --sb-state.
Note, there's a second way of doing this by using sbctl, but I didn't want to wipe my Secure Boot keys.
| /********* Sample code generated by the curl command line tool ********** | |
| * All curl_easy_setopt() options are documented at: | |
| * https://curl.se/libcurl/c/curl_easy_setopt.html | |
| ************************************************************************/ | |
| // Pick up Hackaday home page | |
| #include <curl/curl.h> | |
The following guide is for setting up Docker with docker-compose v2 on Amazon Linux 2023. The steps are intendend for AL2023 on EC2 but should mostly work for the AL2023 VMs running on other hypervisors.
Install the following packages, which are good to have installed:
| { | |
| "clientId": "urn:federation:MicrosoftOnline", | |
| "surrogateAuthRequired": false, | |
| "enabled": true, | |
| "alwaysDisplayInConsole": false, | |
| "clientAuthenticatorType": "client-secret", | |
| "redirectUris": [ | |
| "https://login.microsoftonline.com/login.srf" | |
| ], | |
| "webOrigins": [ |
| #! /bin/bash | |
| # | |
| # Script to detect vulnerable log4j to CVE-2021-44228 | |
| # | |
| # Autor: Gustavo Oliveira Hoyer | |
| # | |
| # Last update: 22/12/2021 - 08:19 | |
| # | |
| # Minum version required |
| ============================================================================ | |
| #Wireshark installation directory: windows | |
| C:\Program Files (x86)\Wireshark>tshark.exe | |
| ============================================================================ | |
| tshark -D #list of available interfaces | |
| ============================================================================ | |
| capture | |
| ============================================================================ | |
| tshark -i 2 #start capturing traffic on interface n°2 | |
| tshark -i 2 -a duration:10 #capture for 10 seconds, then stop |
Script to check password and certificate expiration of Azure Service Principal.Target is all principal IDs assigned roles to the resources under the subscription set in the Azure CLI.
You can get information about IDs(Azure AD App) that have expired or will expire after a specified days as LTSV like followings.
app_id:aaaaaaaa-bbbb-cccc-dddd-eeeeeeee app_display_name:yourspname password_expire:2021-08-29T18:30:00+00:00
NOTE: Kafkacat is renamed to kcat recently and the config variable should be KCAT_CONFIG for version 1.7 onwards.
# you can export the variable or present the config with -F parameter for kafkacat
export KAFKACAT_CONFIG=/home/tools/persistent/kcat/kafkacat_config
This is a short and simple example on how to build a proper Keycloak cluster, using JDBC_PING as discovery protocol and an NGINX server as reverse proxy.
As this is for legacy Keycloak version (Wildfly based, up until version 17), you can find an example for more current and uptodate versions at this gist here: https://gist.github.com/dasniko/3a57913047af3ca1b6b0a83b294dc1a1
Please see also my video about Keycloak Clustering: http://www.youtube.com/watch?v=P96VQkBBNxU
Using the official resource-consumer as a stress tester.
Using EKS on Fargate cluster in eu-west-1:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.3", GitCommit:"b3cbbae08ec52a7fc73d334838e18d17e8512749", GitTreeState:"clean", BuildDate:"2019-11-14T04:25:00Z", GoVersion:"go1.12.13", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.8-eks-b8860f", GitCommit:"b8860f6c40640897e52c143f1b9f011a503d6e46", GitTreeState:"clean", BuildDate:"2019-11-25T00:55:38Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}