Skip to content

Commit b40a3c4

Browse files
mogulOpenCode Agent
andcommitted
fix(isolation): run cloud.gov CF CLI fetch after CA trust
The CF CLI download ran in `phase: install` (create time), before the CA-trust kit's startup step trusted an intercepting proxy's CA. On sbx behind Zscaler, curl exited 60 and the whole sandbox create failed. - Run the fetch as a non-fatal, idempotent `phase: startup` command as the agent user, installing into ~/.local/bin, so it follows the CA kit in kit order. No root step executes the agent-writable script. - Allow release-assets.githubusercontent.com: github.com redirects the pinned release tarballs there. - verify: add ACQ_BACKEND=sbx|msb (passes --backend to acq, fails if the create log names a different backend), a fetch-ordering check, and CA_KIT for bundles with no CA kit. - Add an offline regression test that simulates an intercepted network (curl exits 60 until the CA is trusted), plus SHA-256 mismatch and non-fatal wrapper cases. - Docs: do not add a CA kit the bundle already has (sbx rejects duplicate kit names). Co-authored-by: OpenCode Agent <[email protected]>
1 parent b7c7372 commit b40a3c4

9 files changed

Lines changed: 352 additions & 26 deletions

File tree

‎integrations/isolation/acq-kits/cloud-gov/README.md‎

Lines changed: 39 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,9 @@ sandbox.
1212
## What It Does
1313

1414
- **Cloud Foundry CLI** - uses an existing `cf` binary when the base image already
15-
has one. If `cf` is missing, installs Cloud Foundry CLI v8.19.0 from pinned
16-
upstream release tarballs with committed SHA-256 checks.
15+
has one. If `cf` is missing, installs Cloud Foundry CLI v8.19.0 into
16+
`~/.local/bin` at sandbox startup from pinned upstream release tarballs with
17+
committed SHA-256 checks.
1718
- **cloud.gov egress** - allow-lists exact cloud.gov control-plane and
1819
documentation hosts: the Cloud Foundry API, login/UAA, log-stream hosts, and
1920
user-facing cloud.gov documentation. Public app routes and custom domains stay
@@ -28,7 +29,7 @@ sandbox.
2829
## Backend Parity
2930

3031
The kit declares `sbx` and `msb` support. Both backends consume the neutral kit
31-
fields: `caps.network.allow`, file drops, and create-time/startup commands. There
32+
fields: `caps.network.allow`, file drops, and startup commands. There
3233
is no backend shortcut.
3334

3435
The Cloud Foundry token is not a kit field. The user stores it in the acq secret
@@ -50,6 +51,18 @@ acq run --kit <path-to-this-kit> opencode /path/to/project
5051

5152
The kit is a `mixin`, so it composes with the other acq-kits.
5253

54+
**On a TLS-intercepting network (for example Zscaler), the CA-trust kit must
55+
come before this kit.** Startup commands run in kit order and the CF CLI
56+
download is HTTPS. The global kit bundle applies `zscaler-ca-certificate` before
57+
`ACQ_EXTRA_KITS`, so the default needs no action. Do **not** add the CA kit to
58+
`ACQ_EXTRA_KITS` when the global bundle already has it: sbx rejects a
59+
composition with two kits of the same name (`duplicate kit name`). Only if your
60+
bundle has no CA-trust kit, list one before this kit:
61+
62+
```bash
63+
export ACQ_EXTRA_KITS="<path>/your-ca-kit <path>/cloud-gov"
64+
```
65+
5366
## CF CLI Installation Pin
5467

5568
If the base image already has `cf`, the install step exits successfully without
@@ -58,10 +71,21 @@ CLI v8.19.0 from the upstream GitHub release tarball for `linux_x86-64` or
5871
`linux_arm64`, then verifies the archive SHA-256 before installing it. Unsupported
5972
architectures fail closed.
6073

74+
The install is a **startup** step (as the agent user, into `~/.local/bin`), not
75+
an install-phase step. An install-phase command runs at create time, before a
76+
CA-trust kit's startup step has trusted an intercepting proxy's CA, so the HTTPS
77+
fetch failed with `curl` exit 60 and failed the whole create. The startup step is
78+
non-fatal and idempotent: a failed download logs a warning and is retried on the
79+
next start.
80+
6181
To update the CLI, change the version and both SHA-256 constants in
6282
`files/home/cloud-gov-install-cf-cli.sh` together after reviewing the upstream
6383
release metadata.
6484

85+
`cf` is installed in `~/.local/bin`. A bare `acq exec` runs a non-login shell
86+
that may not have that directory on `PATH`; prepend it
87+
(`PATH="$HOME/.local/bin:$PATH"`) when probing from the host.
88+
6589
## Prerequisites
6690

6791
From a host shell, log in to cloud.gov with the normal human-controlled flow:
@@ -106,7 +130,7 @@ The kit allow-lists:
106130
| `doppler.fr.cloud.gov`, `log-cache.fr.cloud.gov` | Cloud Foundry log streaming/control-plane endpoints |
107131
| `cloud.gov`, `www.cloud.gov`, `docs.cloud.gov` | cloud.gov public documentation |
108132
| `docs.cloudfoundry.org`, `cli.cloudfoundry.org` | Cloud Foundry documentation |
109-
| `github.com`, `objects.githubusercontent.com` | Pinned Cloud Foundry CLI release tarball download during kit install; if runtime access to these hosts is not acceptable for a deployment context, use a base image with `cf` preinstalled or a project-specific vetted artifact source. |
133+
| `github.com`, `objects.githubusercontent.com`, `release-assets.githubusercontent.com` | Pinned Cloud Foundry CLI release tarball download during the startup install; if runtime access to these hosts is not acceptable for a deployment context, use a base image with `cf` preinstalled or a project-specific vetted artifact source. |
110134

111135
The kit intentionally does not allow `*.cloud.gov`. If the project needs a
112136
specific app route, route service, or custom domain, add that exact host in a
@@ -153,8 +177,17 @@ Run the bundled check:
153177

154178
By default it runs offline checks only: repository kit validation, shell syntax
155179
for kit scripts, auth-script guard tests with synthetic placeholders, and exact
156-
egress allow-list assertions. Set `RUN_ACQ=1` to create a throwaway sandbox and
180+
egress allow-list assertions, and that the CF CLI fetch is not an install-phase
181+
command. Set `RUN_ACQ=1` to create a throwaway sandbox and
157182
verify that `cf` is installed, cloud.gov/docs endpoints are reachable, and the
158183
injected placeholder reaches the CF API through a direct HTTPS request.
159-
`RUN_ACQ=1` requires a global `cloud-gov` acq secret. Set `KEEP=1` with
184+
`RUN_ACQ=1` requires a global `cloud-gov` acq secret. On an
185+
intercepted network, run it as is: the global bundle supplies the CA kit ahead
186+
of this one, which is the live regression for the CA-before-fetch ordering. Set
187+
`CA_KIT=<path>` only if your bundle has no CA-trust kit (a kit with the same
188+
name as one already in the bundle is rejected by sbx). Set
189+
`ACQ_BACKEND=sbx` (or `msb`) to pass `--backend` to `acq` without changing your
190+
persisted default; the CA-before-fetch failure only reproduces on sbx, because
191+
msb trusts host CAs natively. The script prints which backend the create log
192+
names and fails if it differs from the one requested. Set `KEEP=1` with
160193
`RUN_ACQ=1` to keep the sandbox for inspection.

‎integrations/isolation/acq-kits/cloud-gov/TROUBLESHOOTING.md‎

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,16 @@ These are failure modes specific to the cloud-gov acq mixin kit.
88

99
**Causes and fixes:**
1010

11+
- **TLS chain untrusted at install (`curl exit 60`).** On a network that
12+
intercepts TLS, the CF CLI download needs the intercepting CA. The install
13+
runs in the startup phase so a CA-trust kit's startup step can run first, but
14+
only if that kit comes **before** `cloud-gov`. The global bundle already does
15+
this. Only if your bundle has no CA-trust kit, list one before `cloud-gov` in
16+
`ACQ_EXTRA_KITS`; do not add a second copy of a kit the bundle already has
17+
(sbx fails the create with `duplicate kit name`). Fix the order, then
18+
`acq restart <sandbox>`: the install step is idempotent and retries on every
19+
start. A failed download never blocks sandbox start; it logs
20+
`cloud-gov: WARNING: cf CLI is not installed`.
1121
- **Install egress blocked.** Check the sandbox policy log and confirm the CF CLI
1222
package hosts in `spec.yaml` are allowed.
1323
- **Unsupported architecture.** The install script supports upstream Linux
@@ -28,7 +38,8 @@ These are failure modes specific to the cloud-gov acq mixin kit.
2838
- **Egress blocked by org policy.** Check `acq policy log <sandbox>` or the
2939
active backend's policy log for `api.fr.cloud.gov`.
3040
- **TLS trust issue.** If your network uses TLS inspection, compose this kit with
31-
`zscaler-ca-certificate` or the local equivalent CA-trust kit.
41+
`zscaler-ca-certificate` or the local equivalent CA-trust kit, ordered before
42+
this one (the global bundle already does this for Zscaler).
3243

3344
## CF Authentication Fails
3445

‎integrations/isolation/acq-kits/cloud-gov/docs/decisions/cloud-gov-cli-and-auth.md‎

Lines changed: 26 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,9 @@ interactive `cf` authentication works.
1919

2020
Create a neutral `cloud-gov` acq mixin kit for sbx and msb that:
2121

22-
1. Installs `cf` at create time from pinned Cloud Foundry CLI release tarballs
23-
with committed SHA-256 values.
22+
1. Installs `cf` at sandbox startup (agent user, `~/.local/bin`) from pinned
23+
Cloud Foundry CLI release tarballs with committed SHA-256 values. See
24+
"Install phase" below for why this is not a create-time install.
2425
2. Allow-lists exact cloud.gov control-plane/documentation hosts and Cloud
2526
Foundry docs domains, without wildcard semantics.
2627
3. Uses acq's custom secret binding for a host-side token captured with
@@ -42,13 +43,36 @@ active backend's secret/proxy mechanism. The kit does not write a placeholder to
4243
`~/.cf/config.json`; authenticated `cf` command support requires a separately
4344
live-tested path because the stock CLI may parse cached tokens locally.
4445

46+
### Install phase
47+
48+
The tarball download is HTTPS. On a TLS-intercepting network the CA-trust kit
49+
(`zscaler-ca-certificate`) installs the intercepting CA in its `startup` step.
50+
A `phase: install` command runs at create time, before that CA is trusted, so
51+
`curl -fsSL` failed with exit 60 and the sandbox create failed. The fetch is
52+
therefore a `startup` command, which kit order runs after the CA kit's startup
53+
step because the global bundle lists it first. It runs as the agent user, so it installs
54+
into `~/.local/bin` (first on the image PATH) instead of `/usr/local/bin`, and no
55+
root step executes the agent-writable script. The agent can replace
56+
`~/.local/bin/cf`; the SHA-256 check covers the download only. It is non-fatal (a failed fetch
57+
logs a warning and leaves the sandbox usable) and idempotent (retried on each
58+
start). Rejected alternative: bundling the binaries in the kit, since kit file
59+
delivery is for text and a pinned download with a SHA-256 check is the
60+
reviewable form. Regression coverage: `scripts/tests/test_cloud_gov_kit_ordering.py`
61+
(simulated intercepted network, offline) and `scripts/verify` with `RUN_ACQ=1`
62+
on an intercepted network with `ACQ_BACKEND=sbx` (live).
63+
4564
## Consequences
4665

4766
- Agents can use `cf` for Cloud Foundry targeting and unauthenticated inspection.
4867
Authenticated operations should use direct HTTPS Cloud Foundry API calls until a
4968
live-tested path for authenticated stock `cf` commands exists.
5069
- The real token remains outside the sandbox; the sandbox may contain only a
5170
backend-generated placeholder.
71+
- The CA-trust kit must precede this kit on an intercepted network (the global
72+
bundle already orders `zscaler-ca-certificate` first; a second copy in
73+
`ACQ_EXTRA_KITS` is rejected by sbx as a duplicate kit name). If no CA kit
74+
precedes it, the startup install logs a warning and `cf` is absent until the
75+
order is fixed and the sandbox restarted.
5276
- The install currently supports Linux x86_64/amd64 and arm64/aarch64 release
5377
tarballs. Other architectures should either preinstall `cf` or add a pinned,
5478
integrity-checked install path before being supported.

‎integrations/isolation/acq-kits/cloud-gov/files/home/cloud-gov-configure-cf-auth.sh‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ set -eu
66
# parses AccessToken locally, so this script deliberately does not write a
77
# placeholder into ~/.cf/config.json and overclaim authenticated cf CLI support.
88

9+
# The install step puts cf in ~/.local/bin; startup shells may not have it on PATH.
10+
PATH="$HOME/.local/bin:$PATH"
11+
912
log() { printf '%s\n' "cloud-gov: $*" >&2; }
1013

1114
mkdir -p "$HOME/.cf"

‎integrations/isolation/acq-kits/cloud-gov/files/home/cloud-gov-install-cf-cli.sh‎

Lines changed: 24 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,22 @@ set -eu
44
# Install the Cloud Foundry CLI from a pinned upstream release tarball. The exact
55
# version and SHA-256 values are committed in this script so the install is
66
# reproducible and fails closed on upstream drift.
7+
#
8+
# Runs in the STARTUP phase as the agent user, never `phase: install`. The
9+
# download is HTTPS; on a network that intercepts TLS the CA-trust kit
10+
# (zscaler-ca-certificate) installs its CA in its own startup step, which kit
11+
# order runs before this one. An install-phase fetch runs at create time, before
12+
# that CA is trusted, and fails with curl exit 60. The binary goes in the agent's
13+
# ~/.local/bin, so no root step runs this agent-writable script. The agent can
14+
# replace that file; the SHA-256 check covers the download, not later tampering.
715

816
CF_CLI_VERSION="8.19.0"
917
CF_CLI_SHA256_X86_64="98268ab3134bb3a1c97ffce797b4e6d35590a82e006cd098ad7a29f0a5cae7d8"
1018
CF_CLI_SHA256_ARM64="454c29a44a51c8edc9696678403e2e40808357a397033af5a018e6ca8ee32117"
1119

20+
INSTALL_DIR="$HOME/.local/bin"
21+
PATH="$INSTALL_DIR:$PATH"
22+
1223
log() { printf '%s\n' "cloud-gov: $*" >&2; }
1324
sha256_of() {
1425
if command -v sha256sum >/dev/null 2>&1; then
@@ -61,23 +72,32 @@ esac
6172
work="$(mktemp -d)"
6273
trap 'rm -rf "$work"' EXIT INT TERM
6374
url="https://github.com/cloudfoundry/cli/releases/download/v${CF_CLI_VERSION}/${asset}"
64-
curl -fsSL "$url" -o "$work/cf-cli.tgz"
75+
curl_rc=0
76+
curl -fsSL "$url" -o "$work/cf-cli.tgz" || curl_rc=$?
77+
if [ "$curl_rc" -ne 0 ]; then
78+
log "download of $url failed (curl exit $curl_rc); cf not installed"
79+
if [ "$curl_rc" -eq 60 ]; then
80+
log "curl exit 60 means the TLS chain is untrusted: apply the CA-trust kit before this kit"
81+
fi
82+
exit 1
83+
fi
6584
got_sha="$(sha256_of "$work/cf-cli.tgz" || true)"
6685
if [ -z "$got_sha" ] || [ "$got_sha" != "$want_sha" ]; then
6786
log "CF CLI release SHA-256 mismatch (got ${got_sha:-none}, want $want_sha); refusing install"
6887
exit 1
6988
fi
7089

7190
tar -xzf "$work/cf-cli.tgz" -C "$work"
91+
mkdir -p "$INSTALL_DIR"
7292
if [ -x "$work/cf8" ]; then
73-
install -m 0755 "$work/cf8" /usr/local/bin/cf8
93+
install -m 0755 "$work/cf8" "$INSTALL_DIR/cf8"
7494
elif [ -x "$work/cf" ]; then
75-
install -m 0755 "$work/cf" /usr/local/bin/cf8
95+
install -m 0755 "$work/cf" "$INSTALL_DIR/cf8"
7696
else
7797
log "pinned CF CLI archive did not contain cf8 or cf executable"
7898
exit 1
7999
fi
80-
ln -sf /usr/local/bin/cf8 /usr/local/bin/cf
100+
ln -sf "$INSTALL_DIR/cf8" "$INSTALL_DIR/cf"
81101

82102
if command -v cf >/dev/null 2>&1; then
83103
log "installed $(cf version 2>/dev/null || printf 'cf CLI')"

‎integrations/isolation/acq-kits/cloud-gov/scripts/verify‎

Lines changed: 72 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,19 @@
44
#
55
# By default this runs offline checks only. Set RUN_ACQ=1 to create a throwaway
66
# sandbox and verify the CF CLI plus exact cloud.gov/docs network reachability.
7+
#
8+
# On a TLS-intercepting network (for example Zscaler) the CF CLI download only
9+
# works if the CA-trust kit is applied BEFORE this kit. The global kit bundle
10+
# already applies zscaler-ca-certificate first, so run on an intercepted network
11+
# without CA_KIT to reproduce that create. CA_KIT is only for a bundle that has
12+
# NO CA-trust kit: sbx rejects a second kit with the same name as a bundled one
13+
# ("duplicate kit name"), so do not point it at a kit the bundle already has.
14+
#
15+
# The CA-before-fetch failure is specific to the sbx file-drop path: msb trusts
16+
# host CAs natively (--trust-host-cas), so an msb run cannot reproduce it. Set
17+
# ACQ_BACKEND=sbx (or msb) to pass `--backend` to acq for the sandbox create,
18+
# exec, and rm calls without changing your persisted default backend. Unset uses
19+
# acq's own selection.
720

821
set -uo pipefail
922

@@ -14,6 +27,20 @@ WORK="$(mktemp -d "${TMPDIR:-/tmp}/cloud-gov-verify.XXXXXX")"
1427
CREATE_LOG="$WORK/create.log"
1528
KEEP="${KEEP:-0}"
1629
RUN_ACQ="${RUN_ACQ:-0}"
30+
CA_KIT="${CA_KIT:-}"
31+
ACQ_BACKEND="${ACQ_BACKEND:-}"
32+
ACQ_BACKEND_ARGS=()
33+
case "$ACQ_BACKEND" in
34+
"") ;;
35+
sbx|msb) ACQ_BACKEND_ARGS=(--backend "$ACQ_BACKEND") ;;
36+
*)
37+
printf 'ACQ_BACKEND must be sbx or msb (got: %s)\n' "$ACQ_BACKEND" >&2
38+
exit 2
39+
;;
40+
esac
41+
# Bash 3.2 (macOS) treats an empty array as unset under `set -u`; the +"..."
42+
# form expands to nothing when no backend was requested.
43+
acq_b() { acq ${ACQ_BACKEND_ARGS[@]+"${ACQ_BACKEND_ARGS[@]}"} "$@"; }
1744

1845
pass=0
1946
fail=0
@@ -27,12 +54,12 @@ cleanup() {
2754
printf '\nKEEP=1 set; leaving sandbox %s and %s in place.\n' "$SBX_NAME" "$WORK" >&2
2855
return
2956
fi
30-
acq rm "$SBX_NAME" >/dev/null 2>&1 || true
57+
acq_b rm "$SBX_NAME" >/dev/null 2>&1 || true
3158
rm -rf "$WORK" >/dev/null 2>&1 || true
3259
}
3360
trap cleanup EXIT INT TERM
3461

35-
in_acq() { acq exec "$SBX_NAME" -- sh -c "$1" </dev/null 2>/dev/null || true; }
62+
in_acq() { acq_b exec "$SBX_NAME" -- sh -c "$1" </dev/null 2>/dev/null || true; }
3663

3764
info "0. Offline preconditions"
3865
if [ -f "$KIT_DIR/spec.yaml" ]; then
@@ -66,6 +93,25 @@ else
6693
skip "bash not on PATH - skipped shell parse checks"
6794
fi
6895

96+
info "0b. CF CLI fetch ordering"
97+
if ! python3 -c 'import yaml' >/dev/null 2>&1; then
98+
skip "fetch-ordering check needs python3 + pyyaml"
99+
elif python3 - "$KIT_DIR/spec.yaml" <<'PY'
100+
import sys
101+
import yaml
102+
103+
spec = yaml.safe_load(open(sys.argv[1]))
104+
for cmd in spec.get("commands", []):
105+
if "cloud-gov-install-cf-cli.sh" in " ".join(cmd["command"]):
106+
sys.exit(0 if cmd.get("phase") == "startup" else 1)
107+
sys.exit(1)
108+
PY
109+
then
110+
ok "CF CLI fetch runs in startup (after CA trust), not install"
111+
else
112+
bad "CF CLI fetch must run in a startup phase so CA trust is available first"
113+
fi
114+
69115
info "1. Auth placeholder guard"
70116
AUTH_SCRIPT="$KIT_DIR/files/home/cloud-gov-configure-cf-auth.sh"
71117
AUTH_PATH="$(mktemp -d "${TMPDIR:-/tmp}/cloud-gov-auth-path.XXXXXX")"
@@ -128,6 +174,7 @@ docs.cloudfoundry.org:443
128174
cli.cloudfoundry.org:443
129175
github.com:443
130176
objects.githubusercontent.com:443
177+
release-assets.githubusercontent.com:443
131178
HOSTS
132179
python3 - "$KIT_DIR/spec.yaml" >"$ACTUAL_HOSTS" <<'PY'
133180
import sys
@@ -205,10 +252,24 @@ else
205252
fi
206253

207254
info "5. Create sandbox with the kit"
208-
printf ' creating %s (workspace %s)...\n' "$SBX_NAME" "$WORK"
209-
# ACQ_EXTRA_KITS bypasses acq's interactive configured-kit picker.
210-
if ACQ_EXTRA_KITS="$KIT_DIR" acq create --name "$SBX_NAME" opencode "$WORK" >"$CREATE_LOG" 2>&1; then
255+
printf ' creating %s (workspace %s, backend %s)...\n' "$SBX_NAME" "$WORK" "${ACQ_BACKEND:-default}"
256+
# ACQ_EXTRA_KITS bypasses acq's interactive configured-kit picker. It is
257+
# whitespace-separated and ordered: the CA kit (if any) must come first so its
258+
# startup step trusts the intercepting CA before this kit fetches the CF CLI.
259+
EXTRA_KITS="$KIT_DIR"
260+
if [ -n "$CA_KIT" ]; then
261+
EXTRA_KITS="$CA_KIT $KIT_DIR"
262+
printf ' CA kit first: %s\n' "$CA_KIT"
263+
fi
264+
if ACQ_EXTRA_KITS="$EXTRA_KITS" acq_b create --name "$SBX_NAME" opencode "$WORK" >"$CREATE_LOG" 2>&1; then
211265
ok "sandbox created with cloud-gov kit"
266+
# acq names the backend that actually ran (for example `acq(msb): ...`); show it
267+
# so a run is never cited as sbx evidence when it ran on msb.
268+
used="$(grep -oE 'acq\((sbx|msb)\)' "$CREATE_LOG" | head -1)"
269+
printf ' backend in create log: %s\n' "${used:-<not stated>}"
270+
if [ -n "$ACQ_BACKEND" ] && [ "$used" != "acq($ACQ_BACKEND)" ]; then
271+
bad "requested backend $ACQ_BACKEND but create log reports ${used:-no backend}"
272+
fi
212273
else
213274
bad "acq create failed"
214275
sed 's/^/ | /' "$CREATE_LOG" >&2
@@ -217,6 +278,12 @@ fi
217278

218279
info "6. CF CLI installed"
219280
cf_version="$(in_acq 'cf version')"
281+
if [ -z "$cf_version" ]; then
282+
# A bare non-login exec may lack ~/.local/bin; retry so the failure message
283+
# says whether cf is missing or only off PATH.
284+
cf_version="$(in_acq 'PATH="$HOME/.local/bin:$PATH" cf version')"
285+
[ -n "$cf_version" ] && printf ' note: cf is installed but ~/.local/bin is not on this exec PATH\n'
286+
fi
220287
printf ' %s\n' "${cf_version:-<no output>}"
221288
case "$cf_version" in
222289
*"cf version"*) ok "cf CLI reports a version" ;;

0 commit comments

Comments
 (0)