[ 
https://issues.apache.org/jira/browse/SSHD-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177008#comment-16177008
 ] 

ASF GitHub Bot commented on SSHD-774:
-------------------------------------

GitHub user mluckam opened a pull request:

    https://github.com/apache/mina-sshd/pull/37

    SSHD-774 SshConfigFileReader cannot parse tab delimiter in conifg file

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mluckam/mina-sshd SSHD-774

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/mina-sshd/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #37
    
----
commit 237c93f265b766c6ab5517773689309d2123ee3a
Author: Matthew Luckam <[email protected]>
Date:   2017-09-22T18:45:09Z

    SSHD-774 SshConfigFileReader cannot parse tab delimiter in conifg file

----


> SshConfigFileReader cannot parse tab delimiter in conifg file
> -------------------------------------------------------------
>
>                 Key: SSHD-774
>                 URL: https://issues.apache.org/jira/browse/SSHD-774
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 1.2.0, 1.6.0
>         Environment: CentOS release 6.9 running sshd-core 1.2.0
>            Reporter: Matthew Luckam
>         Attachments: parser.log, sshd_config, tab_delimiter.patch
>
>
> When running SshConfigFileReader.readConfigFile(BufferedReader) if the 
> delimiter in the configuration file being read is a tab, a 
> StreamCorruptedException is thrown and the file is not parsed.  The 
> delimiters currently being checked for are the space character and the = 
> symbol.  The [parsed file|^sshd_config] and [log|^parser.log] are attached.  
> This was also tested on 1.2.0 and 1.6.0.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to