summaryrefslogtreecommitdiffstats
path: root/usr.bin/diff/diff.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-01-23remove special casing for IFT_MPLSTUNNEL now mpw is IFT_ETHER.dlg1-27/+2
2019-01-23Make route(8) show the same flags in RTM_IFINFO messages askrw1-3/+5
ifconfig(8) shows in its display of interface information. ok bluhm@
2019-01-23rework mpw to be an actual ethernet interface.dlg1-111/+48
this will allow for a lot of special casing in places like vlan and bridge to go away since mpw will do all the same things as any other ethernet tunnel. another benefit is you can run stuff directly on the mpw interface to interact with the pseudowire, rather than requiring a bridge and vether interface. this is like what juniper calls Pseudowire Service Interfaces. the caveat is that the implicit vlan or svlan tagging that mpw did in ethernet-tagged mode now has to be done by hand. however, there is some indication that different vendors pick different types of tags, ie, one uses vlan tags and another uses svlan, so being able to configure the right one has value. it is also possible you would want to bridge the entire tag stack to another site, so being able to bridge mpw without it playing with the tags can be useful. because the if_type on mpw changes from IFT_MPLSTUNNEL to IFT_ETHER, the semantic used to handle incoming packets in mpls_input is changed. instead of mpls_input pushing the packets into mpw based on the if_type being IFT_MPLSTUNNEL, mpw now adds an RTF_LOCAL route to the mpls table. mpls_input falls through to "outputting" the packet to mpw_output, which then uses the RTF_LOCAL flag to decide to input to mpw_input and then ether_input. this semantic will be applied to mpe soon, which removes all the interface special casing in mpls_input. the if_type change also means mpw implements the SIOCGPWE3 ioctl so ldpd can still figure out that the interface is a pseudowire. ok claudio@
2019-01-23rework grep_open to be more careful about directories.tedu5-64/+53
cleaner, but should be no functional change. from Lauri Tirkkonen
2019-01-23eliminate a ?: in witness mtx initializer by pushing the default onetedu2-5/+5
level up. ok guenther mpi visa
2019-01-23machdep.apmwarn and machdep.apmhalt were removed in 2017jsg5-125/+13
2019-01-23assert.h is often misused. It should not be used in a librarybeck2-8/+5
ok bcook@ jsing@
2019-01-23Nuke unused variable.krw1-3/+1
ok phessler@
2019-01-23Sprinkle a pinch of timerisvalid/timespecisvalid over the rest of sys/kerncheloha4-16/+14
2019-01-23Remove support for obsolete host/port syntax.dtucker3-11/+16
host/port was added in 2001 as an alternative to host:port syntax for the benefit of IPv6 users. These days there are establised standards for this like [::1]:22 and the slash syntax is easily mistaken for CIDR notation, which OpenSSH now supports for some things. Remove the slash notation from ListenAddress and PermitOpen. bz#2335, patch from jjelen at redhat.com, ok markus@
2019-01-23Remove duplicate word. bz#2958, patch from jjelen at redhat.comdtucker1-3/+3
2019-01-23fix dumping of trace cmp coverageanton1-2/+2
2019-01-23Modify sigalgs extension processing to accomodate TLS 1.3.beck8-40/+93
- Make a separate sigalgs list for TLS 1.3 including only modern algorithm choices which we use when the handshake will not negotiate TLS 1.2. - Modify the legacy sigalgs for TLS 1.2 to include the RSA PSS algorithms as mandated by RFC8446 when the handshake will permit negotiation of TLS 1.2 from a 1.3 handshake. ok jsing@ tb@
2019-01-23revert previous, accidentally contained another diff in additionbeck10-408/+61
to the one I intended to commit
2019-01-23Modify sigalgs extension processing for TLS 1.3.beck10-61/+408
- Make a separate sigalgs list for TLS 1.3 including only modern algorithm choices which we use when the handshake will not negotiate TLS 1.2 - Modify the legacy sigalgs for TLS 1.2 to include the RSA PSS algorithms as mandated by RFC8446 when the handshake will permit negotiation of TLS 1.2 ok jsing@ tb@
2019-01-23Remove uneeded header.mpi1-2/+1
2019-01-23Pass an `ifp' pointer to bridge_ourether().mpi1-6/+6
ok kn@, claudio@, visa@
2019-01-23Only copy packets for span ports if the bridge is UP.mpi1-4/+3
ok claudio@, kn@, visa@
2019-01-23import unwindctlflorian5-0/+585
"toss it in man" deraadt@
2019-01-23Import unwind(8).florian17-0/+5407
unwind(8) is a hybrid validating stub & recursive resolver. It actively observes the local net to decide how to best resolve names. It can chose to recurse on it's own or talk to dhcp provided forwardes or statically defined forwarders in the config file. The intention is to be able to run it on localhost on every machine. "toss it in man" deraadt@
2019-01-23Import bits from (lib)unbound that we need for unwind(8).florian178-0/+119135
This is probably too much but allows us to keep in sync with usr.sbin/unbound to be able to easily apply updates.
2019-01-23Sync the handshakes table with the generated table in regress.tb1-19/+19
This sorts the valid handshakes with respect to ascending flags value instead of the ad-hoc order produced by the algorithm. ok jsing
2019-01-23Move 802.11n rateset definitions out of MiRA and make them available tostsp7-115/+178
net80211 and drivers in general. Add ratesets for 'short guard interval' (SGI) rates, and add SGI support to MiRA. SGI is currently only used by iwm(4), and of course internally by bwfm(4) firmware. Ratesets for 11n 40 MHz channels and 11ac will come later. ok mpi@ phessler@
2019-01-23sets for apm(4) on arm64phessler3-0/+8
OK jsg@
2019-01-23add a man page for apm(4) on arm64phessler2-2/+220
OK jsg@
2019-01-23enable the apm(4) programs on arm64phessler2-10/+10
previous version OK deraadt@ patrick@ OK jsg@
2019-01-23enable the apm(4) subsystem on arm64phessler1-1/+2
previous version OK deraadt@ patrick@ OK jsg@
2019-01-23Add the apm(4) subsystem to arm64.phessler8-6/+468
NB: acpi(4) is not hooked up to this yet. previous version OK deraadt@ patrick@ OK jsg@
2019-01-23Remove 3 as a guess for possible generator during moduli generation.dtucker1-3/+1
It's not mentioned in RFC4419 and it's not possible for Sophie-Germain primes greater than 5. bz#2330, from Christian Wittenhorst , ok djm@ tb@
2019-01-23teach ldpd to ask if a potential pseudowire interface can do pwe3dlg3-10/+35
this makes ldpd open the ioctl socket early so the config parser can run the SIOCGPWE3 ioctl against the requested interface. ok claudio@
2019-01-23incorrrect spellingtb1-2/+2
2019-01-23do not print the command in the print: targettb1-2/+2
2019-01-23add a SIOCGPWE3 ioctl for interfaces to advertise pwe3 capabilitydlg2-2/+7
im going to turn mpw into an ethernet interface, which includes changing its if_type to IFT_ETHER. currently ldpd looks for if_type IFT_MPLSTUNNEL to decide if an interface is a pseudowire, ie, it's going to break. the ioctl will let ldpd ask the interface if it is pseudowire capable as an alternative. ok claudio@
2019-01-23Sanitize scp filenames via snmprintf. To do this we move thedtucker5-44/+55
progressmeter formatting outside of signal handler context and have the atomicio callback called for EINTR too. bz#2434 with contributions from djm and jjelen at redhat.com, ok djm@
2019-01-23allow auto-incrementing certificate serial number for certs signeddjm2-7/+20
in a single commandline.
2019-01-23Add a regression test that builds up the handshake state tabletb2-1/+399
from graph information and cross-checks it against the state table in tls13_handshake.c. with help from jsing
2019-01-23Remove static from handshakes[][] so it is visible from regress/tb1-2/+2
ok bcook
2019-01-23move a bunch of global flag variables to main(); make the rest staticdjm1-94/+82
2019-01-23factor out parsing of ldp router ids by making it part of the grammardlg1-42/+26
this way we do the inet_aton and bad address check in one place, and just reuse it in the router-id, neighbor, and pseudowire bits. ok claudio@
2019-01-23rework how tcp md5 signatures are configured.dlg11-126/+399
previously ldpd only allowed tcp md5 to be configured against a neighbor (by ldp router id), but other vendors supported configuring tcp md5sig by prefix as well as neighbor. this reworks the config so auth is maintained globally as a list of prefixes that you do and do not want to do tcp md5sig auth with. the config statements look more like what is in bgpd.conf now too. an example of the new config for interoperating with my baby cisco test network: on ios: mpls ldp password required for MPLS mpls ldp password option 1 for MPLS key-chain LDPAUTH key chain LDPAUTH key 1 key-string secret interface Loopback0 ip address 192.168.0.0 255.255.255.255 end ip prefix-list MPLS seq 5 permit 192.168.0.0/24 ip access-list standard MPLS mpls ldp router-id Loopback0 force and in ldpd.conf: router-id 192.168.0.25 tcp md5sig password secret 192.168.0.0/24 address-family ipv4 { interface vmx1 } this still supports specifying tcp md5sig on neighbors, but that is syntactic sugar around adding entries to the list of auths. ok (and lots of help from) claudio@
2019-01-23switch mainloop from select(2) to poll(2); ok deraadt@djm1-22/+19
2019-01-23No need to include <bsd.prog.mk> here.tb2-4/+2
ok bcook
2019-01-23futimens(2), futimes(2), utimensat(2), utimes(2): Validate input at copyincheloha1-15/+25
Currently we validate time input for all four of these syscalls in the workhorse function dovutimens(). This is bad because both futimes(2) and utimes(2) have input as timevals that need to be converted to timespecs. This multiplication can overflow to create a "valid" input, e.g. if tv_usec is equal to 2^61 (invalid value) on a platform with 64-bit longs, the resulting tv_nsec is equal to zero (valid value). This is also a bit wasteful. We aquire a vnode and do other work under KERNEL_LOCK only to release the vnode when the time input is invalid. So, duplicate a bit of code to validate the time inputs before we do any conversions or real VFS work. probably still ok tedu@ deraadt@
2019-01-23pass most arguments to the KEX hash functions as sshbuf ratherdjm5-63/+80
than pointer+length; ok markus@
2019-01-22add some definitions used by elftoolchain's libelfjsg1-1/+15
ok guenther@
2019-01-22backoff reading messages from active connections when the input bufferdjm1-4/+18
is too full to read one, or if the output buffer is too full to enqueue a response; feedback & ok dtucker@
2019-01-22The kernel interpreted bogus lengths in RPC calls during NFS boot.bluhm1-8/+31
A malicious rpc.bootparamd could corrupt memory, but the kernel has to trust the local network anyway in a diskless environment. Now in case of an RPC error, the kernel will stop booting with a specific panic. OK claudio@ beck@
2019-01-22Add file # and block # to the information "mt status" shows.krw1-1/+3
diff from Oscar Endre Edvardsen via misc@ a long time ago. ok sthen@ dlg@
2019-01-22add -m to usage(); reminded by jmc@djm1-3/+4
2019-01-22namei can return a null dvp on success. check this before access.tedu1-3/+4
ok beck Reported-by: syzbot+cc59412ed8429450a1ae@syzkaller.appspotmail.com
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.