Thread
:
TLS1.2 and N9 (polishing brass on a sinking ship)
View Single Post
dredlok706
2024-08-17 , 14:53
Posts: 270 | Thanked: 321 times | Joined on Oct 2021 @ Poland
#
30
I managed to repeat the things done by @n9erator and TLS 1.2 in default browser of my N9 is working!!!
Sadly not certificates thing. I mean - TLS 1.2 in browser itself works. But every site complains about certificates. "Security certificate is not trusted" I know that to fix this aegis-certman-common-ca changes were needed. But.
1. Applying the postinst patch worked
2. In etc/ssl/certs/common-ca I removed all files and inserted crt files from ca-certificates of Ubuntu, moved to *.pem as they were text ones
3. Patch on certman_main.cpp didn't work, something got rejected. I applied changes manually then.
Building worked fine, installing not, though. Error during postinst part:
Code:
ERROR: cannot not convert '00d85a4c25c122e58b31ef6dbaf3cc5f29f10d61-1' to key id
Checking /etc/ssl/certs, it's the first cert. I can't remove them, because they are owned by weird aegis users and chowning to root has no effect. I understand that patched postinst causes that, but what's wrong then?
Tried different way, usually working - injecting PEM files into /usr/local/ssl/certs (my OpenSSL 1.0.1t is in /usr/local + /usr/local/ssl), doing c_rehash then (had to use custom perl), it worked but still browser always complains.
What certs did you use and how did you put them to aegis-certman source? But don't think that's the cause, because only applying patch to postinst causes error on installing as well (keeping default certs from source).
Thanks in advance
__________________
My Telegram group (Maemo / MeeGo / Sailfish)
:
https://t.me/linuxmobile_world
Last edited by dredlok706; 2024-08-17 at
19:26
.
Quote & Reply
|
The Following User Says Thank You to dredlok706 For This Useful Post:
Maemish
dredlok706
View Public Profile
Send a private message to dredlok706
Find all posts by dredlok706