ovh/the-bastion
1
1
Fork 0
mirror of https://github.com/ovh/the-bastion.git synced 2025-01-11 01:41:39 +08:00
Code Issues Projects Releases Packages Wiki Activity

Merge pull request #15 from ovh/doc/fix/design

Browse source 
doc: fix markdown links in design documentation
This commit is contained in:
Stéphane Lesimple 2020-10-26 09:10:04 +01:00 committed by GitHub
commit db98fa962b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
DESIGN.md
View file

@ -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/).