| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
the crunched binary) get a non-cryptographic telnet. This is overkill
in that it covers stuff that is not normally used in a crunched binary.
|
|
|
|
| |
distribution is used. This only affects release-building.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, there were two copies of telnet; a non-crypto version
that lived in the usual places, and a crypto version that lived in
crypto/telnet/. The latter was built in a broken manner somewhat akin
to other "contribified" sources. This meant that there were 4 telnets
competing with each other at build time - KerberosIV, Kerberos5,
plain-old-secure and base. KerberosIV is no longer in the running, but
the other three took it in turns to jump all over each other during a
"make buildworld".
As the crypto issue has been clarified, and crypto _calls_ are not
a problem, crypto/telnet has been repo-copied to contrib/telnet,
and with this commit, all telnets are now "contribified". The contrib
path was chosen to not destroy history in the repository, and differs
from other contrib/ entries in that it may be worked on as "normal"
BSD code. There is no dangerous crypto in these sources, only a
very weak system less strong than enigma(1).
Kerberos5 telnet and Secure telnet are now selected by using the usual
macros in /etc/make.conf, and the build process is unsurprising and
less treacherous.
|
|
|
|
| |
$FreeBSD$ tags and some debug variable safety belts.
|
|
|
|
| |
earlier invocation of unifdef(1).
|
| |
|
|
|
|
|
| |
PR: 45476
MFC after: 5 days
|
|
|
|
|
|
| |
no changes (against crypto telnet).
Reviewed by: MD5
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also change one case of blatant __progname abuse (several more remain)
This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
| |
|
| |
|
|
|
|
|
|
|
| |
this case 16). Use dynamic FD_SETs and calculated high-water marks
throughout.
Obtained from: OpenBSD and Apple's Radar database
MFC after: 2 days
|
|
|
|
| |
the kerberos libraries and includes.
|
| |
|
| |
|
|
|
|
| |
a complete subset of the crypto (master) code.
|
|
|
|
|
| |
Also, add an "unifdef:" target, so that the telnet sources can
be remade from the crypto sources in src/crypto/telnet.
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
Also remove useless AUTHENTICATION code. We have never compiled this
here, and it is doubtful that it even works without crypto.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o This option is not available outside of the United States and Canada.
o Because of export controls, TELNET ENCRYPT option is not supported outside
of the United States and Canada.
src/crypto/README revision 1.5 commit log says:
> Crypto sources are no longer export controlled:
> Explain, why crypto sources are still in crypto/.
and actually telnet encryption is used outside of US and Canada now.
Pointed out by: OHSAWA Chitoshi <ohsawa@catv1.ccn-net.ne.jp>
Reviewed by:no objection on doc
|
| |
|
| |
|
| |
|
|
|
|
| |
Idea from: Theo de Raadt <deraadt@openbsd.org>
|
| |
|
|
|
|
| |
Make usage fit on a standard 80-column display.
|
|
|
|
| |
Obtained from: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
|
| |
|
|
|
|
| |
Approved by: markm
|
|
|
|
| |
(used by install floppy/picobsd)
|
|
|
|
| |
Compatability is not an existing english word.
|
|
|
|
|
|
| |
Seperate does not exist in the english language.
Also add $FreeBSD$ to README.
|
|
|
|
| |
There is no such thing as wierd in the english language.
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Edwin Groothuis <mavetju@chello.nl>
PR: bin/22787
|
| |
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
|
|
|
|
| |
is not exploitable because telnet doesn't run with elevated privs.
Didn't fix all the other potential buffer overflows. Would be a good
task for someone who has lots of time to carefully study each case
because cut and paste solutions are dangerous for this code base.
Added $FreeBSD$ in the same way that command.c did it.
|
|
|
|
| |
getopt returns -1 not EOF.
|
|
|
|
|
| |
PR: bin/20053
Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su>
|
| |
|
|
|
|
| |
change (getaddrinfo.c rev 1.12).
|
|
|
|
|
|
| |
XXX what is the goal of af_switch()? it seems to me it is not necessary
any more with getaddrinfo(3) fix for correct name-resolution ordering.
comments? >shin
|