Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restoring the example policies for blocking sha1 #9677

Merged
merged 3 commits into from
Aug 17, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions website/pages/api-docs/secret/transit/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -885,9 +885,9 @@ supports signing.
only for legacy applications. Signing using SHA-1 can be blocked by operators by
assigning the following policy corresponding to a named key:

```
{
]
```hcl
path "/transit/sign/:name/sha1" {
capabilities = ["deny"]
}
```

Expand Down Expand Up @@ -1040,9 +1040,9 @@ data.
be blocked by operators by assigning the following policy corresponding to a
named key:

```
{
]
```hcl
path "/transit/verify/:name/sha1" {
capabilities = ["deny"]
}
```

Expand Down