diff options
| author | Joey Hess <joey@kitenet.net> | 2014-11-18 18:58:47 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-11-18 18:58:47 -0400 |
| commit | 95fda710cb2c7637ab4b7cc437dfa4e1d1cef831 (patch) | |
| tree | cd09f2129298ceb770c1e6ed68c89254b6a964e2 | |
| parent | 7299cd73206c47b27a0a80ae9810ca4506942b11 (diff) | |
update
| -rw-r--r-- | doc/security.mdwn | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/security.mdwn b/doc/security.mdwn index bcbc28ed..0bc4c6e2 100644 --- a/doc/security.mdwn +++ b/doc/security.mdwn @@ -6,13 +6,13 @@ The only trusted machine is the laptop where you run `propellor --spin` to connect to a remote host. And that one only because you have a ssh key or login password to the host. -Since the hosts propellor deploys are not trusted by the central git -repository, they have to use git:// or http:// to pull from the central -git repository, rather than ssh://. +Since the hosts propellor deploys do not trust the central git repository, +and it doesn't trust them, it's normal to use git:// or http:// to pull +from the central git repository, rather than ssh://. -So, to avoid a MITM attack, propellor checks that any commit it fetches -from origin is gpg signed by a trusted gpg key, and refuses to deploy it -otherwise. +Since propellor doesn't trust the central git repository, it checks +that any commit it fetches from it is gpg signed by a trusted gpg key, +and refuses to deploy it otherwise. That is only done when privdata/keyring.gpg exists. To set it up: |