| 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rationale:
SIGURG is configured by ftpd to interrupt system calls, which is useful
during data transfers. However, SIGURG could interrupt I/O on the
control channel as well, which was mistaken for the end of the session.
A practical example could be aborting the download of a tiny file,
when the abort sequence reached ftpd after ftpd had passed the file
data to the system and returned to its command loop.
Reported by: ceri
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
- always check the return value from getc(3) for EOF;
- if the attempt to read the TELNET command byte has
returned EOF, exit from the loop instead of using
the EOF value as a normal character.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
pathname inside "residue" so "chrootdir" can be simply freed later.
PR: bin/53435
Submitted by: Yutaka Ishihara <yutaka at fandc.co.jp>
MFC after: 1 week
|
|
|
|
| |
MAINTAINER file (which already had entries for sendmail).
|
|
|
|
|
|
|
|
|
| |
rtld. When _DYNAMIC is referenced normally from C the global offset
table is used implicitly, but newer versions of binutils don't initialize
it statically in the binary, so this doesn't work until rtld is relocated,
which _DYNAMIC is needed for... So, as on other systems with the same
problem, we disassemble a call instruction to _DYNAMIC in order to get
its address.
|
|
|
|
| |
leave alone specifying a wrong type for one of them.
|
|
|
|
| |
Noticed by: jake
|
| |
|
|
|
|
| |
claim that they do.
|
|
|
|
|
|
|
| |
Setting the LD_DUMP_REL_PRE or LD_DUMP_REL_POST environment variables
cause rtld-elf to output a table of all relocations.
This is useful for debugging.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
as the source of defaults for terminal device parameters.
- Do duplucate code reduction and simplification enabled by
the above.
Reviewed by: green
MFC after: 1 month
|
| |
|
|
|
|
| |
- Define various things from the most recent ELF spec.
|
| |
|
|
|
|
|
|
|
|
| |
A PPP login program is started _automatically_ (i.e., without
human intervention) even with the "pl" capability unset, as soon
as a PPP frame is detected. But with "pl" set, a PPP login program
is started independently of the result of PPP detection (which is
rendered unnecessary then,) i.e. _unconditionally_.
|
|
|
|
|
|
| |
statically compiled for named to work chroot'ed, and we'd like
to be able to do that from /etc/rc.d without additional user
intervention.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
don't reveal the info in reply to the SYST command.
Get rid of using the "unix" macro at the same time. It was a rather
poor way to check if the system was Unix since there were quite a
few Unix clones out there whose cc didn't define "unix" (e.g.,
NetBSD.) It was also sensitive to the C standard used, which caused
unnecessary trouble: With -std=c99, it should have been "__unix__",
and so on.
PR: bin/50690
Submitted by: Alex Semenyaka <alexs _at_ snark.ratmir.ru>
MFC after: 1 week
|
|
|
|
| |
From NetBSD's bootpd (in src/usr.sbin/bootp)
|
|
|
|
| |
select is broken.
|
| |
|
|
|
|
|
|
|
|
| |
information could only be gleaned from the the tty descriptor itself
was neglected, so never did the tty's default settings get copied from
the kernel. Specifically, this caused all manner of ctrl-keys to not
work. Fix this by calling dogettytab() in all the proper places, and
retrieving the terminfo temporarily in dogettytab().
|
|
|
|
|
|
|
|
|
| |
Re-read gettytab(5) only if needed.
This fixes bugs introduced as long ago as in getty/main.c rev.1.15.
PR: bin/18181
MFC after: 1 month
|
|
|
|
| |
instead of just being assigned a truth value.
|
|
|
|
|
| |
the truth value to a boolean variable, especially when inside
a loop. The variable can overflow otherwise, at least in theory.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
- Use .Va, not .Em, to mark up variable-like identifiers
(capability and database entry names.)
- Stop abusing .Tn (trademark) to emphasize general phrases.
- Spot unmarked capability references.
- Add a missing line break.
Discussed with: ru
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
capabilities:
- Mark up capability identifiers.
- Don't squeeze much text into the capability table given the options
will be described below in detail.
- Keep the capability table sorted.
- Use a consistent term for a PPP login program.
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
| |
it. It's a no-op relocation.
Trigger case: ports/x11-toolkits/pango
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Initialize "rval", which would be used uninitialized
if al or pl options were set.
- Don't pass an empty string to login(1) as a user name
(this could be triggered by entering a name and then killing it
with backspace or ^U.)
- Don't loop endlessly if the al option specifies a bogus (i.e.,
not alphanumeric) auto-login name.
- Don't pass a bogus user name to login(1) if a good name were
entered and then killed with ^U.
- Exit with status 0, not 1, on receiving an EOF character,
since it's not a error condition.
MFC after: 1 week
|
| |
|
|
|
|
| |
We can't use c89 due to use of 'inline', and c99 produces bad code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- be paranoid about honoring LD_LIBMAP_DISABLE.
Suggested by: rwatson
|
|
|
|
| |
into a separate function.
|
| |
|
|
|
|
| |
libmap.conf(5) functionality.
|