[go-nuts] Re: pkg/sftp fails connecting (special char in user/pass)
Now solved, was my misstake with walking some fs path that produced the unexpected error. Just walking and creating files at ~ solved it. Sorry sorry. The sftp package is solid and great! Den fredag 4 november 2016 kl. 15:28:43 UTC+1 skrev Pontus Lundin: > > Hi! > > Having successfully connected to many sftp servers before now having > problem with one a using password auth. > > > ssh -vv yields > debug1: Next authentication method: password > password: > > > The user and password contains a $ character, i have tried encode it '%24' > and in plain text. If having plain string the result is: > > failed to send packet header: EOF > > > if using escaped character the result is: > > Failed to dial: ssh: handshake failed: ssh: unable to authenticate, > attempted methods [none password], no supported methods remain > exit status 1 > > > Using ssh works, however ends with > > PTY allocation request failed on channel 0 > Terminal access is disabled for this site > Connection to xx closed > > if that is something. > > > Any ideas on this one ? > Thanks! > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [go-nuts] pkg/sftp fails connecting (special char in user/pass)
Hi! Thanks. I agree, that was my thinking as well..i just got it from the server/sftp provider. I dont think they are meant and used for anything special.. it just feels wired to be honest :/ Will try to change that to start with. Den fredag 4 november 2016 kl. 18:42:13 UTC+1 skrev Drew Derbyshire: > > my advice: Don't use dollar signs. That's tempting fate, like using a > quote or newline character. > > I suspect one of the values is being used in a shell context and being > expanded. > > Why are they being used in the first place? > > On Fri, Nov 4, 2016 at 7:28 AM, Pontus Lundin > wrote: > >> Hi! >> >> Having successfully connected to many sftp servers before now having >> problem with one a using password auth. >> >> >> ssh -vv yields >> debug1: Next authentication method: password >> password: >> >> >> The user and password contains a $ character, i have tried encode it >> '%24' and in plain text. If having plain string the result is: >> >> failed to send packet header: EOF >> >> >> if using escaped character the result is: >> >> Failed to dial: ssh: handshake failed: ssh: unable to authenticate, >> attempted methods [none password], no supported methods remain >> exit status 1 >> >> >> Using ssh works, however ends with >> >> PTY allocation request failed on channel 0 >> Terminal access is disabled for this site >> Connection to xx closed >> >> if that is something. >> >> >> Any ideas on this one ? >> Thanks! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Drew Derbyshire > *Assistant Cat Valet (Probationary)* > Telephone 425-318-4350 > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[go-nuts] pkg/sftp fails connecting (special char in user/pass)
Hi! Having successfully connected to many sftp servers before now having problem with one a using password auth. ssh -vv yields debug1: Next authentication method: password password: The user and password contains a $ character, i have tried encode it '%24' and in plain text. If having plain string the result is: failed to send packet header: EOF if using escaped character the result is: Failed to dial: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain exit status 1 Using ssh works, however ends with PTY allocation request failed on channel 0 Terminal access is disabled for this site Connection to xx closed if that is something. Any ideas on this one ? Thanks! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[go-nuts] Help with the the Get url: EOF error (http client)
Hi, So i have a client running for months doing re-occuring work against a SOAP web service, suddenly i got the Get url: EOF error and now i am unable to get anything useful back from the server (headers) other than the :EOF There are various threads on this topic http://stackoverflow.com/questions/17714494/golang-http-request-results-in-eof-errors-when-making-multiple-requests-successi That points to if using older Go version (mine being 1.3.3) add req.Close = true I can amend this to my application code (or upgrade to a newer Go version) but what can i do to release the TCP connection that seems to halt me from doing more requests? Is there anything i can do client side or do i need to talk to the server-side people to kill (hanged) open connections? If i try another endpoint (not the SOAP web service) it works (i get the headers response back) so it seems that the server rejects more connection from my client ? Is that right ? Thanks! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
