| /src/contrib/llvm-project/lldb/source/Interpreter/ |
| H A D | InterpreterProperties.td | 7 …Desc<"If true, regular expression alias commands will show the expanded command that will be execu…
11 …Desc<"If true, LLDB will prompt you before quitting if there are any live processes being debugged…
15 Desc<"If true, commands will be saved into a transcript buffer for user access.">;
19 Desc<"If true, LLDB will save the session's transcripts before quitting.">;
23 Desc<"If true, LLDB will open the saved session's transcripts in the external editor.">;
26 …Desc<"A path where LLDB will save the session's transcripts. This is particularly useful when you …
30 Desc<"If true, LLDB will stop running a 'command source' script upon encountering an error.">;
34 Desc<"If true, blank lines will be printed between between REPL submissions.">;
38 Desc<"If true, commands will be echoed before they are evaluated.">;
42 Desc<"If true, commands will be echoed even if they are pure comment lines.">;
[all …]
|
| /src/crypto/openssl/doc/man3/ |
| H A D | OPENSSL_init_crypto.pod | 32 During normal operation OpenSSL (libcrypto) will allocate various resources at
38 As of version 1.1.0 OpenSSL will automatically allocate all resources that it
39 needs so no explicit initialisation is required. Similarly it will also
63 B<OPENSSL_INIT_LOAD_CRYPTO_STRINGS> will be ignored.
68 library will automatically load the libcrypto error strings.
71 B<OPENSSL_INIT_NO_LOAD_CRYPTO_STRINGS> will be ignored.
75 With this option the library will automatically load and make available all
78 B<OPENSSL_INIT_NO_ADD_ALL_CIPHERS> will be ignored.
82 With this option the library will automatically load and make available all
85 B<OPENSSL_INIT_NO_ADD_ALL_DIGESTS> will be ignored.
[all …]
|
| H A D | SSL_key_update.pod | 27 the sending keys for this connection will be updated and the peer will be
29 B<SSL_KEY_UPDATE_REQUESTED> then the sending keys for this connection will be
30 updated and the peer will be informed of the change along with a request for the
37 update will not take place until the next time an IO operation such as
43 update operation will be returned if there is one, or SSL_KEY_UPDATE_NONE
48 connection will result in an error.
53 will be performed to confirm that it is a suitable time to start a
54 renegotiation. If so, then it will be initiated immediately. OpenSSL will not
56 handshake. Note that some servers will respond to reneogitation attempts with
57 a "no_renegotiation" alert. An OpenSSL will immediately fail the connection in
[all …]
|
| H A D | BIO_s_mem.pod | 36 call to L<BIO_write(3)> will write a single datagram to the memory BIO. A
37 subsequent call to L<BIO_read(3)> will read the data in that datagram. The
38 L<BIO_read(3)> call will never return more data than was written in the original
40 wrote more datagrams. Each successive call to L<BIO_read(3)> will read the next
42 the size of the datagram, then the read buffer will be completely filled and the
43 remaining data from the datagram will be discarded.
46 this case will return 0 and no datagrams will be written. Calling L<BIO_read(3)>
47 when there are no datagrams in the BIO to read will return a negative result and
48 the "retry" flags will be set (i.e. calling L<BIO_should_retry(3)> will return
49 true). A datagram mem BIO will never return true from L<BIO_eof(3)>.
[all …]
|
| H A D | EVP_EncodeInit.pod | 36 bytes of binary data provided 4 bytes of base64 encoded data will be produced
38 multiple of 3 then the output data will be padded at the end using the "="
51 final block (which may be less than 48 bytes) will output 4 bytes for every 3
54 will also be output.
62 blocks of data (48 bytes) will be immediately processed and output by this
63 function. Any remainder is held in the B<ctx> object and will be processed by a
67 any remainder). This gives the number of blocks of data that will be processed.
71 EVP_EncodeUpdate() will set B<*outl> to 0 and return 0. On success 1 will be
74 EVP_EncodeFinal() must be called at the end of an encoding operation. It will
76 data will be stored in B<out> and the length of the data written will be stored
[all …]
|
| H A D | SSL_CTX_set_client_cert_cb.pod | 31 certificate will be installed into I<ssl>, see the NOTES and BUGS sections.
33 will be sent. A negative return value will suspend the handshake and the
34 handshake function will return immediately. L<SSL_get_error(3)>
35 will return SSL_ERROR_WANT_X509_LOOKUP to indicate, that the handshake was
36 suspended. The next call to the handshake function will again lead to the call
48 it will be sent to the server. The TLS standard requires that only a
56 SSL object, the callback function will be called.
58 will try to load the private key and certificate data into the SSL
60 Thus it will permanently install the certificate and key for this SSL
61 object. It will not be reset by calling L<SSL_clear(3)>.
[all …]
|
| H A D | SSL_CTX_set_split_send_fragment.pod | 38 each one encrypted independently and in parallel. Note: this will only work in
49 value restricts the amount of plaintext bytes that will be sent in any one
51 functions will only accept a value in the range 512 - SSL3_RT_MAX_PLAIN_LENGTH.
54 of pipelines that will be used at any one time. This value applies to both
55 "read" pipelining and "write" pipelining. By default only one pipeline will be
57 in the range 1 - SSL_MAX_PIPELINES (32). Setting this to a value > 1 will also
59 explained further below. OpenSSL will only ever use more than one pipeline if
66 writing encrypted data. The number of pipelines used will be determined by the
83 This will mean that the same number of records will always be created as would
84 have been created in the non-parallel case, although the data will be
[all …]
|
| H A D | RAND_set_DRBG_type.pod | 20 RAND_set_DRBG_type() specifies the random bit generator that will be
22 with properties I<propq> will be fetched. It will be instantiated with
24 This specifies the type that will be used for the primary, public and
27 RAND_set_seed_source_type() specifies the seed source that will be used
29 with properties I<propq> will be fetched and used to seed the primary
39 created in the library context. They will return an error if the call
|
| /src/contrib/ntp/sntp/libevent/ |
| H A D | Doxyfile | 6 # All text after a hash (#) is considered a comment and will be ignored
27 # will interpret the first line (until the first dot) of a JavaDoc-style
29 # comments will behave just like the Qt-style comments (thus requiring an
35 # sources only. Doxygen will then generate output that is more tailored for C.
36 # For instance, some of the names that are used will be different. The list
37 # of all members will be omitted, etc.
41 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
43 # by member name. If set to NO (the default) the members will appear in
90 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
99 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
[all …]
|
| /src/contrib/libevent/ |
| H A D | Doxyfile | 6 # All text after a hash (#) is considered a comment and will be ignored
27 # will interpret the first line (until the first dot) of a JavaDoc-style
29 # comments will behave just like the Qt-style comments (thus requiring an
35 # sources only. Doxygen will then generate output that is more tailored for C.
36 # For instance, some of the names that are used will be different. The list
37 # of all members will be omitted, etc.
41 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
43 # by member name. If set to NO (the default) the members will appear in
90 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
99 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
[all …]
|
| /src/crypto/heimdal/doc/ |
| H A D | init-creds | 75 This function will attempt to acquire an initial ticket. The function
76 will perform whatever tasks are necessary to do so. This may include
92 and will not be doing any other kerberos functions, then a NULL
93 pointer may be specified, and the credential will be destroyed.
95 If the client name is non-NULL, the initial ticket requested will be
96 for that principal. Otherwise, the principal will be the username
102 Otherwise, the prompter function will be used to prompt the user for
105 If a prompter function is non-NULL, it will be used if additional user
108 no function is specified and input is required, then the login will
116 The banner argument, if non-NULL, will indicate what sort of
[all …]
|
| /src/contrib/libcbor/ |
| H A D | Doxyfile | 9 # All text after a single hash (#) is considered a comment and will be ignored.
61 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
67 # into which the generated documentation will be written. If a relative path is
68 # entered, it will be relative to the location where doxygen was started. If
69 # left blank the current directory will be used.
73 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096
75 # and will distribute the generated files over these directories. Enabling this
84 # Controls the number of sub-directories that will be created when
95 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
97 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
[all …]
|
| /src/crypto/openssl/doc/designs/quic-design/ |
| H A D | quic-fault-injector.md | 5 processes them accordingly. It will need to behave appropriately in the event of
14 Typically an individual test will inject one particular misbehaviour (i.e. a
16 will have to be capable of creating fully normal QUIC protocol elements, but
22 The QUIC Fault Injector will be external to libssl (it will be in the test
23 framework) but it will reuse the standards compliant QUIC implementation in
24 libssl and will make use of 3 integration points to inject faults. 2 of these
25 integration points will use new callbacks added to libssl. The final integration
47 To support this integration point two new callbacks will be introduced to libssl
49 hashed. These callbacks will be internal only (i.e. not part of the public API)
52 The new libssl callbacks will be as follows:
[all …]
|
| /src/contrib/ldns/ |
| H A D | libdns.doxygen.in | 9 # All text after a single hash (#) is considered a comment and will be ignored.
51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
65 # will distribute the generated files over these directories. Enabling this
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
82 # documentation generated by doxygen is written. Doxygen will use this
[all …]
|
| /src/contrib/bearssl/ |
| H A D | Doxyfile | 9 # All text after a single hash (#) is considered a comment and will be ignored.
51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
65 # will distribute the generated files over these directories. Enabling this
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
82 # documentation generated by doxygen is written. Doxygen will use this
[all …]
|
| /src/contrib/unbound/doc/ |
| H A D | unbound.doxygen | 9 # All text after a single hash (#) is considered a comment and will be ignored.
61 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
67 # into which the generated documentation will be written. If a relative path is
68 # entered, it will be relative to the location where doxygen was started. If
69 # left blank the current directory will be used.
73 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096
75 # and will distribute the generated files over these directories. Enabling this
84 # Controls the number of sub-directories that will be created when
95 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
97 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
[all …]
|
| /src/sys/contrib/device-tree/Bindings/sound/ |
| H A D | st,sta350.txt | 9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
13 it will be deasserted before communication to the codec
27 If parameter is missing, mode 0 will be enabled.
46 If present, then fault recovery will be enabled.
80 channels. If not present, normal PWM speed mode (384 kHz) will be used.
90 If present, a mute output will be activated in ase the volume will
94 If present, the bridge will be switched off immediately after the
95 power-down-gpio goes low. Otherwise, the bridge will wait for 13
103 If present, the power-down pin and I2C power-down functions will
104 act on the master volume. Otherwise, the functions will act on the
[all …]
|
| /src/contrib/sendmail/mail.local/ |
| H A D | README | 19 Defining CONTENTLENGTH (-DCONTENTLENGTH) will build a mail.local which
20 outputs a Content-Length: header. Solaris 2.3 and later will automatically
26 Defining MAILGID to a 'gid' (-DMAILGID=6) will cause mailboxes to be
32 mail.local will not be installed set-user-ID root. To use it as local
39 Defining HASHSPOOL (-DHASHSPOOL) will build a mail.local which supports
41 username (i.e., a hash depth of 2 and a username of "user" will result in
43 of the username, "_" will be used. The necessary subdirectories must
44 exist; mail.local will not create them. Use the "-H" option to set the
58 will offer an alternate hash, using a base64 encoding (changing / to _)
60 subdirectory tree. The subdirectories will be named with A-Z, a-z, 0-9,
|
| /src/contrib/kyua/ |
| H A D | INSTALL.md | 43 If you are building Kyua from the code on the repository, you will also
59 system. You will also need to do this if you modify `configure.ac`,
65 If ATF is installed in a different prefix than Autoconf, you will also
67 the configure script will be incomplete and will show confusing syntax
91 not need to be root to do this, but if you are not, some checks will
102 not, some checks will be skipped.
114 Specifies where the program (binaries and all associated files) will
121 Specifies where the installed programs will look for configuration
122 files. `/kyua` will be appended to the given path unless
137 Specifies the path to the GNU GDB binary that Kyua will use to gather a
[all …]
|
| /src/crypto/openssl/crypto/engine/ |
| H A D | README.md | 65 RSA functions (eg. "RSA_free(RSA_new());") will result in large quantities of
96 ENGINE code will return NULL because no ENGINEs will have had any cipher
104 to that ENGINE will be returned to the EVP_CIPHER_CTX during initialisation.
105 That functional reference will be stored in the context (and released on
108 application will actually be replaced by an EVP_CIPHER from the registered
109 ENGINE - it will support the same algorithm/mode as the original but will be a
124 EVP_CIPHER code will link at most code relating to EVP_CIPHER, tb_cipher.c, core
126 implementation that the application loaded. It will *not* however link any
127 class-specific ENGINE code for digests, RSA, etc nor will it bleed over into
135 These nids provide the uniquenness of an algorithm/mode - and each nid will hash
[all …]
|
| /src/contrib/bc/ |
| H A D | MAINTENANCE-TERMS.md | 22 * Compute time will be charged at \$25/hr.
23 * My time will be charged at \$100/hr.
25 source code (anything in `gen`, `include`, or `src`) will require at least two
27 * If errors are found, those hours will still be charged on top of the final
29 * All changes will require running the [release script][2] on Linux (GCC), Linux
32 generated by "AI" will be charged double rates.
48 day that I could be working will be charged at \$100/hr.
55 All amounts will be billed by, and paid to, [Yzena, LLC][2]. Invoices will be
64 Most of that won't be at the \$100/hr rate, but some probably will be. Then
|
| /src/sys/contrib/device-tree/Bindings/hwmon/ |
| H A D | max6697.txt | 21 Set to disable SMBus timeout. If not specified, SMBus timeout will be
25 Extended temperature will be disabled if not specified.
29 Beta compensation will be disabled if not specified.
33 If not specified, alert will be enabled for all channels.
38 If not specified, over-temperature reporting will be enabled for all
46 If not specified, resistance cancellation will be disabled for all
52 Transistor ideality will be initialized to default (1.008) if not
|
| /src/contrib/llvm-project/lld/docs/MachO/ |
| H A D | ld64-vs-lld.rst | 15 within the user's control, this will mitigate users for adoption.
34 1. Duplicate ObjC symbols from the same archives will not raise an error.
35 ld64 will pick the first one.
36 2. Duplicate ObjC symbols from different archives will raise a "duplicate
38 - LLD: Duplicate symbols, regardless of which archives they are from, will
47 duplicate symbols. In particular, we will not report a duplicate symbol error if
48 the aliased symbols turn out to be weak definitions, but ld64 will.
56 of ``ZERO_AR_DATE`` will be ignored.
|
| /src/crypto/openssl/test/ |
| H A D | README-external.md | 23 The tests will run in a python virtual environment which requires virtualenv
31 Some tests target older (<=1.0.2) versions so will not run. Other tests target
40 You will need a git checkout of krb5 at the top level:
56 krb5's tests will then be run as part of the rest of the suite, or can be
64 krb5 will automatically adapt its test suite to account for the configuration
74 You will need a git checkout of gost-engine at the top level:
85 GOST engine tests will then be run as part of the rest of the suite, or can be
97 You will need a git checkout of oqsprovider at the top level:
108 OQSprovider tests will then be run as part of the rest of the suite, or can be
125 You will need a git checkout of pkcs11-provider at the top level:
[all …]
|
| /src/usr.sbin/cron/doc/ |
| H A D | FEATURES | 12 Blanks surrounding the '=' will be eaten; other blanks in value are
22 SHELL and HOME will be used when it's time to run a command; if
26 MAILTO, if set to the login name of a user on your system, will be the
51 no arguments will print a cute little summary of the command syntax.
58 the 'cron' daemon will reload all the tables before running the
65 problem, since 'crontab' will let you do pretty much whatever you
68 -- If any output is generated by a command (on stdout OR stderr), it will
71 of the mail message will include the command that was run, and a
72 complete list of the environment that was passed to it, which will
75 -- the dom/dow situation is odd. '* * 1,15 * Sun' will run on the
[all …]
|