{"id":168,"date":"2017-02-17T21:29:45","date_gmt":"2017-02-17T20:29:45","guid":{"rendered":"http:\/\/xpam.pl\/blog\/?p=168"},"modified":"2017-02-17T21:34:24","modified_gmt":"2017-02-17T20:34:24","slug":"oh-filezilla","status":"publish","type":"post","link":"https:\/\/xpam.pl\/blog\/?p=168","title":{"rendered":"Oh FileZilla…"},"content":{"rendered":"

I have encountered a weird problem when connecting to our FreeBSD server with FileZilla over SFTP. Either with password or key authentication I would get:<\/p>\n

Error:\u00a0\u00a0 \u00a0Server sent disconnect message
\nError:\u00a0\u00a0 \u00a0type 2 (protocol error):
\nError:\u00a0\u00a0 \u00a0\"Too many authentication failures\"<\/p><\/blockquote>\n

So let's turn on debugging shall we?<\/p>\n

 <\/p>\n

Trace:\u00a0\u00a0 \u00a0Pageant is running. Requesting keys.
\nTrace:\u00a0\u00a0 \u00a0Pageant has 15 SSH-2 keys
\nTrace:\u00a0\u00a0 \u00a0Successfully loaded 1 key pair from file
\nTrace:\u00a0\u00a0 \u00a0Trying Pageant key #0
\nTrace:\u00a0\u00a0 \u00a0Server refused our key
\nTrace:\u00a0\u00a0 \u00a0Trying Pageant key #1
\nTrace:\u00a0\u00a0 \u00a0Server refused our key
\nTrace:\u00a0\u00a0 \u00a0Trying Pageant key #2
\nTrace:\u00a0\u00a0 \u00a0Server refused our key
\nTrace:\u00a0\u00a0 \u00a0Trying Pageant key #3
\nTrace:\u00a0\u00a0 \u00a0Server refused our key
\nTrace:\u00a0\u00a0 \u00a0Trying Pageant key #4
\nTrace:\u00a0\u00a0 \u00a0Server refused our key
\nTrace:\u00a0\u00a0 \u00a0Trying Pageant key #5
\nTrace:\u00a0\u00a0 \u00a0Received disconnect message (protocol error)
\nTrace:\u00a0\u00a0 \u00a0Disconnection message text: Too many authentication failures<\/p><\/blockquote>\n

So basically, I give Filezilla a specific keyfile but it tries all my keys anyway. Now let's see what the bright minds on FileZilla issue tracker have to say about this bug.<\/p>\n

https:\/\/trac.filezilla-project.org\/ticket\/7739<\/a> gives us a workaround:<\/p>\n

SSH_AUTH_SOCK=\"\"; filezilla<\/pre>\n
which works nicely. A working workaround is a blessing if you really need to use someting that is essentially broken. The bug is marked as a duplicate of https:\/\/trac.filezilla-project.org\/ticket\/5480<\/a><\/p>\n
This bug contains a brilliant<\/strong> comment by an apparent FileZilla developer:<\/p>\n
This is by design, FileZilla uses the system's SSH agent.<\/p>\n
Just reconfigure the server to allow for more keys.<\/strong><\/p><\/blockquote>\n
What the actual? The bug will apparently be solved via https:\/\/trac.filezilla-project.org\/ticket\/8232<\/a><\/p>\n
which is marked as \"fixed\" and the comment 19 months ago says it will be in the \"next version\". The latest version is 3.24.0 released on January 1st 2017 which is exactly what I have and guess what? Not fixed, after 7 years.<\/p>\n
 <\/p>\n
So at this point I'll just safely assume that FileZilla might as well be the worst SFTP client in existence and just use something else. But guess what? There is more. The exact same problem exists in Gnome Files if you try to open an sftp:\/\/ location. The obvious reason is that Gnome Files does not ask you anything about keys or athenticaton type but just cycles through SSH keys to try and find the correct one. Why did nobody think about offering me a popup dialog to pick the correct key? Probably because Gnome likes to dumb down things, I can't really find any other reason.<\/p>\n
<\/h3>\n
\r\n
\r\n
\r\n Cen
\r\nGitHub<\/a>
\r\nEurobattle.net<\/a>
\r\nLagabuse.com<\/a>
\r\nBnetdocs<\/a>
\r\n<\/div>\r\n","protected":false},"excerpt":{"rendered":"
I have encountered a weird problem when connecting to our FreeBSD server with FileZilla over SFTP. Either with password or key authentication I would get: Error:\u00a0\u00a0 \u00a0Server sent disconnect message Error:\u00a0\u00a0 \u00a0type 2 (protocol error): Error:\u00a0\u00a0 \u00a0\"Too many authentication failures\" So let's turn on debugging shall we?   Trace:\u00a0\u00a0 \u00a0Pageant is running. Requesting keys. Trace:\u00a0\u00a0 […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,1],"tags":[],"class_list":["post-168","post","type-post","status-publish","format-standard","hentry","category-linux","category-other"],"_links":{"self":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts\/168","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=168"}],"version-history":[{"count":5,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts\/168\/revisions"}],"predecessor-version":[{"id":170,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts\/168\/revisions\/170"}],"wp:attachment":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=168"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=168"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=168"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}