Revision tags: release/14.0.0 |
|
#
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 ...
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0 |
|
#
8e9b3e70 |
| 03-Jul-2018 |
Hartmut Brandt <harti@FreeBSD.org> |
Update bsnmp to version 1.13. This does not bring user-visible changes. For developers gensnmptree can now generate functions for enums to convert between enums and strings and to check the validity
Update bsnmp to version 1.13. This does not bring user-visible changes. For developers gensnmptree can now generate functions for enums to convert between enums and strings and to check the validity of a value. The sources in FreeBSD are now in sync with the upstream which allows to bring in IPv6 modifications.
show more ...
|
Revision tags: release/11.2.0 |
|
#
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 ...
|
Revision tags: release/10.4.0, release/11.1.0 |
|
#
e1d581b2 |
| 28-Dec-2016 |
Enji Cooper <ngie@FreeBSD.org> |
style(9): clean up trailing whitespace
MFC after: 3 weeks
|
Revision tags: release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0 |
|
#
8fa0b743 |
| 23-Jan-2012 |
Xin LI <delphij@FreeBSD.org> |
IFC @230489 (pending review).
|
#
80dbff4e |
| 04-Jan-2012 |
Sean Bruno <sbruno@FreeBSD.org> |
IFC to head to catch up the bhyve branch
Approved by: grehan@
|
Revision tags: release/9.0.0 |
|
#
3df5ecac |
| 30-Dec-2011 |
Ulrich Spörlein <uqs@FreeBSD.org> |
Spelling fixes for usr.sbin/
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0 |
|
#
f02a1e57 |
| 15-Dec-2006 |
Shteryana Shopova <syrinx@FreeBSD.org> |
Do not add 'default:' cases inside a switch() on an enum like the SNMP option argument. That way the compiler will give a warning in case of a missing or an extra but unknown 'case:'. Do the same for
Do not add 'default:' cases inside a switch() on an enum like the SNMP option argument. That way the compiler will give a warning in case of a missing or an extra but unknown 'case:'. Do the same for SNMP LEAF objects to be prepared once gensnmptree will auto-generate enums for those too. Add an abort() after the switch() instead of the 'default:' to catch any errors. The nice side effect is that the compiler will correctly track supposed to be 'uninitialized' variables with that.
When trying to set a value sanity check it before calling the OS dependent API of snmp_bridge to tell whether it is an attempt to set a bad value or a general error.
Suggested by: harti (first part) Approved by: bz (mentor)
show more ...
|
#
5b6598a8 |
| 09-Dec-2006 |
Shteryana Shopova <syrinx@FreeBSD.org> |
Instead of explicitly initializing variables to avoid compiler warnings, add a default case to handle the situation when the variables are not initialized. Furthermore, abort() if the snmp agent pass
Instead of explicitly initializing variables to avoid compiler warnings, add a default case to handle the situation when the variables are not initialized. Furthermore, abort() if the snmp agent passes an invalid option to the bridge module. As the option (SET, GET, GETNEXT, COMMIT, ROLLBACK) is determined by the snmp agent based on the operation requested by user, this behaviour is unlikely to be abused as a source for a DoS, but if ever hit will likely reveal a problem in the snmp agent or bridge module.
Approved by: bz (mentor)
show more ...
|
#
7850265e |
| 19-Nov-2006 |
Shteryana Shopova <syrinx@FreeBSD.org> |
Bring in a SNMP module to support monitoring if_bridge(4) interfaces via bsnmpd(1). The module implements IETF BRIDGE-MIB as defined in RFC4188 and a private BEGEMOT-BRIDGE-MIB.
Sponsored by: Googl
Bring in a SNMP module to support monitoring if_bridge(4) interfaces via bsnmpd(1). The module implements IETF BRIDGE-MIB as defined in RFC4188 and a private BEGEMOT-BRIDGE-MIB.
Sponsored by: Google Summer of Code 2006 Reviewed by: bz Approved by: bz (mentor)
show more ...
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0 |
|
#
f02a1e57 |
| 15-Dec-2006 |
Shteryana Shopova <syrinx@FreeBSD.org> |
Do not add 'default:' cases inside a switch() on an enum like the SNMP option argument. That way the compiler will give a warning in case of a missing or an extra but unknown 'case:'. Do the same for
Do not add 'default:' cases inside a switch() on an enum like the SNMP option argument. That way the compiler will give a warning in case of a missing or an extra but unknown 'case:'. Do the same for SNMP LEAF objects to be prepared once gensnmptree will auto-generate enums for those too. Add an abort() after the switch() instead of the 'default:' to catch any errors. The nice side effect is that the compiler will correctly track supposed to be 'uninitialized' variables with that.
When trying to set a value sanity check it before calling the OS dependent API of snmp_bridge to tell whether it is an attempt to set a bad value or a general error.
Suggested by: harti (first part) Approved by: bz (mentor)
show more ...
|
#
5b6598a8 |
| 09-Dec-2006 |
Shteryana Shopova <syrinx@FreeBSD.org> |
Instead of explicitly initializing variables to avoid compiler warnings, add a default case to handle the situation when the variables are not initialized. Furthermore, abort() if the snmp agent pass
Instead of explicitly initializing variables to avoid compiler warnings, add a default case to handle the situation when the variables are not initialized. Furthermore, abort() if the snmp agent passes an invalid option to the bridge module. As the option (SET, GET, GETNEXT, COMMIT, ROLLBACK) is determined by the snmp agent based on the operation requested by user, this behaviour is unlikely to be abused as a source for a DoS, but if ever hit will likely reveal a problem in the snmp agent or bridge module.
Approved by: bz (mentor)
show more ...
|
#
7850265e |
| 19-Nov-2006 |
Shteryana Shopova <syrinx@FreeBSD.org> |
Bring in a SNMP module to support monitoring if_bridge(4) interfaces via bsnmpd(1). The module implements IETF BRIDGE-MIB as defined in RFC4188 and a private BEGEMOT-BRIDGE-MIB.
Sponsored by: Googl
Bring in a SNMP module to support monitoring if_bridge(4) interfaces via bsnmpd(1). The module implements IETF BRIDGE-MIB as defined in RFC4188 and a private BEGEMOT-BRIDGE-MIB.
Sponsored by: Google Summer of Code 2006 Reviewed by: bz Approved by: bz (mentor)
show more ...
|