The OpenSSL wiki has moved to https://github.com/openssl/openssl/wiki. Information on this page is no longer edited and may be out-of-date.

Search results

From OpenSSLWiki
Jump to navigationJump to search

Page title matches

  • 97 bytes (11 words) - 23:03, 28 April 2017

Page text matches

  • ...orial is done on an (X)Ubuntu 15.04, with custom compiled OpenSSL version 1.0.2d. The GCC version is: return 1;
    33 KB (4,951 words) - 08:57, 7 March 2019
  • ...have identity elements. So, for example 0 and 1 where: a + 0 = a, and a * 1 = a ...lar (or clock) arithmetic. So, if p=7 then the elements of the set are {0, 1, 2, 3, 4, 5, 6} and:
    18 KB (3,074 words) - 02:26, 29 July 2019
  • ...1.1.0 and above. This page focuses on the second generation, or OpenSSL 1.1.0 and above. == OpenSSL 1.1.0 ==
    8 KB (1,289 words) - 16:17, 9 February 2020
  • if(1 != EVP_EncryptInit_ex(ctx, EVP_aes_256_gcm(), NULL, NULL, NULL)) if(1 != EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_SET_IVLEN, iv_len, NULL))
    13 KB (1,791 words) - 04:48, 5 June 2019
  • ...is at most 38%. Some estimates have shown English characters provide only 1 bit/byte (or 12%). Other sources used as a random stream will have differen ...ly random data can be thought of as a sequence of binary digits where each 1 or 0 is the result of flipping a perfectly fair, unbiased coin. Such a sequ
    27 KB (4,265 words) - 02:33, 27 July 2019
  • '''''Note''''': CMAC is only supported since the version 1.1.0 of OpenSSL. ...gle.com/forum/#!topic/mailing.openssl.users/1_TFpK6XzQ4 DSA with OpenSSL-1.1] on the mailing list.
    11 KB (1,688 words) - 10:08, 28 April 2020
  • ...a guideline on how to integrate a symmetric block cipher into OpenSSL 1.1.1. This integration procedure will cover all aspects of integration for both 1, EVP_RC4_KEY_SIZE, 0,
    31 KB (4,394 words) - 07:22, 18 April 2021
  • ...evelopers. This wiki article will show you how to use Cryptogams ARMv4 SHA-1 implementation. According to the head notes the ARMv4 implementation runs a ...vp/e_sha_cbc_hmac_sha1.c:615: sha1_block_data_order(&key->md, data, 1);
    15 KB (2,434 words) - 06:10, 14 March 2021
  • This page discusses the API changes for OpenSSL version 1.1. The overall goal of the API changes is to make many data structures opaque ...r provides OpenSSL 1.1.0 functions, like <tt>RSA_get0_key</tt>, to OpenSSL 1.0.2 clients. The source code is available for download below
    16 KB (2,507 words) - 22:23, 3 April 2017
  • ...nSSL [http://www.openssl.org/news/changelog.html Change Log] for OpenSSL 1.1.0 states you can use <tt>-verify_name</tt> option, and <tt>apps.c</tt> offe .../poodleagain.html The POODLE bites again]. The short version: use only TLS 1.2, use only ephemeral key exchanges, and use only AEAD ciphers (like AES/GC
    24 KB (3,955 words) - 15:33, 12 December 2022
  • ...ose further down the page. Note that this uses the auto-init facility in 1.1.0. if(1 != EVP_EncryptInit_ex(ctx, EVP_aes_256_cbc(), NULL, key, iv))
    14 KB (2,119 words) - 10:27, 15 May 2023
  • if(1 != EVP_PKEY_paramgen_init(pctx)) handleErrors(); if(1 != EVP_PKEY_CTX_set_ec_paramgen_curve_nid(pctx, NID_X9_62_prime256v1)) hand
    10 KB (1,677 words) - 12:25, 10 March 2014
  • The [http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf OpenSSL FIPS 140-2 Security Policy] details the way to 2 Intel(R) Itanium 2 processors (1.5 GHz, 6 MB)
    6 KB (930 words) - 08:45, 21 April 2014
  • == Main Changes in OpenSSL 3.0 from OpenSSL 1.1.1 == ...with OpenSSL 3.0 if those applications previously worked with OpenSSL 1.1.1. However this is not guaranteed and some changes may be required in some ca
    54 KB (7,479 words) - 12:36, 20 September 2021
  • |style="padding: 4px;" | Parse an ASN.1 sequence. ...px;" | Message Digest calculation. MAC calculations are superseded by mac(1).
    35 KB (5,360 words) - 11:56, 24 June 2022
  • 33 unsigned long rd_key[4 * (AES_MAXNR + 1)]; 35 unsigned int rd_key[4 * (AES_MAXNR + 1)];
    18 KB (2,869 words) - 06:09, 14 March 2021
  • ...n integer to indicate success or failure. Typically a function will return 1 on success or 0 on error. All return codes should be checked and handled as if(1 != EVP_xxx()) goto err;
    6 KB (896 words) - 03:30, 10 December 2014
  • if(1 != EVP_SealInit(ctx, EVP_aes_256_cbc(), encrypted_key, encrypted_key_len, iv, pub_key, 1))
    4 KB (641 words) - 22:58, 28 April 2017
  • return 1 elif test ! -d $1; then
    6 KB (873 words) - 23:49, 19 July 2014
  • {| class="wikitable sortable" border="1" {| class="wikitable sortable" border="1"
    7 KB (964 words) - 18:13, 6 July 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)