ssh-keygen -t rsa -b 4096 -m PEM -f jwtRS256.key | |
# Don't add passphrase | |
openssl rsa -in jwtRS256.key -pubout -outform PEM -out jwtRS256.key.pub | |
cat jwtRS256.key | |
cat jwtRS256.key.pub |
-
$ sudo pacman -S tor $ ## nyx provides a terminal status monitor for bandwidth usage, connection details and more.
$ sudo pacman -S nyx
Start by checking that there aren't any previous ssh keys inside the FIDO2 authenticator of your YubiKey. You can check if they exist by running the command below:
nix shell nixpkgs#yubikey-manager -c ykman fido credentials list
If the command above outputs a string mentioning "ssh" or "openssh", then you have already got a key generated and store on your YubiKey.
Before generating a new ssh key to store on your YubiKey you must consider which additional required authentication factors you want to use. Below you can see a table with the available factors and their corresponding command:
##TCP FLAGS## | |
Unskilled Attackers Pester Real Security Folks | |
============================================== | |
TCPDUMP FLAGS | |
Unskilled = URG = (Not Displayed in Flag Field, Displayed elsewhere) | |
Attackers = ACK = (Not Displayed in Flag Field, Displayed elsewhere) | |
Pester = PSH = [P] (Push Data) | |
Real = RST = [R] (Reset Connection) | |
Security = SYN = [S] (Start Connection) |
syntax on | |
filetype plugin indent on | |
"Get the 2-space YAML as the default when hit carriage return after the colon | |
autocmd FileType yaml setlocal ts=2 sts=2 sw=2 expandtab | |
set is hlsearch ai ic scs | |
nnoremap <esc><esc> :nohls<cr> | |
"https://vim.fandom.com/wiki/Moving_lines_up_or_down |
Modern OpenSSH has native support for FIDO Authentication. Its much simpler and should also be more stable with less moving parts. OpenSSH also now has support for signing arbitary files witch can be used as replacement of gnupg. Git also supports signing commits/tags with ssh keys.
- Simpler stack / less moving parts
- Works directly with
ssh
,ssh-add
andssh-keygen
on most computers - Simpler
- Private key can never leave the FIDO device
// Some info based on: https://learn.microsoft.com/en-us/microsoft-365/compliance/sit-defn-canada-drivers-license-number?view=o365-worldwide | |
const canadaDLNumberPatterns = { | |
Alberta: /\d{6}-\d{3}|\d{5,9}/, | |
"British Columbia": /\d{7}/, | |
Manitoba: /\w{2}-?\w{2}-?\w{2}-?\w\d{3}\w{2}/, | |
"New Brunswick": /\d{5,7}/, | |
"Newfoundland and Labrador": /\w\d{9}/, | |
"Nova Scotia": /\w{5}-?[0123]\d[01]\d{6}/, | |
Ontario: /\w\d{4}-?\d{5}\d[0156]\d[0123]\d/, |
- If values are integers in [0, 255], Parquet will automatically compress to use 1 byte unsigned integers, thus decreasing the size of saved DataFrame by a factor of 8.
- Partition DataFrames to have evenly-distributed, ~128MB partition sizes (empirical finding). Always err on the higher side w.r.t. number of partitions.
- Pay particular attention to the number of partitions when using
flatMap
, especially if the following operation will result in high memory usage. TheflatMap
op usually results in a DataFrame with a [much] larger number of rows, yet the number of partitions will remain the same. Thus, if a subsequent op causes a large expansion of memory usage (i.e. converting a DataFrame of indices to a DataFrame of large Vectors), the memory usage per partition may become too high. In this case, it is beneficial to repartition the output offlatMap
to a number of partitions that will safely allow for appropriate partition memory sizes, based upon the