path: root/doc/security
diff options
author 06:40:33 +0000
committeradmin2014-08-30 06:40:33 +0000
commit240cbe4c61c5831d473ac8c0355fc21d9b7ff647 (patch)
treeeaaa0948cf89bc3b3a3680650d8337fec4e27447 /doc/security
parent8a4f2aa0f50c87583fc31b56ec79f29189d096f7 (diff)
Added a comment: Remote host fails to connect
Diffstat (limited to 'doc/security')
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/security/comment_3_91876d995c40a24858bce61a749a3c16._comment b/doc/security/comment_3_91876d995c40a24858bce61a749a3c16._comment
new file mode 100644
index 00000000..4d75842d
--- /dev/null
+++ b/doc/security/comment_3_91876d995c40a24858bce61a749a3c16._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username=""
+ nickname="Arnaud"
+ subject="Remote host fails to connect"
+ date="2014-08-30T06:40:33Z"
+ content="""
+Makes sense of course, but the message one gets when doing that is a bit misleading.
+I ran into another issue: propellor deploys itself to remote host, but then the propellor instance run on remote host cannot read the remote git repo, because:
+1. the host key is not initially present in root's known_hosts, then
+2. the user's (root) public key is unknown to the remote git repo, in my case, and the URL used is which implies connection goes through SSH
+I am puzzled: Does this mean I should add some for use by the remote host deployed to? This does not make sense so there should be another way... If I change the origin url to use https, then I cannot push locally anymore.
+Thanks for your help