Sometimes you have a complex object and you need to store it into your database. Most cases the serialize function does work. Unfortunately sometimes it does not ( not because serialize is broken/bugged ).

The Library is useful only if the followings are true:

• You want to store your object inside a database
• Your object is not “Flat”  ( meaning you’ve at least a value in your object that is an array or an object itself )
• You want to use your Database SQL to Search & filter objects with a particular value.

The last sentence is actually the most appealing. Lets take, for example, the following objects:

<?php 
  $bob = new stdClass();
  $bob->name = 'Bob';
  $bob->permissions = array( );
  $bob->permissions['can_write'] = true;
  $bob->permissions['can_read'] = true;

  $mat = new stdClass();
  $mat->name = 'Mat';
  $mat->permissions = array( );
  $mat->permissions['can_write'] = false;
  $mat->permissions['can_read'] = true;

Mat and Bob are 2 users. We’d like to persist them in a database but You can’t design a Database Table that scales well. Why?

1. Cause maybe you’ll also add a “surname” key sometimes in the future
2. Cause you don’t know if you’ll add other permissions in the future ( Sub-Set of the previous sentence )

So, what stops us to use serialize() ? Well, take a look to how $mat looks when “serialized”

O:8:"stdClass":2:{s:4:"name";s:3:"Mat";s:11:"permissions";a:2:s:9:"can_write";b:0;s:8:"can_read";b:1;}}

Good Luck creating an SQL Query that finds all the users that have the permission to write.

Using Flatterizor you’ll have a completely different output. First, lets see how our code would change if we’re going to use the library.

<?php
  require_once('./classes/flatterizor.class.php');

  $mat = new stdClass();
  $mat->name = 'Mat';
  $mat->permissions = array( );
  $mat->permissions['can_write'] = false;
  $mat->permissions['can_read'] = true;

  $flatterizor = new ObjectFlatterizor(true);
  $matGoodLooking = $flatterizor->flatterize($mat);
  var_dump($matGoodLooking);

The output of the flatterize method is an object with 2 keys:

• objectDefinitions:  Used to rebuild the object it contains a plain array of strings with the name of the classes and their paths
• values:  An array of arrays. Each array will contain 2 keys
• path:  It’s the path of the value
• val

Let’s take a look to the var_dump output.

object(stdClass)#4 (2) {
  ["objectDefinitions"]=>
  array(1) {
    ["/"]=>
    string(8) "stdClass"
  }
  ["values"]=>
  array(3) {
    [0]=>
    array(2) {
      ["path"]=>
      string(5) "/name"
      ["val"]=>
      string(3) "Mat"
    }
    [1]=>
    array(2) {
      ["path"]=>
      string(24) "/permissions/[can_write]"
      ["val"]=>
      bool(false)
    }
    [2]=>
    array(2) {
      ["path"]=>
      string(23) "/permissions/[can_read]"
      ["val"]=>
      bool(true)
    }
  }
}

The end goal was to persist the object inside a database so that we could easily search through an SQL Query. For the example I designed the following database table.

CREATE TABLE IF NOT EXISTS `userinfos` (
  `userID` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(256) NOT NULL,
  `val` varchar(256) NOT NULL,
  PRIMARY KEY (`userID`,`name`),
  KEY `name` (`name`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

In our example we’ll need to perform a loop on $matGoodLooking->values and insert the values inside the table where

• ‘path‘ will be mapped in the ‘name‘ column
• ‘val‘  will be mapped in the ‘val‘ column

With a very simple SQL Statement we’ll be able to find all the  users that have the ability to write.

SELECT userID from userinfos
WHERE name='/permissions/[can_write]' 
AND val='true'

Note: It’s not hard to understand that if you’ve a lot of users, the table is going to fill your disk space very quickly. There’re a lot of solutions to this so I won’t cover them here.

Sooner or later you’ll want to retrieve your users in the original form. Doing that is very easy… just use the static method called ObjectFlatterizor::rebuild . It accepts 1 parameter which is the exact output of the flatterize() method… you’ll be required to rebuild it correctly.

Using with WordPress

The idea came working with WordPress. I had a Box inside the “Post Edit” screen, this box contained ~30 input fields. I then created a way to save those fields in an object. Soon I realized I needed to search posts using this object values… since WordPress provides a way to search posts using the post_meta values,  I built the library to serialize/deserialize my objects in the post_meta table.

The whole thing works very well

Authors

• Andrea Baccega me@andreabaccega.com - Author/Ideator of the library
• Emanuele ‘Tex’ Tessore setola@gmail.com - Contributor of the library

More infos

I strongly suggest to:

• take a look @ github
• take a look @ the demo folder

• You lose your data
• You start hosting third party data

Why?

We usually start making backups cause we don’t want to lose important bits. ( or at least we want to minimize the amount of lost data )

What?

This question could be easily under-estimated. This is, imho, one of the most important question when talking about backups.

In my case I wanted to backup:

• My config files ( apache, mysql, nginx etc )
• The www directory
• mysql data

Where?

The backup location differs proportionally with the “security level” you want to get.

In some case scenarios it could be enough to backup your data using the same Hard Drive but just in a different folder.

So here i’ll propose a quick Q&A. list to help you pick the correct “Where” answer:

• Covered from unwanted file deletions => backup on a different folder
• Covered from hard drive failure => backup on a different hard drive
• Covered from robbering/flames/water => backup on a different machine on another location
• Covered from large scale issues ( Earthquakes, Tsunamis, Aliens? ) =>backup on different machine(s) on another country/continent

In this howto we will backup the data using a different server .

How?

There’s no definitive answer to this question! There are only best-practices you can put in place!

The first rule: Running several servers I learned that the server containing the data we want to backup should not be ( as much as possible ) involved in the backup process. I used to backup my data with some scripts inside the same server, I discovered this approach is not scalable and somehow not reliable as I wanted it to be.

The second rule (which is also an effect of the previous one ) is: do not send your backup to the backup servers, let the B.S. fetch the data it needs. Why? Suppouse your server get hacked and the attacker decides to look around and find your scripts, this could lead to 2 problems:

1. If you didn’t configure the backup server ACLs correctly you’re going to give the attacker free access also to your backup servers.
2. They’ll be able to delete your data also from your backup servers.

The third rule: do not re-invent the wheel. There are a lot of free tools in the internet you can use. In my scenario i picked these ones:

• rsync: very popular sync tool for windows and linux
• rsnapshot: a very handy tool that works close with rsync to make incremental backups in a very efficient way
• mysqldump: the console based backup tool.

When?

This is also a crucial question and you’ll need to think about the answer very carefully. It all depends on you and there are no strict rules on this.

My Setup

I probably already mentioned I’ve some web servers. Since some days ago each of them were taking care about its own backup. I manually created a bunch of highly customizable scripts that I used for more than a year now.

Even if I don’t like to change things that simply works I love to improve & optimize.

The old setup was:

• Each web server had a script that was responsible of backing up files and databases,
• Each web server had another script which connected to a remote ftp and send those backups there
• The backup granularity was daily and I had at least 1 week of data.

The new setup i wanted was:

• A new backup server that takes care of everything.
• Only one place where i could change my backup parameters for all the servers.

Obviously the new setup is more complex and expensive than the previous one, but I didn’t want to live with the old setup anymore.

I searched for a backup server online and I eventually found a low-end dedicated server which had with very poor cpu performance but enough space for my needs.

First of all create a user

On the webserver you’d like to backup i suggest to add a brand new user that will handle all the stuff we need to backup our data. The whole “tutorial” is based on this step.

For you lazy sysadmins here is the shell command you should launch to create the user.

sudo adduser backupper

Note: I’ll refer to the “backupper” user in along the tutorial. If you decided to rename it then you should take care to replace the username below.

Setting up regular mysql backups with cronjobs

Data stored in mysql databases are usually, for a web server, a top priority that needs to be backed up regularly.

Before proceding setting up rsnapshot we will need to set up a mysql backup script that will be launched daily with a cronjob.  Before creating the script we need to create a user that, for security purposes, is only allowed to issue commands that are needed to mysqldump.

In order to do that you’ve to open the mysql console using your mysql admin/root password:

mysql -u root -p

Then, choose a password for your new user and issue the following 2 sqls:

CREATE USER 'backupuser'@'localhost' IDENTIFIED BY  'your-password-here';

GRANT SELECT , 
LOCK TABLES , 
SHOW VIEW ON * . * TO  'backupuser'@'localhost' IDENTIFIED BY  'your-password-here' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;

Note: replace the passwords with your own

Once created the user create a file named .my.cnf inside the home directory of backupper user. ( /home/backupper ) with the following content

[client]
   host     = localhost
   user     = backupuser
   password = your-password-here
   socket   = /var/run/mysqld/mysqld.sock

In order to add a bit of security issue the following shell command

chmod 700 .my.cnf

This will prevent other users to read the mysql configuration file.

To test the whole thing issue the following shell command:

mysql -Bse "show databases"

If the result of this command is the list of your databases then everything was setted up correctly. If you get an error ( probably “Access denied” ) then you should double check all the previous steps.

Now that our mysql configuration is up and running we need a shell script that will take care to backup our databases for us. You can use the following simple script. Name it “backup_databases.sh” and place it inside /home/backupper.

#!/bin/bash
mkdir -p ~/mysqlbackups/
for i in $(mysql -Bse "show databases"); do
        mysqldump  $i > ~/mysqlbackups/$i.sql
done

If you’re familiar with bash scripts then you’ll easily understand how the code works. Btw, for the sake of clarity, every time you launch this script a complete backup of all your databases will be placed inside ~/mysqlbackups

The last step is to set up a cronjob that will launch the above mentioned shell script. It’s a good idea to let the cronjob start during the night ( expecially if your server is very busy during the day ). In my crontab i decided to fire the mysql backups at 01:10 each day.

sudo su backupper
crontab -e

while editing the crontab add something like this

10 1 * * * /bin/bash /home/backupper/backup_databases.sh 2>&1 > /dev/null

Now everything related to mysql should be setted up!

Setting up SSH with Public/Private keys

Before going any further we need to make ssh authentication with public/private keys between the 2 servers work properly. There are a lot of tutorials online you can use but for clarity I’ll write the commands i launched:

On the backup server:

cd ~/.ssh
ssh-keygen -f rsynckey -C 'My Rsync Key' -N '' -t rsa -q

Once the key is created you’ll need to copy the public key on the web server appending/creating something like this to the file /home/backupper/.ssh/authorized_keys

ssh-rsa AAAAB3NzaC.......NbPjH veke@backupserver

In order to add some security to the connection i suggest to prepend the following to the previously added line ( Everything must go in the same line )

from="ip_of_backup_server",no-agent-forwarding,no-port-forwarding,no-pty,no-user-rc,no-X11-forwarding

The entire line should look like the following after the mod:

from="ip_of_backup_server",no-agent-forwarding,no-port-forwarding,no-pty,no-user-rc,no-X11-forwarding ssh-rsa AAAAB3NzaC.......NbPjH veke@backupserver

This will restrict the incoming connections only from the specified ip ( You can also specify the hostname there ) and it will disable some unnecessary stuff.

Since from my backup server I want to backup files owned by root I need the “backupper” user to be in sudoers file. Then open up your /etc/sudoers file in the backup server and add the following:

backupper ALL= NOPASSWD: /usr/bin/rsync

Using this trick we’ll let the backupper user to run sudo only if he needs to execute the rsync binary.

In order to make things easier lets create ~/.ssh/config file in the Backup Server.

Host client1
HostName client1.tobackup.com
Port 22
IdentityFile ~/.ssh/rsynckey

This will simplify us the life afterwards while configuring rsnapshot. If you want to test that everything is setted up correctly just fire in the backup server

veke@backupserver:~/$ ssh backupper@client1
PTY allocation request failed on channel 0

It could sound like an error message but it’s not! Infact if you get that response that will mean:

• The public/private key is setted up correctly
• The config file is setted up correctly
• You restricted the key to not have the pty ( Correct since we won’t use it )

If you get a Password prompt that means that something went wrong. Double check the previous steps!

Setting up rsnapshot

Why rsnapshot? Well, cause it’s perfect. It does perfectly handle my situation and it also save some disk space on your backup server using hard links instead of doing each time a full copy ( You’ll also save bandwidth ).

In order to set up rsnapshot correctly you’ll only have to install some goodies.

On both backup server and the web server install rsync:

sudo apt-get install rsync

(Backup server only) install rsnapshot

sudo apt-get install rsnapshot

From now on all the stuff will need to be done on the backup server only.

Like every good tool rsnapshot has a config file. We need to create a config file that will define a couple of things. Remember: TABS must separate all “columns”

config_version	1.2
snapshot_root	/your/backup/folder/
cmd_rsync	/usr/bin/rsync
cmd_ssh	/usr/bin/ssh
cmd_cp	/bin/cp
cmd_rm	/bin/rm
cmd_logger	/usr/bin/logger
cmd_du	/usr/bin/du
retain	daily	7
retain	weekly	7
retain	monthly	3
#client1 backups
backup	backupper@client1:/home/backupper/mysqlbackups	client1/
backup	backupper@client1:/etc	client1/	+rsync_long_args=--rsync-path='sudo rsync'
backup	backupper@client1:/var/www	client1/	+rsync_long_args=--exclude '/stats/*' --exclude '/log/*' --exclude '/phptmp/*' --exclude '/cache/*' --rsync-path='sudo rsync'

• line 2: defines the folder where rsnapshot will write the backups
• from line 3 to 8: we define absolute path to some binaries
• from line 9 to 11:  we define the retain values. This will specify how many backups ( for the specified “timeframes” ) we want rsnapshot to “maintain”
• from line 13 to 15: we define what to backup.
• line 13: we want to backup the folder /home/backupper/mysqlbackups (look at the mysql section above) and we will log in to a host named “client1″ (look at the ssh section above) using the “backupper” user.
• line 14: we want to backup the /etc folder. We also want to run rsync with “sudo”
• line 15: we want to backup the /var/www folder. We will also exclude some folders from the backup ( stats, logs, phptmp … ) since we don’t want to backup temporary files or logs.

Now that we’ve a config file we need to know if everything works. In order to try it just issue the following shell command:

rsnapshot -c /path/to/rsnapshot.conf -t daily

rsnapshot will read your config file and will echo all the commands that he will fire. “-t” specifies “run in test mode”. If no errors appear ( like tab errors ) it’s time to remove the “-t” parameter and see if everything works for real.

If everything works great ( could take some time depending on the size of your data ) It’s time to setup the needed cronjobs. All depends on which “timeframes” ( line 9 to 11 ) you use on your config file.  If , for example, you use only the daily timeframe you’ll only need to setup a daily cronjob.

00 02 * * * rsnapshot -c /path/to/rsnapshot.conf daily

That will be fired at 2:00 am each day ( remember that if you mysqlbackup your data at 01:00 am  you’ll need to be sure you download the fresh dumps after that cronjob ended that task ).

Now, the only thing you’ve to do is to sit and let rsnapshot do the hard job for you!

Conclusions + Security thoughts

Rsnapshot + rsync + ssh seems to be a good choice to make incremental and efficient backups. they seems to be robust and well known tools. About security you can even improve the level just by using rssh or tweaking the “command” parameter inside the ssh key. In my case the security thoughts adopted and implemented in this howto are enough.

I hope I actually helped someone to setup something cool and fully functional.

Lets say you want to show a quick tutorial to the user just once — Indeed, when the user open your app for the first time.

Well, an easy solution would be to use a SharedPreference to store the info we need to accomplish this “task”.

Below, a snippet with a simple method ( to be included inside your activity class ) that will “solve” the problem.

	private Boolean firstTime = null;
	/**
	 * Checks if the user is opening the app for the first time. 
	 * Note that this method should be placed inside an activity and it can be called multiple times.
	 * @return boolean
	 */
	private boolean isFirstTime() {
		if (firstTime == null) {
			SharedPreferences mPreferences = this.getSharedPreferences("first_time", Context.MODE_PRIVATE);
			firstTime = mPreferences.getBoolean("firstTime", true);
			if (firstTime) { 
			    SharedPreferences.Editor editor = mPreferences.edit();
			    editor.putBoolean("firstTime", false);
			    editor.commit();
			}
		}
		return firstTime;
	}

When you build a new Service-Website from scratch you’ll probably have to face with this. Passwords are the most sensitive data we have and your application should behave securely enough to maintain user’s data private!

Some time ago you it was a common pattern to store the user password as plain text ( or with some Symmetric-key algorithm ). This let the user to retrieve their password withouth setting a new one.

From this pattern a fork was born which required to answer a predefined question in order to make the application send the password back to the user.

It seems these patterns are not used anymore in favor of the actual one which involves a more structured application/user flow in order to let the user regain access to the application. I’m talking about password reset.

The new way

Basically the password is stored in the database with a non symmetric-key algorithm ( Ex: md5 hash ) and whenever the user needs to regain access to the application the password needs to be resetted ( and the old one will be lost forever ).

Everything starts when the user can’t find his password to access your application. Then the user needs to remind the email or the username he used to login into your application, once this is done he needs to fill in the “Password reset form” which will ask only for the username.

The application, at this point, will generate a new token and save it inside the database for later usage. The user then receives the  notification from the server ( usually via e-mail ) that contains a string like the following:

Hey, we heard you lost your password.

Use the following link within the next 24 hours to reset your password:

https://example.com/resetpassword/<username>/<token>

Thanks,

When the user clicks over the link the application needs to validate a couple of things:

• Is the username/token pair a valid one?
• Is the token still valid ( not expired ? )
• Was the token already used ?

I also designed a database-table schema for storing/retrieving the token informations.

CREATE TABLE IF NOT EXISTS `resetpasswordtokens` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `userID` int(11) NOT NULL,
  `token` char(32) NOT NULL,
  `status` set('used','new') NOT NULL DEFAULT 'new',
  `date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`),
  KEY `userID` (`userID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

I hope this helps

A common pattern is to create an index.html file ( which gets served – almost ever – before index.php ) which will contain a specific landing page with an “under construction” text.

How to serve the index.html file to “regular people” while you work on wordpress ( index.php ) ?

It’s quite easy using .htaccess and mod_rewrite of apache. The basic concepts are:

• WordPress logged in people will see the “work in progress” website
• Not logged in people will see the “site under construction” page

In order to achieve that, you’ve to prepend the following lines to your .htaccess file  ( placed in your document root ) :

<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /
  RewriteCond %{REQUEST_FILENAME} index.html$
  RewriteCond %{HTTP_COOKIE} ^.*wordpress_logged_in.*$ [NC]
  RewriteRule . /index.php [L]
</IfModule>

As you can see we only override the normal web-flow only if the browser is going to request the index.html file and the user has the wordpress_logged_in cookie setted.

Whenever you need to see your “real website” you just need to point your browser to http://example.com/wp-admin , login and then you’ll be able to see the website you’re creating and not the “under construction” page.

Note: This is only a partial solution and people could be smart enough to emulate the wordpress_logged_in cookie and see your work in progress anyway. In my case-scenarios this was more than enough.

Sooner or later I always remember I’ve a blog. This time the topic is XSS.

If you don’t have a clue of what XSS is maybe you should read this before reading this article.

I’m my day-job the content is generated by third party people. In order to be save I always thought the strip_tags function from PHP was safe enough. In my case I needed to get some html tags working without letting malicious code pass through.

Fortunately strip_tags allows, as second parameter, to specify which tags are allowed. But here is the glitch:

<?php
   strip_tags($toStrip, '<p><a><b><i><em><u><ul><li><ol><span><div>')

What happens if the variable you’d like to strip contains something like this ?

<a href='http://www.example.com' onClick='javascript:alert("blabla");'>Click Me!</a>

Well, since the ‘a’ tag is allowed by our strip_tags call, the malicious code gets injected.

So here is what I discovered today: “strip_tags is not safe enough.”

The next question that popped in my mind was: “How to get strip_tags safe enough without adding any external library to the project?“

Well the easy solution was to strip away also html attributes ( since in my case those weren’t needed ). How to do that? This snippet of code worked ( for now ) for me.

<?php
/*
* Allow only a couple of tags + Strip Slashes + Remove any attribute
* /
$almostSafeOutput = preg_replace(
	"/<([a-z][a-z0-9]*)[^>]*?(\/?)>/i",
	'<$1$2>', 
	stripslashes(
		strip_tags(
			$toStrip, 
			'<p><a><b><i><em><u><ul><li><ol><span><div>'
		)
	)
);

Further readings:

• http://it.wikipedia.org/wiki/Cross-site_scripting
• https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)
• https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet

]]> http://www.andreabaccega.com/blog/2012/03/23/avoiding-xss-injection-without-sacrifying-some-tags-in-php/feed/ 2 http://www.andreabaccega.com/blog/2010/10/09/onchange-event-on-edittext-in-android/ http://www.andreabaccega.com/blog/2010/10/09/onchange-event-on-edittext-in-android/#comments Sat, 09 Oct 2010 12:30:09 +0000 veke87 http://www.andreabaccega.com/?p=470 Continue reading →

			((EditText)findViewById(R.id.et_testo)).addTextChangedListener(new TextWatcher() {

			public void afterTextChanged(Editable s) {
				((TextView)findViewById(R.id.numcaratteri)).setText(String.format(getString(R.string.caratteri), s.length()));

			}

			public void beforeTextChanged(CharSequence s, int start, int count,
					int after) {
				// TODO Auto-generated method stub

			}

			public void onTextChanged(CharSequence s, int start, int before,
					int count) {
				// TODO Auto-generated method stub

			}

		});

In order to get my result on each android device you’ve to download this file and place it on $JAVA_HOME/lib/ext . Plus, you should have $JAVA_HOME/bin in your $PATH

adb pull /system/etc/security/cacerts.bks cacerts.bks
keystore cacerts.bks -storetype BKS -provider org.bouncycastle.jce.provider.BouncyCastleProvider -storepass changeit -list -v >> certificates.txt

After the break my certificates.txt.

Keystore type: BKS
Keystore provider: BC

Your keystore contains 57 entries

Alias name: 29
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=VeriSign\, Inc.,OU=Class 3 Public Primary Certification Authority
Issuer: C=US,O=VeriSign\, Inc.,OU=Class 3 Public Primary Certification Authority
Serial number: 70bae41d10d92934b638ca7b03ccbabf
Valid from: Mon Jan 29 01:00:00 CET 1996 until: Wed Aug 02 01:59:59 CEST 2028
Certificate fingerprints:
	 MD5:  10:FC:63:5D:F6:26:3E:0D:F3:25:BE:5F:79:CD:67:67
	 SHA1: 74:2C:31:92:E6:07:E4:24:EB:45:49:54:2B:E1:BB:C5:3E:61:74:E2
	 Signature algorithm name: MD2WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 28
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Equifax Secure Inc.,CN=Equifax Secure Global eBusiness CA-1
Issuer: C=US,O=Equifax Secure Inc.,CN=Equifax Secure Global eBusiness CA-1
Serial number: 1
Valid from: Mon Jun 21 06:00:00 CEST 1999 until: Sun Jun 21 06:00:00 CEST 2020
Certificate fingerprints:
	 MD5:  8F:5D:77:06:27:C4:98:3C:5B:93:78:E7:D7:7D:9B:CC
	 SHA1: 7E:78:4A:10:1C:82:65:CC:2D:E1:F1:6D:47:B4:40:CA:D9:0A:19:45
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 27
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=VeriSign\, Inc.,OU=Class 3 Public Primary Certification Authority - G2,OU=(c) 1998 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network
Issuer: C=US,O=VeriSign\, Inc.,OU=Class 3 Public Primary Certification Authority - G2,OU=(c) 1998 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network
Serial number: 7dd9fe07cfa81eb7107967fba78934c6
Valid from: Mon May 18 02:00:00 CEST 1998 until: Wed Aug 02 01:59:59 CEST 2028
Certificate fingerprints:
	 MD5:  A2:33:9B:4C:74:78:73:D4:6C:E7:C1:F3:8D:CB:5C:E9
	 SHA1: 85:37:1C:A6:E5:50:14:3D:CE:28:03:47:1B:DE:3A:09:E8:F8:77:0F
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 26
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=IL,O=StartCom Ltd.,OU=StartCom Certification Authority,CN=StartCom Extended Validation Server CA
Issuer: C=IL,O=StartCom Ltd.,OU=Secure Digital Certificate Signing,CN=StartCom Certification Authority
Serial number: 17
Valid from: Thu Jan 01 07:00:00 CET 2009 until: Tue Jan 01 07:00:00 CET 2019
Certificate fingerprints:
	 MD5:  01:D3:0C:7E:B6:FB:E9:EF:80:F5:9D:47:BB:F4:5F:27
	 SHA1: 65:73:55:A6:BB:68:F9:3D:33:CC:B7:58:B4:2F:5E:1A:7D:85:C9:C4
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 25
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=PL,O=Unizeto Sp. z o.o.,CN=Certum CA
Issuer: C=PL,O=Unizeto Sp. z o.o.,CN=Certum CA
Serial number: 10020
Valid from: Tue Jun 11 12:46:39 CEST 2002 until: Fri Jun 11 12:46:39 CEST 2027
Certificate fingerprints:
	 MD5:  2C:8F:9F:66:1D:18:90:B1:47:26:9D:8E:86:82:8C:A9
	 SHA1: 62:52:DC:40:F7:11:43:A2:2F:DE:9E:F7:34:8E:06:42:51:B1:81:18
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 24
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Assured ID Root CA
Issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Assured ID Root CA
Serial number: ce7e0e517d846fe8fe560fc1bf03039
Valid from: Fri Nov 10 01:00:00 CET 2006 until: Mon Nov 10 01:00:00 CET 2031
Certificate fingerprints:
	 MD5:  87:CE:0B:7B:2A:0E:49:00:E1:58:71:9B:37:A8:93:72
	 SHA1: 05:63:B8:63:0D:62:D7:5A:BB:C8:AB:1E:4B:DF:B5:A8:99:B2:4D:43
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 56
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: O=VeriSign Trust Network,OU=VeriSign\, Inc.,OU=VeriSign International Server CA - Class 3,OU=www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign
Issuer: C=US,O=VeriSign\, Inc.,OU=Class 3 Public Primary Certification Authority
Serial number: 46fcebbab4d02f0f926098233f93078f
Valid from: Thu Apr 17 02:00:00 CEST 1997 until: Tue Oct 25 01:59:59 CEST 2016
Certificate fingerprints:
	 MD5:  AC:D8:0E:A2:7B:B7:2C:E7:00:DC:22:72:4A:5F:1E:92
	 SHA1: D5:59:A5:86:66:9B:08:F4:6A:30:A1:33:F8:A9:ED:3D:03:8E:2E:A8
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 23
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=HU,L=Budapest,O=NetLock Halozatbiztonsagi Kft.,OU=Tanusitvanykiadok,CN=NetLock Expressz (Class C) Tanusitvanykiado
Issuer: C=HU,L=Budapest,O=NetLock Halozatbiztonsagi Kft.,OU=Tanusitvanykiadok,CN=NetLock Expressz (Class C) Tanusitvanykiado
Serial number: 68
Valid from: Thu Feb 25 15:08:11 CET 1999 until: Wed Feb 20 15:08:11 CET 2019
Certificate fingerprints:
	 MD5:  4F:EB:F1:F0:70:C2:80:63:5D:58:9F:DA:12:3C:A9:C4
	 SHA1: E3:92:51:2F:0A:CF:F5:05:DF:F6:DE:06:7F:75:37:E1:65:EA:57:4B
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 55
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST Network,OU=http://www.usertrust.com,CN=UTN-USERFirst-Hardware
Issuer: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST Network,OU=http://www.usertrust.com,CN=UTN-USERFirst-Hardware
Serial number: 44be0c8b500024b411d3362afe650afd
Valid from: Fri Jul 09 20:10:42 CEST 1999 until: Tue Jul 09 20:19:22 CEST 2019
Certificate fingerprints:
	 MD5:  4C:56:41:E5:0D:BB:2B:E8:CA:A3:ED:18:08:AD:43:39
	 SHA1: 04:83:ED:33:99:AC:36:08:05:87:22:ED:BC:5E:46:00:E3:BE:F9:D7
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 22
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=BM,O=QuoVadis Limited,OU=Root Certification Authority,CN=QuoVadis Root Certification Authority
Issuer: C=BM,O=QuoVadis Limited,OU=Root Certification Authority,CN=QuoVadis Root Certification Authority
Serial number: 3ab6508b
Valid from: Mon Mar 19 19:33:33 CET 2001 until: Wed Mar 17 19:33:33 CET 2021
Certificate fingerprints:
	 MD5:  27:DE:36:FE:72:B7:00:03:00:9D:F4:F0:1E:6C:04:24
	 SHA1: DE:3F:40:BD:50:93:D3:9B:6C:60:F6:DA:BC:07:62:01:00:89:76:C9
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 54
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=VeriSign\, Inc.,OU=VeriSign Trust Network,OU=(c) 2006 VeriSign\, Inc. - For authorized use only,CN=VeriSign Class 3 Public Primary Certification Authority - G5
Issuer: C=US,O=VeriSign\, Inc.,OU=VeriSign Trust Network,OU=(c) 2006 VeriSign\, Inc. - For authorized use only,CN=VeriSign Class 3 Public Primary Certification Authority - G5
Serial number: 18dad19e267de8bb4a2158cdcc6b3b4a
Valid from: Wed Nov 08 01:00:00 CET 2006 until: Thu Jul 17 01:59:59 CEST 2036
Certificate fingerprints:
	 MD5:  CB:17:E4:31:67:3E:E2:09:FE:45:57:93:F3:0A:FA:1C
	 SHA1: 4E:B6:D5:78:49:9B:1C:CF:5F:58:1E:AD:56:BE:3D:9B:67:44:A5:E5
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 21
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=HU,L=Budapest,O=NetLock Halozatbiztonsagi Kft.,OU=Tanusitvanykiadok,CN=NetLock Uzleti (Class B) Tanusitvanykiado
Issuer: C=HU,L=Budapest,O=NetLock Halozatbiztonsagi Kft.,OU=Tanusitvanykiadok,CN=NetLock Uzleti (Class B) Tanusitvanykiado
Serial number: 69
Valid from: Thu Feb 25 15:10:22 CET 1999 until: Wed Feb 20 15:10:22 CET 2019
Certificate fingerprints:
	 MD5:  39:16:AA:B9:6A:41:E1:14:69:DF:9E:6C:3B:72:DC:B6
	 SHA1: 87:9F:4B:EE:05:DF:98:58:3B:E3:60:D6:33:E7:0D:3F:FE:98:71:AF
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 53
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert Class 1 Policy Validation Authority,CN=http://www.valicert.com/,E=info@valicert.com
Issuer: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert Class 1 Policy Validation Authority,CN=http://www.valicert.com/,E=info@valicert.com
Serial number: 1
Valid from: Sat Jun 26 00:23:48 CEST 1999 until: Wed Jun 26 00:23:48 CEST 2019
Certificate fingerprints:
	 MD5:  65:58:AB:15:AD:57:6C:1E:A8:A7:B5:69:AC:BF:FF:EB
	 SHA1: E5:DF:74:3C:B6:01:C4:9B:98:43:DC:AB:8C:E8:6A:81:10:9F:E4:8E
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 20
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Equifax,OU=Equifax Secure Certificate Authority
Issuer: C=US,O=Equifax,OU=Equifax Secure Certificate Authority
Serial number: 35def4cf
Valid from: Sat Aug 22 18:41:51 CEST 1998 until: Wed Aug 22 18:41:51 CEST 2018
Certificate fingerprints:
	 MD5:  67:CB:9D:C0:13:24:8A:82:9B:B2:17:1E:D1:1B:EC:D4
	 SHA1: D2:32:09:AD:23:D3:14:23:21:74:E4:0D:7F:9D:62:13:97:86:63:3A
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 52
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=EU,O=AC Camerfirma SA CIF A82743287,OU=http://www.chambersign.org,CN=Chambers of Commerce Root
Issuer: C=EU,O=AC Camerfirma SA CIF A82743287,OU=http://www.chambersign.org,CN=Chambers of Commerce Root
Serial number: 0
Valid from: Tue Sep 30 18:13:43 CEST 2003 until: Wed Sep 30 18:13:44 CEST 2037
Certificate fingerprints:
	 MD5:  B0:01:EE:14:D9:AF:29:18:94:76:8E:F1:69:33:2A:84
	 SHA1: 6E:3A:55:A4:19:0C:19:5C:93:84:3C:C0:DB:72:2E:31:30:61:F0:B1
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 51
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Entrust.net,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),OU=(c) 1999 Entrust.net Limited,CN=Entrust.net Secure Server Certification Authority
Issuer: C=US,O=Entrust.net,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),OU=(c) 1999 Entrust.net Limited,CN=Entrust.net Secure Server Certification Authority
Serial number: 374ad243
Valid from: Tue May 25 18:09:40 CEST 1999 until: Sat May 25 18:39:40 CEST 2019
Certificate fingerprints:
	 MD5:  DF:F2:80:73:CC:F1:E6:61:73:FC:F5:42:E9:C5:7C:EE
	 SHA1: 99:A6:9B:E6:1A:FE:88:6B:4D:2B:82:00:7C:B8:54:FC:31:7E:15:39
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 50
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Equifax Secure Inc.,CN=Equifax Secure eBusiness CA-1
Issuer: C=US,O=Equifax Secure Inc.,CN=Equifax Secure eBusiness CA-1
Serial number: 4
Valid from: Mon Jun 21 06:00:00 CEST 1999 until: Sun Jun 21 06:00:00 CEST 2020
Certificate fingerprints:
	 MD5:  64:9C:EF:2E:44:FC:C6:8F:52:07:D0:51:73:8F:CB:3D
	 SHA1: DA:40:18:8B:91:89:A3:ED:EE:AE:DA:97:FE:2F:9D:F5:B7:D1:8A:41
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 9
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=DE,ST=Hamburg,L=Hamburg,O=TC TrustCenter for Security in Data Networks GmbH,OU=TC TrustCenter Class 2 CA,E=certificate@trustcenter.de
Issuer: C=DE,ST=Hamburg,L=Hamburg,O=TC TrustCenter for Security in Data Networks GmbH,OU=TC TrustCenter Class 2 CA,E=certificate@trustcenter.de
Serial number: 3ea
Valid from: Mon Mar 09 12:59:59 CET 1998 until: Sat Jan 01 12:59:59 CET 2011
Certificate fingerprints:
	 MD5:  B8:16:33:4C:4C:4C:F2:D8:D3:4D:06:B4:A6:5B:40:03
	 SHA1: 83:8E:30:F7:7F:DD:14:AA:38:5E:D1:45:00:9C:0E:22:36:49:4F:AA
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 8
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Starfield Technologies\, Inc.,OU=Starfield Class 2 Certification Authority
Issuer: C=US,O=Starfield Technologies\, Inc.,OU=Starfield Class 2 Certification Authority
Serial number: 0
Valid from: Tue Jun 29 19:39:16 CEST 2004 until: Thu Jun 29 19:39:16 CEST 2034
Certificate fingerprints:
	 MD5:  32:4A:4B:BB:C8:63:69:9B:BE:74:9A:C6:DD:1D:46:24
	 SHA1: AD:7E:1C:28:B0:64:EF:8F:60:03:40:20:14:C3:D0:E3:37:0E:B5:8A
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 19
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=DE,ST=Hamburg,L=Hamburg,O=TC TrustCenter for Security in Data Networks GmbH,OU=TC TrustCenter Class 3 CA,E=certificate@trustcenter.de
Issuer: C=DE,ST=Hamburg,L=Hamburg,O=TC TrustCenter for Security in Data Networks GmbH,OU=TC TrustCenter Class 3 CA,E=certificate@trustcenter.de
Serial number: 3eb
Valid from: Mon Mar 09 12:59:59 CET 1998 until: Sat Jan 01 12:59:59 CET 2011
Certificate fingerprints:
	 MD5:  5F:94:4A:73:22:B8:F7:D1:31:EC:59:39:F7:8E:FE:6E
	 SHA1: 9F:C7:96:E8:F8:52:4F:86:3A:E1:49:6D:38:12:42:10:5F:1B:78:F5
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 7
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=The Go Daddy Group\, Inc.,OU=Go Daddy Class 2 Certification Authority
Issuer: C=US,O=The Go Daddy Group\, Inc.,OU=Go Daddy Class 2 Certification Authority
Serial number: 0
Valid from: Tue Jun 29 19:06:20 CEST 2004 until: Thu Jun 29 19:06:20 CEST 2034
Certificate fingerprints:
	 MD5:  91:DE:06:25:AB:DA:FD:32:17:0C:BB:25:17:2A:84:67
	 SHA1: 27:96:BA:E6:3F:18:01:E2:77:26:1B:A0:D7:77:70:02:8F:20:EE:E4
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 18
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=DE,O=TC TrustCenter GmbH,OU=TC TrustCenter Universal CA,CN=TC TrustCenter Universal CA I
Issuer: C=DE,O=TC TrustCenter GmbH,OU=TC TrustCenter Universal CA,CN=TC TrustCenter Universal CA I
Serial number: 1da200010002ecb76080788db606
Valid from: Wed Mar 22 16:54:28 CET 2006 until: Wed Dec 31 23:59:59 CET 2025
Certificate fingerprints:
	 MD5:  45:E1:A5:72:C5:A9:36:64:40:9E:F5:E4:58:84:67:8C
	 SHA1: 6B:2F:34:AD:89:58:BE:62:FD:B0:6B:5C:CE:BB:9D:D9:4F:4E:39:F3
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 6
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=TW,O=Government Root Certification Authority
Issuer: C=TW,O=Government Root Certification Authority
Serial number: 1f9d595ad72fc20644a5800869e35ef6
Valid from: Thu Dec 05 14:23:33 CET 2002 until: Sun Dec 05 14:23:33 CET 2032
Certificate fingerprints:
	 MD5:  37:85:44:53:32:45:1F:20:F0:F3:95:E1:25:C4:43:4E
	 SHA1: F4:8B:11:BF:DE:AB:BE:94:54:20:71:E6:41:DE:6B:BE:88:2B:40:B9
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 17
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST Network,OU=http://www.usertrust.com,CN=UTN - DATACorp SGC
Issuer: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST Network,OU=http://www.usertrust.com,CN=UTN - DATACorp SGC
Serial number: 44be0c8b500021b411d32a6806a9ad69
Valid from: Thu Jun 24 20:57:21 CEST 1999 until: Mon Jun 24 21:06:30 CEST 2019
Certificate fingerprints:
	 MD5:  B3:A5:3E:77:21:6D:AC:4A:C0:C9:FB:D5:41:3D:CA:06
	 SHA1: 58:11:9F:0E:12:82:87:EA:50:FD:D9:87:45:6F:4F:78:DC:FA:D6:D4
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 49
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=ch,O=Swisscom,OU=Digital Certificate Services,CN=Swisscom Root CA 1
Issuer: C=ch,O=Swisscom,OU=Digital Certificate Services,CN=Swisscom Root CA 1
Serial number: 5c0b855c0be75941df57cc3f7f9da836
Valid from: Thu Aug 18 14:06:20 CEST 2005 until: Tue Aug 19 00:06:20 CEST 2025
Certificate fingerprints:
	 MD5:  F8:38:7C:77:88:DF:2C:16:68:2E:C2:E2:52:4B:B8:F9
	 SHA1: 5F:3A:FC:0A:8B:64:F6:86:67:34:74:DF:7E:A9:A2:FE:F9:FA:7A:51
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 5
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=ES,O=FNMT,OU=FNMT Clase 2 CA
Issuer: C=ES,O=FNMT,OU=FNMT Clase 2 CA
Serial number: 36f11b19
Valid from: Thu Mar 18 15:56:19 CET 1999 until: Mon Mar 18 16:26:19 CET 2019
Certificate fingerprints:
	 MD5:  25:9D:CF:5E:B3:25:9D:95:B9:3F:00:86:5F:47:94:3D
	 SHA1: 43:F9:B1:10:D5:BA:FD:48:22:52:31:B0:D0:08:2B:37:2F:EF:9A:54
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 16
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=DE,O=Deutsche Telekom AG,OU=T-TeleSec Trust Center,CN=Deutsche Telekom Root CA 2
Issuer: C=DE,O=Deutsche Telekom AG,OU=T-TeleSec Trust Center,CN=Deutsche Telekom Root CA 2
Serial number: 26
Valid from: Fri Jul 09 14:11:00 CEST 1999 until: Wed Jul 10 01:59:00 CEST 2019
Certificate fingerprints:
	 MD5:  74:01:4A:91:B1:08:C4:58:CE:47:CD:F0:DD:11:53:08
	 SHA1: 85:A4:08:C0:9C:19:3E:5D:51:58:7D:CD:D6:13:30:FD:8C:DE:37:BF
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 48
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=ZA,ST=Western Cape,L=Cape Town,O=Thawte Consulting cc,OU=Certification Services Division,CN=Thawte Server CA,E=server-certs@thawte.com
Issuer: C=ZA,ST=Western Cape,L=Cape Town,O=Thawte Consulting cc,OU=Certification Services Division,CN=Thawte Server CA,E=server-certs@thawte.com
Serial number: 1
Valid from: Thu Aug 01 02:00:00 CEST 1996 until: Fri Jan 01 00:59:59 CET 2021
Certificate fingerprints:
	 MD5:  C5:70:C4:A2:ED:53:78:0C:C8:10:53:81:64:CB:D0:1D
	 SHA1: 23:E5:94:94:51:95:F2:41:48:03:B4:D5:64:D2:A3:A3:F5:D8:8B:8C
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 4
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Digital Signature Trust,OU=DST ACES,CN=DST ACES CA X6
Issuer: C=US,O=Digital Signature Trust,OU=DST ACES,CN=DST ACES CA X6
Serial number: d5e990ad69db778ecd807563b8615d9
Valid from: Thu Nov 20 22:19:58 CET 2003 until: Mon Nov 20 22:19:58 CET 2017
Certificate fingerprints:
	 MD5:  21:D8:4C:82:2B:99:09:33:A2:EB:14:24:8D:8E:5F:E8
	 SHA1: 40:54:DA:6F:1C:3F:40:74:AC:ED:0F:EC:CD:DB:79:D1:53:FB:90:1D
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 15
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=GTE Corporation,OU=GTE CyberTrust Solutions\, Inc.,CN=GTE CyberTrust Global Root
Issuer: C=US,O=GTE Corporation,OU=GTE CyberTrust Solutions\, Inc.,CN=GTE CyberTrust Global Root
Serial number: 1a5
Valid from: Thu Aug 13 02:29:00 CEST 1998 until: Tue Aug 14 01:59:00 CEST 2018
Certificate fingerprints:
	 MD5:  CA:3D:D3:68:F1:03:5C:D0:32:FA:B8:2B:59:E8:5A:DB
	 SHA1: 97:81:79:50:D8:1C:96:70:CC:34:D8:09:CF:79:44:31:36:7E:F4:74
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 47
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST Network,OU=http://www.usertrust.com,CN=UTN-USERFirst-Network Applications
Issuer: C=US,ST=UT,L=Salt Lake City,O=The USERTRUST Network,OU=http://www.usertrust.com,CN=UTN-USERFirst-Network Applications
Serial number: 44be0c8b500024b411d336304bc03377
Valid from: Fri Jul 09 20:48:39 CEST 1999 until: Tue Jul 09 20:57:49 CEST 2019
Certificate fingerprints:
	 MD5:  BF:60:59:A3:5B:BA:F6:A7:76:42:DA:6F:1A:7B:50:CF
	 SHA1: 5D:98:9C:DB:15:96:11:36:51:65:64:1B:56:0F:DB:EA:2A:C2:3E:F1
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 3
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=FR,O=Certplus,CN=Class 2 Primary CA
Issuer: C=FR,O=Certplus,CN=Class 2 Primary CA
Serial number: 85bd4bf3d8dae369f694d75fc3a54423
Valid from: Wed Jul 07 19:05:00 CEST 1999 until: Sun Jul 07 01:59:59 CEST 2019
Certificate fingerprints:
	 MD5:  88:2C:8C:52:B8:A2:3C:F3:F7:BB:03:EA:AE:AC:42:0B
	 SHA1: 74:20:74:41:72:9C:DD:92:EC:79:31:D8:23:10:8D:C2:81:92:E2:BB
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 14
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: O=Entrust.net,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),OU=(c) 1999 Entrust.net Limited,CN=Entrust.net Certification Authority (2048)
Issuer: O=Entrust.net,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),OU=(c) 1999 Entrust.net Limited,CN=Entrust.net Certification Authority (2048)
Serial number: 3863b966
Valid from: Fri Dec 24 18:50:51 CET 1999 until: Tue Dec 24 19:20:51 CET 2019
Certificate fingerprints:
	 MD5:  BA:21:EA:20:D6:DD:DB:8F:C1:57:8B:40:AD:A1:FC:FC
	 SHA1: 80:1D:62:D0:7B:44:9D:5C:5C:03:5C:98:EA:61:FA:44:3C:2A:58:FE
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 46
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=JP,O=Japan Certification Services\, Inc.,CN=SecureSign RootCA1
Issuer: C=JP,O=Japan Certification Services\, Inc.,CN=SecureSign RootCA1
Serial number: 5f60585f00000000
Valid from: Wed Sep 15 17:00:01 CEST 1999 until: Tue Sep 15 16:59:59 CEST 2020
Certificate fingerprints:
	 MD5:  BD:D6:F5:8A:7C:3C:C4:A6:F9:34:CC:C3:89:61:F6:B2
	 SHA1: CA:BB:51:67:24:00:58:8E:64:19:F1:D4:08:78:D0:40:3A:A2:02:64
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 13
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=SE,O=AddTrust AB,OU=AddTrust External TTP Network,CN=AddTrust External CA Root
Issuer: C=SE,O=AddTrust AB,OU=AddTrust External TTP Network,CN=AddTrust External CA Root
Serial number: 1
Valid from: Tue May 30 12:48:38 CEST 2000 until: Sat May 30 12:48:38 CEST 2020
Certificate fingerprints:
	 MD5:  1D:35:54:04:85:78:B0:3F:42:42:4D:BF:20:73:0A:3F
	 SHA1: 02:FA:F3:E2:91:43:54:68:60:78:57:69:4D:F5:E4:5B:68:85:18:68
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 2
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=ES,L=C/ Muntaner 244 Barcelona,CN=Autoridad de Certificacion Firmaprofesional CIF A62634068,E=ca@firmaprofesional.com
Issuer: C=ES,L=C/ Muntaner 244 Barcelona,CN=Autoridad de Certificacion Firmaprofesional CIF A62634068,E=ca@firmaprofesional.com
Serial number: 1
Valid from: Thu Oct 25 00:00:00 CEST 2001 until: Fri Oct 25 00:00:00 CEST 2013
Certificate fingerprints:
	 MD5:  11:92:79:40:3C:B1:83:40:E5:AB:66:4A:67:92:80:DF
	 SHA1: A9:62:8F:4B:98:A9:1B:48:35:BA:D2:C1:46:32:86:BB:66:64:6A:8C
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 45
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=DK,O=TDC Internet,OU=TDC Internet Root CA
Issuer: C=DK,O=TDC Internet,OU=TDC Internet Root CA
Serial number: 3acca54c
Valid from: Thu Apr 05 18:33:17 CEST 2001 until: Mon Apr 05 19:03:17 CEST 2021
Certificate fingerprints:
	 MD5:  91:F4:03:55:20:A1:F8:63:2C:62:DE:AC:FB:61:1C:8E
	 SHA1: 21:FC:BD:8E:7F:6C:AF:05:1B:D1:B3:43:EC:A8:E7:61:47:F2:0F:8A
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 44
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=NL,O=Staat der Nederlanden,CN=Staat der Nederlanden Root CA
Issuer: C=NL,O=Staat der Nederlanden,CN=Staat der Nederlanden Root CA
Serial number: 98968a
Valid from: Tue Dec 17 10:23:49 CET 2002 until: Wed Dec 16 10:15:38 CET 2015
Certificate fingerprints:
	 MD5:  60:84:7C:5A:CE:DB:0C:D4:CB:A7:E9:FE:02:C6:A9:C0
	 SHA1: 10:1D:FA:3F:D5:0B:CB:BB:9B:B5:60:0C:19:55:A4:1A:F4:73:3A:04
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 1
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: OU=GlobalSign Root CA - R2,O=GlobalSign,CN=GlobalSign
Issuer: OU=GlobalSign Root CA - R2,O=GlobalSign,CN=GlobalSign
Serial number: 400000000010f8626e60d
Valid from: Fri Dec 15 09:00:00 CET 2006 until: Wed Dec 15 09:00:00 CET 2021
Certificate fingerprints:
	 MD5:  94:14:77:7E:3E:5E:FD:8F:30:BD:41:B0:CF:E7:D0:30
	 SHA1: 75:E0:AB:B6:13:85:12:27:1C:04:F8:5F:DD:DE:38:E4:B7:24:2E:FE
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 12
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Global Root CA
Issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Global Root CA
Serial number: 83be056904246b1a1756ac95991c74a
Valid from: Fri Nov 10 01:00:00 CET 2006 until: Mon Nov 10 01:00:00 CET 2031
Certificate fingerprints:
	 MD5:  79:E4:A9:84:0D:7D:3A:96:D7:C0:4F:E2:43:4C:89:2E
	 SHA1: A8:98:5D:3A:65:E5:E5:C4:B2:D7:D6:6D:40:C6:DD:2F:B1:9C:54:36
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 11
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=IL,O=StartCom Ltd.,OU=Secure Digital Certificate Signing,CN=StartCom Certification Authority
Issuer: C=IL,O=StartCom Ltd.,OU=Secure Digital Certificate Signing,CN=StartCom Certification Authority
Serial number: 1
Valid from: Sun Sep 17 21:46:36 CEST 2006 until: Wed Sep 17 21:46:36 CEST 2036
Certificate fingerprints:
	 MD5:  22:4D:8F:8A:FC:F7:35:C2:BB:57:34:90:7B:8B:22:16
	 SHA1: 3E:2B:F7:F2:03:1B:96:F3:8C:E6:C4:D8:A8:5D:3E:2D:58:47:6A:0F
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 0
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: OU=Copyright (c) 1997 Microsoft Corp.,OU=Microsoft Corporation,CN=Microsoft Root Authority
Issuer: OU=Copyright (c) 1997 Microsoft Corp.,OU=Microsoft Corporation,CN=Microsoft Root Authority
Serial number: c1008b3c3c8811d13ef663ecdf40
Valid from: Fri Jan 10 08:00:00 CET 1997 until: Thu Dec 31 08:00:00 CET 2020
Certificate fingerprints:
	 MD5:  2A:95:4E:CA:79:B2:87:45:73:D9:2D:90:BA:F9:9F:B6
	 SHA1: A4:34:89:15:9A:52:0F:0D:93:D0:32:CC:AF:37:E7:FE:20:A8:B4:19
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 43
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=ZA,ST=Western Cape,L=Cape Town,O=Thawte Consulting cc,OU=Certification Services Division,CN=Thawte Premium Server CA,E=premium-server@thawte.com
Issuer: C=ZA,ST=Western Cape,L=Cape Town,O=Thawte Consulting cc,OU=Certification Services Division,CN=Thawte Premium Server CA,E=premium-server@thawte.com
Serial number: 1
Valid from: Thu Aug 01 02:00:00 CEST 1996 until: Fri Jan 01 00:59:59 CET 2021
Certificate fingerprints:
	 MD5:  06:9F:69:79:16:66:90:02:1B:8C:8C:A2:C3:07:6F:3A
	 SHA1: 62:7F:8D:78:27:65:63:99:D2:7D:7F:90:44:C9:FE:B3:F3:3E:FA:9A
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 10
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=DE,O=TC TrustCenter GmbH,OU=TC TrustCenter Class 2 CA,CN=TC TrustCenter Class 2 CA II
Issuer: C=DE,O=TC TrustCenter GmbH,OU=TC TrustCenter Class 2 CA,CN=TC TrustCenter Class 2 CA II
Serial number: 2e6a000100021fd752212c115c3b
Valid from: Thu Jan 12 15:38:43 CET 2006 until: Wed Dec 31 23:59:59 CET 2025
Certificate fingerprints:
	 MD5:  CE:78:33:5C:59:78:01:6E:18:EA:B9:36:A0:B9:2E:23
	 SHA1: AE:50:83:ED:7C:F4:5C:BC:8F:61:C6:21:FE:68:5D:79:42:21:15:6E
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 42
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Entrust\, Inc.,OU=www.entrust.net/CPS is incorporated by reference,OU=(c) 2006 Entrust\, Inc.,CN=Entrust Root Certification Authority
Issuer: C=US,O=Entrust.net,OU=www.entrust.net/CPS incorp. by ref. (limits liab.),OU=(c) 1999 Entrust.net Limited,CN=Entrust.net Secure Server Certification Authority
Serial number: 42872d4c
Valid from: Fri Jan 05 20:20:39 CET 2007 until: Thu Jan 05 20:50:39 CET 2017
Certificate fingerprints:
	 MD5:  59:BF:7B:66:82:BE:87:21:9A:A8:14:A5:32:41:61:82
	 SHA1: BE:E7:72:B3:19:0A:C8:4B:F8:31:F9:60:7D:98:89:EC:6A:96:6C:16
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 41
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=America Online Inc.,CN=America Online Root Certification Authority 1
Issuer: C=US,O=America Online Inc.,CN=America Online Root Certification Authority 1
Serial number: 1
Valid from: Tue May 28 08:00:00 CEST 2002 until: Thu Nov 19 21:43:00 CET 2037
Certificate fingerprints:
	 MD5:  14:F1:08:AD:9D:FA:64:E2:89:E7:1C:CF:A8:AD:7D:5E
	 SHA1: 39:21:C1:15:C1:5D:0E:CA:5C:CB:5B:C4:F0:7D:21:D8:05:0B:56:6A
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 40
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert Class 2 Policy Validation Authority,CN=http://www.valicert.com/,E=info@valicert.com
Issuer: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert Class 2 Policy Validation Authority,CN=http://www.valicert.com/,E=info@valicert.com
Serial number: 1
Valid from: Sat Jun 26 02:19:54 CEST 1999 until: Wed Jun 26 02:19:54 CEST 2019
Certificate fingerprints:
	 MD5:  A9:23:75:9B:BA:49:36:6E:31:C2:DB:F2:E7:66:BA:87
	 SHA1: 31:7A:2A:D0:7F:2B:33:5E:F5:A1:C3:4E:4B:57:E8:B7:D8:F1:FC:A6
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 39
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=VeriSign\, Inc.,OU=VeriSign Trust Network,OU=Terms of use at https://www.verisign.com/rpa (c)06,CN=VeriSign Class 3 Extended Validation SSL SGC CA
Issuer: C=US,O=VeriSign\, Inc.,OU=VeriSign Trust Network,OU=(c) 2006 VeriSign\, Inc. - For authorized use only,CN=VeriSign Class 3 Public Primary Certification Authority - G5
Serial number: 112a006d37e5106fd6ca7cc3efbacc18
Valid from: Wed Nov 08 01:00:00 CET 2006 until: Tue Nov 08 00:59:59 CET 2016
Certificate fingerprints:
	 MD5:  15:37:78:6E:D5:89:C8:CF:11:DC:9D:61:70:75:25:E9
	 SHA1: 4A:8A:2A:0E:27:6F:F3:3B:5D:D8:8A:36:21:46:01:0F:2A:8B:6A:EE
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 38
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=BE,O=GlobalSign nv-sa,OU=Root CA,CN=GlobalSign Root CA
Issuer: C=BE,O=GlobalSign nv-sa,OU=Root CA,CN=GlobalSign Root CA
Serial number: 40000000001154b5ac394
Valid from: Tue Sep 01 14:00:00 CEST 1998 until: Fri Jan 28 13:00:00 CET 2028
Certificate fingerprints:
	 MD5:  3E:45:52:15:09:51:92:E1:B7:5D:37:9F:B1:87:29:8A
	 SHA1: B1:BC:96:8B:D4:F4:9D:62:2A:A8:9A:81:F2:15:01:52:A4:1D:82:9C
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 37
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=HU,ST=Hungary,L=Budapest,O=NetLock Halozatbiztonsagi Kft.,OU=Tanusitvanykiadok,CN=NetLock Kozjegyzoi (Class A) Tanusitvanykiado
Issuer: C=HU,ST=Hungary,L=Budapest,O=NetLock Halozatbiztonsagi Kft.,OU=Tanusitvanykiadok,CN=NetLock Kozjegyzoi (Class A) Tanusitvanykiado
Serial number: 103
Valid from: Thu Feb 25 00:14:47 CET 1999 until: Wed Feb 20 00:14:47 CET 2019
Certificate fingerprints:
	 MD5:  86:38:6D:5E:49:63:6C:85:5C:DB:6D:DC:94:B7:D0:F7
	 SHA1: AC:ED:5F:65:53:FD:25:CE:01:5F:1F:7A:48:3B:6A:74:9F:61:78:C6
	 Signature algorithm name: MD5WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 36
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=Entrust\, Inc.,OU=AND ADDITIONAL TERMS GOVERNING USE AND RELIANCE,OU=CPS CONTAINS IMPORTANT LIMITATIONS OF WARRANTIES AND LIABILITY,OU=www.entrust.net/CPS is incorporated by reference,OU=(c) 2008 Entrust\, Inc.,CN=Entrust Certification Authority - L1B
Issuer: O=Entrust.net,OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.),OU=(c) 1999 Entrust.net Limited,CN=Entrust.net Certification Authority (2048)
Serial number: 3863c5ae
Valid from: Mon Aug 25 20:14:26 CEST 2008 until: Sat Aug 25 20:44:26 CEST 2018
Certificate fingerprints:
	 MD5:  C2:DF:86:BD:E4:8B:FF:26:4D:AE:6A:26:1D:7A:70:D9
	 SHA1: 19:98:49:D9:A9:E9:F5:28:43:6C:72:65:30:2A:15:2C:C0:9B:CA:9E
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 35
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=FI,O=Sonera,CN=Sonera Class2 CA
Issuer: C=FI,O=Sonera,CN=Sonera Class2 CA
Serial number: 1d
Valid from: Fri Apr 06 09:29:40 CEST 2001 until: Tue Apr 06 09:29:40 CEST 2021
Certificate fingerprints:
	 MD5:  A3:EC:75:0F:2E:88:DF:FA:48:01:4E:0B:5C:48:6F:FB
	 SHA1: 37:F7:6D:E6:07:7C:90:C5:B1:3E:93:1A:B7:41:10:B4:F2:E4:9A:27
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 34
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=JP,O=SECOM Trust.net,OU=Security Communication RootCA1
Issuer: C=JP,O=SECOM Trust.net,OU=Security Communication RootCA1
Serial number: 0
Valid from: Tue Sep 30 06:20:49 CEST 2003 until: Sat Sep 30 06:20:49 CEST 2023
Certificate fingerprints:
	 MD5:  F1:BC:63:6A:54:E0:B5:27:F5:CD:E7:1A:E3:4D:6E:4A
	 SHA1: 36:B1:2B:49:F9:81:9E:D7:4C:9E:BC:38:0F:C6:56:8F:5D:AC:B2:F7
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 33
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=BM,O=QuoVadis Limited,CN=QuoVadis Root CA 3
Issuer: C=BM,O=QuoVadis Limited,CN=QuoVadis Root CA 3
Serial number: 5c6
Valid from: Fri Nov 24 20:11:23 CET 2006 until: Mon Nov 24 20:06:44 CET 2031
Certificate fingerprints:
	 MD5:  31:85:3C:62:94:97:63:B9:AA:FD:89:4E:AF:6F:E0:CF
	 SHA1: 1F:49:14:F7:D8:74:95:1D:DD:AE:02:C0:BE:FD:3A:2D:82:75:51:85
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 32
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert High Assurance EV Root CA
Issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert High Assurance EV Root CA
Serial number: 2ac5c266a0b409b8f0b79f2ae462577
Valid from: Fri Nov 10 01:00:00 CET 2006 until: Mon Nov 10 01:00:00 CET 2031
Certificate fingerprints:
	 MD5:  D4:74:DE:57:5C:39:B2:D3:9C:85:83:C5:C0:65:49:8A
	 SHA1: 5F:B7:EE:06:33:E2:59:DB:AD:0C:4C:9A:E6:D3:8F:1A:61:C7:DC:25
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

Alias name: 31
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert Class 3 Policy Validation Authority,CN=http://www.valicert.com/,E=info@valicert.com
Issuer: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert Class 3 Policy Validation Authority,CN=http://www.valicert.com/,E=info@valicert.com
Serial number: 1
Valid from: Sat Jun 26 02:22:33 CEST 1999 until: Wed Jun 26 02:22:33 CEST 2019
Certificate fingerprints:
	 MD5:  A2:6F:53:B7:EE:40:DB:4A:68:E7:FA:18:D9:10:4B:72
	 SHA1: 69:BD:8C:F4:9C:D3:00:FB:59:2E:17:93:CA:55:6A:F3:EC:AA:35:FB
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 1

*******************************************
*******************************************

Alias name: 30
Creation date: Jun 7, 2010
Entry type: trustedCertEntry

Owner: C=BM,O=QuoVadis Limited,CN=QuoVadis Root CA 2
Issuer: C=BM,O=QuoVadis Limited,CN=QuoVadis Root CA 2
Serial number: 509
Valid from: Fri Nov 24 19:27:00 CET 2006 until: Mon Nov 24 19:23:33 CET 2031
Certificate fingerprints:
	 MD5:  5E:39:7B:DD:F8:BA:EC:82:E9:AC:62:BA:0C:54:00:2B
	 SHA1: CA:3A:FB:CF:12:40:36:4B:44:B2:16:20:88:80:48:39:19:93:7C:F7
	 Signature algorithm name: SHA1WithRSAEncryption
	 Version: 3

*******************************************
*******************************************

It’s simple as 1,2,3. Hope it helps.

		// CODEIGNITER HACK
		$tmp = explode('?',$_SERVER['REQUEST_URI']);
		$tmp = explode('&', $tmp[1]);

		foreach($tmp as $keyval) {
			$tmpAppoggio = explode('=', $keyval);
			$_GET[urldecode($tmpAppoggio[0])]=urldecode($tmpAppoggio[1]);
		}
		// end of codeigniter hack

I’ll write only the snippet here. Hope it helps

	/**
	 * writes an sms on the contentprovider
	 * @param ctx Context
	 * @param mobNo mobile number
	 * @param msg text of the message
	 */
	private final static void storeMessage(Context ctx,String mobNo, String msg) {
		ContentValues values = new ContentValues();
		values.put("address", mobNo);
		values.put("body", msg);
		ctx.getContentResolver().insert(Uri.parse("content://sms/sent"), values);
	}

Obviously you should set the right permissions on the manifest ( Yes the following are all needed for this task ) :

<manifest>
	....
	....
	<uses-permission android:name="android.permission.WRITE_SMS"></uses-permission>
	<uses-permission android:name="android.permission.READ_SMS"></uses-permission>
</manifest>