I was trying to help out last night in irc.
I tried a lot of things with curl and wget. Could not get any to work. I
did not try the + instead of @ trick in the username bit though.
The thing causing it is the cert is in a different name to the servername.
I was able to get this bash script,
That is outside of my skill set.
Michael
Ben Hamilton (Ben Bradshaw) wrote on 2/12/21 12:21 PM:
Can you recompile curl with ftpes support?
Sent from my iPhone
On Feb 12, 2021, at 2:15 PM, wa7skg wrote:
I finally found the answer, but it doesn't help.
Supposedly, to use FTP over TLS in
And how do I incorporate that into RDCatch?
Michael
Kit Haskins wrote on 2/12/21 12:10 PM:
Would wget work ?
wget -r --level=5 -m --no-remove-listing --reject "index.html" -c
--progress=dot -N --secure-protocol=auto --no-proxy --no-passive-ftp
--ftp-user=X --ftp-password=Y
Can you recompile curl with ftpes support?
Sent from my iPhone
> On Feb 12, 2021, at 2:15 PM, wa7skg wrote:
>
> I finally found the answer, but it doesn't help.
>
> Supposedly, to use FTP over TLS in EXPLICIT mode, you use ftpes instead of
> ftps. However, that kicks back with
>
> curl:
Would wget work ?
wget -r --level=5 -m --no-remove-listing --reject "index.html" -c
--progress=dot -N --secure-protocol=auto --no-proxy --no-passive-ftp
--ftp-user=X --ftp-password=Y --no-check-certificate
ftps://.com:21
I finally found the answer, but it doesn't help.
Supposedly, to use FTP over TLS in EXPLICIT mode, you use ftpes instead
of ftps. However, that kicks back with
curl: (1) Protocol ftpes not supported or disabled in libcurl
So, I guess we're either going to have to do it manually in Filezilla
On 2/11/21 21:54, wa7skg wrote:
>
> Sorry, no joy.
>
> I can't get RDCatch to work for me over SSH right now.
>
> I'm trying this initially using curl from cli.
>
> curl -u u...@host.com:password ftps://hostname.com/path/program.mp3
>
> I get the error
>
> curl: (7) Failed connect to
On 2/11/21 17:44, wa7skg wrote:
>
> I think I found my problem. There are two types of FTP over TLS.
> Explicit uses port 21 while implicit uses port 990. Apparently
> RDCatch/curl uses implicit over port 990, which the host does not
> accept. In Filezilla, I have an option to select implicit or
Sorry, no joy.
I can't get RDCatch to work for me over SSH right now.
I'm trying this initially using curl from cli.
curl -u u...@host.com:password ftps://hostname.com/path/program.mp3
I get the error
curl: (7) Failed connect to hostname.com:990; Connection timed out
when I try normally.
I think I found my problem. There are two types of FTP over TLS.
Explicit uses port 21 while implicit uses port 990. Apparently
RDCatch/curl uses implicit over port 990, which the host does not
accept. In Filezilla, I have an option to select implicit or explicit.
Is there any way to specify
You might need double backslash... But I doubt it. You might at a command
line though... Can you try with curl directly?
Also I seem to remember some ftp daemons that supported + in lieu of @ for
usernames with "@" in them, perhaps this is one of them?
Eric
On Tue, Feb 9, 2021, 2:47 PM
FTPS (FTP over TLS, as opposed to SFTP, Secure Shell FTP) is supported
starting with Rivendell 3.5.0. SFTP has been supported for a long time,
FTPS support is new.
The URL should look like: ftps://host.name/path-maybe-with-wildcards
In what way does the "@" foul things up? I wonder if escaping
Thank you for the FTPS tip. I never saw that as an option anywhere. I
haven't dealt with FTP over TLS before, and there is no reference to it
in the OpsGuide.
As far as the @ is concerned, I was just getting a "failed to connect"
error. I tried the username\@hostname escape, but RDCatch did
We have a program provider who has changed his ftp server and I have
run into two issues.
First, he specifies he is using FTP over TLS. I'm not sure how to set
this up in RDCatch.
The other problem is he is using an email address for a username. I know
this is common for users accessing
14 matches
Mail list logo
