ssh-keygen.exe -t ed25519 -f provisioner_ed25519_key -C "provisioner" -q -N """"
yubico-piv-tool.exe -a generate -s 9a --pin-policy=never --touch-policy=cached -S "/CN=ssh-piv/" -H SHA256 -A ECCP256 -o public-key.pem
yubico-piv-tool.exe -a verify-pin -P $env:PIN -a selfsign-certificate -s 9a --pin-policy=never --touch-policy=cached -S "/CN=ssh-piv/" -H SHA256 -A ECCP256 -i public-key.pem -o selfcert.pem
yubico-piv-tool.exe -a import-certificate -s 9a --pin-policy=never --touch-policy=cached -i selfcert.pem
Couple this with WinCryptoSshAgent, and Windows has easy PIV crypto SSH support.
I hereby claim:
- I am lbruno on github.
- I am lbruno (https://keybase.io/lbruno) on keybase.
- I have a public key ASDkwxl6FyU2oUPdBHBTYAvGCnUSZeewNhdcuketAunP0go
To claim this, I am signing this object:
Using u-boot as an example, I’ve tried vendoring using two methods. A code-drop where an
export of the u-boot repo gets imported as a whole, and a repo-sync method where all
changesets get mirrored into our //third_party
tree.
Further, these changes (either batched up in a code-drop or mirrored 1:1) are imported into
a separate branch, named vendor
. This branch only sees completely clean imports without any
local modifications. We then merge the vendor branch back onto the default branch, where
we’ve committed all our local changes. These will be rebased on top of all merges incoming
Dear Ms. PRINCIPAL,
Hi, I'm a parent of CHILD, one of Ms TEACHER's (future) pupils in Senior Infants.
I hope this finds you and yours well, in these (almost) unprecedented times.
I'm writing to you because I am very wary of sending the Young One to school. Are you able to support parents who wish to continue schooling their children at home?
Below I justify said concern. In my own understanding of the situation, having read: