Whoa. Apps are running on android. Switched to a static build of OpenSSL 1.1.1t for simplicity.

git-svn-id: https://www.unprompted.com/svn/projects/tildefriends/trunk@4211 ed5197a5-7fde-0310-b194-c3ffbd925b24
This commit is contained in:
2023-03-10 02:02:24 +00:00
parent d532795b7f
commit 400f07660f
7649 changed files with 9904 additions and 2321 deletions

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ADMISSIONS 3"
.TH ADMISSIONS 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ADMISSIONS 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
ADMISSIONS.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_INTEGER_GET_INT64 3"
.TH ASN1_INTEGER_GET_INT64 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_INTEGER_GET_INT64 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@ -215,7 +215,7 @@ instead.
.IX Header "NOTES"
In general an \fB\s-1ASN1_INTEGER\s0\fR or \fB\s-1ASN1_ENUMERATED\s0\fR type can contain an
integer of almost arbitrary size and so cannot always be represented by a C
\&\fBint64_t\fR type. However in many cases (for example version numbers) they
\&\fBint64_t\fR type. However, in many cases (for example version numbers) they
represent small integers which can be more easily manipulated if converted to
an appropriate C integer type.
.SH "BUGS"
@ -252,7 +252,7 @@ of \s-1NULL\s0 if an error occurs. They can fail if the passed type is incorrect
were added in OpenSSL 1.1.0.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright 2015\-2018 The OpenSSL Project Authors. All Rights Reserved.
Copyright 2015\-2020 The OpenSSL Project Authors. All Rights Reserved.
.PP
Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
this file except in compliance with the License. You can obtain a copy

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
ASN1_INTEGER_get_int64.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
ASN1_ITEM_lookup.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_ITEM_LOOKUP 3"
.TH ASN1_ITEM_LOOKUP 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_ITEM_LOOKUP 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
ASN1_OBJECT_new.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_OBJECT_NEW 3"
.TH ASN1_OBJECT_NEW 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_OBJECT_NEW 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
ASN1_STRING_TABLE_add.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_STRING_TABLE_ADD 3"
.TH ASN1_STRING_TABLE_ADD 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_STRING_TABLE_ADD 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
ASN1_STRING_TABLE_add.3

View File

@ -0,0 +1 @@
ASN1_STRING_TABLE_add.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -0,0 +1 @@
ASN1_STRING_new.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_STRING_LENGTH 3"
.TH ASN1_STRING_LENGTH 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_STRING_LENGTH 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@ -206,7 +206,7 @@ In general it cannot be assumed that the data returned by \fBASN1_STRING_data()\
is null terminated or does not contain embedded nulls. The actual format
of the data will depend on the actual string type itself: for example
for an IA5String the data will be \s-1ASCII,\s0 for a BMPString two bytes per
character in big endian format, and for an UTF8String it will be in \s-1UTF8\s0 format.
character in big endian format, and for a UTF8String it will be in \s-1UTF8\s0 format.
.PP
Similar care should be take to ensure the data is in the correct format
when calling \fBASN1_STRING_set()\fR.
@ -234,7 +234,7 @@ negative value if an error occurred.
\&\fBERR_get_error\fR\|(3)
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright 2002\-2018 The OpenSSL Project Authors. All Rights Reserved.
Copyright 2002\-2020 The OpenSSL Project Authors. All Rights Reserved.
.PP
Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
this file except in compliance with the License. You can obtain a copy

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_STRING_NEW 3"
.TH ASN1_STRING_NEW 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_STRING_NEW 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
ASN1_STRING_print_ex.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_STRING_PRINT_EX 3"
.TH ASN1_STRING_PRINT_EX 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_STRING_PRINT_EX 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
ASN1_STRING_print_ex.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -0,0 +1 @@
ASN1_STRING_length.3

View File

@ -0,0 +1 @@
ASN1_STRING_new.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_TIME_SET 3"
.TH ASN1_TIME_SET 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_TIME_SET 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@ -243,7 +243,7 @@ one or both (depending on the time difference) of \fB*pday\fR and \fB*psec\fR
will be positive. If \fBto\fR represents a time earlier than \fBfrom\fR then
one or both of \fB*pday\fR and \fB*psec\fR will be negative. If \fBto\fR and \fBfrom\fR
represent the same time then \fB*pday\fR and \fB*psec\fR will both be zero.
If both \fB*pday\fR and \fB*psec\fR are non-zero they will always have the same
If both \fB*pday\fR and \fB*psec\fR are nonzero they will always have the same
sign. The value of \fB*psec\fR will always be less than the number of seconds
in a day. If \fBfrom\fR or \fBto\fR is \s-1NULL\s0 the current time is used.
.PP
@ -291,7 +291,7 @@ format.
.SH "BUGS"
.IX Header "BUGS"
\&\fBASN1_TIME_print()\fR, \fBASN1_UTCTIME_print()\fR and \fBASN1_GENERALIZEDTIME_print()\fR
do not print out the time zone: it either prints out \*(L"\s-1GMT\*(R"\s0 or nothing. But all
do not print out the timezone: it either prints out \*(L"\s-1GMT\*(R"\s0 or nothing. But all
certificates complying with \s-1RFC5280\s0 et al use \s-1GMT\s0 anyway.
.PP
Use the \fBASN1_TIME_normalize()\fR function to normalize the time value before
@ -372,7 +372,7 @@ The \fBASN1_TIME_cmp_time_t()\fR function was added in OpenSSL 1.1.1.
The \fBASN1_TIME_compare()\fR function was added in OpenSSL 1.1.1.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright 2015\-2019 The OpenSSL Project Authors. All Rights Reserved.
Copyright 2015\-2020 The OpenSSL Project Authors. All Rights Reserved.
.PP
Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
this file except in compliance with the License. You can obtain a copy

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TYPE_get.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_TYPE_GET 3"
.TH ASN1_TYPE_GET 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_TYPE_GET 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@ -169,7 +169,7 @@ up after the call.
\&\fBASN1_TYPE_set1()\fR sets the value of \fBa\fR to \fBtype\fR a copy of \fBvalue\fR.
.PP
\&\fBASN1_TYPE_cmp()\fR compares \s-1ASN.1\s0 types \fBa\fR and \fBb\fR and returns 0 if
they are identical and non-zero otherwise.
they are identical and nonzero otherwise.
.PP
\&\fBASN1_TYPE_unpack_sequence()\fR attempts to parse the \s-1SEQUENCE\s0 present in
\&\fBt\fR using the \s-1ASN.1\s0 structure \fBit\fR. If successful it returns a pointer
@ -197,12 +197,12 @@ length octets).
.PP
\&\fBASN1_TYPE_cmp()\fR may not return zero if two types are equivalent but have
different encodings. For example the single content octet of the boolean \s-1TRUE\s0
value under \s-1BER\s0 can have any non-zero encoding but \fBASN1_TYPE_cmp()\fR will
value under \s-1BER\s0 can have any nonzero encoding but \fBASN1_TYPE_cmp()\fR will
only return zero if the values are the same.
.PP
If either or both of the parameters passed to \fBASN1_TYPE_cmp()\fR is \s-1NULL\s0 the
return value is non-zero. Technically if both parameters are \s-1NULL\s0 the two
types could be absent \s-1OPTIONAL\s0 fields and so should match, however passing
return value is nonzero. Technically if both parameters are \s-1NULL\s0 the two
types could be absent \s-1OPTIONAL\s0 fields and so should match, however, passing
\&\s-1NULL\s0 values could also indicate a programming error (for example an
unparsable type which returns \s-1NULL\s0) for types which do \fBnot\fR match. So
applications should handle the case of two absent values separately.
@ -214,7 +214,7 @@ applications should handle the case of two absent values separately.
.PP
\&\fBASN1_TYPE_set1()\fR returns 1 for success and 0 for failure.
.PP
\&\fBASN1_TYPE_cmp()\fR returns 0 if the types are identical and non-zero otherwise.
\&\fBASN1_TYPE_cmp()\fR returns 0 if the types are identical and nonzero otherwise.
.PP
\&\fBASN1_TYPE_unpack_sequence()\fR returns a pointer to an \s-1ASN.1\s0 structure or
\&\s-1NULL\s0 on failure.

View File

@ -0,0 +1 @@
ASN1_TYPE_get.3

View File

@ -0,0 +1 @@
ASN1_TYPE_get.3

View File

@ -0,0 +1 @@
ASN1_TYPE_get.3

View File

@ -0,0 +1 @@
ASN1_TYPE_get.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
ASN1_TIME_set.3

View File

@ -0,0 +1 @@
OPENSSL_load_builtin_modules.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASN1_GENERATE_NCONF 3"
.TH ASN1_GENERATE_NCONF 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASN1_GENERATE_NCONF 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l

View File

@ -0,0 +1 @@
ASN1_generate_nconf.3

View File

@ -0,0 +1 @@
ASN1_STRING_print_ex.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
X509_dup.3

View File

@ -0,0 +1 @@
ASYNC_WAIT_CTX_new.3

View File

@ -0,0 +1 @@
ASYNC_WAIT_CTX_new.3

View File

@ -0,0 +1 @@
ASYNC_WAIT_CTX_new.3

View File

@ -0,0 +1 @@
ASYNC_WAIT_CTX_new.3

View File

@ -0,0 +1 @@
ASYNC_WAIT_CTX_new.3

View File

@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "ASYNC_WAIT_CTX_NEW 3"
.TH ASYNC_WAIT_CTX_NEW 3 "2020-04-21" "1.1.1g" "OpenSSL"
.TH ASYNC_WAIT_CTX_NEW 3 "2023-02-07" "1.1.1t" "OpenSSL"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@ -183,7 +183,7 @@ job in \fB*fd\fR. The number of file descriptors returned will be stored in
\&\fB*numfds\fR. It is the caller's responsibility to ensure that sufficient memory
has been allocated in \fB*fd\fR to receive all the file descriptors. Calling
\&\fBASYNC_WAIT_CTX_get_all_fds()\fR with a \s-1NULL\s0 \fBfd\fR value will return no file
descriptors but will still populate \fB*numfds\fR. Therefore application code is
descriptors but will still populate \fB*numfds\fR. Therefore, application code is
typically expected to call this function twice: once to get the number of fds,
and then again when sufficient memory has been allocated. If only one
asynchronous engine is being used then normally this call will only ever return
@ -248,7 +248,7 @@ success or 0 on error.
On Windows platforms the openssl/async.h header is dependent on some
of the types customarily made available by including windows.h. The
application developer is likely to require control over when the latter
is included, commonly as one of the first included headers. Therefore
is included, commonly as one of the first included headers. Therefore,
it is defined as an application developer's responsibility to include
windows.h prior to async.h.
.SH "SEE ALSO"
@ -262,7 +262,7 @@ windows.h prior to async.h.
were added in OpenSSL 1.1.0.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright 2016 The OpenSSL Project Authors. All Rights Reserved.
Copyright 2016\-2020 The OpenSSL Project Authors. All Rights Reserved.
.PP
Licensed under the OpenSSL license (the \*(L"License\*(R"). You may not use
this file except in compliance with the License. You can obtain a copy

Some files were not shown because too many files have changed in this diff Show More