summaryrefslogtreecommitdiff
path: root/bugs/option_to_not_use_paramiko__63__.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'bugs/option_to_not_use_paramiko__63__.mdwn')
-rw-r--r--bugs/option_to_not_use_paramiko__63__.mdwn11
1 files changed, 0 insertions, 11 deletions
diff --git a/bugs/option_to_not_use_paramiko__63__.mdwn b/bugs/option_to_not_use_paramiko__63__.mdwn
deleted file mode 100644
index deabafe..0000000
--- a/bugs/option_to_not_use_paramiko__63__.mdwn
+++ /dev/null
@@ -1,11 +0,0 @@
-Could we please have an option to force obnam to not use paramiko but instead openssh or libssh2-1? I'd like to get around the whole .ssh/config debacle and other nasty surprises I had when using duplicity, and keep using known and trusted software.
-
----
-
-Switching away from paramiko will require a fair amount of work. For other reasons, I'm going to be looking at doing so, but it's not just a matter of "using openssh". There is, for example, no Python API for openssh. There's other Python APIs for dealing with ssh, which I'm going to investigate, but it's not a one-evening-hack kind of thing.
-
-Also, given that ~/.ssh/config is a configuration file for openssh, and not all programs that use the ssh protocol, I think it's unrealistic to require every program to obey it.
-
-If and when I switch Obnam away from paramiko, it will not be an optional thing. Having to support multiple ways of doing ssh is unnecessary complexity, so I will only support one implementation at a time. Sorry. As such, I'll mark this bug as [[done]].
-
---liw