On 10/16/18 1:44 PM, Richard Welty wrote:
> i'm trying to figure out why BIO_do_connect is failing with
> a negative value. so far as i know i've done all preliminaries
> correctly, but apparently i've missed something. i am dumping
> the SSL errors from ERR_get_erro
i'm trying to figure out why BIO_do_connect is failing with
a negative value. so far as i know i've done all preliminaries
correctly, but apparently i've missed something. i am dumping
the SSL errors from ERR_get_error but am not getting any in
this instance.
OpenSSL version is 1.1.0h
Ubuntu 18.0
i'm working on unit tests for the new NTS stuff for NTP and am having
some issues with setup & teardown for OpenSSL; there may be an actual
bug here; i'm looking for some guidance.
NTP is currently using the Unity test framework, which is a fairly
standard unit testing package. i have two tests fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
ok, i have a crash in CMS_verify that suggests i'm not
setting up the store of CAs properly, or i may have made
an error setting up the CA. what should i be looking at
with this error?
(gdb) bt
#0 0x77909b6c in X509_STORE_get_by_subject ()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 7/9/15 9:53 AM, Dr. Stephen Henson wrote:
> On Thu, Jul 09, 2015, Richard Welty wrote:
>
>>
>> how does one set a content type for a signed CMS object? i am
>> creating it with a call to CMS_sign (with flag CMS_PAR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
how does one set a content type for a signed CMS object?
i am creating it with a call to CMS_sign (with flag CMS_PARTIAL
set among others), then when i call CMS_set1_eContentType
it crashes.
thanks,
richard
-BEGIN PGP SIGNATURE-
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
what is the lowest overhead method for encrypting using
CMS_encrypt then signing using CMS_sign? it seems like
using BIO_new_mem_buf ought to do but i don't see a method
for getting the length of the CMS_ContentInfo object to
feed to the BIO creation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[resending from the correct email address; list moderator, if you see this
first, just delete the one in the non-member queue]
On 2/24/15 10:10 AM, Dr. Stephen Henson wrote:
> So the embedded content type will be enveloped data?
>
> If so first you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 4/30/15 6:32 PM, Richard Welty wrote:
> 1) the documentation on d2i_CMS_ContentInfo() is a bit light on
> details about the parameters. what should the first parameter be, a
> certificate as with d2i_X509?
ok, figured this one out f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2/24/15 10:10 AM, Dr. Stephen Henson wrote:
> On Tue, Feb 24, 2015, Richard Welty wrote:
>
>> On 2/24/15 9:21 AM, Dr. Stephen Henson wrote:
>>>
>>> Typically you'd write the signed content to a memory BIO and t
On 2/24/15 9:21 AM, Dr. Stephen Henson wrote:
>
> Typically you'd write the signed content to a memory BIO and then decrypt
> that. Precisely how you decrypt the enveloped data depends on the format. It
> might be in MIME format in which case you'd pass it through the MIME parser.
> Alternatively i
i'm starting on some work that needs to use CMS in an
application, and i'm having trouble getting my head
wrapped around how to handle the case of verifying
a signature and then decrypting the enveloped data
that has been signed. specifically, i'm not grasping
how to extract the encrypted data to p
12 matches
Mail list logo
