docs: temporarily remove boringcrypto references

This commit removes boringcrypto references until #64 is resolved.
grafana · Mar 28, 2024 · 92f9886 · 92f9886
1 parent ea77e2b
commit 92f9886
Show file tree

Hide file tree

Showing 2 changed files with 33 additions and 0 deletions.
diff --git a/docs/sources/about.md b/docs/sources/about.md
@@ -188,9 +188,12 @@ You should run Flow mode when:
 [vault]: ./reference/components/remote.vault/
 
 -->
+
+<!--
 ### BoringCrypto
 
 [BoringCrypto][] is an **EXPERIMENTAL** feature for building {{< param "PRODUCT_NAME" >}}
 binaries and images with BoringCrypto enabled. Builds and Docker images for Linux arm64/amd64 are made available.
 
 [BoringCrypto]: https://pkg.go.dev/crypto/internal/boring
+-->
diff --git a/docs/sources/reference/config-blocks/http.md b/docs/sources/reference/config-blocks/http.md
@@ -88,6 +88,7 @@ The `cipher_suites` argument determines what cipher suites to use.
 If you don't provide cipher suite, a default list is used.
 The set of cipher suites specified may be from the following:
 
+<!--
 | Cipher                                          | Allowed in `boringcrypto` builds |
 | ----------------------------------------------- | -------------------------------- |
 | `TLS_RSA_WITH_AES_128_CBC_SHA`                  | no                               |
@@ -107,17 +108,46 @@ The set of cipher suites specified may be from the following:
 | `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`         | yes                              |
 | `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`   | no                               |
 | `TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` | no                               |
+-->
+| Cipher                                          |
+| ----------------------------------------------- |
+| `TLS_RSA_WITH_AES_128_CBC_SHA`                  |
+| `TLS_RSA_WITH_AES_256_CBC_SHA`                  |
+| `TLS_RSA_WITH_AES_128_GCM_SHA256`               |
+| `TLS_RSA_WITH_AES_256_GCM_SHA384`               |
+| `TLS_AES_128_GCM_SHA256`                        |
+| `TLS_AES_256_GCM_SHA384`                        |
+| `TLS_CHACHA20_POLY1305_SHA256`                  |
+| `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`          |
+| `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`          |
+| `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`            |
+| `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`            |
+| `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`       |
+| `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`       |
+| `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`         |
+| `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`         |
+| `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`   |
+| `TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256` |
+
 
 The `curve_preferences` argument determines the set of elliptic curves to prefer during a handshake in preference order.
 If not provided, a default list is used.
 The set of elliptic curves specified may be from the following:
 
+<!--
 | Curve       | Allowed in `boringcrypto` builds |
 | ----------- | -------------------------------- |
 | `CurveP256` | yes                              |
 | `CurveP384` | yes                              |
 | `CurveP521` | yes                              |
 | `X25519`    | no                               |
+-->
+| Curve       |
+| ----------- |
+| `CurveP256` |
+| `CurveP384` |
+| `CurveP521` |
+| `X25519`    |
 
 The `min_version` and `max_version` arguments determine the oldest and newest TLS version that's acceptable from clients.
 If you don't provide the min and max TLS version, a default value is used.