date:20170914

[jira] [Created] (SSHD-772) After login using SSHServer program ...It displays "/bin/sh: 0: can't access tty; job control turned off". How to solve this problem?

2017-09-14 Thread Amit Kumar (JIRA)

Amit Kumar created SSHD-772:
---

 Summary: After login using SSHServer program ...It displays 
"/bin/sh: 0: can't access tty; job control turned off". How to solve this 
problem?
 Key: SSHD-772
 URL: https://issues.apache.org/jira/browse/SSHD-772
 Project: MINA SSHD
  Issue Type: Question
Affects Versions: 1.6.0
 Environment: Ubuntu 16.04 LTS
Reporter: Amit Kumar


After login using SSHServer program ...It displays "/bin/sh: 0: can't access 
tty; job control turned off". How to solve this problem



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

[jira] [Updated] (SSHD-745) KnownHostEntry cannot parse [host]:port or IPv6 with %link entries

2017-09-14 Thread Goldstein Lyor (JIRA)


 [ 
https://issues.apache.org/jira/browse/SSHD-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Goldstein Lyor updated SSHD-745:

Issue Type: New Feature  (was: Bug)

> KnownHostEntry cannot parse [host]:port or IPv6 with %link entries
> --
>
> Key: SSHD-745
> URL: https://issues.apache.org/jira/browse/SSHD-745
> Project: MINA SSHD
>  Issue Type: New Feature
>Affects Versions: 1.2.0
>Reporter: Stephen Connolly
>Priority: Minor
>
> My known hosts file contains lines like: (note I have sanitized the lines and 
> switched entries to documentation reserved IP addresses and DNS names)
> {code}
> [host.example.com]:7999,[192.0.2.3]:7999 ssh-rsa ...Z45M/
> 2001:db8:85a3::8a2e:370:7334%en1 ecdsa-sha2-nistp256 E2...q9zmk=
> {code}
> Both of which will bomb out with errors like:
> {code}
> WARNING: Failed (StreamCorruptedException) to reload server keys from 
> /Users/stephenc/.ssh/known_hosts: Failed (IllegalArgumentException) to parse 
> line #96 '2001:db8:85a3::8a2e:370:7334%en1 ecdsa-sha2-nistp256 
> E2...q9zmk=': Invalid host pattern char in 
> 2001:db8:85a3::8a2e:370:7334%en1
> {code}
> or
> (This next one is a thrown away ssh server running in docker and the 
> container is gone so I can provide the full unedited line)
> {code}
> WARNING: Failed (StreamCorruptedException) to reload server keys from 
> /Users/stephenc/.ssh/known_hosts: Failed (IllegalArgumentException) to parse 
> line #60 '[127.0.0.1]:49153 ssh-rsa 
> B3NzaC1yc2EDAQABAAABAQC5ntfSGAQOO2O/8ma7mtk9UaC6JWVlJ+6WAjnN3V510wc4nkkUcL66hZZyPLI0TYhk2CHNNQPeXkc6Cq7enSJab7SI06MhCQhF9yeuBQnphNBsUa01twPgycQOdrYey+4hIVXRF5BbckuU5nVAuFsPv7utNROmo+XoWoAdopSiejWs6Mrox+VIwgeN6peJ5l5jPqCjMEBTP9iNWgZMa+wQN7cTWpi7lIbK+a2hnzHz5P8oWFN8j8jREm+/6NK1IdW3c0CsLRWyee50GYYQOEi0zo1FfGweia5CbzfjRtfd0XFtUxGtULJpPoj9x/7xHuFUL1rYoKAGaTPzPdBHJTiJ':
>  Invalid host pattern char in [127.0.0.1]:49153
> {/code}
> https://en.wikibooks.org/wiki/OpenSSH/Client_Configuration_Files seems to 
> indicate that {{[host]:port}} is the syntax for when the ssh server is using 
> a non-standard port 
> https://serverfault.com/a/771355/147023 reports that the % at the end of the 
> IPv6 address is indicating the local link (in my case %en1 being WIFI on my 
> macbook, but I have seem %eth0 on modern linux servers)
> Completely blowing up for these entries seems rather wrong, I would expect 
> either skipping such entries or actually being able to parse them.
> Checking the current code on master it seems this issue has not been resolved 
> yet:
> IOW 
> https://github.com/apache/mina-sshd/blob/5b0b163c5500fedc2a6bae0fc5e260d64fcf370a/sshd-core/src/main/java/org/apache/sshd/client/config/hosts/HostPatternsHolder.java#L289-L306
>  still will reject a host name containing either the non-standard port 
> specification or the link specifier



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

[jira] [Updated] (SSHD-767) Add support for verifying server keys via DNS and SSHFP records

2017-09-14 Thread Goldstein Lyor (JIRA)


 [ 
https://issues.apache.org/jira/browse/SSHD-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Goldstein Lyor updated SSHD-767:

Labels: client dns fingerprint future key-management ssh  (was: client dns 
fingerprint key-management ssh)

> Add support for verifying server keys via DNS and SSHFP records
> ---
>
> Key: SSHD-767
> URL: https://issues.apache.org/jira/browse/SSHD-767
> Project: MINA SSHD
>  Issue Type: New Feature
>Affects Versions: 1.7.0
>Reporter: Goldstein Lyor
>Assignee: Goldstein Lyor
>Priority: Minor
>  Labels: client, dns, fingerprint, future, key-management, ssh
>
> According to 
> [ssh_config(5)|https://www.freebsd.org/cgi/man.cgi?ssh_config(5)]:
> {quote}
> VerifyHostKeyDNS - Specifies whether to verify the remote key using DNS and 
> SSHFP resource records. If this option is set to ``yes'', the client will 
> implicitly trust keys that match a secure fingerprint from DNS.
> {quote}



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

[jira] [Updated] (SSHD-746) Seems IPv6 addresses are not supported

2017-09-14 Thread Goldstein Lyor (JIRA)


 [ 
https://issues.apache.org/jira/browse/SSHD-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Goldstein Lyor updated SSHD-746:

Issue Type: New Feature  (was: Bug)

> Seems IPv6 addresses are not supported
> --
>
> Key: SSHD-746
> URL: https://issues.apache.org/jira/browse/SSHD-746
> Project: MINA SSHD
>  Issue Type: New Feature
>Affects Versions: 1.2.0
>Reporter: Stephen Connolly
>Priority: Minor
>
> Seems a lot of the code is not aware of IPv6 patterns
> {code}
> java.lang.IllegalArgumentException: Invalid host pattern char in 
> 0:0:0:0:0:0:0:1
>   at 
> org.apache.sshd.common.util.ValidateUtils.throwIllegalArgumentException(ValidateUtils.java:138)
>   at 
> org.apache.sshd.common.util.ValidateUtils.checkTrue(ValidateUtils.java:127)
>   at 
> org.apache.sshd.client.config.hosts.HostPatternsHolder.toPattern(HostPatternsHolder.java:247)
>   at 
> org.apache.sshd.client.config.hosts.HostPatternsHolder.parsePatterns(HostPatternsHolder.java:221)
>   at 
> org.apache.sshd.client.config.hosts.HostConfigEntry.setHost(HostConfigEntry.java:138)
>   at 
> org.apache.sshd.client.config.hosts.HostConfigEntry.(HostConfigEntry.java:123)
>   at org.apache.sshd.client.SshClient.connect(SshClient.java:505)
> {code}



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

[jira] [Updated] (SSHD-737) "Invalid encoding: redundant leading 0s" when establishing session

2017-09-14 Thread Guillaume Nodet (JIRA)


 [ 
https://issues.apache.org/jira/browse/SSHD-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet updated SSHD-737:
-
Fix Version/s: (was: 1.4.0)
   1.7.0

> "Invalid encoding: redundant leading 0s" when establishing session
> --
>
> Key: SSHD-737
> URL: https://issues.apache.org/jira/browse/SSHD-737
> Project: MINA SSHD
>  Issue Type: Bug
>Affects Versions: 0.14.0
>Reporter: Grzegorz Grzybek
>Assignee: Goldstein Lyor
> Fix For: 1.7.0
>
> Attachments: SignatureDSATest.java
>
>
> Probably related to https://bugs.openjdk.java.net/browse/JDK-8175251. I'm 
> getting:
> {noformat}
> 2017-04-03 12:57:52,932 | INFO  | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Client session created
> 2017-04-03 12:57:52,932 | DEBUG | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Send SSH_MSG_KEXINIT
> 2017-04-03 12:57:52,932 | TRACE | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Sending packet #0: 14 5c dd 49 
> 7d 80 20 9d 4b d8 c9 11 ac 42 34 81 08 00 00 00 9b 64 69 66 66 69 65 2d 68 65 
> 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 32 35 
> 36 2c 64 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 63 
> 68 61 6e 67 65 2d 73 68 61 31 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 
> 32 35 36 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 33 38 34 2c 65 63 64 
> 68 2d 73 68 61 32 2d 6e 69 73 74 70 35 32 31 2c 64 69 66 66 69 65 2d 68 65 6c 
> 6c 6d 61 6e 2d 67 72 6f 75 70 31 2d 73 68 61 31 00 00 00 4b 65 63 64 73 61 2d 
> 73 68 61 32 2d 6e 69 73 74 70 32 35 36 2c 65 63 64 73 61 2d 73 68 61 32 2d 6e 
> 69 73 74 70 33 38 34 2c 65 63 64 73 61 2d 73 68 61 32 2d 6e 69 73 74 70 35 32 
> 31 2c 73 73 68 2d 64 73 73 2c 73 73 68 2d 72 73 61 00 00 00 36 61 65 73 31 32 
> 38 2d 63 74 72 2c 61 72 63 66 6f 75 72 31 32 38 2c 61 65 73 31 32 38 2d 63 62 
> 63 2c 33 64 65 73 2d 63 62 63 2c 62 6c 6f 77 66 69 73 68 2d 63 62 63 00 00 00 
> 36 61 65 73 31 32 38 2d 63 74 72 2c 61 72 63 66 6f 75 72 31 32 38 2c 61 65 73 
> 31 32 38 2d 63 62 63 2c 33 64 65 73 2d 63 62 63 2c 62 6c 6f 77 66 69 73 68 2d 
> 63 62 63 00 00 00 47 68 6d 61 63 2d 73 68 61 32 2d 32 35 36 2c 68 6d 61 63 2d 
> 73 68 61 32 2d 35 31 32 2c 68 6d 61 63 2d 73 68 61 31 2c 68 6d 61 63 2d 6d 64 
> 35 2c 68 6d 61 63 2d 73 68 61 31 2d 39 36 2c 68 6d 61 63 2d 6d 64 35 2d 39 36 
> 00 00 00 47 68 6d 61 63 2d 73 68 61 32 2d 32 35 36 2c 68 6d 61 63 2d 73 68 61 
> 32 2d 35 31 32 2c 68 6d 61 63 2d 73 68 61 31 2c 68 6d 61 63 2d 6d 64 35 2c 68 
> 6d 61 63 2d 73 68 61 31 2d 39 36 2c 68 6d 61 63 2d 6d 64 35 2d 39 36 00 00 00 
> 04 6e 6f 6e 65 00 00 00 04 6e 6f 6e 65 00 00 00 00 00 00 00 00 00 00 00 00 00
> 2017-04-03 12:57:52,933 | DEBUG | 3)-192.168.0.220 | ClientUserAuthServiceOld 
> | 33 - org.apache.sshd.core - 0.14.0 | Trying authentication with 
> org.apache.sshd.client.auth.deprecated.UserAuthPassword@30ed5323
> 2017-04-03 12:57:52,933 | DEBUG | 3)-192.168.0.220 | ClientUserAuthServiceOld 
> | 33 - org.apache.sshd.core - 0.14.0 | waiting to send authentication
> 2017-04-03 12:57:52,933 | INFO  | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Server version string: 
> SSH-2.0-SSHD-CORE-0.14.0
> 2017-04-03 12:57:52,947 | TRACE | d]-nio2-thread-2 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Received packet #1: 14 7b 0e 
> 99 05 b0 83 3c be 6a 22 3b 2b a1 c3 0b cb 00 00 00 9b 64 69 66 66 69 65 2d 68 
> 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 32 
> 35 36 2c 64 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 
> 63 68 61 6e 67 65 2d 73 68 61 31 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 
> 70 32 35 36 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 33 38 34 2c 65 63 
> 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 35 32 31 2c 64 69 66 66 69 65 2d 68 65 
> 6c 6c 6d 61 6e 2d 67 72 6f 75 70 31 2d 73 68 61 31 00 00 00 07 73 73 68 2d 64 
> 73 73 00 00 00 0a 61 65 73 31 32 38 2d 63 74 72 00 00 00 0a 61 65 73 31 32 38 
> 2d 63 74 72 00 00 00 09 68 6d 61 63 2d 73 68 61 31 00 00 00 09 68 6d 61 63 2d 
> 73 68 61 31 00 00 00 04 6e 6f 6e 65 00 00 00 04 6e 6f 6e 65 00 00 00 00 00 00 
> 00 00 00 00 00 00 00
> 2017-04-03 12:57:52,947 | DEBUG | d]-nio2-thread-2 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Received SSH_MSG_KEXINIT
> 2017-04-03 12:57:52,947 | TRACE | d]-nio2-thread-2 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Kex: negotiate(kex algorithms) 
> guess=diffie-hellman-group-exchange-sha256 (client: 
>

[jira] [Resolved] (SSHD-737) "Invalid encoding: redundant leading 0s" when establishing session

2017-09-14 Thread Guillaume Nodet (JIRA)


 [ 
https://issues.apache.org/jira/browse/SSHD-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guillaume Nodet resolved SSHD-737.
--
Resolution: Fixed
  Assignee: Guillaume Nodet  (was: Goldstein Lyor)

> "Invalid encoding: redundant leading 0s" when establishing session
> --
>
> Key: SSHD-737
> URL: https://issues.apache.org/jira/browse/SSHD-737
> Project: MINA SSHD
>  Issue Type: Bug
>Affects Versions: 0.14.0
>Reporter: Grzegorz Grzybek
>Assignee: Guillaume Nodet
> Fix For: 1.7.0
>
> Attachments: SignatureDSATest.java
>
>
> Probably related to https://bugs.openjdk.java.net/browse/JDK-8175251. I'm 
> getting:
> {noformat}
> 2017-04-03 12:57:52,932 | INFO  | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Client session created
> 2017-04-03 12:57:52,932 | DEBUG | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Send SSH_MSG_KEXINIT
> 2017-04-03 12:57:52,932 | TRACE | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Sending packet #0: 14 5c dd 49 
> 7d 80 20 9d 4b d8 c9 11 ac 42 34 81 08 00 00 00 9b 64 69 66 66 69 65 2d 68 65 
> 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 32 35 
> 36 2c 64 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 63 
> 68 61 6e 67 65 2d 73 68 61 31 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 
> 32 35 36 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 33 38 34 2c 65 63 64 
> 68 2d 73 68 61 32 2d 6e 69 73 74 70 35 32 31 2c 64 69 66 66 69 65 2d 68 65 6c 
> 6c 6d 61 6e 2d 67 72 6f 75 70 31 2d 73 68 61 31 00 00 00 4b 65 63 64 73 61 2d 
> 73 68 61 32 2d 6e 69 73 74 70 32 35 36 2c 65 63 64 73 61 2d 73 68 61 32 2d 6e 
> 69 73 74 70 33 38 34 2c 65 63 64 73 61 2d 73 68 61 32 2d 6e 69 73 74 70 35 32 
> 31 2c 73 73 68 2d 64 73 73 2c 73 73 68 2d 72 73 61 00 00 00 36 61 65 73 31 32 
> 38 2d 63 74 72 2c 61 72 63 66 6f 75 72 31 32 38 2c 61 65 73 31 32 38 2d 63 62 
> 63 2c 33 64 65 73 2d 63 62 63 2c 62 6c 6f 77 66 69 73 68 2d 63 62 63 00 00 00 
> 36 61 65 73 31 32 38 2d 63 74 72 2c 61 72 63 66 6f 75 72 31 32 38 2c 61 65 73 
> 31 32 38 2d 63 62 63 2c 33 64 65 73 2d 63 62 63 2c 62 6c 6f 77 66 69 73 68 2d 
> 63 62 63 00 00 00 47 68 6d 61 63 2d 73 68 61 32 2d 32 35 36 2c 68 6d 61 63 2d 
> 73 68 61 32 2d 35 31 32 2c 68 6d 61 63 2d 73 68 61 31 2c 68 6d 61 63 2d 6d 64 
> 35 2c 68 6d 61 63 2d 73 68 61 31 2d 39 36 2c 68 6d 61 63 2d 6d 64 35 2d 39 36 
> 00 00 00 47 68 6d 61 63 2d 73 68 61 32 2d 32 35 36 2c 68 6d 61 63 2d 73 68 61 
> 32 2d 35 31 32 2c 68 6d 61 63 2d 73 68 61 31 2c 68 6d 61 63 2d 6d 64 35 2c 68 
> 6d 61 63 2d 73 68 61 31 2d 39 36 2c 68 6d 61 63 2d 6d 64 35 2d 39 36 00 00 00 
> 04 6e 6f 6e 65 00 00 00 04 6e 6f 6e 65 00 00 00 00 00 00 00 00 00 00 00 00 00
> 2017-04-03 12:57:52,933 | DEBUG | 3)-192.168.0.220 | ClientUserAuthServiceOld 
> | 33 - org.apache.sshd.core - 0.14.0 | Trying authentication with 
> org.apache.sshd.client.auth.deprecated.UserAuthPassword@30ed5323
> 2017-04-03 12:57:52,933 | DEBUG | 3)-192.168.0.220 | ClientUserAuthServiceOld 
> | 33 - org.apache.sshd.core - 0.14.0 | waiting to send authentication
> 2017-04-03 12:57:52,933 | INFO  | d]-nio2-thread-1 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Server version string: 
> SSH-2.0-SSHD-CORE-0.14.0
> 2017-04-03 12:57:52,947 | TRACE | d]-nio2-thread-2 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Received packet #1: 14 7b 0e 
> 99 05 b0 83 3c be 6a 22 3b 2b a1 c3 0b cb 00 00 00 9b 64 69 66 66 69 65 2d 68 
> 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 63 68 61 6e 67 65 2d 73 68 61 32 
> 35 36 2c 64 69 66 66 69 65 2d 68 65 6c 6c 6d 61 6e 2d 67 72 6f 75 70 2d 65 78 
> 63 68 61 6e 67 65 2d 73 68 61 31 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 
> 70 32 35 36 2c 65 63 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 33 38 34 2c 65 63 
> 64 68 2d 73 68 61 32 2d 6e 69 73 74 70 35 32 31 2c 64 69 66 66 69 65 2d 68 65 
> 6c 6c 6d 61 6e 2d 67 72 6f 75 70 31 2d 73 68 61 31 00 00 00 07 73 73 68 2d 64 
> 73 73 00 00 00 0a 61 65 73 31 32 38 2d 63 74 72 00 00 00 0a 61 65 73 31 32 38 
> 2d 63 74 72 00 00 00 09 68 6d 61 63 2d 73 68 61 31 00 00 00 09 68 6d 61 63 2d 
> 73 68 61 31 00 00 00 04 6e 6f 6e 65 00 00 00 04 6e 6f 6e 65 00 00 00 00 00 00 
> 00 00 00 00 00 00 00
> 2017-04-03 12:57:52,947 | DEBUG | d]-nio2-thread-2 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Received SSH_MSG_KEXINIT
> 2017-04-03 12:57:52,947 | TRACE | d]-nio2-thread-2 | ClientSessionImpl
> | 33 - org.apache.sshd.core - 0.14.0 | Kex: negotiate(kex algorithms) 
> guess=diffie-hellman-group-exchange-sha256 (client: 
>

[jira] [Created] (SSHD-772) After login using SSHServer program ...It displays "/bin/sh: 0: can't access tty; job control turned off". How to solve this problem?

[jira] [Updated] (SSHD-745) KnownHostEntry cannot parse [host]:port or IPv6 with %link entries

[jira] [Updated] (SSHD-767) Add support for verifying server keys via DNS and SSHFP records

[jira] [Updated] (SSHD-746) Seems IPv6 addresses are not supported

[jira] [Updated] (SSHD-737) "Invalid encoding: redundant leading 0s" when establishing session

[jira] [Resolved] (SSHD-737) "Invalid encoding: redundant leading 0s" when establishing session

6 matches

Site Navigation

Mail list logo

Footer information