/openssl/test/helpers/ |
H A D | noisydgrambio.c | 119 if (limit->bw == 0) /* 0 -> no limit */ in bandwidth_limit() 126 for (i = 0; i < limit->num; i++) { in bandwidth_limit() 131 limit->size_sum -= limit->pinfos[idx].size; in bandwidth_limit() 133 limit->start = (limit->start + i) % MAX_PKTS_PER_WINDOW; in bandwidth_limit() 134 limit->num -= i; in bandwidth_limit() 140 if ((limit->size_sum + pktsize) / SAMPLING_WINDOW_PERIOD > limit->bw) { in bandwidth_limit() 156 limit->size_sum -= limit->pinfos[limit->start].size; in bandwidth_limit() 157 limit->start = (limit->start + 1) % MAX_PKTS_PER_WINDOW; in bandwidth_limit() 159 ++limit->num; in bandwidth_limit() 161 end = (limit->start + limit->num) % MAX_PKTS_PER_WINDOW; in bandwidth_limit() [all …]
|
/openssl/ssl/quic/ |
H A D | quic_sf_list.c | 223 if (!ossl_assert(limit >= fl->offset) in ossl_sframe_list_drop_frames() 225 || limit <= fl->tail->range.end) in ossl_sframe_list_drop_frames() 227 || limit == fl->offset)) in ossl_sframe_list_drop_frames() 230 fl->offset = limit; in ossl_sframe_list_drop_frames() 277 uint64_t limit = fl->offset; in ossl_sframe_list_move_data() local 289 if (limit < sf->range.start) in ossl_sframe_list_move_data() 290 limit = sf->range.start; in ossl_sframe_list_move_data() 293 if (limit > sf->range.start) in ossl_sframe_list_move_data() 295 len = (size_t)(sf->range.end - limit); in ossl_sframe_list_move_data() 297 if (!write_at_cb(limit, data, len, cb_arg)) in ossl_sframe_list_move_data() [all …]
|
/openssl/doc/designs/quic-design/ |
H A D | stream-receive-buffers.md | 18 - The application should be able to set the limit on how much data should 20 more data. Without the flow control limit a rogue peer could trigger 23 data can be released and flow control limit can be raised. 92 the limit reached. See the `SSL_set_max_unprocessed_quic_packet_data()` 124 effectively raise the stream data flow control limit quadratically. 127 more data than what is allowed by the stream data flow control limit 130 Although intuitively the MAX_DATA flow control limit might be used to 131 somehow limit the allocated packet buffer size, it is defined as sum 134 especially with a rogue peer, that means MAX_DATA limit cannot be used 135 to limit the memory occupied by packet buffers. [all …]
|
H A D | dgram-api.md | 78 - Even if we did support iovecs, we would have to impose a limit 228 However, it does seem like we will need to limit *v*, the number of iovecs 229 per message. So what limit should we give to *v*, the number of iovecs? We 233 until we reach our iovec limit, and then return. 249 is the limit of iovecs on a single message; in other words, the 256 iovecs are small, so we can afford to set the limit high enough 258 the limit later without a breaking API change, but we cannot decrease 283 - Another option could be a variable limit on the number of iovecs, 290 another, because the author didn't realise the iovec limit is 1 on some 291 platforms. Possibly we could have an “iovec limit” variable in the
|
H A D | demuxer.md | 36 connection; limit the number of such packets with the same destination
|
/openssl/crypto/ec/curve448/ |
H A D | word.h | 76 unsigned int limit = sizeof(c448_bool_t) / sizeof(mask_t); in bool_to_mask() local 78 if (limit < 1) in bool_to_mask() 79 limit = 1; in bool_to_mask() 80 for (i = 0; i < limit; i++) in bool_to_mask()
|
/openssl/doc/man3/ |
H A D | SSL_CTX_get_verify_mode.pod | 26 SSL_CTX_get_verify_depth() returns the verification depth limit currently set 27 in B<ctx>. If no limit has been explicitly set, -1 is returned and the 30 SSL_get_verify_depth() returns the verification depth limit currently set 31 in B<ssl>. If no limit has been explicitly set, -1 is returned and the
|
H A D | SSL_CTX_set_verify.pod | 159 SSL_CTX_set_verify_depth() and SSL_set_verify_depth() set a limit on the 169 The default depth limit is 100, 243 failure, if wished. The callback realizes a verification depth limit with 287 * Catch a too long certificate chain. The depth limit set using 288 * SSL_CTX_set_verify_depth() is by purpose set to "limit+1" so 290 * have violated the limit and want to log this error condition.
|
H A D | BN_mod_exp_mont.pod | 36 memory layout to limit data-dependency to a minimum to protect secret exponents.
|
H A D | SSL_set_fd.pod | 58 upper limit is INVALID_SOCKET-1 (2^64 - 2), in practice the current socket()
|
H A D | X509_VERIFY_PARAM_set_flags.pod | 113 A maximal depth chain contains 2 more certificates than the limit, since 115 limit. 116 Thus a B<depth> limit of 0 only allows the end-entity certificate to be signed 117 directly by the trust anchor, while with a B<depth> limit of 1 there can be one
|
H A D | OSSL_HPKE_CTX_new.pod | 219 implementation we apply a limit of 66 octets for the I<ikmlen>, I<psklen>, and 221 functions below. The constant I<OSSL_HPKE_MAX_PARMLEN> is defined as the limit 229 While RFC9180 also RECOMMENDS a 64 octet limit for the I<infolen> parameter, 231 enforce a limit of I<OSSL_HPKE_MAX_INFOLEN> with a value of 1024 as the limit
|
H A D | OSSL_HTTP_REQ_CTX.pod | 199 The OSSL_HTTP_REQ_CTX_set_max_response_hdr_lines() function changes the limit 201 value is 256. If the number of HTTP headers in a response exceeds the limit, 203 limit to 0 disables the check.
|
H A D | EVP_PKEY_get_size.pod | 64 the upper limit in advance.
|
H A D | OPENSSL_riscvcap.pod | 24 RISC-V Instruction Set Manual. It is case insensitive. Though due to the limit
|
H A D | SSL_CTX_set_record_padding_callback.pod | 50 of the B<block_size>. A B<block_size> of 0 or 1 disables block padding. The limit of
|
H A D | SSL_get_error.pod | 84 There is no fixed upper limit for the number of iterations that 153 L<SSL_set_mode(3)> and a maximum limit has been set on the async job pool
|
/openssl/fuzz/ |
H A D | quic-srtm.c | 53 size_t limit = 0; in FuzzerTestOneInput() local 67 if (++limit > MAX_CMDS) { in FuzzerTestOneInput()
|
H A D | quic-lcidm.c | 77 size_t limit = 0; in FuzzerTestOneInput() local 97 if (++limit > MAX_CMDS) in FuzzerTestOneInput()
|
/openssl/include/internal/ |
H A D | quic_sf_list.h | 104 int ossl_sframe_list_drop_frames(SFRAME_LIST *fl, uint64_t limit);
|
/openssl/crypto/rand/ |
H A D | rand_pool.c | 203 const size_t limit = pool->max_len / 2; in rand_pool_grow() local 212 newlen = newlen < limit ? newlen * 2 : pool->max_len; in rand_pool_grow()
|
/openssl/test/ |
H A D | http_test.c | 419 static int test_http_resp_hdr_limit(size_t limit) in test_http_resp_hdr_limit() argument 447 OSSL_HTTP_REQ_CTX_set_max_response_hdr_lines(rctx, limit); in test_http_resp_hdr_limit() 454 if (limit == 1) in test_http_resp_hdr_limit()
|
/openssl/providers/implementations/ciphers/ |
H A D | cipher_aes_xts_s390x.inc | 126 * Impose a limit of 2^20 blocks per data unit as specified by 129 * NIST SP 800-38E mandates the same limit.
|
/openssl/test/recipes/30-test_evp_data/ |
H A D | evppbe_scrypt.txt | 41 # scrypt memory limit and return an error. To run this test without error
|
/openssl/doc/designs/ |
H A D | thread-api.md | 51 The maximum thread count is a limit, not a target. Threads will not be spawned
|