CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fixed typo: specifc -> specific, varibles -> variables, idomatic -> idiomatic. (#1421)

Browse Source
This commit is contained in:
xuwhao authored and GitHub committed 2021-07-27 19:36:42 -04:00
1 parent acede17909
commit ade67e6bb5
3 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx
+2 -2
View File
@@ -7,7 +7,7 @@ description: How to manage SSH proxy configuration with Boundary
# SSH ProxyCommand Workflow
The most common pattern for using Boundary to SSH is with the built-in `boundary connect ssh` command. However,
there are more idomatic approaches that can be employed to make Boundary transparent to users, and at the same
there are more idiomatic approaches that can be employed to make Boundary transparent to users, and at the same
time simplify common developer and operator workflows. Using `ProxyCommand` to execute a proxy when invoking the
SSH client is a common practice. In this workflow, we'll cover configuring your SSH client to execute the
`boundary` command, enabling a simplified SSH workflow that leverages Boundary's authenticated proxy for accessing
@@ -24,7 +24,7 @@ Host ttcp_*
The `ProxyCommand` tells the SSH client to invoke `boundary connect`. We are passing the `-exec nc` flag to
`boundary connect` to wrap [netcat](http://netcat.sourceforge.net/), and then pass the `boundary.ip` and `boundary.port`
varibles as arguments to `nc`. This allows us to proxy our SSH connection through a local netcat tunnel that's
variables as arguments to `nc`. This allows us to proxy our SSH connection through a local netcat tunnel that's
managed as a Boundary session.
When you run `ssh ttcp_1234567890` (example target ID), SSH will invoke `boundary connect`, and will tunnel the traffic through
website/content/docs/configuration/kms/aead.mdx
+1 -1
View File
@@ -2,7 +2,7 @@
layout: docs
page_title: AEAD - Configuration
description: |-
The AEAD KMS configures AEAD-specifc parameters.
The AEAD KMS configures AEAD-specific parameters.
---
~> This is mostly used for `dev` workflows or testing. The key will be exposed
website/content/docs/configuration/kms/index.mdx
+1 -1
View File
@@ -2,7 +2,7 @@
layout: docs
page_title: KMS - Configuration
description: |-
The KMS stanza configures KMS-specifc parameters.
The KMS stanza configures KMS-specific parameters.
---
# `kms` Stanza