https://bugs.kde.org/show_bug.cgi?id=475638

Pedro V <voidpointertonull+bugskde...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
                 CC|                            |voidpointertonull+bugskdeor
                   |                            |g...@gmail.com
     Ever confirmed|0                           |1

--- Comment #1 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
Can confirm, likely an upstream (libssh) issue, although it seems to be capable
of processing multiple includes, and I'm really not seeing what's the logical
problem preventing it.

Suspecting a corrupt state returning from include directive processing and
looking for some extra noise between the 2 includes, ended up with the
following config:
```
Include ~/.ssh/config0
Host test
        HostKeyAlias test
Include ~/.ssh/config1
```

Running `KIO_SFTP_LOG_VERBOSITY=10 KDE_FORK_SLAVES=1
QT_LOGGING_RULES="log_kio_sftp=true;kf.kio.workers.sftp=true;" krusader` , got
the following output:
```
kf.kio.workers.sftp: list directory:  QUrl("sftp://test1";)
kf.kio.workers.sftp: checking cache: info.username = "" , info.url =
"sftp://test1";
kf.kio.workers.sftp: 
kf.kio.workers.sftp: Creating the SSH session and setting options
kf.kio.workers.sftp: [ ssh_config_parse_file ] ( 3 )  ssh_config_parse_file:
Reading configuration data from /home/user/.ssh/config
kf.kio.workers.sftp: [ local_parse_file ] ( 3 )  local_parse_file: Reading
additional configuration data from /home/user/.ssh/config0
kf.kio.workers.sftp: [ ssh_config_parse_line ] ( 2 )  ssh_config_parse_line:
Unsupported option: HostKeyAlias, line: 3
```

SOC_INCLUDE appears to be correctly excluded from the seen[opcode] check,
suspecting the parsing variable to be handled silly.
Looking for a way to reset it, I cooked up:
```
Include ~/.ssh/config0
Match user user
        HostKeyAlias test
Include ~/.ssh/config1
```

With that, connecting to sftp://user@test1 (note the inclusion of the
username!) succeeds as the parsing of the second inclusion isn't skipped
anymore:
```
kf.kio.workers.sftp: [ ssh_config_parse_file ] ( 3 )  ssh_config_parse_file:
Reading configuration data from /home/user/.ssh/config
kf.kio.workers.sftp: [ local_parse_file ] ( 3 )  local_parse_file: Reading
additional configuration data from /home/user/.ssh/config0
kf.kio.workers.sftp: [ ssh_config_parse_line ] ( 4 )  ssh_config_parse_line:
line 2: Processing Match keyword 'user'
kf.kio.workers.sftp: [ ssh_config_match ] ( 4 )  ssh_config_match: Matched
'user' against pattern 'user' (ok=1)
kf.kio.workers.sftp: [ ssh_config_parse_line ] ( 2 )  ssh_config_parse_line:
Unsupported option: HostKeyAlias, line: 3
kf.kio.workers.sftp: [ local_parse_file ] ( 3 )  local_parse_file: Reading
additional configuration data from /home/user/.ssh/config1
```

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to