New answers tagged

2

Assuming you posted correctly, your second file has the base64 body of the claimed PEM format as a single line, not broken/folded into lines of 64 chars (max) as required. See RFC 7468 section 2 near the end. Some software is lax about this (including, usefully, openssl asn1parse !) but not all. I wonder if you got these switched, because OpenSSL commandline ...


0

So first, we need to decode these two CSRs which are ASN.1 encoded. SpongyCastle CSR OpenSSL CSR As you can see they differ in their values for the public key, for the Locality Name (= the town), the OrganizationalUnit name (marketing vs software), the OrganizationName (Inforpires vs SISOFT srl) and in the signature at the end. However the most important ...


6

I do not know how they are related to each other. EtM, MtE and E&M are generic constructions that take pairs of schemes that satisfy weaker security notions (chosen-plaintext security and unforgeability) and turn them into AEAD-secure schemes. GCM is a construction that takes a 128-bit block cipher and turns it into - an AEAD-secure scheme and ...


0

The secp256k1 ECDSA vectors provided in bouncycastle are correct, exception made for the s field in the signature. My verification results in: M = octet[32] 4b688df40bcedbe641ddb16ff0a1842d9c67ea1c3bf63f3e0471baa664531d1a, d = octet[32] ebb2c082fd7727890a28ac82f6bdf97bad8de9f5d7c9028692de1a255cad3e0f, k = octet[32] ...


Top 50 recent answers are included