You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Refactor USWDS alert component into a shortcode. (#4027)
* Add alert shortcode, remove component.
This is a cleaner syntax for alerts.
* move low-system banners to the top of pages
---------
Co-authored-by: Greg Walker <[email protected]>
Copy file name to clipboardexpand all lines: pages/general-information-and-resources/tech-policies/gsa-pages.md
+6-3
Original file line number
Diff line number
Diff line change
@@ -9,16 +9,20 @@ redirect_from:
9
9
---
10
10
# Authority to Use (ATU) Process
11
11
12
-
{% include "alert.html" level:"warning" content: "This guide is for **GSA Employees or Contractors** operating a GSA Website" %}
12
+
{% alert "", "warning" %}
13
+
This guide is for **GSA Employees or Contractors** operating a GSA Website
14
+
{% endalert %}
13
15
14
16
"GSA Pages" is a **GSA only Authority to Operate (ATO)** of [cloud.gov's FEDRAMP Authorization](https://marketplace.fedramp.gov/products/F1607067912) of their [cloud.gov Pages](https://pages.cloud.gov) service. As such, it adds the Security Controls around the source code and contents for the website (e.g. Github). It provides **GSA employees** with a fast and secure approach to getting a web presence for your projects/programs.
15
17
18
+
{% include "low-system.html" %}
19
+
16
20
## Launching a Website at GSA
17
21
- Confirm your website is listed on [https://touchpoints.digital.gov](https://touchpoints.digital.gov)
18
22
- if not listed, [complete a new website request](https://touchpoints.app.cloud.gov/admin/websites/new)
19
23
- Follow [GSA's Digital Lifecycle Program Guide](https://insite.gsa.gov/employee-resources/communications/websites/strategy-policy-and-standards/digital-lifecycle-program)
20
24
21
-
Prior to standing up a site with GSA Pages, you will need a domain or subdomain. To obtain a new domain or subdomain with GSA, approval is needed by GSA Leadership and Office of Customer Experience in Touchpoints.
25
+
Prior to standing up a site with GSA Pages, you will need a domain or subdomain. To obtain a new domain or subdomain with GSA, approval is needed by GSA Leadership and Office of Customer Experience in Touchpoints.
Copy file name to clipboardexpand all lines: pages/tools/airtable.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@ redirect_from:
8
8
9
9
[Airtable](https://airtable.com/) is a cloud-based tool that allows users to organize their workflow, data, and records in a flexible and visually appealing way without the need for any coding. **Licenses are now available for all TTS employees**.
10
10
11
+
{% include "low-system.html" %}
12
+
11
13
### How to Request a License
12
14
13
15
TTS employees can obtain a free, read-only license by making a request to [email protected]. Read-only users can view but not edit or comment on anything in the workspace, base, or interface.
@@ -31,4 +33,3 @@ Tech Operations serves as the enterprise admins and can override all permissions
31
33
32
34
Airtable has an Authorization to Operate (ATO) at FIPS 199 Low Impact Level; therefore, sensitive data such as personal identifiable information (PII) and controlled unclassified information (CUI) is not allowed. In addition, TTS is only authorized to give view-only access to partner agencies due the uncertainty of their ATO statuses. Other GSA Components are covered under the GSA ATO but should procure their own licenses. More detailed privacy and security guidance can be found [here](https://airtable.com/appQbn3D4GMM8SD0O/pagaDV7VWDAjLdAC0).
Copy file name to clipboardexpand all lines: pages/tools/git-signing.md
+22-28
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ questions:
7
7
cSpell: ignore allstar
8
8
---
9
9
10
-
TTS strongly encourages all git commits to be cryptographically signed. A cryptographic signature is a strong indication that that the work was authored by the person claiming to have authored it and that it has not been changed since they authored it.
10
+
TTS strongly encourages all git commits to be cryptographically signed. A cryptographic signature is a strong indication that that the work was authored by the person claiming to have authored it and that it has not been changed since they authored it.
11
11
12
12
## Signing requirements
13
13
@@ -19,13 +19,13 @@ We strongly recommend [using a password manager]({% page "general-information-an
19
19
20
20
### Using GitHub on the web does not require signing
21
21
22
-
If you only use GitHub from the web interface, you do not need to configure signing. The web interface automatically signs your work for you.
22
+
If you only use GitHub from the web interface, you do not need to configure signing. The web interface automatically signs your work for you.
23
23
24
24
If you do any work with git repos on your local computer, however, you need to set up commit signing.
25
25
26
26
## 1. Create your keys
27
27
28
-
Cryptographically signing your commits requires creating a pair of keys. One of them is your private key, and you must keep it secret. Think of it much like a password – only you should ever have access to it. Anyone with this private key can sign with your identity, so protect it!
28
+
Cryptographically signing your commits requires creating a pair of keys. One of them is your private key, and you must keep it secret. Think of it much like a password – only you should ever have access to it. Anyone with this private key can sign with your identity, so protect it!
29
29
30
30
The other key is your public key, and it may be shared widely. In fact, in order to verify your signed commits, others will need access to your public key.
31
31
@@ -34,12 +34,9 @@ The other key is your public key, and it may be shared widely. In fact, in order
34
34
ssh-keygen -t ed25519 -C "[YOUR EMAIL]@gsa.gov"
35
35
```
36
36
37
-
{%
38
-
include "alert.html"
39
-
level: "info"
40
-
heading: "About the cryptographic algorithm"
41
-
content: "We recommend using the ED25519 algorithm, a particular configuration of the EdDSA algorithm family. This is stronger than the default DSA family. This algorithm may not be appropriate for all cases, however, as it is newer and is not as widely supported yet. git and GitHub both support the ED25519 algorithm."
42
-
%}
37
+
{% alert "About the cryptographic algorithm" %}
38
+
We recommend using the ED25519 algorithm, a particular configuration of the EdDSA algorithm family. This is stronger than the default DSA family. This algorithm may not be appropriate for all cases, however, as it is newer and is not as widely supported yet. git and GitHub both support the ED25519 algorithm.
39
+
{% endalert %}
43
40
44
41
2. You will be asked where to save the key: `Enter file in which to save the key (/Users/[username]/.ssh/[key name])`
45
42
- If you are using a password manager like KeePassXC, it will be more convenient if you change this path. Type `/Users/[username]/Desktop/git-signing-key`. (`[username]` is your login name on your laptop.)
- If you already have an entry in KeePassXC for your GitHub account, double-click it to open it in editing mode.
68
-
- Otherwise, create a new entry using the **+ (Add a new entry)** button in the top bar.
65
+
- Otherwise, create a new entry using the **+ (Add a new entry)** button in the top bar.
69
66
2. On the left side of the editing window, click the **Advanced** button to navigate to the Advanced screen.
70
-
3. Scroll down to the section titled **Attachments**.
67
+
3. Scroll down to the section titled **Attachments**.
71
68
4. Click the **Add** button on the right side, and use the file browser to find the key you created above. Look for the files called `git-signing-key` and `git-signing-key.pub`, and add them both.
@@ -76,9 +73,9 @@ Once you have added the files to KeePassXC, you can delete them from your deskto
76
73
77
74
#### 3. Tell KeePassXC that these are keys
78
75
1. Double-click to edit the entry that has the keys attached.
79
-
2. Click the button that says **SSH Agent** on the left sidebar.
80
-
3. Look for the section labeled **Private key** that includes a drop-down box labeled **Attachment**.
81
-
3. Click in the drop-down box and select the private key you added as an attachment. The sections below should then populate with information such as "Fingerprint," "Comment," and "Public key."
76
+
2. Click the button that says **SSH Agent** on the left sidebar.
77
+
3. Look for the section labeled **Private key** that includes a drop-down box labeled **Attachment**.
78
+
3. Click in the drop-down box and select the private key you added as an attachment. The sections below should then populate with information such as "Fingerprint," "Comment," and "Public key."
82
79
-**IMPORTANT:** Use the _private_ key, the one that is just `git-signing-key`, not the public key!
2. You will be prompted to enter the password you created for your key.
96
+
2. You will be prompted to enter the password you created for your key.
100
97
- Using the `--apple-use-keychain` option will store your password securely in the macOS keychain, where it will only be available when you are logged into your computer.
101
98
102
99
#### Linux
@@ -111,7 +108,7 @@ You may be required to enter the password associated with your key every time yo
111
108
112
109
## 3. Configure git to sign commits
113
110
114
-
By default, git uses a format called GPG for commit signing. However, GPG keys are more difficult to create and manage, so we recommend SSH keys, which is what you created in the previous steps.
111
+
By default, git uses a format called GPG for commit signing. However, GPG keys are more difficult to create and manage, so we recommend SSH keys, which is what you created in the previous steps.
115
112
116
113
1. Tell git to use SSH keys instead of GPG keys. In a terminal, enter this command:
Git may be configured to sign your commits, but GitHub will mark them as `Unverified` and they will not be accepted under the Allstar policy.
174
+
Git may be configured to sign your commits, but GitHub will mark them as `Unverified` and they will not be accepted under the Allstar policy.
178
175
179
-
In order to verify your signed commits, you must associate the public key with your GitHub account.
180
-
1. Go to your [GitHub SSH and GPG keys settings page]({% link "https://github.com/settings/keys" %}).
176
+
In order to verify your signed commits, you must associate the public key with your GitHub account.
177
+
1. Go to your [GitHub SSH and GPG keys settings page]({% link "https://github.com/settings/keys" %}).
181
178
2. Follow the [instructions provided by GitHub]({% link "https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account" %}) to add your signing key.
182
179
183
-
{%
184
-
include "alert.html"
185
-
level: "warning"
186
-
heading: "Add a signing key, not an authentication key"
187
-
content: "When you add your key to GitHub, it presents a drop-down for key types. By default, it will add an authentication key. Be sure to click the drop-down and select the signing key option instead."
188
-
%}
180
+
{% alert "Add a signing key, not an authentication key", "warning" %}
181
+
When you add your key to GitHub, it presents a drop-down for key types. By default, it will add an authentication key. Be sure to click the drop-down and select the signing key option instead.
0 commit comments