Bugs item #2445001, was opened at 2008-12-18 12:33
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=703942&aid=2445001&group_id=125852
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: API
Group: None
>Status: Closed
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Tiago Rossi (tiarossi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Inform password in libssh2_userauth_keyboard_interactive API
Initial Comment:
It would be interesting if whe cold inform password in libssh2_userauth_keyboard_interactive API and let libssh2 manage data to send like keyboard interactive.
In some c++ aplications when the static callback function is called, the context of the caller object isn't available at this point, and is more dificult to assossiate LIBSSH2_SESSION data with this object.
----------------------------------------------------------------------
>Comment By: Daniel Stenberg (bagder)
Date: 2009-04-05 23:11
Message:
This really isn't a bug.
----------------------------------------------------------------------
Comment By: alamaison (alamaison)
Date: 2008-12-18 15:02
Message:
If you mean that you want keyboard-interactive authentication to work more
like simple password authentication then I'm afraid this isn't possible.
The whole point of KB-interactive authentication is that the server can
send any number of prompts asking any questions it wants. It just happens
that asking for a password is quite common.
----------------------------------------------------------------------
Comment By: Paul Thomas (thomaspu)
Date: 2008-12-18 14:34
Message:
Actually, this can be easily gotten around:
"In some c++ aplications when the static callback function is called, the
context of the caller object isn't available at this point..."
The trick is to store a pointer to your object in libssh2's abstract
pointer. Then when the callback is called and it runs your callback
function, your callback function pulls the pointer out of libssh2's
abstract field and boom! Your object is now accessible.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=703942&aid=2445001&group_id=125852
------------------------------------------------------------------------------
_______________________________________________
libssh2-devel mailing list
libssh2-devel_at_lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
Received on 2009-04-05