Myth about associative arrays in BASH
To be clear: It's possible to pass associative arrays in BASH.
TL;DR you probably didn't RTFM so please njoy following session!
|# vim:tabstop=2 softtabstop=2 shiftwidth=2 noexpandtab|
|# ssh-copy-key - a better ssh-copy-id|
|# - have a different identify file to copy to remote host (and just one!)|
|# - (infrastructure where you don't own private key but wanna role out your private key –like it should be done ;)|
|# - automatically generates public key if not yet given|
This page will assist you in retrieving important information from so called Snowflake Server which exist in your infrastructure unversioned and with unknown status. The basic idea is that system files in a modern system are under packages control, which enables us to do following:
|# SSH Remote Forwarded Clipboard|
|# You can copy stuff on a remote machine to your local clipboard (e.g. you could use the script in a shell theme)|
|# It is not intended to do it the other way round (makes no sense since you usually will use your local clipboard)|
|# Security Concerns|
|# Someone else on the remote host could spam or exploit your clipboard exploit it (xsel, xclipbaord, parcellite etc.)|
So, you are a proud OpenSource developer and work for a company using GitHub.com for GIT repository hosting?
While SSH auth to GitHub.com is based on public keys and it automatically chooses the right account you have to take care when you quickly clone a repository, change something and whoops your company has your private email address or hacker pseudo within their repository.
The scenario we are speaking about looks like following:
|# Logging of bash output and preventing stderr written before stdout|
|# If STDERR is not relvant to yout consider using `exec 1&>>(logger) 2>&1`|
|# Culprit is Unix stdio buffering, as implemented on Linux by glibc which is a system library|
|# that most programs implemented in C use to handle basic stuff (e.g., IO).|