From 27f77506c40588f8372184b81868b23b072c9c11 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fran=C3=A7ois=20Samin?= Date: Fri, 23 Oct 2020 16:49:43 +0200 Subject: [PATCH] doc: fix markdown linsk in design documentation --- DESIGN.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DESIGN.md b/DESIGN.md index 4ca5316..16d26c2 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -21,7 +21,7 @@ system user, and same goes for the group private keys. This way, even if the code is tricked to allow access when it shouldn't have (flawed logic or bug), then the OS will still deny reading the key file. -This concept has been explained in the ([https://www.ovh.com/blog/the-bastion-part-3-security-at-the-core/](Blog Post #3 - Security at the Core)) +This concept has been explained in the [Blog Post #3 - Security at the Core](https://www.ovh.com/blog/the-bastion-part-3-security-at-the-core/). ## Zero trust between portions of code running at different permission levels @@ -37,4 +37,4 @@ run under perl tainted mode. Helpers communicate back their result using JSON, which is then read from the plugin (the unprivileged portion of code), and parsed. -This concept has been explained in the ([https://www.ovh.com/blog/the-bastion-part-3-security-at-the-core/](Blog Post #3 - Security at the Core)) +This concept has been explained in the [Blog Post #3 - Security at the Core](https://www.ovh.com/blog/the-bastion-part-3-security-at-the-core/).