Skip Menu |

This queue is for tickets about the Net-xFTP CPAN distribution.

Report information
The Basics
Id: 58210
Status: resolved
Priority: 0/
Queue: Net-xFTP

People
Owner: turnerjw784 [...] yahoo.com
Requestors: chris [...] theclonchs.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Feature Request: Net::FTPSSL Integration
I noticed in your open bug ticket you mentioned support for Net::FTPSSL would be upcoming. I'd like to formal request this feature. I'm looking to rewrite a transfer script of my own to use your wrapper but an upcoming client needs FTP over SSL (FTPS) support. Your script is perfect for my needs sans FTPS support ATM. Thanks for your work! -Chris
Done - Upgrade to Net::xFTP, v0.4! You're welcome & Thanks, Chris! Plz rpt. any pbms in a new bug. Jim Turner On Mon Jun 07 16:37:18 2010, cacack wrote: Show quoted text
> I noticed in your open bug ticket you mentioned support for Net::FTPSSL > would be upcoming. I'd like to formal request this feature. I'm > looking to rewrite a transfer script of my own to use your wrapper but > an upcoming client needs FTP over SSL (FTPS) support. Your script is > perfect for my needs sans FTPS support ATM. > > Thanks for your work! > > -Chris
Subject: Re: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration
Date: Mon, 7 Jun 2010 21:01:34 -0700 (PDT)
To: bug-Net-xFTP [...] rt.cpan.org
From: Jim Turner <turnerjw784 [...] yahoo.com>
Done - upgrade to Net::xFTP, v. 0.4! Regards, JIm --- On Mon, 6/7/10, Chris via RT <bug-Net-xFTP@rt.cpan.org> wrote: From: Chris via RT <bug-Net-xFTP@rt.cpan.org> Subject: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration To: Date: Monday, June 7, 2010, 3:37 PM Mon Jun 07 16:37:18 2010: Request 58210 was acted upon. Transaction: Ticket created by cacack        Queue: Net-xFTP      Subject: Feature Request: Net::FTPSSL Integration    Broken in: (no value)     Severity: (no value)        Owner: Nobody   Requestors: chris@theclonchs.com       Status: new Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=58210 > I noticed in your open bug ticket you mentioned support for Net::FTPSSL would be upcoming.  I'd like to formal request this feature.  I'm looking to rewrite a transfer script of my own to use your wrapper but an upcoming client needs FTP over SSL (FTPS) support.  Your script is perfect for my needs sans FTPS support ATM. Thanks for your work! -Chris
From: chris [...] theclonchs.com
Wow, Thanks for the uber-quick response! I will be converting my code over the next few weeks so I will be sure to let you know of any problems with the module. Thanks again! -Chris
Subject: Re: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration
Date: Thu, 10 Jun 2010 06:47:41 -0700 (PDT)
To: bug-Net-xFTP [...] rt.cpan.org
From: Jim Turner <turnerjw784 [...] yahoo.com>
You're welcome, but actually I had already added it a month or so ago, but had just been lazy & forgot to put it on CPAN, but your request reminded me that I hadn't done so, so thanks!  It's always nice to know that someone (else besides me) is actually using this stufff! Jim --- On Thu, 6/10/10, Chris via RT <bug-Net-xFTP@rt.cpan.org> wrote: From: Chris via RT <bug-Net-xFTP@rt.cpan.org> Subject: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration To: Date: Thursday, June 10, 2010, 7:19 AM        Queue: Net-xFTP Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=58210 > Wow, Thanks for the uber-quick response!  I will be converting my code over the next few weeks so I will be sure to let you know of any problems with the module. Thanks again! -Chris
From: chris [...] theclonchs.com
Jim, I seem to be having problems. Using "FTPSSL" as my protocol does not seem to use encryption. My target host is running Centos 5.4 with vsftpd 2.0.5-16.el5_4.1 configured with SSL. I verified FTPS is working using my Windows workstation and WinSCP. From a Linux workstation I wrote a quick xftp client to test the waters. The debug output from it shows Net::FTP being used. Here is the snippet from the session: Net::FTP>>> Net::FTP(2.77) Net::FTP>>> Exporter(5.63) Net::FTP>>> Net::Cmd(2.29) Net::FTP>>> IO::Socket::INET(1.31) Net::FTP>>> IO::Socket(1.31) Net::FTP>>> IO::Handle(1.28) Net::FTP=GLOB(0xd8359d0)<<< 220 (vsFTPd 2.0.5) Net::FTP=GLOB(0xd8359d0)>>> USER chris Net::FTP=GLOB(0xd8359d0)<<< 331 Please specify the password. Net::FTP=GLOB(0xd8359d0)>>> PASS .... Net::FTP=GLOB(0xd8359d0)<<< 230 Login successful. Net::FTP=GLOB(0xd8359d0)>>> PWD Net::FTP=GLOB(0xd8359d0)<<< 257 "/home/chris" Show quoted text
xftp> : pwd
/home/chris Show quoted text
xftp> : cwd bin
Net::FTP=GLOB(0xd8359d0)>>> CWD bin Net::FTP=GLOB(0xd8359d0)<<< 250 Directory successfully changed. I further verified no encryption by capturing the packets and inspecting with Wireshark. So the issues are: 1) Encryption was not used. 2) It some how reverted to plain FTP even though I explicitly stated I wanted encryption. This is bad as I could foresee a client which has both available and therefore my session could end up in clear text.
Subject: Re: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration
Date: Fri, 11 Jun 2010 14:15:45 -0700 (PDT)
To: bug-Net-xFTP [...] rt.cpan.org
From: Jim Turner <turnerjw784 [...] yahoo.com>
How are you specifying encryption?  Can you show me your xFTP->new() statement? JIm --- On Fri, 6/11/10, Chris via RT <bug-Net-xFTP@rt.cpan.org> wrote: From: Chris via RT <bug-Net-xFTP@rt.cpan.org> Subject: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration To: Date: Friday, June 11, 2010, 3:21 PM        Queue: Net-xFTP Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=58210 > Jim, I seem to be having problems.  Using "FTPSSL" as my protocol does not seem to use encryption. My target host is running Centos 5.4 with vsftpd 2.0.5-16.el5_4.1 configured with SSL.  I verified FTPS is working using my Windows workstation and WinSCP.  From a Linux workstation I wrote a quick xftp client to test the waters.  The debug output from it shows Net::FTP being used. Here is the snippet from the session: Net::FTP>>> Net::FTP(2.77) Net::FTP>>>   Exporter(5.63) Net::FTP>>>   Net::Cmd(2.29) Net::FTP>>>   IO::Socket::INET(1.31) Net::FTP>>>     IO::Socket(1.31) Net::FTP>>>       IO::Handle(1.28) Net::FTP=GLOB(0xd8359d0)<<< 220 (vsFTPd 2.0.5) Net::FTP=GLOB(0xd8359d0)>>> USER chris Net::FTP=GLOB(0xd8359d0)<<< 331 Please specify the password. Net::FTP=GLOB(0xd8359d0)>>> PASS .... Net::FTP=GLOB(0xd8359d0)<<< 230 Login successful. Net::FTP=GLOB(0xd8359d0)>>> PWD Net::FTP=GLOB(0xd8359d0)<<< 257 "/home/chris" Show quoted text
xftp> : pwd
/home/chris Show quoted text
xftp> : cwd bin
Net::FTP=GLOB(0xd8359d0)>>> CWD bin Net::FTP=GLOB(0xd8359d0)<<< 250 Directory successfully changed. I further verified no encryption by capturing the packets and inspecting with Wireshark.  So the issues are: 1) Encryption was not used. 2) It some how reverted to plain FTP even though I explicitly stated I wanted encryption.  This is bad as I could foresee a client which has both available and therefore my session could end up in clear text.
From: chris [...] theclonchs.com
Ahh, I'm didn't realize I needed to specify the encryption method. FYI, I was calling new() like this: my $Session = Net::xFTP->new("$Proto", "$RemoteHost", user=>"$User",password=>"$Pass") or die... However adding "Encryption => EXP_CRYPT" to the statement doesn't seem to change anything...
On Tue Jun 15 10:11:31 2010, cacack wrote: Show quoted text
> Ahh, I'm didn't realize I needed to specify the encryption method. FYI, > I was calling new() like this: > > my $Session = Net::xFTP->new("$Proto", "$RemoteHost", > user=>"$User",password=>"$Pass") or die... > > However adding "Encryption => EXP_CRYPT" to the statement doesn't seem > to change anything...
Ok, 2 pbms - one on my end & one on yours: To fix my pbm, download xFTP, v. 0.41 from my website (http://home.mesh.net/turnerjw/jim/ or from CPAN. The pbm was that v0.4 was silently using Net::FTP by mistake for FTPSSL! The issue on your end is that you will either need to also include a "use Net::FTPSSL" line in your code to get the crypting constants such as "EXP_CRYPT", or use their actual string values (ie. "E" for EXP_CRYPT)! That should fix it! Jim
Subject: Re: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration
Date: Wed, 16 Jun 2010 22:24:57 -0700 (PDT)
To: bug-Net-xFTP [...] rt.cpan.org
From: Jim Turner <turnerjw784 [...] yahoo.com>
Chris, 2 pbms - one on my end & one on yours: To fix my pbm, download xFTP, v. 0.41 from my website (http://home.mesh.net/turnerjw/jim/ or from CPAN. The pbm was that v0.4 was silently using Net::FTP by mistake for FTPSSL! The issue on your end is that you will either need to also include a "use Net::FTPSSL" line in your code to get the crypting constants such as "EXP_CRYPT", or use their actual string values (ie. "E" for EXP_CRYPT)! That should fix it!  Let me know either way, if fixed, so i can close the bug. --- On Tue, 6/15/10, Chris via RT <bug-Net-xFTP@rt.cpan.org> wrote: From: Chris via RT <bug-Net-xFTP@rt.cpan.org> Subject: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration To: Date: Tuesday, June 15, 2010, 9:11 AM        Queue: Net-xFTP Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=58210 > Ahh, I'm didn't realize I needed to specify the encryption method.  FYI, I was calling new() like this: my $Session = Net::xFTP->new("$Proto", "$RemoteHost", user=>"$User",password=>"$Pass") or die... However adding "Encryption => EXP_CRYPT" to the statement doesn't seem to change anything... --- On Tue, 6/15/10, Chris via RT <bug-Net-xFTP@rt.cpan.org> wrote: From: Chris via RT <bug-Net-xFTP@rt.cpan.org> Subject: [rt.cpan.org #58210] Feature Request: Net::FTPSSL Integration To: Date: Tuesday, June 15, 2010, 9:11 AM        Queue: Net-xFTP Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=58210 > Ahh, I'm didn't realize I needed to specify the encryption method.  FYI, I was calling new() like this: my $Session = Net::xFTP->new("$Proto", "$RemoteHost", user=>"$User",password=>"$Pass") or die... However adding "Encryption => EXP_CRYPT" to the statement doesn't seem to change anything...
Done! Upgrade to latest version. Closing ticket due to lack of news.