From d55e34970ba48832683b2ac2c98755829859bd08 Mon Sep 17 00:00:00 2001 From: Simon Fels Date: Wed, 28 Aug 2024 16:11:15 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Keirthana T S --- explanation/cryptography/crypto_stream_gateway.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/explanation/cryptography/crypto_stream_gateway.md b/explanation/cryptography/crypto_stream_gateway.md index db5f8a4b..0468549a 100644 --- a/explanation/cryptography/crypto_stream_gateway.md +++ b/explanation/cryptography/crypto_stream_gateway.md @@ -9,15 +9,15 @@ Anbox Streaming Gateway is using cryptographic technology for: ## TLS transport encryption -All network endpoints exposed by the Anbox Stream Gateway are secured with TLS using an 4096 bit RSA key. The Anbox Stream Gateway strictly enforces TLS 1.3 or better and does not provide backward compatibility with older TLS versions. +All network endpoints exposed by the Anbox Stream Gateway are secured with TLS using an 4096 bit RSA key. The Anbox Stream Gateway strictly enforces TLS 1.3 or later and does not provide backward compatibility with older TLS versions. ## Mutual TLS based authentication -In order to exchange messages with the Anbox Stream Agent through the [NATS](https://nats.io/) message queue, the Anbox Stream Gateway uses a CA certificated signed by a 4096 bit RSA key to ensure trust with the NATS server. +To exchange messages with the Anbox Stream Agent through the [NATS](https://nats.io/) message queue, the Anbox Stream Gateway uses a CA certificate signed by a 4096 bit RSA key to ensure trust with the NATS server. ## Token based authentication -Users can generate API tokens to authenticate with the HTTP API provided by the Anbox Stream Gateway. For the API tokens a scope-limited [Macaroon](http://theory.stanford.edu/~ataly/Papers/macaroons.pdf) is used. The token is signed with a [HMAC](https://www.okta.com/identity-101/hmac/) using SHA-256 (HS256) and a 64 byte secret key. The [`macaroon.New`](https://pkg.go.dev/gopkg.in/macaroon.v2@v2.1.0#New) method is used internally to generate the JWT token. +Users can generate API tokens to authenticate with the HTTP API provided by the Anbox Stream Gateway. For the API tokens, a scope-limited [Macaroon](http://theory.stanford.edu/~ataly/Papers/macaroons.pdf) is used. The token is signed with a [HMAC](https://www.okta.com/identity-101/hmac/) using SHA-256 (HS256) and a 64 byte secret key. The [`macaroon.New`](https://pkg.go.dev/gopkg.in/macaroon.v2@v2.1.0#New) method is used internally to generate the [JWT](https://jwt.io/) token. ## Packages used