Age | Commit message (Collapse) | Author |
|
and X509_get_default_cert_file_env(3).
LibreSSL itself does not call getenv(3), but a few application programs
including epic5, fetchmail, fossil, slic3r call these functions, so in
case programmers find them in existing code, telling them what they do
seems useful.
|
|
Put it into this page because this is the code actually using it.
Despite its name and include file, it is unrelated to X.509
and unrelated to certificates: it is just the default directory
containing the library configuration file, openssl.cnf(5).
|
|
Lower limits lead to excessive rekeying and lost data in high performance
setups without much benefit.
Brought up by mvs@
ok patrick@ sthen@
|
|
relies upon this; sparc64 turned out to be the only platform where this
was not the case.
help, diff, and commit message from Miod Vallat
"makes sense" kettenis@
|
|
|
|
Jelen in GHPR#194 ok markus
|
|
new "-M sftp" option. Marked as experimental for now.
Some corner-cases exist, in particular there is no attempt to
provide bug-compatibility with scp's weird "double shell" quoting
rules.
Mostly by Jakub Jelen in GHPR#194 with some tweaks by me. ok markus@
Thanks jmc@ for improving the scp.1 bits.
|
|
ok deraadt@
|
|
The preceding trunk_link_active() already produced RTM_IFINFO message when
trunk(4) state was changed. I such case we double RTM_IFINFO message or we
produce false message when trunk(4) state was not changed.
ok florian@
|
|
FENCE.I instruction on the remote harts. According to the RISC-V
ISA documentation this is necessary to make remote harts observe earlier
stores. Also issue the local FENCE.I first; this is what both FreeBSD and
Linux does. Seems to fix at least some of the issue we've seen running
GENERIC.MP on MP machines.
ok jca@
|
|
so simply look up the first clock instead of looking for a specific one by
name. Allows rkpwm(4) to find the clock when using a recent device tree.
From Tomasz Bielecki
ok kettenis@
|
|
This may help to spot encoding errors a bit more easily.
|
|
|
|
* document the X509_OBJECT output parameter
* more precision regarding return values
* clarify relationship with X509_LOOKUP_ctrl(3) for the dir lookup method
|
|
|
|
"makes perfect sense to me" chris
ok gnezdo jca
|
|
bounce report.
From Erik Brens
|
|
ok kettenis@ sthen@
|
|
During install (not upgrade) the installer parses resolv.conf looking for
nameservers, FQDN and domain information; it also prompts for nameservers
if none were found.
If DHCP is used and nameservers were found, resolv.conf gets recreated from
scratch.
Under dhclient(8) this was fine, but resolvd(8) persists learned proposals
across such file modifications and resolv.conf will thus contain a mix
between managed and manual entries -- stale duplicates which users have to
remove manually.
Do not touch resolv.conf anymore in case resolvd knows better and thus
provide a clean file for installations.
OK florian
|
|
also clean up a comment
OK tb@
|
|
|
|
|
|
|
|
|
|
This is a type-O that snuck in when merging traphandler into snmpe.
OK jmatthew@
|
|
OK jmatthew@
|
|
REBOOTING. There will be a few more cases internal to dhcpleased that
have nothing to do with the control socket.
While here move requesting a new lease via a call to dhclient under
ifndef SMALL, nothing on the ramdisk uses this.
|
|
OK benno@
|
|
|
|
and add a new manual page X509_LOOKUP_new(3)
|
|
"The BeagleV-Starlight prototype will not be going into mass production"
https://forum.beagleboard.org/t/the-future-of-beaglev-community/30463
|
|
|
|
From Zheyu Ma
5c3d753b872a706af9317fef4edfb6b640d8a71e in linux 5.10.y/5.10.55
9e5c772954406829e928dbe59891d08938ead04b in mainline linux
|
|
framebuffer when Backspace is typed.
Reading data from LUNA framebuffer's 'common write plane' is not
valid. But on 1bpp framebuffer routine attempts to read from common
write plane in macro. That causes displaying incorrect patterns.
This bug was found on nono's LUNA-88K emulation first, then inspected
on the real hardware after I fortunately got 1bpp framebuffer.
Spotted and investigated by Isaki and Sugahara of nono procject.
Tested on my LUNA-88K2.
|
|
|
|
e.g. uvideo(4) with lower resolutions.
In general we might need to re-write parts of the nframes handling in the
driver, since the NetBSD nframes transfer allocation doesn't match with our
USB stack.
With this we can at least start further testing and improvement for ISOC
support.
|
|
Ensure the maxLength is greater than or equal to the length of
the accompanying prefix, and less than or equal to the length
(in bits) of an IP address in the address family (32 for IPv4
and 128 for IPv6). The same checks are applied when reading VRPs
from configuration on disk.
OK claudio@
|
|
the lie that *ptree is set upon success - in some cases of success,
it is set to NULL, whereas in some cases of failure, a non-trivial
tree may be returned.
beck@ pointed out that statements related to *ptree were scattered
all over the place, and this patch works for him.
|
|
from debian at helgefjell de
removed references to rlogin etc. as no longer relevant;
suggested by djm
ok djm dtucker
|
|
issues reported by debian at helgefjell de
ok djm dtucker
|
|
Starting with major version 35 the Linux driver prints the minor version
number in hexadecimal.
Same change was made for iwm(4) in CVS commit LCM6R5u9jeF8bcXB
|
|
This allocation was left over from code inherited from iwm(4) where
it is used for transferring firmware code to the device. Devices
supported by iwx(4) use an entirely different mechanism for loading
firmware and don't need this allocation at all.
Based on a patch by zxystd from the OpenIntelWireless project.
|
|
clobber in the inline assembly.
|
|
|
|
recently updated code. There, sync the hardware specific parts with the
NetBSD driver.
|
|
|
|
tweaks by schwarze@ okay millert@
|
|
OK florian@
|
|
|
|
|