mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Seliger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SSHD-473) PasswordAuthentifikation
Date Fri, 05 Jun 2015 18:41:00 GMT

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

Jochen Seliger commented on SSHD-473:

Hi Guillaume,
We've build an adaptive work flow solution for advertisement production for
Here we need a long time connection via the internet (HTTP) from our work flow
clients (somewhere) to the network, where the components of tis system are
The clients need jbbc-connection to the data base server first.
Next they need the RMI-Registry (and the contact to the WS-Server), pubished by
the WF-Sever.
And lastly there is implemented a messaging system between all components of the
work flow solution via RMI-Communication, what sould be enabled also in that
That case occures, because we have separated generally the advertisement
production from the commercials ad systems.
The existing systems claiming to handle the ad production, are bound to one
single commercial ad system.
Our customers may bind unlimited number of work streams  (from news providers
spread over the world) within one instance of our work flow solution.
Generally we've implemented the outer communicatuion via generic assynchron
But as the advertisers will appear at the work stations of the news providers
commercial ad system and they may provide data (logos and/or scibbels) to be
used within the ad design, they order, there is a requirement to involve the ad
recordes serving the advertiser with a specific work item into the work flow
But the work item processing is requiring the intergation of these work stations
on demand into the network of the work flow system.
As VPN is not handable under the named circumstances, I'm looking for a way to
establish that network intergration via the internet.
As MINA is talking about HTTP1.5 Sockets and Shells, I came to you.
Here I found the problems, we have talked about.
If you now say that I only need the client (probably JSch-Client) that may be
But why MINA has build an wrapper around the ssh with such an unclear concept?
If you will not correct the failures within the PassWordAuthenticator-procedure,
I'll have to look for another way.
But it si not undertandable to me.
Jochen Seliger 

> PasswordAuthentifikation
> ------------------------
>                 Key: SSHD-473
>                 URL: https://issues.apache.org/jira/browse/SSHD-473
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 0.14.0
>         Environment: Windows 7, Java 8, Eclipse JUNO
>            Reporter: Jochen Seliger
>            Priority: Critical
>         Attachments: Loggs.doc, SSHDPasswordAuthenticator.java, SSHDPasswordAuthenticator.java,
SSH_SERVER.java, SSH_SERVER.java, createSSHDClient-method.doc
> I run the sshd and the ssh client both on the windos mashine.
> The sshd I start on port 8000 and with password authentificator ans an own atthenicator
class, which shall shoe a messagebox when envoced.
> The client I start aftercreating it as SshClient.setUpDefaultClient(); without stting
any factury with the statement ClientSession session = client.connect("Jochen","",8000).await().getSession();
(Jochen is an existing user on the mashine).
> But till shellChannel I can proceed only when setting after session creation session.addPasswordIdentity("Jochen");
(it is tha same user as provided at session creation)
> There is no functionality to set the password.
> The method authPassword is depreciated.
> 1. My first question: How to proceed th use PasswordAuthentification?
> As stated I can proceesd til ssh-Shell, but the server is logging at a first run an autentification
failure and at a second run authentification success:
> Mai 22, 2015 12:14:21 PM org.apache.sshd.client.session.ClientSessionImpl readIdentification
> INFORMATION: Server version string: SSH-2.0-SSHD-CORE-0.14.0
> Mai 22, 2015 12:14:22 PM org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier
> WARNUNG: Server at / presented unverified DSA key: e4:76:f3:c2:15:64:7f:e4:5f:b7:86:35:a5:3e:85:35
> Mai 22, 2015 12:14:22 PM org.apache.sshd.common.session.AbstractSession doHandleMessage
> INFORMATION: Dequeing pending packets
> Mai 22, 2015 12:14:22 PM org.apache.sshd.client.session.ClientUserAuthServiceNew processUserAuth
> Mai 22, 2015 12:14:22 PM org.apache.sshd.client.auth.UserAuthKeyboardInteractive process
> INFORMATION: Received Password authentication  en-US
> Mai 22, 2015 12:14:22 PM org.apache.sshd.client.session.ClientUserAuthServiceNew processUserAuth
> ShellChannell opened
> Microsoft Windows [Version 6.0.6001]
> Copyright (c) 2006 Microsoft Corporation. Alle Rechte vorbehalten.
> C:\Users\Jochen\workspace\USF_SSH_WS>
> allthoug I did not provide an password.
> 2. Why thes two runs are processed?
> 3. Why the first run fails and the second one succedes?
> 4. How to proceede to get a functioning password and keypair authentication?
> Regards
> Jochen Seliger

This message was sent by Atlassian JIRA

View raw message