1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
|
#!/bin/bash
# This script allows bash to export environment
# variables as JSON. A list of environment
# variables and their values is exported as a
# single JSON object containing key-value mappings
# of JSON strings. It uses the external tool "jq"
# to parse string values # placed in jq's argument
# list by bash and then encode them as JSON string
# values. This is no accidental dependency. The jq
# program is the foundation of the trustworthiness
# of this code. If we were encoding JSON strings
# in bash (and not just encoding the JSON objects
# containing the strings) we would have to be a
# lot more careful.
# This is the simple code I wanted to replace:
#
# jq --arg SITE "$SITE" "$json"
# jq -n \
# --arg h "$db_host" \
# --arg u "$db_user" \
# --arg p "$db_password" \
# --arg n "$db_name" \
# --arg t "$table_prefix" \
# '{ db_host: $h
# , db_user: $u
# , db_password: $p
# , db_name: $n
# , table_prefix: $t
# }'
#
# The problem with the above is that the names are
# repeated.
# This creates the possibility that the names not
# match, creating a bug.
# This code allows the names to be specified only
# one time.
# It allows the bug where the names do not match
# to be fixed only one time by one person.
# IF ... the fix can be distributed back to the
# extant copies.
# How to get the beneficial mutations
# back into the living organisms?
# Life tries not to answer this question
# until very late in its development
# since after all
# the extant copies are the past
# and life looks into the future
# But because consciousness
# is the mirror of time
# the question is asked
# eventually
# when that level
# of life
# consciousness is reached.
arg1_to_env0()
{
case "$1" in
*[^a-zA-Z0-9_=]* )
echo "Error: invalid variable: '$1'" >&2
return 10
;;
[a-zA-Z_]* )
set -- "${1#*=}" "${1%%=*}"
;;
* )
echo "Error: invalid variable: '$1'" >&2
return 20
;;
esac
if [ -v "$2" ]
then
printf '%s=%s\0' "$1" "${!2}"
else
echo "Warning: ignoring unset variable: '$2'" >&2
fi
}
vars_to_env0()
{
while [ $# -gt 0 ]
do
arg1_to_env0 "$1" || return
shift
done
}
env0_to_JSON()
{
set --
while read -d ''
do
set -- "$@" --arg "${REPLY%%=*}" "${REPLY#*=}"
done
jq -n -r '$ARGS.named' "$@"
}
export_JSON_simple()
{
(
set -o pipefail
vars_to_env0 "$@" | env0_to_JSON
)
}
safe_stdout()
{
set -- "$(mktemp)" "$@"
(
exec 3>"$1" 4<"$1"
shift
"$@" >&3 && cat <&4
)
rm "$1"
}
export_JSON()
{
safe_stdout export_JSON_simple "$@"
}
try()
{
"$@"
: printf '%s -> %s\n' "${*@Q}" "$?" >&2
}
runtest()
{
set -- SSH_CLIENT SSH_TTY SSH_AUTH_SOCK SSH_CONNECTION
try export_JSON "$@"
unset unsetvar
try export_JSON SSH_TTY unsetvar
try export_JSON
try export_JSON ''
try export_JSON '' SSH_TTY
}
# Cryptography and routing needs to and does work like the benefits
# office where there is a fixed supply to hand out so there is a line
# of recipients waiting and in order to save resources there is a
# limit to its size and a residue of turnaways. So it is with tcp
# connections and in order for a service to minimize disruption to other
# tcp connections it need only limit the number of open connections it
# allows; understanding that the residue of turnaways will increase but
# the fixed supply will be delivered and the turnaways will re-enter the
# queue to receive belatedly.
#
# The connections in which we are interested are not TCP connections,
# they are VPN connections over UDP, but not really, they are social
# connections sustained through a software<->computer interface
# intermediary.
#
# The social program of Samizdat involves tending to the computers by
# interfacing with their USB ports and network ports, not their screens!
# The screen is used to seek user confirmation WITH DEfAULT TIMEOUT
# that makes Samizdat human-interaction-optional. Furthermore, Samizdat
# attempts to use the network to make human-interaction require no
# physical presence, but rather the human can interact from any one of
# their nodes that is live at the time! These identity-holding nodes
# hold SSH servers open on the internet AND thereby hold the personal
# cryptographic identity that YOU can most easily export and use on YOUR
# OWN servers.
#
# Anyway, we allow connectivity onto these machines in various ways,
# for example, the local network can take over the display if the user
# has never logged in, allowing to authorize the first install to disk
# on the machine without needing the machine to have a working display
# or input device.
|
