| #
b3e76948
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
| #
4d846d26
|
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
| #
b3e76948
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line .h pattern
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
|
| #
4d846d26
|
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
| #
1de7b4b8
|
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
| #
61a651a4
|
| 27-Aug-2009 |
Brian Somers <brian@FreeBSD.org> |
MFC: When ``ppp -direct'' is invoked by a program that uses pipe(2) to create stdin and stdout, don't blindly try to use stdin as a bi-directional channel. Instead, detect the pipe and set
MFC: When ``ppp -direct'' is invoked by a program that uses pipe(2) to create stdin and stdout, don't blindly try to use stdin as a bi-directional channel. Instead, detect the pipe and set up a special exec handler that indirects write() calls through stdout.
This fixes the problem where ``set device "!ssh -e none host ppp -direct label"'' no longer works with an openssh-5.2 server side as that version of openssh ignores the USE_PIPES config setting and *always* uses pipes (rather than socketpair) for stdin/stdout channels.
Approved by: re (kib)
show more ...
|
| #
1de7b4b8
|
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
| #
61a651a4
|
| 27-Aug-2009 |
Brian Somers <brian@FreeBSD.org> |
MFC: When ``ppp -direct'' is invoked by a program that uses pipe(2) to create stdin and stdout, don't blindly try to use stdin as a bi-directional channel. Instead, detect the pipe and set
MFC: When ``ppp -direct'' is invoked by a program that uses pipe(2) to create stdin and stdout, don't blindly try to use stdin as a bi-directional channel. Instead, detect the pipe and set up a special exec handler that indirects write() calls through stdout.
This fixes the problem where ``set device "!ssh -e none host ppp -direct label"'' no longer works with an openssh-5.2 server side as that version of openssh ignores the USE_PIPES config setting and *always* uses pipes (rather than socketpair) for stdin/stdout channels.
Approved by: re (kib)
show more ...
|
| #
10b3b545
|
| 17-Sep-2009 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Merge from head
|
| #
cbd59a4f
|
| 08-Sep-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC from head@196987
|
| #
887ff31f
|
| 24-Aug-2009 |
Brian Somers <brian@FreeBSD.org> |
When ``ppp -direct'' is invoked by a program that uses pipe(2) to create stdin and stdout, don't blindly try to use stdin as a bi-directional channel. Instead, detect the pipe and set up a special e
When ``ppp -direct'' is invoked by a program that uses pipe(2) to create stdin and stdout, don't blindly try to use stdin as a bi-directional channel. Instead, detect the pipe and set up a special exec handler that indirects write() calls through stdout.
This fixes the problem where ``set device "!ssh -e none host ppp -direct label"'' no longer works with an openssh-5.2 server side as that version of openssh ignores the USE_PIPES config setting and *always* uses pipes (rather than socketpair) for stdin/stdout channels.
MFC after: 3 days
show more ...
|
| #
057f1760
|
| 05-Sep-2004 |
Brian Somers <brian@FreeBSD.org> |
Make ppp WARNS=5 clean
|
| #
de59e178
|
| 14-May-2002 |
Brian Somers <brian@FreeBSD.org> |
o Clean up some #includes o Bump version number to 3.0.4 o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal to the SES
o Clean up some #includes o Bump version number to 3.0.4 o When talking to a RADIUS server, provide a NAS-Port-Type.
When the NAS-Port-Type is Ethernet, provide a NAS-Port value equal to the SESSIONID from the environment in direct mode or the NGM_PPPOE_SESSIONID message in other modes. If no SESSIONID is found, default to the interface index in client mode or zero in server mode.
When the NAS-Port-Type is ISDN, set the NAS-Port to the minor number of the physical device (ie, the N in /dev/i4brbchN).
This makes it easier for the RADIUS server to identify the client WRT accounting data etc.
Prompted by: lsz8425 <lsz8425@mail.cd.hn.cn>
show more ...
|
| #
fb11a9c2
|
| 30-Mar-2002 |
Brian Somers <brian@FreeBSD.org> |
Merge the NETGRAPH branch into HEAD. tty devices now use netgraph's line discipline to do the async escaping, but no other benefits are available yet.
Change ``ifdef HAVE_DES'' to ``ifndef NODES''
Merge the NETGRAPH branch into HEAD. tty devices now use netgraph's line discipline to do the async escaping, but no other benefits are available yet.
Change ``ifdef HAVE_DES'' to ``ifndef NODES'' for consistency.
Make the Makefile a little more sane WRT RELEASE_CRUNCH.
show more ...
|
| #
c8b9fb53
|
| 18-Jun-2001 |
Brian Somers <brian@FreeBSD.org> |
Handle hardware-imposed MTU/MRU limitations. PPPoE will no longer allow MRU/MTU negotiations to exceed 1492.
Add an optional ``max'' specifier to ``set m[rt]u'', ie.
set mtu max 1480
Bump the pp
Handle hardware-imposed MTU/MRU limitations. PPPoE will no longer allow MRU/MTU negotiations to exceed 1492.
Add an optional ``max'' specifier to ``set m[rt]u'', ie.
set mtu max 1480
Bump the ppp version number.
Sponsored by: Monzoon Networks AG and FreeBSD Services Limited
show more ...
|
| #
68602c3e
|
| 18-Aug-2000 |
Brian Somers <brian@FreeBSD.org> |
Make -DNOSUID (or -DPPP_NOSUID) possible to build ppp without SUID capabilities.
|
| #
a1bc3dcc
|
| 22-Jun-2000 |
Brian Somers <brian@FreeBSD.org> |
Correct PPPoE in multi-link mode Submitted by: jason@OpenBSD.org
|
| #
07e4efad
|
| 26-May-2000 |
Brian Somers <brian@FreeBSD.org> |
Remove an unused variable
|
| #
d9626e94
|
| 24-May-2000 |
Brian Somers <brian@FreeBSD.org> |
Honour ``set speed sync'' and ``set device !program'' when used together by creating a SOCK_DGRAM socketpair() between the processes.
Be polite when closing !program links and send a HUP to the proc
Honour ``set speed sync'' and ``set device !program'' when used together by creating a SOCK_DGRAM socketpair() between the processes.
Be polite when closing !program links and send a HUP to the process. This makes ssh tunnels over unreliable media (such as via httptunnel) reconnect properly.
show more ...
|
| #
3ce91245
|
| 22-Mar-2000 |
Brian Somers <brian@FreeBSD.org> |
Do some vfork() trickery so that the parent can determine if the childs exec() has succeeded or failed by taking advantage of the fact that both processes share the same memory.
FWIW: I tried to i
Do some vfork() trickery so that the parent can determine if the childs exec() has succeeded or failed by taking advantage of the fact that both processes share the same memory.
FWIW: I tried to implement this by doing a pipe(), setting the write desciptors close-on-exec flag in the child and writing errno to the descriptor if the exec() fails. The parent can then ``if (read()) got errno else exec worked''.
This didn't work though - the child could write() to fd[1] on exec failure, but the parent got 0 trying to read() from fd[0] ! Is this a bug in execve() ?
show more ...
|
| #
8e7bd08e
|
| 14-Mar-2000 |
Brian Somers <brian@FreeBSD.org> |
Correct some typos introduced in the descriptor -> fdescriptor change.
|
| #
f013f33e
|
| 14-Mar-2000 |
Brian Somers <brian@FreeBSD.org> |
To avoid namespace polution in NetBSD:
``struct descriptor'' -> ``struct fdescriptor''
|
| #
e7d008b4
|
| 30-Dec-1999 |
Brian Somers <brian@FreeBSD.org> |
Add a few missing #includes
|
| #
a19a5c02
|
| 30-Dec-1999 |
Brian Somers <brian@FreeBSD.org> |
Correct usages of getuid() and geteuid()
Pointed out by: billf
|
| #
5b78bdf8
|
| 27-Dec-1999 |
Brian Somers <brian@FreeBSD.org> |
Don't allowt '#' as a comment when it's embedded in quotes:
set something "xxx yyy # zzz" aaa
shouldn't be interpreted as
set something "xxx yyy" aaa
|