summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Sync correct ROUNDUP() from net/route.ctobhe2021-03-251-3/+2
|
* The server only sends a cookie during a HRR, not a SHtb2021-03-241-4/+4
|
* test HEAD requests, from niklas@benno2021-03-242-9/+56
|
* Responses to HEAD requests must not have a message body (even though they havebenno2021-03-243-14/+99
| | | | | a Content-Length header). HTTP RFC 7231 section 4.3.2. found by niklas@, claudio@ agrees.
* Update regress for new_cipher rename.jsing2021-03-242-6/+6
|
* Add mouse.tp.tapping example.bru2021-03-241-1/+3
| | | | ok kn@
* syncsthen2021-03-242-6/+6
|
* remove vendor name (Dell) repeated in product namesthen2021-03-241-2/+2
|
* Rename new_cipher to cipher.jsing2021-03-2411-64/+64
| | | | | | | | This is in the SSL_HANDSHAKE struct and is what we're currently negotiating, so there is really nothing more "new" about the cipher than there is the key block or other parts of the handshake data. ok inoguchi@ tb@
* Add SSL_HANDSHAKE_TLS12 for TLSv1.2 specific handshake data.jsing2021-03-245-40/+48
| | | | | | Move TLSv1.2 specific components over from SSL_HANDSHAKE. ok inoguchi@ tb@
* Improve the tap detection mechanism.bru2021-03-241-12/+21
| | | | | | | | | Revision 1.29 of wstpad.c has removed the 'maxdist' checks for multi-finger taps. While this change makes tap detection more reliable, and does not affect inputs intended for pointer movement, it might interfere with short scroll gestures. This version reorganizes the filtering code, and reintroduces a weaker version of those checks for MT touchpads.
* cd9660, mfs: do not hide generic vop functions behind #definesemarie2021-03-243-31/+15
| | | | | | | | It makes clearer which vop functions are real fileystem-implementations and which one are only stubs. No functional changes are intented. ok visa@
* make some `struct vops' members explicitly NULL instead of implicitly NULLsemarie2021-03-243-4/+8
| | | | ok mpi@
* More timespec conversions. Less 'seconds' arithmetic.krw2021-03-242-58/+75
|
* The logic in mmrw() to check whether an address is within directbluhm2021-03-241-4/+4
| | | | | | | | | | | | | map was the wrong way around. The && prevented an EFAULT error and could pass userland addresses as kernel source to copyout(9). The kernel could crash with protection fault due to an invalid offset when reading /dev/kmem. Also make the range checks stricter. Not only the start address must be valid, but also the end address must be within the region to be copied. Note that sysctl kern.allowkmem=0 makes the bug unreachable by default. OK deraadt@
* Convert openssl(1) x509 option handlinginoguchi2021-03-241-414/+747
| | | | | | | | | | | | | Apply new option handling to openssl(1) x509. To handle incremental order value, using newly added OPTION_ORDER. I left the descriptions for -CAform, -inform, and -outform as it was, for now. These description would be fixed. And digest option handler could be consolidated to one between some subcommands in the future. ok and comments from tb@, and "I'd move forward with your current plan." from jsing@
* Add option type OPTION_ORDERinoguchi2021-03-242-2/+9
| | | | | | | | | | To handle incremental order value, added new option type OPTION_ORDER. openssl(1) x509 requires this option handling, since, - -CA and -signkey require to set both filename and incremental 'num'. - -dates requires to set two variables in a row, startdate and enddate. and this couldn't be solved by OPTION_FLAG_ORD. ok tb@ and "I'd move forward with your current plan." from jsing@
* Make tap detection less restrictive for multi-finger taps.bru2021-03-241-9/+3
| | | | | | | | | In order to distinguish tap gestures from short movements, the mechanism checks whether the distance between the first and the last position of a touch exceeds the 'maxdist' limit. Some touchpads provide unreliable coordinates when more than one contact is being made simultaneously, and in this case the filter may be too strong - and superfluous, because only one-finger contacts should trigger pointer movement.
* Define a USB quirk for devices that need to keep their pipes open atjcs2021-03-244-14/+63
| | | | | | | | | | | | | | | all times, before the device is enabled and after the device is disabled by wscons. This was originally needed by umt for the Microsoft Surface Type Cover to avoid it resetting (or at least detaching and reattaching) when the touchpad was touched while at the console. A similar problem occurs with the Pinebook Pro's keyboard when switching from X to the console due to the touchpad getting disabled, so add it to ums as well. with and ok kurt
* regenjcs2021-03-242-4/+16
|
* add HAILUCK Keyboardjcs2021-03-241-1/+5
| | | | from kurt
* ensure the long-name version of ld is in the base set (rather than thederaadt2021-03-2429-15/+15
| | | | | comp set), as it is supposed to be hard-linked. found by Yoshihiro Kawamata
* Fix some ranges and type handling.martijn2021-03-232-9/+18
| | | | OK sthen@
* Add DisplayString/SnmpAdminString in accordance with recent OPENBSD-PF-MIBmartijn2021-03-231-5/+5
| | | | | | changes. OK sthen@
* Don't send DELETE notify if IKE SA is replaced because oftobhe2021-03-231-2/+2
| | | | | | | 'enforcesingleikesa'. Fixes an interop problem with strongswan if make-before-break is enabled. ok patrick@
* OCSP_basic_verify() doesn't set errno, so use tls_set_errorx()tb2021-03-231-2/+2
| | | | ok inoguchi
* change pfIfDescr and pfLogIfName from plain OCTET STRING (which has nosthen2021-03-231-11/+16
| | | | | | | | | | textual-convention so is sometimes printed as hex dump) to DisplayString (ascii). likewise change pfLabelName and pfTblName to SnmpAdminString (UTF-8 textual-convention). feedback/tweaks (notably pointing out UTF-8)/ok martijn@
* Use a pointer called bufp to point to a buffer called bufnlum2021-03-231-4/+4
| | | | consistantly.
* Correct how many arguments some functions take for interpreter.c.lum2021-03-231-31/+31
|
* Use time_t for intermediate lease time values when calculating humanflorian2021-03-231-7/+17
| | | | | | | | | | readable output for very long timeouts to prevent overflow. While here add years and days. Days might actually show up in normal leases. Years is to catch "infinity" which is encoded as UINT32_MAX and used by vmd(8). Previously we would overflow, wrap to negative which then got transformed to 0s. Pointed out by Dave Voutila while working on the vmd(8) dhcp code.
* Timed out RSA key ops, may leave uncalled for responses in the imsg returnclaudio2021-03-232-6/+24
| | | | | | path. These have to be dropped or every subsequent call will cause decrypt errors. Use a sequence number cookie to keep the systems in sync. Diff from niklas@ with some minor adjustments by myself.
* Document SIOCGIFADDR and SIOCSIFADDR ioctls for tap devices.claudio2021-03-231-2/+6
| | | | OK kn@
* Make a parameter to an mg function not throw an error justlum2021-03-231-3/+12
| | | | because it is numerical.
* Document the @version suffix that can be added when running 'portgen go'abieber2021-03-231-2/+11
| | | | Patch from Josh Rickmar. Ty jrick!
* Fix a corner case bug in Rx block ack window gap-wait timeout handling.stsp2021-03-231-1/+5
| | | | | | | | | | | | | | | If ieee80211_input_ba_flush() was called when there was nothing to flush, the (already pending) gap wait timeout was re-armed. This is only correct if we flush at least one packet. Otherwise packets that arrive at a constant rate of about 4-5 packets per second would extend the gap-wait timeout until the block ack window fills up. In extreme cases this can result in packets being queued for almost 20s. Fix this by returning immediately from ieee80211_input_ba_flush() if the first packet in the reordering buffer is missing. This prevents the timeout from being re-armed. Patch by Christian Ehrhardt. Tested by me on iwm(4) 7265.
* When moving the Rx block ack window forward do not implicitly rely onstsp2021-03-231-2/+3
| | | | | | | | | ieee80211_input_ba_flush() for updating ba->ba_winend. Required for an upcoming ieee80211_input_ba_flush() fix. Patch by Christian Ehrhardt who found one instance of this problem in ieee80211_input_ba_seq(). I spotted another in ieee80211_ba_move_window().
* Make a child execute fork_return() only if PTRACE_FORK has been specified.mpi2021-03-231-3/+6
| | | | | | | | | | fork_return() does an additional check to send a SIGTRAP (for a debugger) but this signal might overwrite the SIGSTOP generated by the parent doing a PT_ATTACH before the child has a change to execute any instruction. Prevent a race visible only on SP system with regress/sys/kern/ptrace2. ok kettenis@
* Skip first frame when saving stacktraces, it's always witness_checkorder().mpi2021-03-231-3/+3
| | | | ok visa@
* Pack the SPCR struct definition since the struct isn't naturally alignedpatrick2021-03-232-4/+4
| | | | | | | or padded, and hence e. g. the access to the PCI vendor/device id would be broken. The structs for the other tables all seem to be packed as well. ok kettenis@
* Now that MSI pages are properly mapped, all that debug code in smmu(4)patrick2021-03-221-34/+2
| | | | | | can be removed. The only thing left to implement for smmu(4) to work out of the box with PCIe devices is to reserve the PCIe MMIO windows. Let's see how we can do this properly.
* Don't leak ca in test_cms_sign_verify().tb2021-03-221-1/+2
| | | | Reported by Ilya Shipitsin
* Load MSI pages through bus_dma(9). Our interrupt controllers for MSIspatrick2021-03-225-22/+153
| | | | | | | | | | | | | | | | | | | | | | | | | typically pass the physical address, however retrieved, to our PCIe controller code. This physical address can in practise be directly given to the PCIe, but it is not a given that the CPU and the PCIe controller are able to use the same physical addresses. This is even more obvious with an smmu(4) inbetween, which can change the world view by introducing I/O virtual addresses. Hence for this it is indeed necessary to map those pages, which thanks to integration with bus_dma(9) works easily. For this we remember the PCI devices' DMA tag in the interrupt handle during the MSI map, so that we can use the smmu(4)-hooked DMA tag to load the physical address. While some systems might prefer to implement "trapping" pages for MSIs, to make sure devices cannot trigger other devices' interrupts, we only make sure the whole page is mapped. Having the IOMMU create a mapping for each MSI is a bit wasteful, but for now it's the simplest way to implement it. Discussed with and ok kettenis@
* Plug a few memory leaks reported by Ilya Shipitsintb2021-03-221-9/+7
|
* Properly reflect stopping statekn2021-03-221-4/+4
| | | | | | | | | | | | | Diff from Preben Guldberg < preben at guldberg dot org>, thanks! In "vmctl status", VMs that are being stopped but are still running will simply show up as "running". Give preference to showing the "stopping" state akin to how a paused VM is handled. Tested by Dave Voutila OK tb
* Update device-tree bindingskn2021-03-221-6/+6
| | | | | | | | | | | | | | | | | Using the DTB from our dtb package this driver no longer attaches (on a Pinebook Pro)due to renamed bindings: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/power/supply/cw2015_battery.yaml Thanks to kettenis and patrick for pointing this out. Follow upstream's rename and acccount for the monitor interval now being milliseconds not seconds anymore. This makes cwfg(4) export values under hw.sensors as expected when using /usr/local/share/dtb/arm64/rockchip/rk3399-pinebook-pro.dtb . Input patrick kettenis OK kettenis
* BOOTP has a minimum packet length of 300 bytes. Since DHCP isflorian2021-03-221-2/+10
| | | | | | | | | interoperable with BOOTP we should also send packets that have a minimum size of 300. I haven't seen a DHCP server that actually enforces this except the one in vmd(8), but it doesn't cost us much and prevents hair pulling later on when we find one in the wild. OK deraadt
* Avoid overflow by writing x = (y * 7) / 8 as x = y - (y / 8); ok florianotto2021-03-221-2/+2
|
* Remove unveil() from the rsync_sender() and flist_gen(). The sender isclaudio2021-03-222-24/+4
| | | | | | | | | | not able to properly unveil itself because you can request many files as arguments. At the same time the sender is read-only and uses rpath pledge() so the gain from unveil() is less of an issue. On the receiver side all files land in one directory and this part still uses unveil() to protect rsync to somehow walk out of the destination directory. From kristaps@
* Adjust function name in error strings.claudio2021-03-221-4/+4
| | | | From kristaps@
* Adjust a type to unsigned since the io function works on unsigned ints.claudio2021-03-221-4/+5
| | | | | | Also the id is a strictly positve integer so this make sense. Cleanup comments and a spacing while there. From kristaps@
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.