The Following User Says Thank You to rainisto For This Useful Post: | ||
![]() |
2013-01-06
, 17:39
|
|
Posts: 2,222 |
Thanked: 12,651 times |
Joined on Mar 2010
@ SOL 3
|
#12
|
[...]
For N900 users, please refer to below script.
[...]
Simple script/guide to remove fraudulent CAs:
Code:#!/bin/sh #removing fraudulent CAs echo enter the cert\(ifier\) You are looking for: read cert cmcli -T common-ca -L | grep "$cert" echo now copy the full cert ID ... read nothing echo and give it as input \(for removal\) read certID if [ `id -u` != 0 ] ; then sudo cp /etc/certs/common-ca/$certID.pem /etc/certs/common-ca/$certID.pem.old sudo cmcli -c common-ca -r $certID else cp /etc/certs/common-ca/$certID.pem /etc/certs/common-ca/$certID.pem.old cmcli -c common-ca -r $certID fi echo now open microb and goto echo chrome://pippki/content/certManager.xul echo and delete the cert also there in the CA manager read nothing dbus-send --system --type=method_call --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"chrome://pippki/content/certManager.xul"
I have no idea, why we do have them twice. Or if we need to block/delete both. Or if only one is fraudulent ...
The Following 2 Users Say Thank You to joerg_rw For This Useful Post: | ||
![]() |
2013-01-06
, 18:16
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#13
|
sudo cp
and others won't work on sane default sudo setup, so you'll have to run this in a root account instead (install rootsh, do `root`)
/j
#!/bin/sh if [ `id -u` != 0 ] ; then exec sudo gainroot <<EOF exec sh $0 $* EOF exit $? fi #removing fraudulent CAs echo enter the cert\(ifier\) You are looking for: read cert cmcli -T common-ca -L | grep "$cert" echo now copy the full cert ID ... read nothing echo and give it as input \(for removal\) read certID cp /etc/certs/common-ca/$certID.pem /etc/certs/common-ca/$certID.pem.old cmcli -c common-ca -r $certID echo now open microb and goto echo chrome://pippki/content/certManager.xul echo and delete the cert also there in the CA manager read nothing dbus-send --system --type=method_call --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"chrome://pippki/content/certManager.xul"
The Following 2 Users Say Thank You to peterleinchen For This Useful Post: | ||
![]() |
2013-01-19
, 23:40
|
Posts: 2,292 |
Thanked: 4,135 times |
Joined on Apr 2010
@ UK
|
#14
|
![]() |
2013-01-20
, 00:55
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#15
|
![]() |
2013-01-20
, 00:57
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#16
|
No, it is due to the cert name begins with "(".
You may check with
Code:dbus-send --system --type=method_call --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"chrome://pippki/content/certManager.xul"
Yes, there is such possibility. I will put a script (produced at DigiNotar times) at the end of post.
For N900 users, please refer to below script.
For N9 users, do we need to delete that CA also from browser? (but according to open mentioned bug, there is no such possibility?)
Simple script/guide to remove fraudulent CAs:
Code:#!/bin/sh #removing fraudulent CAs echo enter the cert\(ifier\) You are looking for: read cert cmcli -T common-ca -L | grep "$cert" echo now copy the full cert ID ... read nothing echo and give it as input \(for removal\) read certID if [ `id -u` != 0 ] ; then sudo cp /etc/certs/common-ca/$certID.pem /etc/certs/common-ca/$certID.pem.old sudo cmcli -c common-ca -r $certID else cp /etc/certs/common-ca/$certID.pem /etc/certs/common-ca/$certID.pem.old cmcli -c common-ca -r $certID fi echo now open microb and goto echo chrome://pippki/content/certManager.xul echo and delete the cert also there in the CA manager read nothing dbus-send --system --type=method_call --dest=com.nokia.osso_browser /com/nokia/osso_browser/request com.nokia.osso_browser.load_url string:"chrome://pippki/content/certManager.xul"
--edit
BUT, one more question arises here:
I do see two certificate IDs for TÜRKTRUST
and also in browsers
they do appear twice.
So maybe for harmattan users, you also check bettwer twice?
I have no idea, why we do have them twice. Or if we need to block/delete both. Or if only one is fraudulent ...
$ perl /usr/bin/c_rehash /etc/certs/common-ca
The Following User Says Thank You to pali For This Useful Post: | ||
![]() |
2013-01-20
, 01:06
|
Posts: 3,074 |
Thanked: 12,964 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#17
|
@sixwheeledbeast: This certificate applet had bug - it shown blacklisted certificates as valid. Bug was fixed in PR1.3.1 by this commit: https://gitorious.org/maemo-5-certif...4945c1dce4bf6e
So for blacklisting you *need* PR1.3.1
The Following 3 Users Say Thank You to freemangordon For This Useful Post: | ||
![]() |
2014-09-01
, 21:49
|
Posts: 27 |
Thanked: 5 times |
Joined on Mar 2010
|
#18
|
But if your in open mode then you can just install opensh with (if you have downloaded the deb package to your device).
Harmattan openmode:
apt-get install wget
wget http://maemo.cloud-7.de/HARM/N9/open...nsh/opensh.deb
AEGIS_FIXED_ORIGIN=com.nokia.maemo dpkg -i opensh.deb
IRC: jonni@freenode
Sailfish: ¤ Qt5 SailfishTouchExample ¤ Qt5 MultiPointTouchArea Example ¤ ipaddress ¤ stoken ¤ Sailbox (Dropbox client) ¤
Harmattan: ¤ Presence VNC for Harmattan ¤ Live-F1 ¤ BTinput-terminal ¤ BabyLock ¤ BabyLock Trial ¤ QML TextTV ¤
Disclaimer: all my posts in this forum are personal trolling and I never post in any official capacity on behalf of any company.
Last edited by rainisto; 2013-01-06 at 15:46.