Age | Commit message (Collapse) | Author |
|
!SMALL and SMALL sections. This makes future changes easier to review
and to compare with the man page's synopsis.
The usage output is the same as before so there is no change from the
user's point of view.
usage() cleanup and !SMALL/SMALL separation suggested by jmc@
ok jmc@
|
|
ok beck@ deraadt@
|
|
correct newlines. Of course, that means removing stdio use from
signal handlers. Can we find someone to rewrite the entire interactive
half of this program?
ok guenther
|
|
ok lteo@
|
|
-U command-line option.
feedback from deraadt@, halex@, and Adam Thompson
ok deraadt@ sthen@, man page changes ok jmc@
|
|
and password info before base64 encoding it for the Authorization header.
Also:
- eliminate the COOKIE_MAX_LEN constant (if they can fit it on the command
line or in their environment, surely we can malloc the base64 version)
- rename the variable with user:pass from "cookie" to "credentials"
- empty password isn't an error
- add a boolean ishttpurl so that we don't have to do strcmps on the schema
that we just set
- when looping across multiple ftp:// urls on the command line, don't
leak the username/password memory
problem noted by Se'bastien Marie (semarie-openbsd (at) latrappe.fr)
|
|
which we don;t have in base. after some discussion with jca, i've not removed
these references, but tried to make it clearer it's distributed with openssl
and not included in base;
|
|
Also, in 'ftp', always put the error message last, after the hostname/ipaddr.
ok jsing@ krw@ millert@
|
|
No functional change. Reported by Mike Small and Maxime Villard.
|
|
commit, to please lteo@
|
|
only once, and reuse the crafted SSL_CTX for further connections.
ok lteo@
|
|
From Fritjof Bornebusch.
|
|
|
|
check the server hostname against the subjectAltName extension field
and/or the CommonName DN portion. ok sthen@
|
|
|
|
ok guenther@ sthen@
|
|
kill the former. ok guenther@ sthen@
|
|
reported by matthieu. ok deraadt
|
|
ok deraadt
|
|
ok tedu@
|
|
|
|
of reason why it is processing a certain file. This will be used by the
installer for that purpose.
ok krw rpe
|
|
default. See the documentation for the `-S' switch. This also allows
setting the preferred ciphers for the communication. Documentation bits
ok'ed by jmc@, ok beck@ sthen@.
|
|
just EPIPE, else we'll just reattempt the write with non-sensical
values. From Maxime Villard (max at m00nbsd dot net).
|
|
|
|
|
|
|
|
pointer or non-const array, as that minimizes the symbols, maximizes the
placement into read-only memory, and avoids warnings from gcc -Wformat=2
when they're used as format strings.
ok deraadt@
|
|
4.2BSD servers.
ok jmc nick tedu
|
|
an https server attempts renegotiation. ok jung@
|
|
ok deraadt, halex, sthen
|
|
(matches the STANDARDS section on the ftpd(8) man page); suggested by
jmc@ in a discussion about this man page with Sebastian Rother and
myself.
ok jmc phessler
|
|
ok jmc
|
|
|
|
ok guenther millert kettenis
|
|
client got the -r switch and -d depth option.
From Jan Klemkow <j.klemkow AT wemelug DOT de>
OK haesbaert@
|
|
authentication:
- Combine the http and https usage formats into a single http[s] format
to make it more concise.
- In the AUTO-FETCHING FILES section of the ftp(1) man page, mention
that specifying "user" and "password" with HTTP and HTTPS URLs will
log in using Basic authentication (if http_proxy is not defined).
- When compiled with -DSMALL, fix ftp(1) usage so that
"[user:password@]" is not shown for http[s] since Basic authentication
is not supported with -DSMALL.
Done with a lot of discussion with and help from jmc@ (thank you!).
ok deraadt haesbaert jmc
|
|
spotted by bluhm.
ok bluhm.
|
|
RFC 3986. This allows the following idiom in ftp:
ftp http[s]://user:pass@host/file
With some pointers from halex a lot of testing and feedback from lteo,
thanks a lot.
ok lteo@
|
|
looks on the man page.
ok haesbaert jmc henning
|
|
of the connection. This is useful for testing ftp(1) over VPN tunnels.
This -s flag is present in the other BSDs, including OS X.
All work was done by Lawrence Teo, thanks (-:.
ok myself mikeb
|
|
|
|
advice and ok martynas@
|
|
|
|
|
|
responses. Yes, they are violating the rfc's. Yes they do exist anyway.
Also fix a memory leak when url_encode fails to malloc, by simply
err'ing out if so.
feedback and ok phessler@
|
|
who asked me to commit because he is just running out of the door.
|
|
ok phessler@
|
|
|
|
- if a remote file by the name '-' is retrieved, that does not imply
it should go to standard output...
- make -o '' reset any previous -o action
- properly handle multiple -o 's
ok phessler@
|