Thread: [Ssh-sftp-perl-users] Change port used in Net::SFTP
Brought to you by:
dbrobins
From: Vitali C. <CV...@me...> - 2004-04-02 09:28:08
|
Hi to all, I need to get a file on a server that use a non-standard port for ssh daemon, 222, but I don't find a way to specify it on create of connection my $sftp =3D Net::SFTP->new($host, $user, $passw) or die "Cannot connect to host : $host \n" ; There is a way to specify it in the module Net::SFTP, like in Net::SSH::W32Perl my $ssh =3D new Net::SSH::W32Perl($host, port =3D> 22, debug =3D> 1, = protocol =3D> 2) Many thanks for your time Best regards Cesare ------------------------ Cesare Vitali ------------------------ Met Sogeda S.p.A. ------------------------ mailto:cv...@so... Sistemista Microsoft=20 HP Certified Engineer ------------------------=20 |
From: Mark F. <mar...@ea...> - 2004-04-03 06:40:12
|
You want to use the "ssh args" part of the net::sftp "new" method. This is where you can specify parms to net::ssh::perl. Unfortunately, it is as clear as *mud* how to do this. my $sftp = Net::SFTP->new('somehost.domain.domain', ( user => 'someuser', ssh_args => ( ( [port => (['1234']) ] ) ) ) ); Dave, I asked you *6 months ago* to add an example to the POD. You keep saying it shouldn't work this way. Until it doesn't work this way, wouldn't it be helpful to document how it works now? It took me *two days* to figure out how to do the above. It seems other users have the same challenge. Why not just add it to the POD so we don't have to suffer with it any more? I don't think it's a problem how convoluted it is. Just that it's not documented -- and apparently no interest in documenting it. Mark ----- Original Message ----- From: "Vitali Cesare" <CV...@me...> To: <ssh...@li...> Sent: Friday, April 02, 2004 2:30 AM Subject: [Ssh-sftp-perl-users] Change port used in Net::SFTP Hi to all, I need to get a file on a server that use a non-standard port for ssh daemon, 222, but I don't find a way to specify it on create of connection my $sftp = Net::SFTP->new($host, $user, $passw) or die "Cannot connect to host : $host \n" ; There is a way to specify it in the module Net::SFTP, like in Net::SSH::W32Perl my $ssh = new Net::SSH::W32Perl($host, port => 22, debug => 1, protocol => 2) Many thanks for your time Best regards Cesare ------------------------ Cesare Vitali ------------------------ Met Sogeda S.p.A. ------------------------ mailto:cv...@so... Sistemista Microsoft HP Certified Engineer ------------------------ ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=ick _______________________________________________ Ssh-sftp-perl-users mailing list Ssh...@li... https://lists.sourceforge.net/lists/listinfo/ssh-sftp-perl-users |
From: Dave R. <au...@ur...> - 2004-04-03 06:48:51
|
On Fri, 2 Apr 2004, Mark Fuller wrote: > Dave, I asked you *6 months ago* to add an example to the POD. You keep Wow, was it that long? > saying it shouldn't work this way. Until it doesn't work this way, wouldn't > it be helpful to document how it works now? It took me *two days* to figure > out how to do the above. It seems other users have the same challenge. Why > not just add it to the POD so we don't have to suffer with it any more? I > don't think it's a problem how convoluted it is. Just that it's not > documented -- and apparently no interest in documenting it. Hey, don't blame me! It wasn't documented when I got this thing. But yes, it should be documented. Is there an RT ticket for this? -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/ |
From: Mark F. <mar...@ea...> - 2004-04-03 07:00:01
|
I don't know what an "RT ticket" is. :) I'm sorry if my bad day came through in that email. But, if the ssh-args parm isn't going to change anytime soon, I think the convoluted usage should be exampled. The convoluted thing isn't too bad if it's just documented with an example. I know I've mentioned it a couple of times. One of which should be in the archives (which seem to be unavailable at the moment). If I need to do something formal, tell me what to do. I know it was this way before you tookover support. I'm sorry if I came on too strong. It just needs an example in the POD. Mark ----- Original Message ----- From: "Dave Rolsky" <au...@ur...> To: "Mark Fuller" <mar...@ea...> Cc: "Vitali Cesare" <CV...@me...>; <ssh...@li...> Sent: Friday, April 02, 2004 11:48 PM Subject: Re: [Ssh-sftp-perl-users] Change port used in Net::SFTP > On Fri, 2 Apr 2004, Mark Fuller wrote: > > > Dave, I asked you *6 months ago* to add an example to the POD. You keep > > Wow, was it that long? > > > saying it shouldn't work this way. Until it doesn't work this way, wouldn't > > it be helpful to document how it works now? It took me *two days* to figure > > out how to do the above. It seems other users have the same challenge. Why > > not just add it to the POD so we don't have to suffer with it any more? I > > don't think it's a problem how convoluted it is. Just that it's not > > documented -- and apparently no interest in documenting it. > > Hey, don't blame me! It wasn't documented when I got this thing. But > yes, it should be documented. Is there an RT ticket for this? > > > -dave > > /*======================= > House Absolute Consulting > www.houseabsolute.com > =======================*/ |
From: Dave R. <au...@ur...> - 2004-04-03 07:03:12
|
On Fri, 2 Apr 2004, Mark Fuller wrote: > I don't know what an "RT ticket" is. :) I'm sorry if my bad day came through On rt.cpan.org, that's where I check for stuff to do for modules I maintain. > If I need to do something formal, tell me what to do. I know it was this way > before you tookover support. I'm sorry if I came on too strong. It just > needs an example in the POD. Well, I think what these modules need is a maintainer who uses them regularly _and_ understands the protocols involved. I took them over mainly because I wanted to fix the memory leaking/handle persistence problems so it would be more usable for Bricolage, but I don't really need them to do anything beyond that, and I can't even answer many of the questions people have about the finer details of their usage. So if anyone reading this is really motivated, I'd be happy to give you access to the SF project. I can still do the CPAN release bits if people want, or I can give someone else CPAN co-maintainership. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/ |
From: Mark F. <mar...@ea...> - 2004-04-03 07:23:34
|
Dave, I have entered the "rt". I appreciate your taking ownership/support of these modules and I didn't intend to diminish that generosity. I was just frustrated that something as easy as updating the documentation with an example (as discussed in an email last November?, and a posting to the mailing list a few months later) was delayed this long. If I was supposed to make a more formal request I didn't realize it. Frankly, I don't know how I figured out how the ssh-parms worked and I feel sorry for anyone who has to repeat the exericise. You didn't create it that way. But, after discovering it, it seems like just documenting it would be a huge step forward. It's in "rt" now. I'm sorry if I was disrespectful of your volunteer role. I'm eager to help any way I can. Mark ----- Original Message ----- From: "Dave Rolsky" <au...@ur...> To: "Mark Fuller" <mar...@ea...> Cc: "Vitali Cesare" <CV...@me...>; <ssh...@li...> Sent: Saturday, April 03, 2004 12:03 AM Subject: Re: [Ssh-sftp-perl-users] Change port used in Net::SFTP > On Fri, 2 Apr 2004, Mark Fuller wrote: > > > I don't know what an "RT ticket" is. :) I'm sorry if my bad day came through > > On rt.cpan.org, that's where I check for stuff to do for modules I > maintain. > > > If I need to do something formal, tell me what to do. I know it was this way > > before you tookover support. I'm sorry if I came on too strong. It just > > needs an example in the POD. > > Well, I think what these modules need is a maintainer who uses them > regularly _and_ understands the protocols involved. I took them over > mainly because I wanted to fix the memory leaking/handle persistence > problems so it would be more usable for Bricolage, but I don't really need > them to do anything beyond that, and I can't even answer many of the > questions people have about the finer details of their usage. > > So if anyone reading this is really motivated, I'd be happy to give you > access to the SF project. I can still do the CPAN release bits if people > want, or I can give someone else CPAN co-maintainership. > > > -dave > > /*======================= > House Absolute Consulting > www.houseabsolute.com > =======================*/ > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Ssh-sftp-perl-users mailing list > Ssh...@li... > https://lists.sourceforge.net/lists/listinfo/ssh-sftp-perl-users |