| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
- move ftp-proxy from libexec to usr.sbin
- add tftp-proxy
- new altq mtag link
Approved by: re (kensmith)
|
|
|
|
|
| |
Sort FILES section while there.
Touch document date.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
errno is irrelevant. Some code duplication can be reduced
if perr() is variadic and perrx() is available.
|
|
|
|
|
| |
Besides aesthetic benefits, that makes at(1) jobs subject to such
login.conf(5) settings as resource limits.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
strncpy(dst, src, sizeof(dst));
by substituting the safer strlcpy() for strncpy().
X-Security: none (the source string isn't user-supplied)
|
|
|
|
|
| |
PR: 106049
Submitted by: edwin (as part of a larger patch)
|
|
|
|
|
| |
the case that the program is set-user-ID or set-group-ID. Add missing
annotations for LIBMAP and LIBMAP_DISABLE.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
potentially dangerous environment variables all together. It should be
noted that the run-time linker will not honnor these environment variables
if the process is tainted currently. However, once a child of the tainted
process calls setuid(2), it's status as being tainted (as defined by
issetugid(2)) will be removed. This could be problematic because
subsequent activations of the run-time linker could honnor these
dangerous variables.
This is more of an anti foot-shot mechanism, there is nothing I am
aware of in base that does this, however there may be third party
utilities which do, and there is no real negative impact of clearing
these environment variables.
Discussed on: secteam
Reviewed by: cperciva
PR: kern/109836
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
symbol lookup failures that later result in null-pointer
dereferences. This needs looking into, but since we're
close to release it's possible that it's not resolved before
that time.
|
|
|
|
| |
shared object.
|
|
|
|
|
|
|
|
|
|
| |
Warning, after symbol versioning is enabled, going back is not easy
(use WITHOUT_SYMVER at your own risk).
Change the default thread library to libthr.
There most likely still needs to be a version bump for at least the
thread libraries. If necessary, this will happen later.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
PR: docs/66265 (inspired by)
Submitted by: Michel Lavondes <fox@vader.aacc.cc.md.us>
MFC after: 1 week
|
|
|
|
|
| |
PR: threads/112297
MFC: 1 week
|
|
|
|
|
|
|
|
|
| |
Not because I admit they are technically wrong and not because of bug
reports (I receive nothing). But because I surprisingly meets so
strong opposition and resistance so lost any desire to continue that.
Anyone who interested in POSIX can dig out what changes and how
through cvs diffs.
|
| |
|
|
|
|
| |
don't allow putenv() arg be on the stack, replace putenv() with setenv()
|
|
|
|
|
|
|
| |
to override weak symbols exported by libc, so by definition these two
are using the same symbol version names.
Reflect the reality by referring to libc's Versions.def directly.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
to myself that I understand it.
Bump document date.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The support for RFC 2640 (UTF8) is optional and rudimentary.
The server just advertises its capability to handle UTF-8 file
names and relies on its own 8-bit cleanness, as well as on
the backward compatibility of UTF-8 with ASCII. So uploaded
files will have UTF-8 names, but the initial server contents
should be prepared in UTF-8 by hand, no on-the-fly conversion
of file names will be done.
PR: bin/111714
Submitted by: Zhang Weiwu <see email in the PR>
MFC after: 1 week
|
|
|
|
|
|
|
| |
libc.
Disable SYMVER_DEFAULT n rtld until its implications are understood
better.
|
|
|
|
| |
module yet.
|
|
|
|
|
|
|
|
| |
main object list, its versioning information needs to be examined
separately.
This hopefully fixes problems that people running with SYMVER_ENABLED
are experiencing.
|
| |
|
|
|
|
|
| |
Convert boolean flags in internal Obj_Entry structure into bitfields.
Properly check for loaded segment alignment in map_object.
|
|
|
|
| |
ops function prototypes.
|
|
|
|
|
| |
setting the SO_SNDBUF socket option. Using a hard-coded value for
it was a poor idea anyway in the face of diverse network conditions.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
activate the traces, set the LD_UTRACE (or LD_32_UTRACE) environment
variable. This also includes code in kdump(8) to parse the traces.
Reviewed by: kan, jdp
MFC after: 2 weeks
|
|
|
|
|
| |
Approved by: rwatson (mentor)
Reviewed by: jmg and marcel
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dso that are actually loading. If dso a.so depends on b.so, then dlsym
with handle from dlopen("b.so") will fail unconditionally.
Correct implementation shall use the Obj_Entry.needed list to walk
dependencies DAG.
Test provided by: jkim
Tested (prev. version) by: jkim, Nicolas Blais <nb_root at videotron ca>, h.blanke at chello nl
Pointy hat to: kib
Approved by: kan (mentor)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
given as dso handle, but also in the implicit dependencies of that dso.
Also, const-ify the read-only parameter objlist of symlook_list.
Reported by: "Simon 'corecode' Schubert" <corecode at fs ei tum de>
Approved by: kan (mentor)
X-MFC-After: 6.2
|
|
|
|
|
| |
that the documented TCB is at the tail of the extended TCB. In other
words, the base of the TCB has a negative offset from the TLS.
|
|
|
|
|
|
| |
the TCB.
o Use NULL for null pointer argument.
o Replace magic 8 with TLS_TCB_SIZE.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
primitives.
|
|
|
|
| |
assembly.
|