September 21, 2019, 09:50:52 pm


Have you visited the Allwinner Chipset wiki? -

openssl Problme

Started by harvey186, November 16, 2017, 07:55:26 am

Previous topic - Next topic


Hi, ich habe auf meinem Cubietruck / Linaro OS openssl installiert. Wenn ich nun meinen webserver aufrufe, dann bekomme ich aber immer die Meldung, dass die Verbindung nicht sicher ist. Das Zertifikat wird aber gefunden (siehe Anhang).
Die Zertificate habe ich im unter /etc/ssl/cert abgespeichert.

By the way: Die Meldung bekomme ich sowohl beim lokalen Zugriff, als auch ├╝ber eine dyndns domain

Wo ist also das Problem ??



I work a lot with OpenSSL (1.1.0), but on Fedora/Centos and ONLY in English.

If you provide your question and screen capture in English I may be able to help.

I really wish I could deal with German, but I am dyslexic a highly mono-linguistic.


Hi, no problem, I can explain in english :)

I have setup my cubietruck with debian linaro as a NAS. I have installed openSSL and the certificates I have stored under /etc/ssl/cert.
When I access my NAS via browser I'm always getting the hint / error message:
and that the connection is not secure and the https:// is in red in the browser address line.

The certificate is found but will not accepted. Ok, I can tell the browser that that's OK, but ist's worst to tell all people that the have to accept this unsecure site. 

What can I do, that the certificate will be accept in all browsers ?

I hope this will explain my issue.


You probably have a self-signed certificate.  Browsers today treat this as an error condition that the user has to accept the 'risk' of using a self-signed cert.  After all, Mal could make a cert with the same content (other than the keys) as yours and trick your users into accepting it.

Thus you need to provide your users with YOUR keyid so they can store your certificate with confidence.  Or have control over the network such that they cannot be connected to anything but your NAS.  If you store the cert, you only go through this warning once.  Per user.

Or buy a cert.

If you are interested, I have published an Internet Draft on building an ECDSA PKI.  This does not directly fix your challenge, but if you have multiple servers for your users, they only need to accept your root cert then they will auto accept all certs signed in that PKI.

My draft can be found at:

I do have to rev it, as one grad student using it for his thesis for his PKI found a typo in one of the chmod commands...

Plus I want to add support for 802.1AR iDevID CSRs.

Note this is only for ECDSA certificates.  I try not to use RSA certs anymore, and EDDSA certs are in the next release (1.1.1).

Hope this helps



Another option is to get your certificate from: