From 7c1d375182930e80561322f47a2dc694c31f2f29 Mon Sep 17 00:00:00 2001
From: timvisee <tim@visee.me>
Date: Fri, 30 Jun 2023 15:19:09 +0200
Subject: [PATCH 1/5] Add warning explaining users must protect internal gRPC
 channels

---
 qdrant-landing/content/documentation/guides/security.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/qdrant-landing/content/documentation/guides/security.md b/qdrant-landing/content/documentation/guides/security.md
index 8d08b5aa1..9681fc7e8 100644
--- a/qdrant-landing/content/documentation/guides/security.md
+++ b/qdrant-landing/content/documentation/guides/security.md
@@ -60,6 +60,8 @@ qdrant_client = QdrantClient(
 )
 ```
 
+<aside role="alert">Internal communication channels are **never** protected by an API key. It (internal gRPC) uses port 6335 by default if running in distributed mode. You must make sure this port is not publicly reachable and can only be used for node communication or bad things will happen. In Qdrant Cloud and the Qdrant Helm chart access to this is disabled by default.</aside>
+
 ## TLS
 
 *Available as of v1.2.0*

From 17e119ad6e343d783c0239d5dc2258cdbb660bb6 Mon Sep 17 00:00:00 2001
From: timvisee <tim@visee.me>
Date: Fri, 30 Jun 2023 15:20:26 +0200
Subject: [PATCH 2/5] Add open to everyone note

---
 qdrant-landing/content/documentation/guides/security.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/qdrant-landing/content/documentation/guides/security.md b/qdrant-landing/content/documentation/guides/security.md
index 9681fc7e8..d237a70bc 100644
--- a/qdrant-landing/content/documentation/guides/security.md
+++ b/qdrant-landing/content/documentation/guides/security.md
@@ -9,6 +9,10 @@ aliases:
 
 There are various ways to secure your own Qdrant instance.
 
+By default no security measures are enabled for your own Qdrant instances and
+they are open to everyone. Read this page carefully on how to secure your
+instance for production use.
+
 ## Authentication
 
 *Available as of v1.2.0*

From 4084386a13a3000011ac323ec5e62fc4cc9bf7ba Mon Sep 17 00:00:00 2001
From: timvisee <tim@visee.me>
Date: Fri, 30 Jun 2023 15:24:59 +0200
Subject: [PATCH 3/5] Do not use markdown in alert

---
 qdrant-landing/content/documentation/guides/security.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qdrant-landing/content/documentation/guides/security.md b/qdrant-landing/content/documentation/guides/security.md
index d237a70bc..d7fb4abad 100644
--- a/qdrant-landing/content/documentation/guides/security.md
+++ b/qdrant-landing/content/documentation/guides/security.md
@@ -64,7 +64,7 @@ qdrant_client = QdrantClient(
 )
 ```
 
-<aside role="alert">Internal communication channels are **never** protected by an API key. It (internal gRPC) uses port 6335 by default if running in distributed mode. You must make sure this port is not publicly reachable and can only be used for node communication or bad things will happen. In Qdrant Cloud and the Qdrant Helm chart access to this is disabled by default.</aside>
+<aside role="alert">Internal communication channels are <strong>never</strong> protected by an API key. It (internal gRPC) uses port 6335 by default if running in distributed mode. You must make sure this port is not publicly reachable and can only be used for node communication or bad things will happen. In Qdrant Cloud and the Qdrant Helm chart access to this is disabled by default.</aside>
 
 ## TLS
 

From 0ffce5b310ba5ef02ace502f2dc01725c3a0ded9 Mon Sep 17 00:00:00 2001
From: David Sertic <davidmyriel@gmail.com>
Date: Thu, 6 Jul 2023 14:31:06 +0200
Subject: [PATCH 4/5] Update
 qdrant-landing/content/documentation/guides/security.md

---
 qdrant-landing/content/documentation/guides/security.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qdrant-landing/content/documentation/guides/security.md b/qdrant-landing/content/documentation/guides/security.md
index d7fb4abad..8cb78b4d9 100644
--- a/qdrant-landing/content/documentation/guides/security.md
+++ b/qdrant-landing/content/documentation/guides/security.md
@@ -64,7 +64,7 @@ qdrant_client = QdrantClient(
 )
 ```
 
-<aside role="alert">Internal communication channels are <strong>never</strong> protected by an API key. It (internal gRPC) uses port 6335 by default if running in distributed mode. You must make sure this port is not publicly reachable and can only be used for node communication or bad things will happen. In Qdrant Cloud and the Qdrant Helm chart access to this is disabled by default.</aside>
+<aside role="alert">Internal communication channels are <strong>never</strong> protected by an API key. Internal gRPC uses port 6335 by default if running in distributed mode. You must ensure that this port is not publicly reachable and can only be used for node communication. By default, this setting is disabled for Qdrant Cloud and the Qdrant Helm chart.</aside>
 
 ## TLS
 

From 3dcd9efb4e498ba061409b8ad3c2bd564566d231 Mon Sep 17 00:00:00 2001
From: David Sertic <62056091+davidmyriel@users.noreply.github.com>
Date: Thu, 6 Jul 2023 14:42:53 +0200
Subject: [PATCH 5/5] fix security banners

---
 qdrant-landing/content/documentation/guides/security.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/qdrant-landing/content/documentation/guides/security.md b/qdrant-landing/content/documentation/guides/security.md
index 8cb78b4d9..70afa9ca3 100644
--- a/qdrant-landing/content/documentation/guides/security.md
+++ b/qdrant-landing/content/documentation/guides/security.md
@@ -7,11 +7,10 @@ aliases:
 
 # Security
 
-There are various ways to secure your own Qdrant instance.
 
-By default no security measures are enabled for your own Qdrant instances and
-they are open to everyone. Read this page carefully on how to secure your
-instance for production use.
+
+Please read this page carefully. Although there are various ways to secure your Qdrant instances, **they are unsecured by default**. 
+You need to enable security measures before production use. Otherwise, they are completely open to anyone
 
 ## Authentication