fix certificate date encoding

RFC 3280 requires in section
 - 4.1.2.5 Validity
 - 5.1.2.4 This Update
 - 5.1.2.5 Next Update
 - 5.1.2.6 Revoked Certificates
that dates are to be encoded as utcTime iff they are before 2050 and
as generalTime otherwise.

Currently, phpseclib does not respect this by always choosing generalTime.
Further, the format used interally to represent dates only keeps two digits,
so dates in 2050 and later cannot be represented in this format.

This patch fixes this by
 1. changing the interal format to be capable of unambiguously representing
    dates in 2050 or later (i.e. use four digits to represent the year),
 2. choosing between utcTime and generalTime accordingly.

Without this patch, openssl_x509_parse complains:
 Warning: openssl_x509_parse(): illegal ASN1 data type for timestamp
Merge remote-tracking branch 'michael/fix_cert_time_encoding'
X509: Array -> array (CS consistency)
Merge remote-tracking branch 'michael/fix_cert_time_encoding' into php5
Merge remote-tracking branch 'origin/master' into php5
add error suppression to phpinfo()

bad timezone settings can make phpinfo() throw errors so we'll just
suppress them. if there are legit non-timezone errors with php install
those will probably be hit in other parts of the code
Merge pull request #299 from terrafrost/phpinfo-fix

add error suppression to phpinfo()

* terrafrost/phpinfo-fix:
  add error suppression to phpinfo()
Merge branch 'master' into php5

* master:
  add error suppression to phpinfo()