Scope: This project focuses purely on JavaScript and, sure, Typescript 😎 but the same patterns could be applied to other languages and/or systems.
Dependabot is great! Why did I learn how I could replace it?
<# | |
.SYNOPSIS | |
Prepares the Az Module for use with an OIDC credential much more quickly than azure/login action | |
#> | |
param ( | |
$applicationId = $env:AZURE_CLIENT_ID, | |
$tenantId = $env:AZURE_TENANT_ID, | |
$subscription = $env:AZURE_SUBSCRIPTION_ID, | |
$resourceGroup = $env:AZURE_RESOURCEGROUP | |
) |
My complete configuration is now hosted at https://gitlab.mim-libre.fr/-/snippets/13 |
The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the
First download alpine-make-vm-image from https://github.com/alpinelinux/alpine-make-vm-image
wget https://raw.githubusercontent.com/alpinelinux/alpine-make-vm-image/v0.4.0/alpine-make-vm-image \
&& echo '5fb3270e0d665e51b908e1755b40e9c9156917c0 alpine-make-vm-image' | sha1sum -c \
|| exit 1
mv alpine-make-vm-image /usr/local/bin/
chmod +x /usr/local/bin/alpine-make-vm-image
Create a new alpine qcow2 image
❱ git config user.signingKey 38AF394C | |
❱ git config commit.gpgSign true | |
❱ echo "test" | gpg --clearsign | |
-----BEGIN PGP SIGNED MESSAGE----- | |
Hash: SHA256 | |
test | |
gpg: signing failed: Inappropriate ioctl for device | |
gpg: [stdin]: clear-sign failed: Inappropriate ioctl for device |
These are my notes, not a generic solution. They are not meant to work anywhere outside my machines. Update version numbers to whatever are the current ones while you do this.
asdf
lives in https://github.com/asdf-vm/asdf
Follow its installation instructions, which at the moment of writing were:
Download the package: http://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/rsync-3.1.2-2-x86_64.pkg.tar.xz
Extract it and move rsync.exe
to %HOMEDRIVE%%HOMEPATH%\AppData\Local\Programs\Git\usr\bin
.
:: Windows 10 Hardening Script | |
:: This is based mostly on my own personal research and testing. My objective is to secure/harden Windows 10 as much as possible while not impacting usability at all. (Think being able to run on this computer's of family members so secure them but not increase the chances of them having to call you to troubleshoot something related to it later on). References for virtually all settings can be found at the bottom. Just before the references section, you will always find several security settings commented out as they could lead to compatibility issues in common consumer setups but they're worth considering. | |
:: Obligatory 'views are my own'. :) | |
:: Thank you @jaredhaight for the Win Firewall config recommendations! | |
:: Thank you @ricardojba for the DLL Safe Order Search reg key! | |
:: Thank you @jessicaknotts for the help on testing Exploit Guard configs and checking privacy settings! | |
:: Best script I've found for Debloating Windows 10: https://github.com/Sycnex/Windows10Debloater | |
: |
# Write policies from Pillar data | |
/etc/vault.d/policies.d: | |
file.directory: | |
- mode: 0700 | |
{% for name, policy in salt['pillar.get']('vault:policies').iteritems() %} | |
/etc/vault.d/policies.d/{{ name }}.json: | |
file.managed: | |
- source: salt://shopstyle-vault/files/policy.json | |
- mode: 0600 |