> On Feb 15, 2018, at 12:29 AM, e...@coderhacks.com wrote:
>
> If I try SMIME_read_CMS it is working well if the signature (the 2nd
> MIME-part with smime-type=singed-data)
> has a Content-Transfer-Encodeing of "base64" (as it is in my example)
>
> But It is not working if the CTE is "binary"
Hello!
I need a little hint for parsing SMIME into a CMS_ContentInfo.
Here is an shortend example of my SMIME to make clear the structure of
my content.
Content-Type: multipart/signed; protocol="application/pkcs7-signature";
micalg=sha1; boundary="=_Part_abcde"
Hi, Matt,
Yes, I did with root user, but it was failed like "access denied" when I
tried to do with normal user account.
Also, I didn't get any error messages like "root" user or something in the
log file.
Regards
2018-02-15 9:44 GMT+09:00 Matt Caswell :
> Did you run "make
Hi Matt, thanks for your prompt answer. The testclient is using openssl-1.0.2m
and my previous assumption that the IV was derived from the key_block as in TLS
1.0 was wrong.
It seems that when initialising the cipher with the IV is ignored when the
crypto is AES and the first 16 bytes of the
Did you run "make test" as root by any chance? There is a known issue
where this test fails if you run it as root (fixed in git by commit
b15e62ecc).
Matt
On 14/02/18 21:33, Sakuma, Koshiro wrote:
> Hi, Team,
>
> I'm trying to install openssl-1.1.0g on my CentOS7, but I've gotten
> error during
On 14/02/18 19:39, Hubert Kario wrote:
> How to start current master branch OpenSSL so that it will support static PSK
> key exchange in TLS1.3?
>
> with client running as:
> openssl s_client -psk
>
>
> I've tried:
> openssl
For the failing test, try this
make TESTS=test_rehash V=1 tests
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Thanks for your feedback.
You’re welcome.
You think it might be something like "BUG"??
Probably yes – but the question is whether it’s with the new OpenSSL test
infrastructure, or something with how one of my machines is configured. I do
not know.
Anyway, you are also waiting
Hi, Uri,
Thanks for your feedback. You think it might be something like "BUG"??
Anyway, you are also waiting for the answers right?
Regards,
2018-02-15 6:57 GMT+09:00 Blumenthal, Uri - 0553 - MITLL :
> Funny. I have the same problem with the current master on one of my two
>
Funny. I have the same problem with the current master on one of my two MacOS
High Sierra machines. Surprisingly, the other machine builds and runs the
current master just fine. Configuration and build scripts are automated and
exactly the same between the two.
The “bad” machine runs a
Hi, Team,
I'm trying to install openssl-1.1.0g on my CentOS7, but I've gotten error
during do the "make test" phase. The error I've gotten is as follows.
-
How to start current master branch OpenSSL so that it will support static PSK
key exchange in TLS1.3?
with client running as:
openssl s_client -psk
I've tried:
openssl s_server -psk
On 14 February 2018 at 16:34, Matt Caswell wrote:
>
>
> On 14/02/18 16:27, Richard Moore wrote:
> > If I run the following:
> >
> > openssl-1.1.1pre1 ciphers -tls1_3 -v
>
> The man page says this about the "-tls1_3" option:
>
> "In combination with the B<-s> option, list the
On 14/02/18 16:27, Richard Moore wrote:
> If I run the following:
>
> openssl-1.1.1pre1 ciphers -tls1_3 -v
The man page says this about the "-tls1_3" option:
"In combination with the B<-s> option, list the ciphers which would be
used if TLSv1.3 were negotiated."
So you need to add "-s". If
If I run the following:
openssl-1.1.1pre1 ciphers -tls1_3 -v
Then I get lots of ciphers, for example AES128-SHA however the latest draft
TLS 1.3 RFC states:
The list of supported symmetric algorithms has been pruned of all
algorithms that are considered legacy. Those that remain all use
In message on Tue, 13
Feb 2018 19:58:34 -0800, Norm Green said:
norm.green> In 1.1.1 pre-relase 1, we have this new function:
norm.green>
norm.green> int OSSL_STORE_ctrl(OSSL_STORE_CTX *ctx, int cmd, ...
16 matches
Mail list logo