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