<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Support that principle fully! The code should not depend on the
syntax of<br>
a prompt. Should be solved otherwise (if possible).<br>
<br>
<br>
Am 17.03.2015 um 13:42 schrieb swizz ly:<br>
<span style="white-space: pre;">> I admin it might not be the
most elegant solution, but I find it better than to hardcode the
prompt in the sourcecode. Isn't it possible to modify to code to
be able to work with whatever prompt? Isnt't there any function in
the libraries x2goclient uses that can handle this?<br>
> <br>
> Swizzly<br>
> <br>
> *Gesendet:* Montag, 16. März 2015 um 17:07 Uhr<br>
> *Von:* "Mihai Moldovan" <a class="moz-txt-link-rfc2396E" href="mailto:ionic@ionic.de"><ionic@ionic.de></a><br>
> *An:* "swizz ly" <a class="moz-txt-link-rfc2396E" href="mailto:swizz.ly@gmx.ch"><swizz.ly@gmx.ch></a><br>
> *Cc:* <a class="moz-txt-link-abbreviated" href="mailto:x2go-user@lists.x2go.org">x2go-user@lists.x2go.org</a><br>
> *Betreff:* Re: [X2Go-User] X2Go Two-factor-authentication
with SecurID<br>
> On 16.03.2015 04:53 PM, swizz ly wrote:<br>
> > I have found the problem. The prompt of the SSH server
is coded in the<br>
> > source code of x2goclient.<br>
> > We use for authentication via SecurID a different SSH
promtp to<br>
> > emphasize the difference. Last week I already changed
the prompt of<br>
> > the SecurID prompt to be the same as the normal SSH, but
I didn't<br>
> > notice the blank after the "Password: "...<br>
> > Unfortunately, I haven't managed to get the blank space
at the end of<br>
> > "Password: ". So I just edited the source code of the
x2goclient, and<br>
> > changed the line where the expected prompt is defined.<br>
> > This solution worked.<br>
> > Would it make sense to include the expected ssh prompt
as a parameter<br>
> > in x2go in order to avoid having to recomplie the source
code in a<br>
> > such case?<br>
><br>
> Hum, maybe. I would be a really obscure setting, though. Is
there no<br>
> default other than "Password: "? Adding/hardcoding other
defaults is<br>
> definitely an option. Everybody else who deviates from that
is basically<br>
> on their own -- so a parameter would make sense.<br>
><br>
> Then again, how much sense does that make as a default
parameter?<br>
> Suppose you have multiple sessions and want to connect to
different<br>
> servers -- which also happen to have different prompts. A
global command<br>
> line parameter would make connecting to one prompt type
possible (only.)<br>
><br>
> This probably should be a per-session preference, if
anything. But the<br>
> use case is so special that I'm unsure whether it makes sense
as a<br>
> general setting in the client or not...<br>
><br>
><br>
><br>
> Mihai<br>
> <br>
><br>
><br>
> _______________________________________________<br>
> x2go-user mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:x2go-user@lists.x2go.org">x2go-user@lists.x2go.org</a><br>
> <a class="moz-txt-link-freetext" href="http://lists.x2go.org/listinfo/x2go-user">http://lists.x2go.org/listinfo/x2go-user</a></span><br>
<br>
<br>
</body>
</html>