Age | Commit message (Collapse) | Author |
|
Link to X509_ALGOR_new(3) because one of the functions uses X509_ALGOR.
Delete a sentence about a function we don't have.
Delete another sentence that says nothing new.
Remove some macros that we don't normally use.
|
|
|
|
listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod.
Explain what an X509_ALGOR object represents and where it is used.
Explain how copying works, like in similar pages.
New RETURN VALUES, SEE ALSO, and STANDARDS sections.
Some macro and wording fixes.
|
|
ok deraadt@
|
|
|
|
|
|
down doas for install media.
ok tedu@
|
|
It seems unlikely that any future new platform will ever need them.
OK mpi@
|
|
|
|
|
|
|
|
link back to X509_EXTENSION_new(3).
|
|
and link to X509_EXTENSION_new(3) instead
|
|
in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod.
Explain what an X509_EXTENSION object is and where it is used.
Add STANDARDS references.
Sort the functions into a more logical order.
Link to all other pages dealing with X509_EXTENSION objects.
|
|
cert.pem entries. ok jsg
|
|
document things this way and DESCRIPTION is clear anyway that this
should not be used; wording of the Nd suggested by schwarze
ok schwarze
|
|
ok mikeb@
|
|
|
|
With testing from Jon Bernard
OK mlarkin@
|
|
gateway is not reachable (e.g. not on a local subnet).
ok millert@ mikeb@ mpi@
(and shrugs by jca@)
|
|
For some reason this crashes on armv7. Issue reported by Lars Nooden.
|
|
|
|
This is technically a reset since memory is cleared and the dmesg
buffer is lost.
Patch from Jon Bernard (jbernard at jbernard.io) - Thanks
OK reyk@ mlarkin@
|
|
|
|
|
|
OpenSSL doc/man3/X509_dup.pod and d2i_X509_NAME_ENTRY(3) and
i2d_X509_NAME_ENTRY(3) listed in OpenSSL doc/man3/d2i_X509.pod.
Also add a RETURN VALUES section.
|
|
ok mikeb@, phessler@
|
|
Ultimately, this page will have to be merged into X509_new(3),
but we're not quite ready for that just yet.
|
|
reference X509_NAME_new(3). Sparingly add a few other
references to relevant X509_NAME*(3) pages while here.
|
|
Add some cross references and STANDARDS.
|
|
both listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.h.
Note that the OpenSSL documentation specifies the wrong header file.
Explain what X509_NAME_ENTRY represents.
Simplify and clarify some wording.
Sort parts of the text into a more logical order.
Delete an irrelevant cross reference and add some relevant ones.
Add a STANDARDS section.
|
|
listed in <openssl/x509.h> and in OpenSSL doc/man3/X509_dup.pod.
Note that the OpenSSL documentation specifies the wrong header file.
|
|
bit, so they should be mounted on a filesystem without the nosuid
option. OpenBSD's /var/www is mounted nosuid by default and using
bgplg with the statically-linked "ping" doesn't work with nosuid.
Reported by Michael W. Lucas (mwlucas at michaelwlucas.com)
OK jmc@ jca@
|
|
|
|
is too slow and the invariant TSC more accurate.
The commit includes joint work by mikeb@ kettenis@ and me;
tested for some time by a large group of volunteers.
OK mikeb@ kettenis@
|
|
The patch was already committed upstream.
OK tb@ and sthen@. jca@ has a valid point that the error would be fatal and
most likely the socket would not leak, nevertheless create_tcp_accept_sock()
close the socket everytime so for clarity apply the same principal here in
create_local_accept_sock()
|
|
|
|
|
|
pty and re-send it to the vmm monitor process. With additional
changes in vmm.c, this will allow perform a cold reboot of VM.
With testing and feedback from Jon Bernard
OK mlarkin@
|
|
from scratch. All these functions are listed in <openssl/ts.h>
and in OpenSSL doc/man3/X509_dup.pod.
Note that the OpenSSL documentation specifies the wrong header file.
|
|
|
|
No objections from deraadt@, OK dlg
Thanks to stsp@ who has extended ifm_media field to 64 bits.
|
|
|
|
are listed in <openssl/rsa.h> and OpenSSL doc/man3/X509_dup.pod.
Note that the OpenSSL documentation specifies the wrong header file.
More could probably be said about PSS, but this is a start...
|
|
With help from and OK sf, OK mpi on the previous version.
|
|
|
|
Thanks to the detailed report from Nathanael Rensen, the issue
with unaligned transfer data became apparent: the backend expects
buffers be multiple of 512 bytes and to be 512 byte aligned, which
is not always satisfied.
This isn't an issue when requests are coming from the buffer cache,
but can happen with raw device access since physio(9) ensures the
former requirement is met by disallowing non-block sized reads, but
doesn't enforce the latter. It remaps userland buffers into the
kernel virtual space which preserves the data offset within the
memory page and thus the original alignment.
Buffers with offsets under the block size can't be referenced by
Blkfront ring descriptors that measure data in blocks and must be
substituted with temporary buffers for the duration of the I/O
operation.
|
|
|
|
to our arm version.
ok millert@
|
|
ok reyk@
|