You are not logged in. Please login or register.
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
ReferenceswolfSSL - Embedded SSL Library → Posts by anthony
Note, you can also get the generated certificates from here: https://github.com/wolfSSL/wolfssl-examples/pull/375
Hi Basak,
but, still I cannot start my server with it.
What error message are you seeing?
And yes, the generated files should be moved to wolfssl/certs/ directory
Hi Basak,
I don't know your computer's directory setup so I cannot give you the exact commands you need to execute. When I say /path/to/osp/... I mean "The path to where you downloaded osp project to...."
Hope this helps!
Warm regards, Anthony
Hi basak,
My name is Anthony and I'm a member of the wolfSSL team. Please note that the certificates are not included as part of wolfSSL. They need to be generated. The instructions for generating them are at https://github.com/wolfSSL/osp/tree/mas … /README.md .
Please let us know about your progress with this experiment.
Warm regards, Anthony
Ok, so you are now having success with our example client. You can now use that as a template to better understand what you need to do. Since you mentioned embedded, please do consider tiny curl. It just might fit your use case!
Warm regards, Anthony
Hi msorage,
There is some sort of problem here. Your debug output indicates you only processed 2 certificates. You should have processed all the certificates in the /etc/ssl/certs.
Please use a debugger to figure why that hasn't happened.
Warm regards , Anthony
Hi,
Please do this and then send over the logs:
./configure --enable-sys-ca-certs --enable-debug
make all
./examples/client/client -h www.wolfssl.com -p 443 --sys-ca-certs
Hi msorage,
I guess you're going to have to try again with --enable-debug to get some more verbose logging since I can't reproduce your issue here.
Warm regards, anthony
That's odd. This is my output:
SSL version is TLSv1.2
SSL cipher suite is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
SSL curve name is SECP256R1This is where we are looking for the certificates:
"/etc/ssl/certs", /* Debian, Ubuntu, Gentoo, others */
"/etc/pki/ca-trust/source/anchors", /* Fedora, RHEL */
"/etc/pki/tls/certs" /* Older RHEL */What distribution of linux are you using? Can you check the locations specified above to see if there are certificates there?
Warm regards, Anthony
Hi,
Also, please consider tiny-curl. You can find it at https://www.wolfssl.com/download/
Warm regards, Anthony
On Linux, this worked for me:
./configure --enable-sys-ca-certs
make all
./examples/client/client -h www.wolfssl.com -p 443 --sys-ca-certs Warm regards, Anthony
Hi,
May I ask why you are doing this and what you are trying to achieve? Is this an academic or hobby project? We love know what people are doing with wolfSSL.
Have you considered using curl? You can download the source for curl and build it with wolfSSL underneath. Then you can look at how curl is calling wolfSSL to get a better understanding of what is needed. Or, depending on your needs, curl might be a better fit.
Warm regards, Anthony
I noticed your address is a numeric IP address. within the certificate, is that numeric ip address specified?
What names are specified in the certificate?
Hi msorage,
Thanks for trying this out. I guess we're going to need more information. Can you start by turning on logging? Build with --enable-debug and call wolfSSL_Debugging_ON() at the beginning of your application.
Warm regards, Anthony
Hi msorage,
This return code indicates that you do not have a root certificate that chains up to the certificate provided by the server. You can use your browser to go to any site, look up the security settings for that site and from there get the root certificate that chains up to it held by your browser.
I hope this helps!!
Warm regards, Anthony
Hi jobryansr,
My name is Anthony Hu and I am a member of the wolfSSL team. Can you please e-mail facts@wolfssl.com with your question? This forum is more focused on technical questions. We can handle your FIPS questions better via email.
Warm regards, Anthony
Hello jferraris,
This issue was fixed in wolfssl's `master` branch. Please see the following pull request that has already been merged: https://github.com/wolfSSL/wolfssl/pull/6085
Warm regards, Anthony
Hi _angelo_
1) are you asking to never send change_cipher_spec and to ignore them if received ?
2) in `wolfssl/internal.h` we define max record size as follows:
MAX_RECORD_SIZE = 16384, /* 2^14, max size by standard */
Hope this helps. Let me know your clarifications on the first point and if you have any further questions.
Warm regards, Anthony
Hello m_u_h, how are you?
My name is Anthony Hu and I am part of the wolfSSL team.
There are many reasons why openssl might not be using wolfengine. How are you performing SSH and TLS? Are they separate applications? If so, then it could be that the application doing TLS was built with static libraries in which case that particular application would not support engine usage.
Can you please share details about your applications? For example, how are they built?
Also, here at wolfSSL we love hearing about how our software is being used. Can you let us know about your project and what your goals are?
Warm regards, Anthony
Hello ajmal,
Thank you for reaching out and asking about wolfSSL! My name is Anthony Hu and I will do my best to help you. At wolfSSL, We love hearing about how people are using our projects so can you please tell us about your project and what you are trying to achieve?
wolfSSL's INSTALL file has instructions for building and installing on both IOS and Android: https://github.com/wolfSSL/wolfssl/blob/master/INSTALL
Here you will find some examples for BTLE: https://github.com/wolfSSL/wolfssl-exam … aster/btle
Here are some examples for using our libraries on Android: https://github.com/wolfSSL/wolfssl-exam … er/android
After looking at these resources, please do let us know if we can be of further assistance.
Warm regards, Anthony
In the meantime, I will also try to create an example using with custom extensions.
Warm regards, Anthony
Hi stroebeljc,
how are you today? I'm glad to see you have discovered our `--enable-asn=template` flag! You say enabling it made other things break. I'm sorry to hear that.
Can you be more specific? Can you let us know what broke?
Please send your details to support@wolfssl.com. That will open up a support ticket and I will personally take ownership of it.
Warm regards, Anthony
wolfSSL - Embedded SSL Library → Posts by anthony
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.010 seconds (64% PHP - 36% DB) with 5 queries