Hi thanks for the responses. I try not to do crypto for the very reasons
you raise - i simply don't know enough and your (good) pointed questions
have demonstrated that.
Context:
We are trying for GDPR and other privacy law compliance. We probably need
to meet GDPR, US requirements, Australian r
On Thu, Oct 11, 2018 at 01:23:41AM +, Michael Wojcik wrote:
> - Data recovery from an encrypted backup is tough. With CBC, one bit goes
> astray and you've lost everything after that.
No, a 1 bit error in CBC ciphertext breaks only the current block,
and introduces a 1 bit error into the plai
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> Paul Chubb
> Sent: Wednesday, October 10, 2018 19:16
> I am in the process of using the openssl suite for many things including
> encrypting private information. There is a heap of information on the internet
> sugges
Hi,
I am in the process of using the openssl suite for many things
including encrypting private information. There is a heap of information on
the internet suggesting using the openssl client for these sort of
purposes. However in a very few places there are also statements that the
client is
Hi there,
I have a client can talk with server, where the client certificate is
loaded in client_cert_cb based on matching the server side certificate.
it works perfectly in openssl 1.1.0h, however it stops working after I
upgrade to openssl 1.1.1.
In client_cert_cb , when I call SSL_get_peer_c
On 10/10/2018 13:55, RudyAC wrote:
Hello,
when verifying a signed email with CMS_verify() the verification failed.
That is not the main problem.
My problem is that the out data is empty. Using the library I got following
error:
OpenSSL Error code all:<772382878d>
OpenSSL Error code lib:
Hello,
when verifying a signed email with CMS_verify() the verification failed.
That is not the main problem.
My problem is that the out data is empty. Using the library I got following
error:
OpenSSL Error code all:<772382878d>
OpenSSL Error code lib:<46d>
OpenSSL Error code func: <15
Hi All,
I came across a term "Full PKI Authentication".
Please someone clarify, what the name "Full" suggests here ? Is there
any specific "Full PKI" version available ? Anay specific RFC
available for "Full" PKI other than the following ?
https://tools.ietf.org/html/rfc5280.html
I could see s
Actually, for public CAs, the current standard (the CAB/F
Basic Requirements) require (a), (b) or (c), and prohibit
(d).
The prohibition on (d) is stated indirectly as a prohibition
against putting something that isn't the subjects validated
public DNS name in CN.
In practice, most public CAs us
nothing don't need to happen to the kid and I can't pick any one so I just
come out side
On Wed, Oct 10, 2018, 3:14 AM Dustin Albright
wrote:
> I come out side on fruit porch the kid and dad's in side like I said I
> can't pick I'd how I ended up doing this but I'm here on the porch u diseve
>
I come out side on fruit porch the kid and dad's in side like I said I
can't pick I'd how I ended up doing this but I'm here on the porch u diseve
the respece
On Wed, Oct 10, 2018, 3:02 AM Dustin Albright
wrote:
> this really wasn't my intention on all this not really sure how I don't
> it eat
this really wasn't my intention on all this not really sure how I don't it
eat her
On Wed, Oct 10, 2018, 2:18 AM Walter H. wrote:
> Hello,
>
> which of these possibilities is the correct one?
>
> (a) CN=*.example.com
> and subjectAltName = DNS:*.example.com, DNS:example.com
>
> (b) CN=ex
if u would like to talk I will come talk with u because u divers the
respect
On Wed, Oct 10, 2018, 2:18 AM Walter H. wrote:
> Hello,
>
> which of these possibilities is the correct one?
>
> (a) CN=*.example.com
> and subjectAltName = DNS:*.example.com, DNS:example.com
>
> (b) CN=example.c
13 matches
Mail list logo
